Marking rubrics put the difference between a 3 and a 4 in one word: “evidenced”. Yet most teams treat proof as a deadline-week scavenger hunt — hunting certificates, chasing referees, rebuilding the same case study from memory. This playbook builds the alternative: an evidence library — proof captured once, kept current, ready to drop into any bid.
What evaluators accept as evidence
In rough order of weight:
- Named, dated reference projects — client, period, value band, scope, measurable outcome, referee.
- Certifications and registrations — with numbers and validity dates (ISO 27001, ISO 9001, sector registrations).
- Contactable referees and reference letters — the difference between asserted and checkable.
- CVs tied to the bid — showing the named people did the comparable work.
- Audited numbers — accounts, insurance, capacity figures the buyer’s diligence will confirm.
The common thread is verifiability. Evaluators must defend marks in a moderation meeting — verifiable proof is defensible; adjectives are not. (The marking mechanics are in how evaluation works.)
The library: five shelves
| Shelf | Contains | Review cycle |
|---|---|---|
| Case studies | One-pagers per closed project | On project close |
| Certificates | Certifications, insurances, registrations | Expiry-driven |
| People | Bid-ready CVs, mapped to capabilities | Quarterly |
| Referees | Who, for what, last used, consent status | Per use |
| Standing answers | Capability statements, methodologies, policies | Quarterly |
The case-study one-pager
The library’s atomic unit. Five fields, written when the project closes, while the numbers and contacts are fresh:
- Context — client (anonymised only if the contract requires), sector, period, value band.
- Challenge — what made it hard, in one paragraph. This is what makes it comparable to the next tender’s problem.
- Delivery — what you actually did, with the method named.
- Outcome — measured, dated, specific. One real number outranks three superlatives.
- Referee — name, role, consent, last contacted.
Deploying evidence inside the response
- Beside the claim, not behind it. Appendix-only evidence is unread evidence. The claim-method-evidence pattern from the RFT playbook puts proof in the scored section itself.
- Matched to the criterion. The same project tells a technical story or a delivery story depending on what’s being marked — re-aim per bid.
- Two strong beats five thin. Evaluators under time pressure reward depth and verifiability over volume.
- In the matrix. Every “met” row of your compliance matrix names its evidence — certificate ID, case study, CV — so the final check is a read-through, not a hunt.
Where software fits
A folder system with an owner genuinely works at low volume. What changes with Palmar is that the library becomes active: your past bids and documents form an answer library that drafting pulls from automatically — the “14 comparable programmes” line in our sample draft came from the (sample) company’s own library, cited, not invented. Start by uploading your last three bids; plans from $99/mo. The deeper operating model this belongs to is Bid Ops — answers as assets is its third practice.
Frequently asked questions
What counts as past performance evidence in a tender?
Anything an evaluator can verify: named reference projects with dates, values and outcomes; client reference letters or contactable referees; certifications with registration numbers; CVs showing the relevant engagements; audited results. The test is verifiability — 'extensive experience' is a claim, 'a 2025 programme for a named hospital group, delivered on schedule, referee available' is evidence.
How do you write a case study for a bid?
One page, five fields: client and context (anonymised only if contractually required), the challenge, what you delivered, the measurable outcome, and a referee. Write it once, properly, when the project closes — then tailor the emphasis per tender. The discipline is capturing it while the numbers and contacts are fresh, not reconstructing it at midnight during a live bid.
Can you use the same case studies in every tender?
Reuse the asset, re-aim the telling. The same project can evidence technical capability in one bid and delivery-under-constraints in another — the facts stay identical, the emphasis follows the criterion being scored. What you must never reuse unedited is the framing: evaluators spot a case study that wasn't written for their question.
