Chapter 1
Understand the route
Map direct awards, quotations, open competitions, frameworks and dynamic markets.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Identify the routes your target buyers actually use. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 2
Qualify ruthlessly
Test strategic fit, eligibility, evidence, capacity, competition and commercial risk.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Use a written bid/no-bid decision before drafting. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 3
Prove the organisation
Connect every material claim to current, attributable evidence.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Create an evidence index with owners and review dates. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 4
Read the documents as a system
Link specification, questions, evaluation, terms, pricing and mobilisation.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Build a compliance matrix before writing answers. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 5
Write for evaluation
Answer the exact question with method, ownership, evidence, risk and benefit.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Score a draft against the published criterion, not personal preference. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.
Chapter 6
Prepare to deliver
Handover promises, dependencies and reporting into mobilisation.
Why this matters
A strong result begins with an explicit decision and a proportionate evidence boundary. Record what is known, what is reported by another party, what is inferred and what remains untested. This prevents enthusiasm, seniority or polished presentation from being mistaken for operating proof.
Do the work
Turn every scored commitment into an owned delivery action. Name the owner, affected people, dependencies, risk and review date. Where another organisation or person is involved, confirm their role, permission and expectations rather than assuming agreement.
Review questions
- What decision will this evidence support?
- Whose experience, data or opinion is it?
- What could make the conclusion inaccurate or unsafe?
- What is the smallest useful next test?
- Who can challenge or approve the result?
Practical checkpoint
Do not move on because a document exists. Sample a real record, observe the process where possible and ask whether a capable third party could reproduce the reasoning. Record a proceed, change, pause or stop decision and the evidence behind it.