Job search
Federal Tentative Job Offer vs. Final Offer: Track the Steps Before Entering on Duty
Track which actions you completed, which decisions remain with the agency, and what the final offer and first-day instructions actually confirm.
Accepting a federal tentative job offer does not authorize you to begin work. Treat the TJO, requested onboarding actions, agency review, final or official offer, and confirmed entrance-on-duty arrangements as separate records. For a first federal IT role, the useful question is not simply whether the portal says “accepted.” It is which step has been confirmed, by whom, and what remains outstanding before the agency expects you to report.
This LandOffer.ai guide reviews official USAJOBS, OPM and GSA TTS public materials inspected October 22, 2026. It does not access an applicant account, complete forms, determine clearance or employment eligibility, or accept an offer. The examples below are fictional administrative records and unsent questions. You can browse recent roles on LandOffer.ai, then use each federal announcement and the hiring agency’s instructions for its actual requirements.

Read the tentative offer as a conditional stage
A TJO identifies a proposed appointment and starts a response process; it is not the same document as the final offer. Read the actual response deadline, position, organization, grade or pay system, duty location and stated conditions. If the deadline or meaning of a term is unclear, identify the HR contact named in the communication. Do not invent a government-wide number of days to respond.
Keep the offer itself and the acknowledgement of your response together, labelled by document type, issue date and response date. Those fields let you distinguish accepting the TJO from responding to a later official offer. An automated confirmation can show that a response was recorded without showing that every hiring condition has been satisfied. Likewise, an onboarding invitation or a requested appointment can indicate a next task without establishing that the agency has issued its final offer.
The current USAJOBS hiring-timeline article says the interval after accepting a tentative offer can span weeks or months. That is broad process guidance, not a completion deadline for a particular IT vacancy. A colleague’s faster timeline supplies no approval for your own start date.
Separate your actions from agency decisions
For every requested action, record the instruction, due date, responsible party and evidence of submission or completion. This makes a follow-up answerable: HR can identify a missing action without reconstructing your entire history. Then separately record the agency decision that may depend on it. “I submitted the requested item” and “the agency approved the next stage” answer different questions.
USAJOBS explains background checks and security clearances as job-dependent processes and distinguishes Public Trust investigations from security clearances. Use the announcement’s background and security section and the agency’s instructions. A technical title alone does not identify the required investigation, credential or trust determination.
This distinction also protects the task record from becoming a private-data archive. Track a task’s label and status rather than copying investigation answers, identification numbers or personal documents into a general job-search spreadsheet. Keep sensitive submissions within the channel the agency specifies. This guide supplies no questionnaire answers or judgment about whether a person will receive a favorable determination.
When one office reports that its part is finished, ask it to name the completed step and the office responsible for the next one. It may concern receipt, scheduling, review or a particular authorization. Avoid translating a narrow update into “all conditions cleared” unless the responsible agency explicitly confirms that broader meaning.
Account for agency variation and continuing investigations
GSA’s TTS hiring and onboarding FAQ provides a useful agency-specific example: it describes initial access before a final offer and notes that the full investigation can continue afterward. The page also separates recruiter, HR, security and onboarding contacts. Its advice is to wait for the final offer before giving notice to an existing employer.
Do not turn that example into every agency’s sequence. The TTS page names particular systems and steps; your current agency communication must identify the systems, deadlines and instructions that apply to your case. A general hiring summary and an agency’s more specific process description can operate at different levels of detail.
In your record, leave “review complete,” “authorized to start” and “investigation complete” as distinct fields when the agency distinguishes them. You do not need to decide the security significance yourself. Ask HR which confirmations are required for the stated start date and which processes, if any, continue after entry.
Interpret portal labels without promoting them into approval
OPM’s USA Staffing task reference distinguishes tentative-offer response, official-offer response, a projected EOD date and first-day arrival verification. It is documentation for system workflows, not a promise that every candidate sees the same screens or that a completed task settles all hiring conditions.
That distinction matters when someone sees a future date next to a completed task. Recording a projected date can complete that particular system task; it does not mean the person has already reported for duty. Read what the task describes before using its status in a personal calendar.
OPM’s notification guidance also treats invitations, tentative offers and official offers separately. It directs users with an inactive or cancelled record message to HR. A portal error therefore needs clarification; it is not enough information for this guide to diagnose an offer’s status. These are public documentation observations, not a test of an applicant’s private account.
A completed evidence ledger for a first federal IT offer
Mina’s fictional record concerns a proposed IT Specialist appointment at an invented agency. The dates and documents are supplied only to demonstrate status tracking. No actual offer is being accepted, and no security outcome is assigned to her.
| Item | Supplied fictional evidence | Responsible party or next confirmation | Status on October 22 |
|---|---|---|---|
| TJO | Letter dated October 19, response requested October 21 | Mina’s response, then HR receipt | Response acknowledgement dated October 20 saved |
| Onboarding item | Task A instruction with October 23 due date | Mina, using the designated system | Submission receipt October 21 saved; review not confirmed |
| Fingerprint appointment | Appointment notice for October 26 | Designated appointment office | Scheduled; not yet attended |
| Agency review | No completion notice supplied | Responsible agency office, coordinated through HR | Unconfirmed |
| Projected EOD | Portal field displays November 16 | HR must explain whether this remains projected | Planning date only |
| Final offer | No final or official offer supplied | HR | Not received |
| First-day reporting | No location, time or orientation notice supplied | HR/onboarding | Not confirmed |
Her completed status memo reads: “TJO response acknowledgement and Task A submission receipt exist. Neither is evidence of completed agency review. The appointment is future, November 16 is labelled projected, and no final offer or reporting instruction has been received. The next action is to clarify the remaining steps with HR, not to mark the job started.”
Her complete unsent question is: “Subject: Remaining steps and projected EOD for IT Specialist offer. Thank you for the tentative offer. My record shows the response acknowledgement dated October 20 and Task A submission receipt dated October 21. The appointment notice lists October 26, and the portal shows a projected November 16 EOD. Please confirm which items remain with me, which remain with the agency, and whether November 16 is still a planning date. When should I expect the final-offer and reporting instructions? I am not including investigation information in this message.”
The ledger is complete even though the hiring process is not. Its value is making unsupported conclusions visible. Mina has one forthcoming appointment and several agency confirmations outstanding; counting submitted tasks cannot convert those unknowns into a final offer. A new notice would update its own row rather than erase the earlier record.

Reconcile the final offer with the actual reporting plan
An FJO is often called a final job offer; OPM’s system documentation uses “official offer.” Use the agency’s actual document names. Read the final terms and any remaining instructions instead of assuming that every field matches the TJO or that acceptance of one document automatically records a response to another.
Theo’s separate fictional example begins after an official offer has arrived. It tests document reconciliation, not whether Theo is eligible or should accept. A proposed date and two locations appear in different communications, so the finished output must identify exactly what needs confirmation.
| Field | Earlier record | Later fictional record | Reconciliation result |
|---|---|---|---|
| Position and organization | TJO: IT Specialist, Agency B | Official offer: same position and agency | Descriptions align; retain both documents |
| Duty location | TJO: Arlington | Official offer: Arlington | No documented location change |
| Start date | Earlier projection: November 16 | Official offer: November 30 | November 16 is superseded in this record |
| First-day site | Not specified | Orientation email: Washington office | Reporting site differs from duty location; ask for confirmation |
| Reporting time | Not specified | Orientation email: 9 a.m., time zone omitted | Request the time zone and exact reporting instructions |
| Security status | Earlier note: processing | No separate completion statement supplied | Do not label the full investigation complete |
| Offer response | TJO acknowledgement saved | No official-offer response receipt supplied | Check the final document’s response requirements |
His finished reconciliation memo is: “The official offer names November 30, replacing the earlier November 16 projection in this example. Arlington remains the duty location, while the orientation email names Washington for the first day. That may be intentional; it needs confirmation rather than an assumption that either message is wrong. Reporting time zone, remaining requirements and final-offer response status remain unresolved.”
His complete unsent follow-up reads: “Subject: Confirm November 30 reporting details. Thank you for the official offer. I see November 30 as the start date and Arlington as the duty location. The orientation email names a Washington office and 9 a.m. Please confirm the first-day address, time zone, check-in contact and whether that orientation location is separate from the regular duty location. Please also identify any remaining actions required before reporting and the applicable official-offer response deadline. My records do not yet contain a response acknowledgement for that offer.”
Theo’s earlier November 16 projection and later November 30 official-offer date are fourteen calendar days apart. That arithmetic describes the supplied documents, not fourteen days of pay, a guaranteed delay allowance or permission to choose a date. He has produced a precise question without changing any employment record or treating equipment delivery as approval to work.
Keep a dated next step rather than an assumed start
Maintain a compact status note with the last confirmed event, remaining candidate actions, responsible agency contact and a follow-up date. For example, label a privately chosen October 29 reminder “my follow-up reminder,” while retaining an October 23 task deadline as “agency instruction.” The follow-up date is your reminder unless HR has agreed to it; label it accordingly. Do not call it the agency’s promised decision date.
When an update arrives, preserve what changed and its source. A revised offer, a confirmed reporting location or a rescheduled appointment should not silently overwrite an earlier assumption. If instructions conflict, ask the responsible office to reconcile them before treating either version as settled.
Aim for a reporting plan confirmed by the responsible agency, supported by the actual offer and current instructions, with any continuing obligations identified. A complete personal ledger helps you ask questions; it does not itself grant permission to start. This article does not decide when a particular person may enter on duty or provide personal legal advice. When comparing recent roles on LandOffer.ai, record federal selection, tentative acceptance, final-offer response and reporting readiness in separate fields, then name the next unresolved confirmation rather than treating the whole process as complete.
Sources and Further Reading
Official materials inspected October 22, 2026. Agency-specific instructions control the individual process; public guidance does not determine a person’s clearance, appointment or start authorization.


