Pulse ← Trainings
Sales Trainings · sales-training
Current Quality5/10?

The Contract Pre-Flight — 60-Min Training

📖 1,631 words⏱ 7 min read5/23/2026

The Contract Pre-Flight

A 60-Minute Team Working Session Where Reps Surface Legal and Security Landmines Before Procurement Goes Dark

Why Run This Session

Deals slip when legal and security surprises appear after verbal yes. Reps forecast Commit while MSA status, security questionnaire, data residency, and signature authority are still "unknown"—then procurement goes silent for six weeks.

Pre-flight is a checklist discipline run before forecast commit, not after the buyer ghosts legal. Early legal intro on a twenty-minute buyer call prevents redline ping-pong nobody modeled.

This session co-builds the checklist with legal/RevOps, applies it to top commits live, and downgrades any deal with unchecked unknowns until pre-flight is green.

Managers who skip this ritual pay for it in forecast calls: reps defend numbers they cannot tie to buyer-side evidence or CRM artifacts. Running the session quarterly keeps new hires from inheriting bad habits from shadow pipeline—and gives RevOps a consistent field to audit when conversion or stage velocity drops.

The hour is not enablement theater; it is the minimum viable discipline before you scale headcount or raise quota.

What Reps Will Walk Out With

Who Should Be in the Room

Account executives, sales manager, and strongly recommended: legal counsel or deal desk plus RevOps. Reps bring top three forecast commits. Without legal present, use recorded checklist from last quarter and schedule legal office hours within a week.

Before the Meeting (Manager Prep — 15 Minutes)

  1. Legal/RevOps drafts draft checklist items before the room (MSA, security, insurance, residency, payment terms, authority).
  2. Reps pull status on each item for top three commits—honest unknowns allowed.
  3. Manager brings one slipped deal caused by late security review.
  4. CRM: ensure Pre-Flight Status field or note template exists.
flowchart TD A[Verbal yes on deal] --> B[Run pre-flight checklist] B --> C{Blockers found?} C -->|Yes| D[Engage legal early] C -->|No| E[Confirm close timeline] D --> F[Update forecast category] F --> G[Audit commits weekly]

The 60-Minute Agenda

This session runs 0:00 to 1:00. The agenda blocks below sum to exactly 60 minutes.

Walk through slipped commit: verbal yes in week four, security appeared week eight. Manager says: "Pre-flight is how we earn Commit, not how we decorate it."

Facilitator script: Legal states average security duration this quarter—write it on the board.

CRM setup (first two minutes): Open top commit opps; create Pre-Flight note stub on each.

Close this block: Agree: Unknown = not Commit until dated task exists.

Timer and room mechanics (Frame — Late Legal Surprises): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Build the Ten-Item Checklist (0:08–0:20, 12 minutes)

Legal and RevOps finalize yes/no/unknown items. Define evidence required for Yes (ticket ID, signed DPA, etc.).

Facilitator script: Reps ask clarifying questions—capture edge cases in footnotes on worksheet.

Live demo in CRM: Publish checklist link in CRM sidebar or sales wiki; pin in Slack.

Manager checkpoint: Align forecast stage definition with pre-flight complete.

Timer and room mechanics (Build the Ten-Item Checklist): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Apply to Live Commits (0:20–0:36, 16 minutes)

Each rep completes checklist for three commits. Manager and legal circulate—any Unknown without owner/date gets immediate downgrade discussion.

Facilitator script: Manager says: "Show me the task in CRM for every Unknown."

CRM action (required before timer ends): Create tasks for each Unknown with legal or buyer owner; set due dates.

Circulate and challenge: Legal flags deals that need buyer-side security contact this week.

Timer and room mechanics (Apply to Live Commits): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Practice inviting legal to a short buyer call: champion present, agenda tight, no redline negotiation on the call.

Facilitator script: Interrupt if rep apologizes for legal—coach confidence framing.

Pair exercise rules: Buyer played by manager or legal; objections must be realistic.

CRM action after swap: Log scheduled legal intro as activity on opportunity.

Timer and room mechanics (Role-Play Early Legal Intro): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Forecast Hygiene Rule (0:49–0:56, 7 minutes)

Team adopts written rule: no Commit without completed pre-flight. RevOps describes audit cadence.

Facilitator script: Manager names first weekly audit date.

Capture on whiteboard: Document downgrade triggers.

Each rep commits: Each rep states one deal they downgraded today and why.

Timer and room mechanics (Forecast Hygiene Rule): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Close — Audit Promise (0:56–1:00, 4 minutes)

Legal/RevOps confirms support SLA for Unknown clearance.

Facilitator script: Thank legal for attending—reinforce partnership not police.

Forecast / pipeline tie-in: Pipeline review sorts Commit opps by pre-flight status first.

Manager records in CRM or tracker: RevOps saves report: Commit opps missing pre-flight note.

Timer and room mechanics (Close — Audit Promise): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Agenda check: 8 + 12 + 16 + 13 + 7 + 4 = 60 minutes.**

Worksheet / Artifact

Pre-Flight ItemY / N / UnknownOwnerTarget DateNotes
MSA path (new vs. existing)_____________________
Security questionnaire status_____________________
Data residency / DPA_____________________
Insurance / vendor onboarding_____________________
Payment terms within policy_____________________
Signature authority confirmed_____________________
Procurement / PO process known_____________________
Forecast category after pre-flight______

How to Use This With the Buyer

  1. Invite legal early as a service: "Twenty minutes to align on paper path" reduces buyer anxiety.
  2. Share checklist transparency with champion—shows you have closed similar deals.
  3. Use unknowns to co-build timeline with buyer procurement, not to hide internally.
  4. Reset close date when security queue length is buyer-confirmed, not rep-assumed.

Manager Coaching Notes

The Bottom Line

Verbal yes is not commit-ready. Reps who run pre-flight before forecast calls surface landmines while buyers still care—and managers who enforce green pre-flight stop week-twelve collapses from invisible legal queues.

Download:
Was this helpful?  
Sources cited
Pulse RevOps sales training methodologyPulse RevOps sales training methodology
⌬ Apply this in PULSE
Pillar · Deal Desk ArchitectureFrom founder override to scaled governance
Deep dive · related in the library
sales-training · concession-ledger-trainingThe Concession Ledger — 60-Min Trainingsales-training · 60-min-meetingThe Split Documentation Standup — 60-Min Trainingsales-training · 60-min-meetingThe Territory Signal Stack — 60-Min Trainingsales-training · 60-min-meetingThe Win-Loss Sprint — 60-Min Trainingsales-training · 60-min-meetingThe Executive Access Workshop — 60-Min Trainingsales-training · 60-min-meetingThe Three-Touch Outbound Sprint — 60-Min Trainingsales-training · 60-min-meetingThe Renewal Rescue Standup — 60-Min Trainingsales-training · 60-min-meetingThe Discovery Debrief Ritual — 60-Min Trainingsales-training · 60-min-meetingThe Mutual Action Plan Co-Build — 60-Min Trainingsales-training · 60-min-meetingThe Incumbent Displacement Map — 60-Min Training
More from the library
revops · revops-500What CRM fields prove you fixed UTM loss across subdomains after migrating to Zoho CRM for pod-based selling (batch 1 #394)?revops · economy-modeHow do you run win-loss interviews into structured CRM fields without a dedicated analyst?revops · economy-modeHow do you calculate true pipeline coverage when usage-based deals have variable ACV?revops · revops-500How do you reconcile multi-thread gaps when no dedicated RevOps hire yet and leadership only reviews bookings vs billings monthly on Dynamics 365 (batch 1 #455)?revops · economy-modeHow do you enforce mutual action plan completion before legal review in enterprise deals?revops · revops-500Why do most vendors get expansion white space wrong for outbound SDR RevOps teams using HubSpot (batch 1 #488)?revops · revops-500What CRM fields prove you fixed procurement black holes after migrating to Zoho CRM for AE-led (batch 1 #489)?revops · revops-500Why do most vendors get territory collisions wrong for PLG-to-sales handoff RevOps teams using HubSpot (batch 1 #413)?revops · revops-500How do you measure pipeline coverage for land-and-expand on Pipedrive without another point solution (batch 1 #467)?revops · revops-500How do you attribute stage conversion for marketplace listings on Pipedrive without another point solution (batch 1 #432)?revops · revops-500How do you automate broken lead routing when no dedicated RevOps hire yet and leadership only reviews CAC payback monthly on Dynamics 365 (batch 1 #410)?revops · economy-modeHow do you prevent SDRs from creating duplicate accounts during territory splits?revops · economy-modeHow do you redesign territory assignments mid-year without reassigning closed-won accounts?