Tender teams often collect documents only after drafting the response. That reverses the safest sequence. First identify what must be proved, then collect and validate the evidence, then write the claim using only what the evidence supports.
Start from the evaluation criteria
Create an evidence register with one row for every mandatory or scored claim. Include the tender clause, criterion, required evidence type, owner, status, expiry where relevant and final attachment reference.
This turns the evidence pack into part of the bid-control system rather than a folder of unrelated PDFs.
Separate corporate, technical and experience evidence
Useful categories include:
- Corporate: registration, tax-related records, banking, ownership, declarations and authority.
- People: CVs, qualifications, professional registrations, licences and appointment commitments.
- Experience: reference letters, contracts, purchase orders, completion certificates and delivery records.
- Products: datasheets, manufacturer letters, certifications, warranties and technical comparisons.
- Capacity: facilities, equipment, vehicles, systems, insurance, finance or supplier commitments where requested.
- Methodology: project plans, quality processes, risk controls, mobilisation plans and reporting structures.
Use references that prove the criterion
A reference for software development is not automatically strong evidence for national equipment distribution. Choose projects that match the criterion being scored and identify the aspect that makes them relevant: scope, sector, value, quantity, geography, technology or delivery complexity.
Where the tender prescribes a reference template, use it exactly.
Make experience attribution explicit
Record whether each project belongs to the bidding entity, a director, a proposed employee, a consortium member or a subcontractor. If a person gained the experience while working elsewhere, state that context.
This protects credibility and helps reviewers determine whether the evidence satisfies the tender's wording.
Check that documents are complete and readable
Scanned documents should include every relevant page, signature and annexure. Certificates should show the holder, scope, number and validity information where applicable. Remove duplicate and superseded versions from the final pack.
Use descriptive file names rather than “scan001.pdf”. A reviewer should understand what a file contains before opening it.
Validate third-party evidence early
Manufacturer appointments, supplier quotations, specialist CVs and partner references depend on other organisations. Request them early and verify that they identify the correct bidder, tender or offered product where required.
Do not wait until the final submission day to discover that a manufacturer letter names a different reseller or an important certificate has expired.
Reconstruct older experience carefully
Where a historical project lacks a formal reference letter, other records may help establish what occurred: purchase orders, invoices, delivery notes, contracts, acceptance records, project photographs, archived correspondence or public records. Whether those documents satisfy a tender criterion depends on the wording of that criterion.
Never convert circumstantial records into a stronger claim than they support.
Index the pack for the evaluator
For larger submissions, create a table of contents or evidence index that maps each criterion to the exact attachment and page. If the portal requires separate uploads, use consistent numbering and naming across the response and attachments.
Keep a reusable corporate evidence library
Frequently used corporate records should be maintained continuously, not rebuilt for every tender. Store document owner, issue date, expiry date, current version and permitted use. This reduces last-minute administration and prevents old certificates from reappearing in new bids.
Build the evidence pack before writing the strongest claims
A tender response becomes more defensible when the narrative is constrained by verified evidence. The question changes from “what can we say?” to “what can we prove, and how does that proof answer this criterion?”
That discipline is especially important for new businesses, multidisciplinary teams and bids that depend on several suppliers or specialists.