SuperAPI AI Directory
Partner中文AI newsFavorites
Skillstender-orals-and-proposal-presentation

tender-orals-and-proposal-presentation

Office & productivity

View repository

Updated 10-26 04:07

About this skill

Tender Orals and Proposal Presentation

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Turn a submitted or near-final proposal into a spoken presentation that an evaluation panel or client can score with confidence: plan from the scoring criteria, storyboard one point per slide or card, rehearse against a rubric, prepare for hard questions, and control the room, the screen and the fallbacks.

Use When

  • Use when a tender invites shortlisted bidders to an oral presentation, interview, demonstration or clarification meeting.
  • Use when a private client asks for a proposal walk-through, pitch meeting or board presentation of a proposal.
  • Use when the team needs a rehearsal plan, a scoring rubric, a hard-questions pack or a room and equipment checklist.
  • Use when a presenter must be introduced, briefed or coached before a decision meeting.

Do Not Use When

  • Use proposal-storytelling-and-evaluator-journey to build the written narrative spine of the proposal itself.
  • Use saas-mutual-action-planning-and-close-plans or the SaaS demo-script reference for a SaaS product demonstration plan.
  • Route slide typography, layout, colour and deck templates to chwezi-design-engine; this skill owns content, structure, rehearsal and logistics.
  • Stop when the invitation's rules (duration, attendees, permitted materials, recording, language) are unknown; request them before designing the session.

Inputs

Artefact Source/provider Required? Missing-input behaviour
Invitation to present: date, duration, format, attendees, permitted materials, scoring criteria Procurement or client Yes Request clarification; plan a draft only, marked provisional.
Submitted proposal and power-paragraph sheet Proposal record Yes Stop; the presentation must not contradict the written offer.
Panel intelligence: names, roles, decision-maker, prior knowledge Invitation, public sources, account team Conditional Plan for a mixed technical and non-technical panel.
Venue and equipment facts Venue or organiser Conditional Assume no projector, no internet and unreliable power; prepare fallbacks.
Presenters and availability Proposal lead Yes Name substitutes; do not present staff who are not bid to the assignment.

Outputs

Artefact Consumer Acceptance condition
Presentation strategy sheet Proposal lead Objectives stated as the panel's problems; timing plan within the allotted slot including Q&A.
Storyboard and deck brief Presenters, design engine One point per slide or card, mapped to scoring criteria; consistent with the written proposal.
Hard-questions pack Presenters At least the twenty hardest questions with agreed answers and owners.
Rehearsal scores and after-action notes Proposal lead Two scored rehearsals with fixes recorded before the event.
Room, equipment and fallback checklist Logistics owner Every item confirmed or marked with a fallback.
Leave-behind (one-page summary) Panel Matches the proposal; no new commitments.

Evidence Produced

Evidence Consumer Acceptance condition
Criteria-to-slide map and consistency check against the submission Reviewer Every slide traces to a criterion and a proposal section; no new price, staff or scope.
Rehearsal rubric sheets Proposal lead Scores, reviewer names, dates and fixes are retained.
Post-event debrief Kaizen owner Questions asked, answers given, follow-ups owed and lessons recorded within one working day.

Capability Contract

Read and search access to the proposal and invitation is required. Drafting the storyboard, scripts and checklists is permitted when authorised. Contacting the procurement entity, confirming attendance, submitting materials, recording people or making new commercial commitments requires explicit human authority. Presenters must not add price, staffing or scope commitments that differ from the submitted proposal.

Degraded Mode

When venue, equipment or panel details are unavailable, fall back to a low-technology design: a printed one-page summary and handout, a talk that works without slides, a flip-chart option, and the deck saved offline on two devices. Mark unconfirmed items not assessed in the logistics checklist and name who will confirm them.

Decision Rules

Condition or choice Action Failure or risk avoided
The invitation publishes scoring criteria Order the talk by the criteria and use their wording in section titles Panel cannot find what it must score
No criteria published Order by the panel's likely decision questions: problem, approach, team, risk, value Unscored storytelling
Slot is short (under 30 minutes) Cut depth, not the Q&A; plan more material than needed and cut live Rushing and overrunning
Panel includes non-specialists Lead each technical point with its consequence for the client Losing the decision-maker
A question exposes a gap Admit it, state what you will verify and when, and follow up in writing if the rules allow Bluffing and loss of trust
Power, projector or internet is uncertain Prepare offline deck, printed handouts and a talk that stands without slides Presentation collapse
Opening protocol is expected (dignitaries, prayer, introductions by precedence) Budget time for it and keep a hard close Losing the substantive slot
Team members are not on the bid Do not field them Misrepresentation of the offered team

Workflow

  1. Read the invitation. Confirm duration, format, attendees, materials, recording and scoring; stop and request missing rules.
  2. Write the strategy sheet. Audience, slot, venue, equipment, objectives framed as the panel's problems, and the success criterion. See orals preparation and room readiness.
  3. Storyboard. Content outline, then one card per point; choose the form for each point (words, numbers, diagram, image); map each card to a criterion and a proposal section.
  4. Script the opening and close. Open with the client's situation and the governing idea in under a minute (the need lead paragraph); close with the value beyond the project and one requested next step.
  5. Build the hard-questions pack. Twenty hardest questions, answers, owners and supporting evidence. See orals rehearsal, rubric and questions.
  6. Brief the design engine for the deck and leave-behind; review the result for consistency with the proposal.
  7. Rehearse twice, scored by two colleagues with the rubric. If a run scores below 38, stop, revise the weakest section and rehearse again; time and rehearse transitions and hand-offs between presenters.
  8. Prepare the room using the checklist; arrive early; test sound, screen and sightlines from the back row.
  9. Deliver and handle questions: repeat each question, answer briefly, check it was answered, and note follow-ups.
  10. Debrief the same day. Record questions, answers, follow-ups owed and lessons; feed changes into the relevant skills. If rules permit, send promised follow-ups in writing within the agreed time.

Quality Standards

  • Every point in the talk traces to a scoring criterion and to the submitted proposal; nothing contradicts it.
  • The talk finishes within the slot and leaves the planned Q&A time.
  • Slides carry keywords, numbers and diagrams; the presenters say more than the slides.
  • Each presenter's part ends with a hand-off to the next; the team leader opens and closes.
  • Every unanswered question has an owner and a follow-up date.

Anti-Patterns

  • Reading slides aloud or filling them with paragraphs. Fix: one point per slide; speak to it; move details to the handout.
  • Apologetic openings ("Sorry, we will try not to take too much of your time"). Fix: open with the client's situation and the governing idea.
  • Talking faster to fit an overlong deck. Fix: plan more than needed and cut live to the time.
  • Fielding people who are not on the offered team. Fix: present with the named key experts only.
  • Answering a question the panel did not ask, or bluffing. Fix: restate the question, answer it briefly, and admit gaps with a follow-up commitment.
  • Relying on the venue's equipment and connection. Fix: offline deck on two devices, adapters, printed handouts and a no-slides fallback.
  • Importing old presentation "research" claims (for example fixed percentages for visual learning or left-brain/right-brain learning styles). Fix: omit them; they are unsupported.

References