Run a bid kick-off that leaves nothing unowned

A bid kick-off meeting has done its job when every question or section of the response leaves the room with a named owner, a different named reviewer and a date, on a bid the team has just confirmed it can deliver. That fits into one meeting only if you've mapped the tender pack before anyone sits down and you open on the bid/no-bid decision rather than on drafting. The work runs in five stages, in this order: map the pack, confirm the decision, allocate owners and reviewers, build the timeline back from submission, and send the plan round. Together, they mark the point in bid management where a tender pack becomes a set of dates people are held to.

Who runs it and what you need before starting

The bid manager chairs the kick-off because they own the resulting plan and are accountable for the response's quality, compliance, and deliverability. BSI's PAS 360:2023, the code of practice for bid and proposal management, covers roles and responsibilities as part of good working practice. The kick-off is where those roles turn into names against questions.

Who is in the room

Invite everyone who will hold a line in the plan: the bid writers, the subject matter experts whose input the questions need, the reviewers, and anyone who holds a sign-off gate in your governance process, such as commercial for price or legal for contract terms. If a subject matter expert can't attend, still name them in the room, and have someone who can speak to their availability attend. Keep it to people who will own, review or approve something. Observers make a working meeting longer without adding a single owner.

Inputs to have ready

• The full tender pack, every file, not the notice or a summary.
• The bid/no-bid record so far, with the reasons behind the provisional decision.
• The availability of each named person across the response window, including leave and live delivery work.
• The map of the pack described in the next section, which is the meeting's working document.

The agenda in order

A proposal kick-off meeting agenda follows the order of the work itself, and that order is also the answer to what should be included in a kick-off meeting:

1. Confirm the bid/no-bid decision against the full pack.
2. Walk through the map: requirements, dependencies, submission instructions and award criteria.
3. Allocate an owner, a reviewer and, where needed, an approver to each question or section.
4. Agree the timeline worked back from submission, with its gates.
5. Agree the clarification questions to raise, who drafts each and when it goes.
6. Confirm what goes round afterwards and the date of the next checkpoint.

Make the decision first, so you don't spend anything on a bid you might withdraw.

Map the tender pack before anyone meets

Read every file in the pack yourself before the meeting and turn it into one map, so the meeting spends its time assigning work rather than discovering it.

Requirements and their dependencies

List every requirement, question and evaluation criterion, marked pass/fail or scored, with its weighting. Then mark which ones depend on another. For example, a mobilisation plan can't be written until the staffing model is settled, and the staffing model may rest on pricing assumptions commercial hasn't made yet. Those chains decide the order in which questions get drafted and which owners need to talk to each other in the first week. They belong on the map, not in someone's head.

The map feeds your compliance matrix. It doesn't replace it, but it gives the matrix a structure the whole team has seen before drafting starts.

Submission instructions across files

Pull every submission instruction into a single list on the map, with the file each one comes from.

Finding them now means each one gets an owner in the meeting, rather than surfacing in the last days before upload.

In SEQUESTO: James, the orchestrating agent in SEQUESTO aOS, reads the pack and flags which requirements depend on one another, while Agent Force extracts the questions, evaluation criteria, mandatory attachments and word limits. You confirm that extracted structure before the meeting, and it becomes the map you bring into the room.

Confirm the bid/no-bid decision first

Open the meeting by rechecking the bid/no-bid decision against what the full pack has added, before anyone talks about content. The provisional decision may have been taken on less than the full pack: a notice, a summary, an account manager's read of the opportunity.

The full pack is where mandatory requirements surface, along with thresholds such as turnover, insurance levels and certifications, accreditations you don't hold, and what delivery would actually demand of your people. Check each against two budgets: the capacity to deliver the contract if you win, and the capacity to staff this bid alongside the others already running. PAS 360 describes its governance as reducing the risk that a contract is undeliverable in practice or needs more resources than budgeted. The kick-off is the last cheap point to apply that test, before the team starts writing.

When the pack reopens the decision, such as a required accreditation you lack, settle in the room what kind of gap it is. It may be one you can close before submission, one a clarification question to the buyer could resolve, or one that ends the bid. Name who acts on it, and record the reasoning either way.

If the decision is still open at the end of that item, the meeting either decides it or stops. Allocating questions on a bid you may withdraw spends the very capacity the decision was meant to protect. When it can't be settled in the room, take it back through the full method in making go/no-go calls you can defend.

Give every question an owner and a reviewer

Give each question or section one named owner who writes it, a different named reviewer who checks it, and an approver for anything that commits the organisation. Harvard Business Review's editors give the general version of this for any meeting: assign an owner to every action item and clarify next steps before the meeting ends. On a bid, the action items are scored questions, so a shared or unnamed owner means a question nobody drafts until someone notices the gap.

The reviewer is a separate role because the owner can't see their own assumptions. A reviewer reads the answer against the question and its award criteria and catches what the writer took as read. In a small team where the obvious reviewer is the owner, pair writers so each reviews the other's questions, or assign the review to a subject matter expert or the bid manager who didn't write the answer.

The allocation table

Build the table in the meeting, on screen, so every name goes in with its owner present. Its columns:

• question or section reference, from the map
• pass/fail or weighting
• owner
• reviewer
• approver, where the answer commits the organisation
• dependencies on other questions
• starting point: an approved answer to tailor, or new content
• draft due date
• review due date

Let the weighting decide where your strongest writers and earliest dates go. A heavily weighted scored question needs the owner with the most relevant experience and an early first draft. A pass/fail question needs an owner who meets the requirement exactly and a reviewer who checks it against the instructions. For getting usable content out of the experts the table names, see working with subject matter experts on tenders.

Routing what the response commits to

The bid manager carries the legal accountability for every response, so anything the response promises needs a route to the person who can approve it. Mark those rows in the meeting: prices, service levels, contract terms, delivery dates, data protection and security statements, staffing commitments. Each gets an approver from the function that will be held to it, whether commercial, legal, compliance or delivery. Routed now, the approver knows what's coming and when, instead of meeting a binding commitment for the first time at final sign-off.

Build the timeline back from the submission deadline

Start from the time the response has to be in the buyer's portal and work backwards, placing each internal gate with a named reviewer before you set any drafting date. Planned forwards from today, a timeline fills with drafting and squeezes review and sign-off into the last days. Planned backwards, the gates get their time first, and drafting gets what's left. BSI lists timeliness beside consistency, rigour and quality among the aims of PAS 360, and the backward plan is where timeliness is decided.

The gates in reverse order

Work back through these in order, giving each a named reviewer and a date:

1. Portal upload, with an internal deadline set ahead of the buyer's so a portal or file problem doesn't decide the bid.
2. Final sign-off by the bid manager.
3. Pricing check and commercial approval.
4. Approval of the commitments routed in the allocation table, by legal, compliance or delivery.
5. Final compliance check against the submission instructions list: attachments, word limits, formats, naming.
6. Review gates, including any colour-team reviews your process runs.
7. Draft due dates per question, in the order the dependencies are set.
8. Subject matter expert input dates.

Take the duration of each gate from your last comparable bid, not from a rule of thumb. If the dates don't fit, the conflict shows up now, while scope, staffing and the decision itself can still change.

Where the clarification cut-off sits

The buyer's documents set a deadline for clarification questions, and it goes into the timeline as a fixed date like any gate. Questions raised in mapping have to be drafted, approved and sent before it, so give each an owner and a send date in the meeting. Answers can arrive after drafting has started and change scope, so leave room in the review dates for the rows they could touch. For how to use the window itself, see clarification questions as strategy.

In SEQUESTO: specialist agents in Agent Force turn every dated requirement in the pack into a task list from day one, and James reads your governance process alongside the tender and adds sign-off and review gates as milestones, each with time and a named reviewer allocated. Your team adjusts those dates and names in the meeting, so everyone works to the project timeline.

Send the plan around before drafting starts

Circulate a written record of the kick-off before anyone starts drafting, so everyone works to the written plan, not each person's memory of the meeting. It holds:

• the bid/no-bid decision and its reasons
• the allocation table
• the timeline, with its gates, reviewers and dates
• the clarification questions, each with its owner and send date
• the dependencies between questions
• the date and purpose of the next checkpoint

The record then becomes the baseline for change. When a clarification answer alters scope, update the record, mark what changed and send it to the owners of the affected rows. Rerun the meeting only if the answer reopens bid/no-bid.

Keeping the decision's reasons in the record matters for the same governance reason as checking them. If delivery capacity is questioned later, the team can see what it committed to and on what basis.

Bid kick-off checklist

• The team read and mapped every file in the pack before the meeting.
• Every requirement is on the map, marked pass/fail or scored, with its weighting and dependencies.
• Every submission instruction sits on one list, with the file it comes from.
• The bid/no-bid decision was rechecked against the full pack, delivery capacity and bid resource, and recorded with its reasons.
• Every question or section has one named owner and a different named reviewer.
• Every commitment the response makes has an approver from the function it belongs to.
• The timeline runs back from an internal upload deadline, and every gate has a named reviewer and a date.
• The timeline includes a clarification cut-off, with an owner and a send date for each question.
• The written record reached the whole team before drafting started.