How to Present an RFP Response: The Orals Deck That Wins
July 2026 · Docslide
An RFP presentation, usually called orals or the shortlist presentation, should follow the evaluation criteria in the same order the solicitation lists them, not your company's org chart. Build it from the response you already submitted so nothing on screen contradicts the filed document, keep it to one message per slide with pricing and staffing as charts, and put the substantiating detail in speaker notes where the presenter can reach it under questioning.
Most bid teams spend six weeks on the written response and one evening on the deck. Then the deck is the only part the evaluators actually experience with your team in the room. This is the practical version: what belongs in an RFP presentation, how long it should run, who should present, and how to build it from the proposal without a night of copy-paste.
What is an RFP orals presentation?
Orals are the live presentation stage that follows a written RFP response. The buyer scores the submitted proposals, shortlists two to four bidders, and invites each to present, usually with a fixed time slot and a question period. In federal and state procurement, orals are often formally scored against published criteria, and in some solicitations they carry meaningful weight in the total evaluation. In private-sector enterprise buying the format is looser but the function is identical: the panel is deciding whether the team they are about to hire is the team described in the document.
What should be in an RFP presentation?
Follow the evaluation criteria. If the solicitation scores technical approach, management approach, past performance, and price, present them in that order. A panel scoring a rubric should never have to hunt for the section they are on.
| Section | Slides | What it has to prove |
|---|---|---|
| Understanding of the requirement | 1 to 2 | You read their document, not a template. Name their constraints in their words. |
| Technical approach | 3 to 5 | How the work actually gets done, with the specific risk they are worried about addressed head on. |
| Team and past performance | 2 to 3 | The named people in the room are the people who will do the work, with comparable contracts cited. |
| Transition and schedule | 1 to 2 | Day one through day ninety, as a timeline, not a paragraph. |
| Price and value | 1 to 2 | The cost structure as a chart, matching the filed price to the dollar. |
| Why us, and questions | 1 | Two or three discriminators, then get out of the way and take questions. |
Everything else belongs in the appendix or the notes. Compliance matrices, resumes, and certifications were already submitted and scored; re-presenting them burns the clock you need for the technical approach.
How long should an RFP presentation be?
Fill roughly two thirds of the allotted slot and leave the rest for questions. If you have 60 minutes, plan for about 35 to 40 minutes of presentation and protect 20 for discussion. Panels remember the question period more than the slides, because that is where they find out whether your team knows the material or memorized it. On slide count, plan for roughly one slide per minute of talking, and cut anything that needs two minutes to explain.
Who should present at RFP orals?
The people who will do the work. Panels are alert to bait and switch, and a polished business developer presenting a program they will never touch is the oldest tell in procurement. Put the program manager or engagement lead front and center, give the technical lead the technical section, and keep the total to three or four speakers so handoffs stay clean. Rehearse the handoffs specifically, because a fumbled transition reads as a team that has not worked together.
How do you make sure the deck matches the filed response?
This is the failure mode that costs deals. Someone builds the deck from a previous pitch, a number drifts, and a panelist notices that the staffing on slide 9 does not match the staffing plan on page 47 of the proposal. Now the panel is auditing you instead of evaluating you.
The reliable fix is to generate the deck from the submitted document rather than assembling it fresh. Upload the response, a Word file, the submitted PDF, or the compliance matrix in a spreadsheet, to Docslide's RFP response deck flow. It extracts the outline from your document's structure and shows it to you before generating a single slide, so you choose which sections become slides. Then it builds the deck, rebuilds your pricing, labor mix, and schedule tables as native editable charts carrying the filed figures, and moves the substantiating detail into speaker notes cited to the source section. Every slide traces back to the response on record, so when a panelist challenges a number, the presenter has the provenance rather than a guess.
If your proposal lives in Word, the direct path is Word to PowerPoint; if you only have the submitted PDF, run it through PDF to PowerPoint instead.
How do you present price without losing the room?
Show the shape, not the spreadsheet. A cost table with 40 line items pasted onto a slide is unreadable at presentation distance and invites the panel to hunt for something to object to. Put the total and the structure on screen as a chart, labor mix, phase-by-phase spend, or cost per unit of the thing they care about, and keep the full breakdown in the appendix for the question period. If your price is not the lowest, say so on the slide and immediately give the reason. Panels respect that far more than a bidder who hopes nobody notices.
What about the compliance documents?
Certificates of insurance, bonding letters, licenses, and subcontractor agreements are usually submission requirements rather than presentation content. Do not spend orals time on them. Do make sure they are current before the presentation, because an expired certificate discovered during award is an avoidable way to lose a contract you already won. Teams bidding regularly find it worth tracking insurance certificates and expiration dates in one place rather than chasing brokers the week of an award.
Rehearsal is where the deck gets good
Run at least two full dry runs with someone playing the panel. The first one finds the slides that do not survive being spoken aloud. The second one, with hostile questions, finds the claims you cannot substantiate. Write down every question you get asked and make sure the answer lives in a speaker note or an appendix slide, because those are the questions you will actually get. A team that has rehearsed the hard questions sounds like a team that has done the work before, which is precisely what the panel is trying to determine.
Common mistakes to avoid
- Opening with 10 minutes of company history. The panel already read your qualifications; they shortlisted you on them.
- Reading the slides. If the deck can be read, it does not need presenting.
- Restating the compliance matrix. It was scored in writing.
- Bringing a slide count that cannot fit the slot, then rushing the technical section that carries the most points.
- Letting the deck and the filed response disagree on a single number.
- Skipping the transition plan. Buyers switching vendors are frequently more anxious about the first 30 days than about your methodology.
The short version
Structure the deck around the evaluation criteria, build it from the response you already submitted so nothing drifts, keep one message per slide with the detail in the notes, present price as a chart, and staff the room with the people who will do the work. Then protect a third of the slot for questions, because that is the part the panel scores hardest.
Turn your submitted proposal into an orals deck and review the extracted outline before any slide is built. Selling commercially rather than bidding? The same flow drives your sales proposal decks.
Your next deck is already written.
Docslide turns the documents you already wrote into finished, editable decks: layouts, charts from your data, and speaker notes, exported to PowerPoint and Google Slides.