When the evaluation happens in a room, not a binder

More federal solicitations now ask for an oral proposal — a live presentation to the evaluation team, sometimes replacing the written technical volume entirely, sometimes sitting alongside it. The government's reasoning is sound: a slide deck and a conversation reveal whether the people who'll actually do the work understand it, in a way a ghost-written document never can. For a small shop, that's often good news — orals reward genuine expertise over proposal-department polish, which levels the field against primes who can out-write you but can't out-know you. But only if you prepare for the format that's actually being scored, and orals are a different discipline from writing.

The trap is treating an oral like a written proposal read aloud. The evaluation criteria in Section M still govern — you're scored against the same factors — but the delivery vehicle is a presentation, and the failure modes are different. You can be ruled out for running over the time limit, for presenting slides that violate the format instructions, or for a presenter who can't answer a clarifying question. The compliance discipline that governs a written bid applies just as hard here — it's just that the requirements now include a clock and a room.

Read the instructions for the format, not just the content

Oral solicitations come with instructions as specific as any Section L, and they're easy to skim past because they feel like logistics rather than requirements. They aren't — they're pass/fail. Typical rules the government sets and scores against:

  • A hard time limit — often with the microphone cut mid-sentence when it hits. Overrunning isn't rudeness, it's non-compliance, and it means the last third of your message never gets scored.
  • Slide constraints — a maximum count, no animations, no builds, sometimes a rule that slides must be submitted in advance and can't change. Prepare to a format the government dictates, not the one you'd prefer.
  • Who may present — frequently limited to proposed key personnel, specifically to prevent a slick capture lead from fronting for a team that will never touch the work. That means your actual technical people have to perform, which changes who you prepare.
  • Rules on Q&A — whether evaluators can ask questions, whether you can caucus before answering, whether note-taking is allowed. These shape your entire rehearsal plan.

Extract every one of these into the same requirements shred you'd build for a written bid. An oral has a compliance matrix too; it just includes "finish in 30 minutes" as a line item.

Prepare the team, because the team is what's scored

In a written proposal you can hide a weak contributor behind strong editing. In an oral, the person presenting a factor is the score for that factor. So preparation is about people, not just slides. The technical lead who'll present the approach has to know it cold, anticipate the evaluator's likely questions, and stay inside the message you storyboarded — which makes an oral the ultimate test of whether your win themes are real or just words on a page.

The single highest-value activity is the rehearsal against hostile questions. You sit your presenters in front of colleagues playing skeptical evaluators, run the deck against the clock, and drill the Q&A until answers are crisp and consistent. This is the color-team review of the oral world — an outside party scoring the presentation the way the government will, so weaknesses surface in the practice room instead of the real one. A team that has been grilled twice walks into the actual evaluation calm; a team seeing its own questions for the first time in the room does not.

Track the prep like the multi-owner effort it is

An oral is a pursuit with a lot of moving parts on a fixed date: slides to build and submit, presenters to assign and rehearse, questions to anticipate, a dry run to schedule, logistics to confirm. Miss any one and the polished content doesn't matter. That's exactly the kind of multi-owner, deadline-bound work a CRM keeps from slipping. In Hitt CRM, every prep item — build the deck, submit slides by the deadline, run rehearsal one, confirm the room — becomes an assignable task hanging off the same pursuit record where your capture history and Pwin already live, so nothing depends on one person's memory. Automations fire the reminders against the presentation date, and after the decision — win or lose — the debrief notes land on the same record, so what you learn about presenting to this customer sharpens the next oral instead of evaporating.

The one-sentence version

An oral proposal is scored against the same evaluation factors as a written one but delivered as a live, time-boxed presentation by your actual key personnel — so you shred the format instructions as strictly as any Section L, prepare the people who'll present rather than just the slides, rehearse relentlessly against hostile questions until the answers are crisp, and run the whole prep as tracked, owned, deadline-driven work on the pursuit record (the kind a CRM manages naturally) so the only thing left to chance is the room itself.