1. LandOffer
  2. Blog
  3. All articles
  4. First OPT Job Offer: Gather the Employer Details for Your SEVP Portal Update

Job search

First OPT Job Offer: Gather the Employer Details for Your SEVP Portal Update

Build an employer fact packet from the offer and authorized clarification, then follow your school’s current route for the employment update.

10 min readLandOffer team

Before updating an employer record for a first OPT job, gather the employer’s confirmed legal name, relevant addresses, actual work location, employment dates, work schedule and duties. Confirm those facts with the employer; an advertisement’s brand name and an offer’s proposed start date do not establish every reporting field. Then follow your designated school official’s current reporting instructions and the portal route that applies to your training category.

This guide reviews official public guidance checked on October 22, 2026. It organizes employer facts; it does not determine anyone’s immigration status, job eligibility or permission to begin work. No portal account, private offer, identification document or student record was accessed. The two completed administrative examples below contain no student profile or immigration outcome. LandOffer publishes this guide and provides recent job listings; a listing is a research lead, not verified reporting data.

An offer folio, magnifier and cards depicting an organization, location, calendar and tools illustrate gathering employer facts.

Separate the offer from the reporting record

An offer can establish proposed employment terms, but it may not contain every fact needed for reporting. A marketing name, headquarters address and intended start date can all differ from the details relevant to an employer record. Read each field rather than copying the offer’s heading into every box.

USCIS describes OPT as temporary employment directly related to the student’s major area of study in its OPT overview. Reporting an employer does not replace the separate authorization process. This article does not evaluate a real job’s relationship to a degree or decide when a person may start working.

Use the offer and an authorized employer contact to establish the employment facts. Use your DSO and current official instructions to clarify reporting requirements. A recruiter’s confirmation of the employing entity answers a factual question; it is not an immigration ruling. Similarly, a public portal guide describes fields without approving the underlying employment.

Maintain a short source note beside each item: offer, employer clarification, current duties description or school instruction. If the offer and employer clarification differ, note the exact field and ask the employer which fact is current. Ask the DSO separately how that fact should be reported. Do not change a proposed date into an actual employment date simply because the latter has not yet been confirmed.

Confirm the employer name and location instead of borrowing a brand

The University of Maryland, Baltimore County’s SEVP Portal help tells its students to confirm the legal company name when an employer uses multiple names. It also distinguishes the company that legally hired the person from a client company in a contracted arrangement. These are useful factual distinctions, not proof that every arrangement qualifies for OPT.

Ask the employer which entity appears in the employment relationship and how its name should be stated. A parent company, product brand, staffing firm and client are not interchangeable merely because their names appear in the interview process. Do not infer the legal employer from the application website’s logo or a job-board heading.

Collect the headquarters or business address and the actual work-location information separately. UMBC’s instructions distinguish the physical worksite from headquarters and describe where its students should add additional context. That is an institution-specific reporting procedure. It should not be presented as a universal rule for every school or every remote arrangement.

If the role is remote, hybrid or assigned to a client site, describe the arrangement factually to your DSO and ask how the current fields should reflect it. Avoid choosing a home address or headquarters address simply because an online discussion says it worked for someone else. Keeping both facts available lets the DSO address the reporting question without forcing you to guess which address the employer meant.

Read the portal category before treating every field as yours

DHS’s Update Employer Information guide, updated May 25, 2023, lists employer information such as name, address, job title, full- or part-time designation, dates and relationship to the field of study. Its public Add Employer instructions describe saving required fields and receiving a success message.

The same page says STEM OPT participants cannot use that Add Employer feature; their DSO enters employer information after the required training-plan process. It also marks certain fields, including the employer identification number and supervisor fields, for STEM OPT. Do not turn a combined documentation list into a claim that every field is mandatory or editable for every initial post-completion OPT user.

This guide focuses on collecting facts for a first employer update. It does not supply Form I-983 answers or instructions for a STEM employer change. If your category or record is unclear, resolve that with the DSO before treating the visible controls as the correct route.

The official help also directs users to their DSO if the employment-authorization information displayed in the portal is wrong. Do not try to fix an authorization discrepancy by changing unrelated employer fields or substituting a convenient date. A data-entry workaround is not confirmation that a record is accurate.

Worked fact packet: Record A separates four organization details

Record A is an original fictional employer-information exercise. It includes no student identity, immigration status, authorization dates or actual company address. The invented documents use administrative placeholders rather than a real offer. The purpose is to reconcile the facts before any reporting action.

The made-up offer heading uses Harbor Sketch, while an invented HR note identifies Harbor Sketch Operations LLC as the employing entity. The fiction does not assert that either name belongs to a real business. The employer note supplies separate headquarters and worksite placeholders and says the final start information still needs confirmation.

Packet field Completed fictional record Source or unresolved boundary
Advertised brand Harbor Sketch Invented heading, not the reporting entity by default
Employing entity Harbor Sketch Operations LLC Invented HR clarification; no actual legal-entity verification
Headquarters [EMPLOYER_HEADQUARTERS_ADDRESS] Kept separate from the worksite
Work arrangement Hybrid, as an invented administrative input No school-specific address entry inferred
Worksite [CONFIRMED_WORKSITE_ADDRESS] Placeholder only; actual reporting instruction still needed
Employment start [ACTUAL_START_DATE_NOT_YET_CONFIRMED] Proposed offer date is not substituted
Employer contact [AUTHORIZED_EMPLOYER_CONTACT_ROLE] No private name, email or phone supplied

The completed reconciliation reads: “The invented brand and employing-entity name are different. Both address categories are retained, and the work arrangement is described without deciding which address goes in a particular field. The actual-start-date field remains unresolved. No reporting, authorization assessment or employment event has occurred.”

Record A’s complete UNSENT employer question is:

Subject: Confirming employer details for an administrative employment update

Hello Employer Contact,

Could you confirm the employing entity’s full name, headquarters address and the worksite associated with this position? Please distinguish the employing entity from any product brand or client organization.

I would also like to confirm the actual employment start information, expected weekly schedule, current job title and duties, and the appropriate contact role for questions about these facts.

I will use my school’s current instructions to determine the reporting route and field requirements. This draft asks for employer facts only; it does not request an immigration or work-authorization decision and contains no student record or identification document.

Thank you

The completed packet distinguishes an invented brand from an invented employing entity and identifies the missing facts. It does not verify a real company or a person’s employment. It is not a submitted employer record. An actual employer’s confirmed information and the school’s instructions would replace the invented inputs.

The portal’s relation-to-field-of-study prompt calls for an explanation, not a job-title match. Collect the actual tasks, tools, methods and expected outputs from the employer’s current duties description. Keep the source of each fact beside the study material you can substantiate. Do not paste a generic job-board description that the employer has not confirmed as your work.

A useful preparation note distinguishes “builds data validation routines” from “works in technology.” The former identifies a task that can be discussed; the latter leaves the relationship unexplained. Avoid adding responsibilities, projects or coursework solely because they would make a connection sound stronger.

This article does not write an actual student’s degree-relationship statement. Questions about whether the work satisfies the applicable requirements belong with the DSO or qualified adviser. A clear factual explanation is useful supporting information, but clarity alone does not establish eligibility or approval.

Keep contacts and schedule facts available even where a specific initial-OPT portal field does not request them. They may help the school clarify the record. That does not mean you should enter extra personal information into unrelated fields or upload the complete offer to a service that has not requested it through an authorized route.

Worked readiness record: Record B separates facts from an unsupported connection

Record B is a separate original administrative exercise using only fictional work-description categories and document states. It does not depict an actual student, degree, immigration category or portal account. Its invented task note describes maintaining a data-quality tool; its study-record placeholder has not been reviewed.

The completed readiness record below explains what can be organized and what remains unsupported. It is not an answer to a live portal question.

Preparation item Completed fictional finding What remains to establish
Current job title [EMPLOYER_CONFIRMED_TITLE] retained as a placeholder Actual employer confirmation, not a public advertisement
Duty description Maintain validation rules and investigate failed data checks in the invented exercise No real employment or implementation claimed
Work output A maintained data-quality tool is the fictional output No actual production result or measured impact
Study evidence [RELEVANT_STUDY_RECORD] not reviewed No degree or coursework invented
Relationship explanation Not drafted as an eligibility conclusion Facts and appropriate adviser review required
Schedule [CONFIRMED_WEEKLY_SCHEDULE] missing No full-time designation or hours inferred
Reporting route [CURRENT_DSO_INSTRUCTION] missing No portal save, school submission or confirmation claimed

The completed note reads: “The invented duties are concrete enough to request confirmation, but the study and schedule evidence are absent. I will not fill those gaps with a generic computer-science claim or an assumed full-time schedule. The next administrative step is to obtain the missing facts and current DSO instruction. This record establishes no person’s qualification, authorization or reporting compliance.”

Record B’s final state is “fact inventory prepared; relationship statement not submitted; reporting route unresolved.” The readiness review is complete because it identifies the missing evidence and its owner. The underlying reporting update remains unperformed. It does not convert incomplete information into a simulated approval or calculate unemployment time.

Two notebooks of tools and books connect through small bridges, with an unfinished bridge segment kept separate.

Follow the school’s route and verify what was actually recorded

DHS’s SEVP Portal Help hub presents resources for maintaining information, while the detailed instructions preserve a role for the DSO. A school can also specify its own collection process. UMBC’s page, for example, gives its students particular portal, address and follow-up instructions. Use your own school’s current procedure rather than treating that example as a national form template.

Reporting is time-sensitive. Confirm the applicable timing promptly with your DSO and the current official instructions; this article does not calculate an individual reporting deadline or count unemployment days. A question waiting for a reply is not a completed update, and a saved local draft is not a portal record.

After any real update you perform through the authorized route, distinguish the submitted information, the confirmation displayed and any school follow-up still requested. If a field is unavailable, an address is rejected or an employment date cannot be entered, explain the precise issue to the DSO. Do not create a duplicate employer or alter a factual date merely to get past validation.

For other search activity, browse recent roles on LandOffer.ai. For the first offer already received, put each employer fact beside its source and identify who can resolve any gap. Follow the confirmed reporting route and verify what was recorded; keep unconfirmed facts out of the completed record.

Sources and Further Reading