How to Read Tender Documents Before You Bid

Government tender documents are not written to be read cover to cover like a report — they are legal solicitation instruments, and every section carries different consequences for your bid. New suppliers often skim straight to the statement of work, get excited about the opportunity, and start writing. Experienced bidders do the opposite: they read the entire package methodically first, because a single missed mandatory requirement or an overlooked addendum can disqualify an otherwise excellent proposal before anyone reads a word of it.

This guide walks you through the anatomy of a typical Canadian RFP or RFQ package, explains how mandatory and rated evaluation criteria work, shows you how to build a compliance matrix, covers the addenda and question periods that too many bidders ignore, and flags the warning signs that a competition may not be worth your time.

The Anatomy of an RFP or RFQ Package

Most Canadian RFP and RFQ packages follow a recognizable structure, even though every buyer formats them differently. The package usually opens with a cover page and a set of instructions to bidders: the closing date and time, the submission method, the contact for questions, and the rules of the competition. Treat this section as non-negotiable. It tells you exactly how, where, and when your bid must arrive — and bids that arrive late or through the wrong channel are almost always rejected regardless of their quality.

The statement of work (sometimes called the statement of requirements) describes what the buyer actually wants: deliverables, timelines, service levels, technical specifications, and the context of the project. Read it twice — once for the big picture and once for the details that will drive your costs. The evaluation criteria section then tells you how bids will be scored. This is arguably the most important part of the package, because it defines what a winning response looks like. If the statement of work tells you what to deliver, the evaluation criteria tell you what to emphasize.

Finally, the package includes the resulting contract terms and a set of annexes: pricing forms or tables, certification forms, security requirements, and sometimes drawings or data sets. The pricing forms deserve special care — many buyers require you to use their exact format, and altering or omitting a pricing table can render a bid non-compliant. The contract terms are the deal you are agreeing to perform if you win, which is why they get their own section later in this guide.

Mandatory vs. Rated Criteria: Why Pass/Fail Matters

Evaluation criteria in Canadian public procurement typically come in two flavours. Mandatory criteria are pass/fail: either your bid demonstrates the requirement, or it is set aside without further evaluation. There is no partial credit, and evaluators generally have no discretion to overlook a missed mandatory — public buyers are bound by the terms of their own solicitation, so explaining what you meant to include does not help you after closing. Common mandatories include signed certification forms, minimum years of relevant experience, specific licences or security clearances, and a required number of project references presented in a required format.

Rated (or point-rated) criteria are where competitions are won. Evaluators score your response against a published scale — points for the depth of your methodology, the qualifications of your proposed team, or the relevance of your past projects. When reading rated criteria, note the maximum points available for each item and any minimum thresholds a bid must reach to stay in the running. Read carefully: the rated criteria are effectively an outline of your proposal. Respond to each one explicitly, in the buyer's own vocabulary, and never make evaluators hunt for the information they are scoring.

How Evaluation Weighting Works

Most RFPs combine a technical score with a price score to select a winner, and the solicitation tells you exactly how. Some competitions weight technical merit more heavily than price; others do the reverse. Lowest-priced compliant bid is common for straightforward goods and services, while best-value formulas that blend technical points and price tend to dominate complex services. The weighting varies from solicitation to solicitation, so never assume — find the selection methodology section and write the formula down before you plan your response.

The formula changes how you should bid. Under a lowest-price selection among technically compliant bids, extra technical polish beyond the pass mark earns you nothing — sharpen your pricing instead. Under a heavily technical weighting, a modest price premium can be overcome by a stronger technical response. Price scores are often calculated relative to the lowest bid received, which means your price score depends partly on competitors you cannot see. Understanding the mechanics before you write lets you allocate your effort where the points actually are, instead of spreading it evenly across sections that are not worth equal marks.

Build a Compliance Matrix Before You Write a Word

A compliance matrix is a simple table you build during your first full read: one row for every requirement in the solicitation, with columns for the requirement text or reference number, whether it is mandatory or rated, where in your bid you will address it, who on your team owns it, and its current status. It sounds bureaucratic, and it is also the single most effective habit for avoiding disqualification. Requirements hide everywhere — in the instructions to bidders, the statement of work, the evaluation criteria, the contract clauses, and the annexes — and the matrix forces you to capture all of them in one place.

Use the matrix throughout the bid, not just at the start. It becomes your writing outline, your task assignment sheet, and your final pre-submission checklist: before you submit, walk every row and confirm the response is in the bid, in the right place, with the required evidence attached. Many teams also include a version of the matrix in their bid as a cross-reference table, making it easy for evaluators to find each requirement — a small courtesy that pays off when tired evaluators are scoring a tall stack of proposals against the same list of criteria.

Addenda and the Question Period

Tender documents change after publication. Buyers issue addenda (also called amendments) to answer bidder questions, correct errors, extend deadlines, and revise requirements — and each addendum becomes part of the solicitation. You must monitor for addenda until closing, because an addendum can quietly change a mandatory requirement, a pricing form, or the closing date itself. Many solicitations also require you to formally acknowledge every addendum in your bid, and failing to acknowledge one can make your bid non-compliant even when nothing substantive changed.

The question-and-answer period is your only sanctioned channel to the buyer, so use it strategically. Ask early — buyers need time to respond, and the cut-off date for questions usually arrives well before closing. Ask about genuine ambiguities, conflicting requirements, or restrictive specifications, and frame your questions neutrally so they invite a useful answer. Remember that questions and answers are normally shared with all bidders, so avoid revealing your solution or your pricing approach in the question itself. A well-crafted question can loosen an overly narrow requirement and open up a competition you would otherwise have had to walk away from.

Read the Contract Terms Before You Decide to Bid

The resulting contract terms are part of the tender package because, in most Canadian public procurement, submitting a bid means accepting them. You generally cannot renegotiate liability caps or payment terms after you win, so the time to read the contract is before you bid. Pay particular attention to limitation of liability and indemnification clauses — what you are on the hook for if something goes wrong — along with insurance requirements, warranty obligations, and termination provisions.

Intellectual property clauses matter more than many bidders expect: some contracts vest ownership of everything created under the contract in the buyer, which is a serious issue if your business model depends on reusable tools, software, or methodologies. Payment terms deserve equal scrutiny, because invoicing milestones, holdbacks, and payment timelines determine your cash flow for the life of the contract. If a clause is genuinely unworkable for your business, raise it during the question period; if the buyer will not budge and the risk is intolerable, a deliberate no-bid is the professional answer.

Red Flags: How to Spot a Wired Bid

Occasionally you will read a solicitation and get the uneasy feeling it was written with a specific vendor in mind. Classic signs of a wired or pre-directed bid include requirements so specific they read like one product's brochure, mandatory experience criteria that only an incumbent could satisfy — such as prior experience with the buyer's exact internal systems — an unreasonably short bidding window for the complexity of the work, and evaluation criteria that reward attributes with no obvious connection to the actual requirement.

None of these signs is proof of bias on its own. Sometimes a short timeline is just poor planning, and sometimes a narrow specification reflects a genuine technical constraint. Your first response should be to use the question period: ask whether an equivalent product will be accepted, whether comparable experience can substitute for the named system, or whether the deadline can be extended. Buyers sometimes loosen requirements when asked, because they also want a defensible, competitive process.

If the answers come back rigid and the field still looks tilted, a deliberate no-bid is often the right business decision — bidding costs real money, and chasing a competition you cannot realistically win drains resources from ones you can. In federal procurement, suppliers who believe a process was genuinely unfair also have formal recourse: the Office of the Procurement Ombud reviews complaints involving smaller federal contracts and promotes fairness in procurement, and the Canadian International Trade Tribunal hears federal procurement complaints under strict filing deadlines that are measured in days, not weeks. Keep notes and copies of the solicitation documents if you think you may need them.

A Disciplined First-Pass Reading Order

Here is a disciplined first-pass order that experienced bidders use. First, the instructions to bidders: closing date, submission method, and question deadline — put them in your calendar immediately. Second, the mandatory criteria: if you cannot meet even one of them, stop reading and save yourself days of wasted effort. Third, the evaluation criteria and selection formula, so you know how the game is scored. Fourth, the statement of work, read against your actual capabilities and current capacity. Fifth, the contract terms, hunting for deal-breakers. Sixth, the annexes and pricing forms, which reveal the real shape and scale of the work.

Only after that first pass should you make the bid/no-bid decision — and only after a firm decision to bid should anyone start writing. Then read the package again, slowly, building your compliance matrix as you go. Two structured readings before writing feels slow, but it is far faster than discovering a fatal requirement three days before closing, and far cheaper than submitting a bid that gets rejected on a technicality you could have caught on page four.