How to Turn a Verbal Promise Into Signed Physician Contract Terms

A recruiter says, "Don't worry, we'll take care of that." A medical director says, "Yes, the call is light." Someone on the interview day says, "You'll definitely get the sign-on bonus and protected admin time."

Good. Helpful. Not binding.

Here's my position: a verbal promise in physician recruiting is real enough to pursue, but stupid to trust until it becomes precise written language. I've seen too many new attendings assume everyone "was on the same page," only to discover that salary was described as a range, call became "shared equitably," and bonus timing somehow turned into "after board approval." That's not bad luck. That's poor process.

Educational disclaimer: This article is for education only and is not legal, financial, tax, or employment advice. Physician contracts, compensation structures, enforceability, malpractice provisions, and related obligations vary by employer, specialty, contract type, and state. Review important terms with a qualified physician contract attorney and, when appropriate, other licensed professionals before signing.

This article is for the stretch between the exciting phone call and the actual signature. At each point, you should be turning memory into documentation, documentation into contract language, and contract language into something enforceable.

This article is for educational purposes only. It is not financial advice, not legal advice, and not tax advice. Figures vary by individual circumstances, consult a qualified professional before acting.

Start With the Verbal Promise: What You Can Safely Rely On Today

First, define the promise clearly. In physician recruiting, a "verbal promise" usually means one of these:

• Your role or title
• Clinical scope
• Practice location
• Schedule
• Call expectations
• Compensation range or guarantee
• Start date
• Sign-on bonus
• Relocation support
• Loan repayment
• Protected time
• Partnership track
• Moonlighting permission

That counts as meaningful negotiation material. It does not count as settled deal terms.

What is not enough on its own?

• "We usually do it this way."
• "That shouldn't be a problem."
• "HR will put it in."
• "Leadership already agreed in principle."
• "We'll clean up the details later."

No. "In principle" is where physician contract promises go to die.

At this point you should capture four things immediately:

1. The exact wording
   • Not your summary. Their words.
2. The date and time
   • Especially if there were multiple conversations.
3. Who said it
   • Recruiter, chair, department administrator, managing partner, CEO.
4. Who else heard it
   • Spouse on speakerphone, another interviewer, site lead, recruiter assistant.

Why this matters: not every speaker has authority. A recruiter may confidently promise call relief that the department chair never approved. A partner may describe a partnership track that isn't written anywhere. Friendly people overpromise all the time. Not maliciously. Just casually. Casual is dangerous.

So your mindset on day one should be simple: Useful promise? Yes. Settled term? Not yet.

Day 0 to Day 2: Document the Promise Before It Changes

This is the highest-yield move in the whole process. Same day, or at worst within 48 hours, send a recap email.

Short. Professional. Clean.

Something like:

• Thank them for the conversation.
• Restate the discussed terms in plain language.
• Ask them to confirm that your summary is accurate.
• Keep it in email, not text.

Example structure:

• "Thank you for speaking today."
• "My understanding is that the position includes..."
• "Base compensation will be..."
• "Call will be..."
• "Start date is expected to be..."
• "Sign-on bonus/loan support discussed was..."
• "Please let me know if I've misunderstood any part of this."

That email does three jobs at once:

1. It creates a timestamp.
2. It forces correction early.
3. It exposes fuzzy promises before they harden into assumptions.

Also create a note log for yourself. I like a simple template:

• Date
• Time
• Who was present
• Method: phone / Zoom / in person
• Exact phrase used
• Numbers mentioned
• Deadlines mentioned
• Conditions or contingencies
• Next promised action

At this point you should avoid casual text follow-up. Text threads blur details, invite shorthand, and make later review miserable. I've seen residents rely on "Yep should be fine" in a text as if it settled a relocation clause. It didn't. Keep a clean written trail in email and stored notes.

If they won't confirm by email, that's information. Not good information.

Week 1: Convert the Conversation Into Written Terms

Now you stop thinking in promises and start thinking in contract categories.

Take every verbal commitment and turn it into a checklist. Your list should include:

• Position title
• Specialty scope and duties
• Practice site(s)
• FTE status
• Clinic hours
• Call frequency and backup structure
• Salary guarantee
• Productivity formula
• Bonus timing
• Sign-on terms
• Relocation assistance
• Loan repayment
• CME
• Vacation/PTO
• Benefits start date
• Malpractice coverage and tail
• Restrictive covenant
• Moonlighting
• Partnership path, if applicable
• Termination without cause
• Notice period
• Start date
• Credentialing contingencies

Then ask for the full draft contract, not a summary sheet, not a benefits handout, not a recruiter bullet list. The draft is where reality lives.

Once you have it, compare line by line:

• What was promised?
• Is it in the draft?
• If it's in the draft, is it specific enough?
• If it's missing, is there another clause that undermines it?

Here's where vague language causes trouble. Watch for phrases like:

• "As assigned by employer"
• "At employer discretion"
• "As needed"
• "Consistent with business needs"
• "Subject to policy"
• "May be eligible"

Those phrases aren't always wrong. But if the verbal promise was specific, vague language is a downgrade.

For example:

• Verbal promise: "One weekend in six."
• Draft language: "Physician shall participate in call coverage as assigned."

That is not the same deal.

At this point you should request precise replacements before the draft advances. Don't wait until "final version" to raise obvious problems. Early correction is easier and less political.

A good rule for Week 1: if a term matters enough to influence whether you take the job, it belongs in writing with enough detail to survive turnover, memory gaps, and selective amnesia.

Week 2 to Week 3: Negotiate the Missing Pieces and the Risky Language

Now you negotiate what's absent, watered down, or dangerous.

Prioritize the terms most likely to become disputes later:

• Guaranteed compensation
• Sign-on bonus timing and repayment triggers
• Call burden
• Clinic schedule
• Protected administrative time
• Partnership track
• Termination rights
• Restrictive covenant scope
• Tail coverage
• Work location flexibility

This is where I want you to be a little tough. Not dramatic. Just clear.

If someone verbally promised a specific condition, ask for matching language. If the employer needs flexibility, fine, but define the limits. "Flexible" without boundaries is usually employer-friendly and physician-hostile.

Common traps:

• "Subject to approval" If approval hasn't happened, the promise isn't done.
• "At employer discretion" That means they can change it.
• "As needed" That can swallow your schedule whole.
• "May receive" or "may be eligible" That's not a commitment.
• Policy references not attached to the contract If the policy matters, get it.

At this point you should trade on priorities. That means:

• Be firm where the verbal promise was specific.
• Be flexible where the employer genuinely needs operational room.
• Don't waste leverage on minor cosmetic edits if your real concern is call, termination, or compensation structure.

A practical way to negotiate:

1. Send a marked list of discrepancies.
2. Group them by importance:
   • Must match discussion
   • Needs clarification
   • Nice to have
3. Ask for a call if the issues are easier to resolve live.
4. Follow the call with, again, an email recap.

That last step matters. Every time.

I've seen this exact sequence: a physician has a productive call, gets reassured verbally, assumes legal will update the draft, then signs a version that still contains the original bad clause in Exhibit B. Brutal. Preventable.

Final Review to Signature: Lock the Paper to the Promise

Before you sign, do one last side-by-side review:

• Original note log
• Same-day recap email
• Redline history
• Final contract
• Attachments
• Exhibits
• Compensation addenda
• Call schedules or referenced policies, if included

Your job here is not just to confirm what's included. It's also to confirm what's not included.

If a promised term didn't make it into the contract, you need one of two outcomes:

1. It gets added, or
2. Everyone explicitly agrees it is not part of the deal

Ambiguity is the enemy. "We all understand" is garbage at signature stage.

At this point you should check especially for:

• Dates that changed
• Bonus conditions hidden in exhibits
• Repayment language for sign-on or relocation
• Notice periods
• Restrictive covenant geography
• Tail coverage obligations
• Start date contingencies
• Policy documents incorporated by reference

Do not sign because you're tired of the process. That's how people inherit bad contracts. Sign when the final version actually matches the negotiated deal.

If you hired a physician contract attorney, this is the moment to have them review the exact final copy, not an earlier draft. Final means final.

After Signature: Keep the Record and Prepare for Start Date Issues

Once signed, your work isn't over. It just changes.

Store everything in one folder:

• Signed contract PDF
• All redlined drafts
• Email threads
• Compensation exhibits
• Benefits documents
• Note logs
• Any policy documents referenced in the contract

Then set reminders right away for:

• Licensing deadlines
• Credentialing submissions
• DEA and payer enrollment tasks
• Start date
• Bonus payment milestones
• Relocation reimbursement deadlines
• Notice dates tied to contingencies
• Onboarding paperwork

At this point you should also know which promises are now contract rights and which still require separate follow-up in practice operations.

Example:

• "You'll get one MA" may not be contract language.
• "Protected admin half-day weekly" might be in the agreement.
• "Partnership after two years" had better be clearly defined somewhere if it mattered to your decision.

A signed contract is not self-executing magic. It's a record. Keep it accessible, and use it.

The Reminder You Need

Treat the verbal promise as the starting point, not the finish line.

Day by day, your job is simple:

• capture what was said,
• confirm it in writing,
• convert it into contract language,
• and refuse to sign a watered-down version of the deal.

At each stage, ask one question: Does the paper match the promise?

If the answer is no, you're not done.