How to build a tender compliance matrix (free CSV template)

Good bid teams don't rely on memory. They keep one running list of everything the tender asks for, and they don't lodge until every pass/fail line on it is done.

That list is a compliance matrix. It sounds like consultant jargon, but it's just a spreadsheet, and it's the cheapest insurance you'll ever buy against being excluded on a technicality. As the mandatory vs desirable guide explains, most exclusions come from admin, not from the quality of your answers.

What a compliance matrix is for

It does three jobs:

1. Nothing that can exclude you gets missed. Every condition, form, format rule and deadline has a row.
2. The work gets shared out. Every row has one owner, so "I thought you were doing that" doesn't happen at 1 pm on closing day.
3. You can prove you're ready. Before you lodge, you filter for anything not done. If the filter is empty, you're ready.

If the tender asks you to submit a statement of compliance or a schedule of departures, your matrix is the raw material for it. Use the buyer's form for that, though, not your internal spreadsheet.

The columns

The template has nine columns. Keep them in this order so the matrix stays readable when it's printed or shared.

The seven types

The types match what buyers have to tell you. For Commonwealth procurements at or above the threshold, request documentation must describe the conditions for participation (including documents you must submit), minimum content and format requirements, evaluation criteria and delivery dates (Commonwealth Procurement Rules, para 10.6). State and council tenders cover the same ground in their own words. A NSW council, for example, must specify the criteria it will assess tenders on and whether formal tender documents must be submitted (Local Government (General) Regulation 2021, s 170).

• Mandatory. Pass/fail. This includes conditions for participation and minimum content and format requirements, which the CPRs define in Appendix B.
• Desirable. Preferred but not pass/fail. Usually scored.
• Returnable. A document, form or schedule you must send back.
• Insurance. Each type of cover and limit you must hold.
• Certification. Certifications, accreditations, licences, clearances and registrations.
• Date. Any deadline or event: closing, questions, site inspection, registration, offer validity, contract start.
• Evaluation. Each criterion, with its weighting and any page or word limit.

One type per row. If a clause is two things, split it. "You must hold $20 million public liability cover and submit a certificate of currency with your tender" becomes an Insurance row (hold the cover) and a Returnable row (send the certificate). They often have different owners and finish at different times, and splitting them keeps your filters honest.

Building it, step by step

Work through the pack in this order. It puts the deal-breakers in the matrix first, so even a half-finished matrix is useful.

1. Set it up. Copy the template, one file per tender, named with the tender number. Freeze the header row. Add drop-down lists for Type and Status so nobody invents a new status called "nearly".
2. Pass 1: the conditions of tender. Add a row for every must, shall, mandatory and will not be considered, including the lodgement rules. On AusTender, for example, file names should be under 100 characters with no special characters, and only five files can be submitted in one lodgement session (AusTender: lodge a tender response). Rules like that belong in the matrix too.
3. Pass 2: the returnable schedules. Add one row per schedule, plus separate rows for signatures and file formats.
4. Pass 3: insurances, certifications and licences. Search every document for them, not only the conditions. They hide in the draft contract and the specification.
5. Pass 4: dates. Closing time, questions deadline, briefings and site inspections, and any registration deadline. If a Commonwealth tender requires a separate registration, the time limit must be stated in the approach to market (CPR 10.26). Add how long your offer must stay open: under the Commonwealth's standard terms, a response stays open for acceptance for 90 days after closing (Commonwealth ATM Terms, cl 4.1(b)). Then add your own internal dates: drafts due, sign-off and upload.
6. Pass 5: evaluation criteria. One row per criterion, with its weighting and limits. These rows become the outline of your response.
7. Pass 6: the specification. Only the must and shall items, plus volumes and locations. Don't paste in the whole specification.
8. Pass 7: the draft contract. Insurance clauses, security, liability, payment terms, and anything you'd list as a departure.
9. Assign owners and statuses. Then hold a short daily check: filter to Not started and Waiting on third party, and chase.
10. Log addenda as they arrive. Add new rows and put the addendum number in Section/Clause, for example "Addendum 2, item 3 (replaces cl 6.3)". Mark the rows it replaces as N/A, with the reason. Commonwealth buyers must send changes to criteria or specifications to all participating suppliers in time for them to adjust (CPR 10.13), and NSW councils must take reasonably practicable steps to tell people about amendments (s 170(4)). Check your inbox and the portal every day anyway.
11. Run the final check. Filter Type to Mandatory, Returnable, Insurance and Certification, and Status to anything except Done or N/A. You want zero rows before you upload.

If you'd rather not do passes 1 to 5 by hand, FileAI's tender pack breakdown builds this spreadsheet for A$79 per tender pack: every mandatory requirement, returnable, insurance, certification, key date and evaluation criterion, checked, with each row linked to its page. You then add owners, evidence and status.

Worked example rows

These rows come from a fictional council tender: Wattle Creek Shire Council's RFT 2026-14, Cleaning of Council Facilities. The template includes all 12.

Scroll sideways for more columns →

Look at EX-04 and EX-05. They come from the same clause but have different statuses: the cover is in place, but the certificate hasn't arrived. In a single merged row, that gap would be invisible.

The insurance and certification checklist goes through what to check on a certificate of currency before you tick the row off.

Rules that keep a matrix useful

• One requirement per row. Split compound clauses, even when it feels pedantic.
• Keep the buyer's wording. Paraphrasing is where meaning drifts. "Not less than $20 million for any one occurrence" isn't the same as "$20 million cover".
• Pick one page convention. PDF page numbers (what your viewer shows) and printed page numbers often differ. Use one, and say which in the header or a note.
• Never delete rows. Mark them N/A with a reason. Deleted rows are how you lose track of what an addendum replaced.
• Make the evidence specific. Write a file name or a section number, not "yes".
• One owner per row. A row owned by "team" is owned by nobody.
• Save a dated copy at lodgement. If questions come up during evaluation or at debrief, that copy shows what you submitted and why.

Turning the matrix into your response

The matrix isn't the bid, but it drives it.

• Returnable rows become your upload checklist, in the order and with the file names the tender asks for.
• Evaluation rows become your response outline. Spend effort in proportion to the weightings. A criterion worth 40% deserves more of your time than one worth 10%.
• Mandatory rows become your pre-lodgement check. Every one should point to evidence that's actually in the upload.
• Contract rows become your departures list, if the tender lets you lodge one.

Download the template

Download tender-compliance-matrix-template.csv. It opens in Excel, Google Sheets and Numbers. The 12 example rows have IDs starting with EX- and are marked as examples in the Notes column. Delete them before you start, then add your drop-down lists for Type and Status.

For the reading order that feeds the matrix, see how to read a tender pack in 30 minutes.

Sources

• Department of Finance, Commonwealth Procurement Rules (17 November 2025), paras 10.6, 10.13, 10.26 and Appendix B
• Department of Finance, Commonwealth Approach to Market Terms, version 10.0 (November 2025), cl 4.1
• AusTender, Lodge a tender response
• NSW Legislation, Local Government (General) Regulation 2021, Part 7 Tendering, s 170

This guide is general information, not legal or procurement advice. Always follow the conditions of the specific tender you're responding to.