Job search
Changing Employers on STEM OPT: Coordinate the Old Evaluation and New Training Plan
Organize separate old-employer and new-employer records, check your school’s reporting route and resolve date conflicts without mistaking a receipt for completed review.
When changing employers during STEM OPT, coordinate two separate records with your designated school official: the final evaluation for the opportunity you are leaving and the new employer’s Form I-983 training plan. Confirm the actual change dates, responsible employer contacts and your school’s current submission procedure. A new offer or a saved portal entry does not establish that both records have reached the DSO.
This guide reviews public DHS and university instructions checked October 22, 2026. Its examples contain administrative labels and invented scheduling records only, with no training-plan answers, identifiers or immigration histories. LandOffer publishes it for candidates using its job search; it does not assess individual eligibility, calculate unemployment days or determine when anyone is authorized to work.

Give the old evaluation and new plan separate owners
The old evaluation concerns the training opportunity that ended. The new plan concerns the new opportunity and employer commitments. They belong to different parts of the transition even when a school collects them in the same reporting workflow. Keep each record’s review, signature and receipt status separate; evidence for the new plan does not close the old evaluation.
DHS’s Students and the Form I-983 guidance, updated November 26, 2024, says a student changing employers must submit the final self-evaluation within ten days of ending employment with the current employer. It also describes employer signatures and return of evaluations to the DSO. That public requirement is a reason to organize the departing employer’s review promptly, rather than treating the evaluation as something to revisit at the end of the entire extension.
Identify the appropriate contact at each employer through the established process. The person handling departure paperwork may need to coordinate with the person responsible for reviewing the evaluation. At the new employer, ask who will work with you on the training plan and the required employer review. This article does not identify a substitute signer or suggest signing on anyone else’s behalf.
Give each record its own status line and source of confirmation. An administrative note can say “old evaluation: employer review pending” and “new plan: employer coordination pending.” Neither label claims that the underlying form is complete or accurate. It tells you which process still needs attention without reproducing personal material in a general-purpose tracker.
Check the federal reporting rule and the school’s route
The current DHS STEM OPT reporting page, updated July 6, 2026, addresses employer changes directly. It states that the new employer must be enrolled in E-Verify before the student begins work for pay, and that the student must submit a new I-983 to the DSO within ten days of starting the new practical training opportunity. It separately repeats the departing-employer final-evaluation requirement.
The same page says that when the period between employers is longer than ten days, the student must first report the loss of employment and later submit a new I-983. Do not turn that reporting description into permission to wait for the next employer before notifying your DSO. It also does not establish that a particular person, employer or proposed role meets every applicable requirement.
Your school determines its submission route and administrative instructions. For example, Harvard International Office’s change-in-employment page describes a departing-employer final evaluation and a new completed I-983 for employer changes, and provides its own reporting form. That is Harvard’s procedure, not a universal portal shared by all schools. Its page also separates approved and pending STEM OPT scenarios; a reader should not choose a category by analogy to somebody else’s experience.
Ask your own DSO which current workflow applies, which records it requires and how receipt will be confirmed. A school’s estimate of how long it takes to process a request does not redefine the federal reporting period. Do not assume that office processing time extends a reporting requirement or that a portal’s ability to save a draft proves submission.
Record dates accurately without inventing a legal calculation
Keep the actual last date of the old opportunity distinct from the date someone replied to an email, the date a form was signed and the date a file was sent. Likewise, distinguish the proposed new start from the actual beginning of the new opportunity. If the dates change, ask the DSO how to correct the administrative record rather than silently retaining the convenient older version.
A date log lets you identify which source needs clarification before inconsistent dates spread into later records. It does not decide which days count toward unemployment, whether a role is qualifying or whether work may begin. Those questions can depend on facts and official records beyond a planning sheet. Raise them with your DSO and, when appropriate, qualified immigration counsel rather than deriving an answer from a calendar example.
Avoid unnecessary identity data in the log. Use labels such as “Employer A” and “new-plan receipt pending,” with the real records kept through the institution’s approved channels. Do not put document images, government identifiers, signatures or private immigration information into a shared job-search worksheet just to make the status board look complete.
Worked example: coordinate two incomplete record sets
Mira is a fictional person planning an administrative handoff. The example uses an invented old-opportunity end date of October 23, 2026, and a proposed new-opportunity start of November 2. These dates are record labels only. No eligibility, authorization, reporting-deadline or unemployment-day conclusion is calculated from them.
| Record or question | Fictional evidence as of October 22 | Administrative next step |
|---|---|---|
| Old opportunity end | Employer A message lists October 23 | Confirm the actual date if it changes |
| Old final evaluation | No completed evaluation recorded | Coordinate the required review with the old employer |
| Old employer review | Contact identified, review not completed | Track the response without labeling it signed |
| New opportunity start | November 2 is proposed | Keep proposed and actual dates distinct |
| New training plan | Employer B coordination not completed | Identify the responsible employer contact |
| School submission route | No current DSO instructions saved | Obtain the applicable school workflow |
| DSO receipts | Neither record has a receipt | Track each receipt separately after actual submission |
Mira’s completed coordination memo reads: “Two record sets remain incomplete. Employer A’s message supplies a planned end date, not a final evaluation. Employer B’s proposed start does not supply a completed training plan or resolve authorization. The DSO’s current procedure and separate receipt expectations need confirmation. No form has been completed, signed or transmitted in this example.”
Her full unsent administrative question reads: “Hello, I am organizing an employer-change reporting handoff and would like to confirm the current school procedure. Could you clarify how to submit the departing employer’s final evaluation and the new employer’s training plan, how to distinguish proposed dates from actual dates, and how receipt of each record will be confirmed? Please also tell me how to report a change if one record is still awaiting employer review. I will use the approved channel for any required personal records. This message contains no documents or identifiers. Thank you.”
The finished next-step plan is to obtain instructions, coordinate the two employer reviews and retain the resulting submission evidence separately. It is not to wait for a perfect combined packet before raising an approaching reporting issue, invent signatures or decide that the proposed start is authorized. The example provides no evaluation narrative or training objectives to reuse.
Keep training content with the student and employer
DHS’s Form I-983 overview, updated October 2, 2025, describes the plan as articulating learning objectives and employer commitments. It lists the connection to the qualifying degree, goals, work-based learning, evaluation and supervision among the matters the plan must explain. The student and employer work together on the actual form; the DSO maintains the completed record.
A job description alone does not supply all of that information. Do not reuse another employer’s learning objectives, supervision description or evaluation narrative because the job title looks similar. Those statements need to reflect the actual opportunity and the responsible parties’ review.
This article deliberately leaves all personal training content blank. A coordination record can identify who needs to respond without writing the substance for them. If a supervisor, location, employer identity or training arrangement changes, ask your DSO how the change should be reported. Do not independently classify it as immaterial merely because the role remains in software engineering.

Worked example: a receipt for one file leaves the other unresolved
The second fictional case starts after an imaginary administrative handoff attempt. Noah’s private documents are not shown or described. The only invented evidence is a set of generic status messages: one acknowledges a new-plan upload, while the old-evaluation record has no receipt and an earlier note contains a different end-date label.
| Checkpoint | Fictional record | Limited finding |
|---|---|---|
| Old end-date note | Earlier note says October 23 | Date source needs reconciliation |
| Later date message | Employer A message says October 26 | Ask the responsible parties which date reflects the actual end and how to correct the school record |
| Old final evaluation | Review status marked pending | No completed old record established |
| New plan | Generic upload acknowledgement recorded | Evidence of that upload only |
| DSO review | No review-completion message recorded | Receipt does not establish substantive review |
| New start | A separate note says “proposed” | No actual start or authorization conclusion |
| Remaining reporting tasks | No DSO response to date discrepancy | Ask how to correct and complete the handoff |
Noah’s completed reconciliation memo reads: “The upload acknowledgement concerns the new-plan record only. It does not close the old evaluation, reconcile the conflicting old-end dates or establish DSO review. The proposed new-start label remains separate. Neither the number of uploaded files nor a generic receipt determines compliance or work authorization.”
His complete unsent process question reads: “Hello, I have an acknowledgement associated with the new-plan upload, but I do not have confirmation for the old final evaluation. My administrative notes also contain two different old-end-date labels. Could you advise how to reconcile the date through the school’s current process, how to report the still-pending employer review and what separate confirmations I should expect? I am asking about the procedure and will provide any required records only through the approved channel. Thank you.”
The completed action record reads: “Keep the new-upload acknowledgement; leave old evaluation and date reconciliation open; request the current correction route; record any DSO response without converting it into an individual authorization decision.” No actual school account, document or status has been changed. Unlike Mira’s initial planning case, this example addresses contradictory administrative evidence after one acknowledgement exists.
Ask about missing pieces promptly and retain the response
If an employer contact is unavailable or a record is still under review, describe the missing step to your DSO promptly. A pending signature is not a reason to invent completion or backdate a record. Ask how the school wants the issue reported and preserve the answer through the established process.
Likewise, a technical problem with a portal does not establish an extension of a federal reporting period. Keep a nonsensitive note of the problem and ask for the institution’s approved alternative. Do not redirect private records to an unfamiliar address or use another school’s form because it was easier to find online.
Maintain separate administrative states: instructions received, employer coordination pending, actual submission acknowledged and DSO follow-up pending. Record the confirmation’s date, source and exact scope, so a file receipt remains distinct from a review outcome. Leave an unresolved field open rather than marking it complete because another file has a receipt.
The useful outcome is a truthful handoff record and a clear route for resolving questions with the DSO responsible for your record. It is not a self-issued conclusion about immigration status or permission to work. While organizing your next role, browse recent roles on LandOffer.ai and keep job-search notes separate from sensitive immigration documents.
Sources and Further Reading
- DHS: Students—STEM OPT Reporting Requirements, updated July 6, 2026; checked October 22, 2026.
- DHS: Students and the Form I-983, updated November 26, 2024; checked October 22, 2026.
- DHS: Form I-983 Overview, updated October 2, 2025; checked October 22, 2026.
- Harvard International Office: STEM OPT Change in Employment, checked October 22, 2026; school-specific procedure.


