Job search
Verbal Job Offer but No Letter: Confirm the Terms and the Next Step
Request written terms, separate stated proposals from unresolved approvals, and make a dated follow-up record while keeping other deadlines intact.
If an employer gives you a verbal job offer but no letter, ask for the written terms, identify what still needs confirmation and agree on the next update. Record the conversation accurately without turning a proposed salary, start date or manager's enthusiasm into final approval. A delay alone does not tell you whether the offer is progressing or has changed.
Your next useful result is a specific answer: which document is coming, who owns it, what remains unresolved and when you should hear again. Keep other search activity visible, including recent roles on LandOffer.ai, while you clarify this opportunity. Track the encouraging conversation separately from receipt and review of the written terms.

Ask for the document and an expected update
Sources checked October 22, 2026: UConn's negotiation guide recommends requesting a written offer and clarifying its details after a verbal conversation. It suggests a follow-up if a document has not arrived 48 hours after requesting it. That is the university's guidance, not a service deadline every employer has agreed to meet.
If the recruiter already gave a date, use that date in your record. If the date was simply “soon,” ask for an expected day and, if a deadline matters, the time and time zone. A proposed check-in can be polite and concrete without sounding like an ultimatum. You are asking for information needed to make a decision, not pretending that your preferred date is binding on the employer.
LandOffer.ai publishes this guide. We read current public university guidance and one employer's published offer-delivery process. We did not contact employers, inspect a private application, receive an offer or send the messages below. Both cases are original fiction, and their dates are planning examples rather than completed candidate events.
Separate what was said from what was confirmed
Write down who spoke, when, the role discussed and the words you remember. A note made soon after the call helps you spot a changed term or a question you still need answered. Label a paraphrase as your recollection; do not put quotation marks around a polished sentence the recruiter never actually said.
Then separate three kinds of entry. First, the recruiter may have described a term. Second, the recruiter may have described an approval or condition as pending. Third, you may have inferred something because it sounded likely. Only the first two belong in your account of the conversation; an inference needs its own explicit label.
For an engineering role, title and level can matter independently. A team may discuss work resembling a senior position without confirming the level in the offer. Similarly, “remote-friendly” does not settle permitted location, office attendance or an eventual change in policy. Ask for the actual arrangement rather than complete those fields from your preferred interpretation.
Avoid diagnosing silence. Rollins College's guidance describes several possible causes of delay and recommends asking for a timeline and clarifying terms and contingencies. Those possibilities do not establish which explanation applies to your employer. Leave finance approval marked unknown unless the employer identifies it as pending.
Worked record: turn one engineering call into a precise clarification
Fictional case: Isha discusses an API engineering role with recruiter Morgan on November 3, 2026 at 10:00 a.m. Los Angeles time. Her invented notes say a letter is expected Thursday, but no time is given. The following is her completed preparation record, not an offer document.
| Item | Isha's stipulated call record | Classification and next owner |
|---|---|---|
| Role | API engineer on the integrations team; “Engineer II” discussed. | Title and level described verbally; Morgan to confirm written version. |
| Compensation | $145,000 described, but her notes do not establish whether it means base alone. | Amount discussed; compensation basis unresolved. |
| Other components | A possible sign-on payment mentioned without an amount. | Proposal only; Morgan to clarify whether anything is approved. |
| Location | Two office days discussed; permitted home location not specified. | Working arrangement incomplete; ask recruiter to identify the responsible contact. |
| Start | December 7 mentioned as a possible start. | Tentative date, not a completed onboarding instruction. |
| Conditions | Recruiter mentioned “remaining checks” without identifying them. | Type, status and candidate action unknown. |
| Document | Letter expected Thursday, November 5; delivery method not stated. | Expected event, not received; Morgan is current contact. |
| Response deadline | None recorded. | Ask when a decision would be needed after the document is available. |
Her complete, unsent message reads:
Subject: Written terms and next update for the API engineering role
Hi Morgan, thank you for discussing the integrations-team role with me on November 3. I remain interested and would appreciate the written terms so I can review the opportunity. My notes include Engineer II, a $145,000 figure, a possible December 7 start and two office days, but I have not received the document. Could you confirm the title and level, whether the amount is base salary, the working location and any additional compensation? Please also identify the remaining conditions, any action needed from me and how the letter will be delivered. You mentioned Thursday; if it is still pending then, could we plan an update Friday, November 6 at 10:00 a.m. Los Angeles time? Please let me know the expected response deadline once the written terms are available.
Isha's decision is request clarification; keep the record unconfirmed. She has expressed interest without inventing an acceptance or claiming that all approvals are finished. Her requested Friday update is also just a request until Morgan agrees.
Isha leaves the cause of the delay unknown. It does not say legal, finance or a background-check company has blocked the letter, because those facts were not provided. “Remaining checks” stays unresolved rather than becoming a named screening process in her notes.
Review terms and conditions when the document arrives
UC Berkeley's offer-evaluation guidance identifies title, salary, start date, supervisor and response deadline as information to review. It also recommends obtaining missing benefits information and checking any stated contingencies. Use that as a preparation framework, then read the actual document and attachments for your opportunity.
Check whether each important verbal term appears and whether it changed. A general benefits brochure may explain available plans without fixing your individual eligibility, cost or effective date. A compensation figure might be recurring base pay, a target bonus, a one-time payment or an equity description. Do not combine those into one guaranteed cash amount.
For a software engineer, also resolve anything that changes the decision: team assignment, location, work schedule, level or the responsibilities you were recruited to perform. You do not need to ask every imaginable question. Prioritize the gaps that would cause you to reconsider the role or that the employer specifically asked you to act on.
Receiving a document does not prove that every condition has cleared. Your own tracking can say “written terms received” while separately saying “review incomplete” or “condition pending.” This guide organizes communications; it does not decide the legal effect of a conversation or document in a particular jurisdiction.
Check the delivery route without assuming a universal portal
An offer need not arrive as a particular PDF attachment. Microsoft's current hiring guide describes offer paperwork delivered through recruiter email, a secure link or, in some countries, its Action Center. That is one employer's published process, not an instruction to expect Microsoft's workflow from another company.
Ask your recruiter which route applies. If they say the document was sent, confirm the destination address and approximate sending time, check the relevant inbox and portal, and report what you actually see. “I cannot locate the document” is more accurate than “the offer was never issued” when delivery is still unclear.
Keep requests for sensitive information within the verified recruiting process. A follow-up does not require sending a passport, banking details or an entire competing offer to someone merely because they ask. Establish the intended recipient and purpose through the employer's legitimate route before deciding what to provide.
Worked follow-up plan: an outside deadline does not create approval
Separate fictional case: Kai has an oral discussion with Company Cedar about a platform engineering role on Monday, October 26. Cedar's recruiter proposes Wednesday for written terms. Kai also has a separate written offer from Company Birch with a stated response deadline of Friday, October 30 at 4:00 p.m. New York time. Neither employer is real.
He completes this action record:
| Planning point | What is established in the example | Kai's completed next-step decision |
|---|---|---|
| October 26 | Cedar conversation; no written terms received. | Record the discussion and Wednesday estimate, without calling it final approval. |
| October 28 | The expected date passes without a document in the stipulated record. | Prepare a dated follow-up with the real outside deadline. |
| October 29 | A hypothetical reply says approval is pending. | Ask for the next update and responsible contact; keep approval pending. |
| October 30 | Birch's existing deadline still applies unless Birch changes it. | Request any extension before that deadline; an unanswered request does not extend it. |
His full, unsent Cedar follow-up reads:
Hi Avery, I am following up on the platform engineering discussion and the written terms expected Wednesday. I remain interested, but I have not received them. I also have a separate response deadline Friday, October 30 at 4:00 p.m. New York time. Could you tell me whether the role and terms have final approval, what is still pending, and when I can expect the document or a definite update? If the timing cannot fit that deadline, please let me know so I can evaluate the information actually available to me. I am not assuming that the earlier conversation completed your approval process.
His separate, unsent Birch extension request reads:
Hi Jordan, thank you for the written offer and the October 30 response deadline. I would appreciate additional review time and would like to ask whether you can extend the deadline to Monday, November 2 at noon New York time. Please confirm whether that is possible. Until I receive confirmation, I will continue treating the existing Friday deadline as the applicable one.
Berkeley's guidance recommends asking for an extension before the original deadline and recognizing that an employer may decline. Kai has requested time, not obtained it. The example makes no recommendation to accept or reject either opportunity and supplies no outcome prediction.
He also writes three response branches. If Cedar names a new date, record that estimate and any remaining approval. If Cedar says it cannot provide a date, retain the uncertainty rather than announce an offer loss. If a document arrives, review its contents and conditions; do not treat arrival alone as agreement to everything discussed.
An executed Python timezone calculation converted Birch's October 30 deadline to 1:00 p.m. Los Angeles time and 20:00 UTC. It also converted Isha's proposed November 6 check-in to 1:00 p.m. New York time and 18:00 UTC. These dates straddle the US daylight-saving change, so the UTC hours differ. The calculation checks those invented timestamps only; it does not book meetings, extend a deadline or establish an employer response.

Keep your next decision tied to confirmed information
When an expected update passes, make the follow-up useful: name the role, the earlier conversation, what you have not received and the next answer you need. Keep a single accurate chronology rather than repeatedly rewriting uncertainty as approval or rejection.
For substantial decisions about notice, relocation or expenses, identify the written terms and unresolved conditions first. Neither this checklist nor an encouraging call supplies missing employer confirmation. Browse recent roles on LandOffer.ai while maintaining one dated record of this opportunity, and use the next confirmed update to decide what information is still missing.


