A municipal procurement is a legal process wearing the clothes of an administrative one. Every step has a reason, and most of the reasons only become visible when someone challenges the award. This is the sequence a Canadian municipality, school board or health authority typically runs, and what each step is actually protecting against.
1. Start with the bylaw, not the budget
Before anything else, establish which rules bind this purchase. There are usually two layers, and the stricter one governs:
- Your procurement bylaw or policy — internal thresholds for quotes, invitational competitions and formal open tenders. Typically far lower than the trade agreement figures.
- Trade agreements — the CFTA, plus CETA, the CPTPP or the WTO-GPA where applicable. For MASH-sector entities the CFTA thresholds sit at $139,000 for goods or services and $347,400 for construction for 2026–2027.
Write the determination down at the outset: which threshold applies, what the estimated total value is, and therefore what process is required. That single note answers the first question any auditor or challenger asks.
2. Scope before you draft
The most expensive errors in municipal procurement are made before a word of the solicitation is written. Settle these with the requisitioning department first:
- What outcome are you buying? Not the product someone has already picked — the result the organization needs.
- What is genuinely mandatory versus desirable? Every mandatory requirement is a disqualification trigger, so each one needs to survive the question 'would we truly reject an otherwise excellent bid over this?'
- How will you evaluate? The criteria and weights have to be settled now, because they must be published and cannot be adjusted once bids are in.
- Who evaluates? Confirm availability and conflict-of-interest declarations before you post, not after close.
A 70/30 split between technical and price produces a different winner than 50/50, and deciding it after seeing the submissions is the clearest possible bias. Lock weights before posting.
3. Draft the solicitation
A solicitation document has to carry everything a supplier needs to respond and everything an evaluator needs to score consistently. At minimum: scope of work, mandatory requirements, evaluation criteria with weights, submission format, closing date and time with time zone, the question deadline, contract terms, and required certificates and insurance.
Ambiguity in the scope becomes a flood of questions during the open period, and an unclear evaluation criterion becomes a scoring disagreement you cannot defend. Our RFP and RFQ templates cover the standard structure if you are building one from nothing.
4. Post it where you are obliged to post it
For a covered procurement, the notice goes on an electronic tendering system open to suppliers — commonly bids&tenders on your own subdomain, MERX, or a provincial portal, depending on your jurisdiction and what your bylaw specifies. The open period must be long enough to let a supplier actually assemble a response; where an international agreement applies, minimum periods may be prescribed.
Do not shorten the period to recover time lost earlier in the process. A compressed tendering period is both a fairness problem and, in practice, a bid-quality problem.
5. Run questions and addenda properly
This is where otherwise clean procurements come apart. Two rules carry most of the weight:
- Every answer goes to everyone. A clarification given to one supplier by email and nobody else is the textbook fairness breach — even when the answer itself was harmless.
- Every change is a formal addendum, numbered, dated and issued to all registered suppliers. Scope changes, deadline extensions, corrected drawings, revised criteria: all of them.
Set a question deadline several days before close so there is time to issue an addendum, and extend the closing date if a late addendum materially changes what suppliers are pricing.
6. Close and open
Submissions stay sealed until the closing time. After close, record what was received and when, and apply the late-submission rule exactly as written — consistently, every time, including for the incumbent and including when the lateness is trivially small. Discretion applied unevenly here is a challenge waiting to happen.
Then check compliance against the mandatory requirements before any scoring begins. A non-compliant bid is set aside at this stage; it is not scored and quietly ranked last.
7. Evaluate against what you published
Evaluators score independently against the published criteria first, then meet to reach a consensus score. Keep both records — the individual scores and the agreed one — along with the rationale for any score that moved materially in the discussion.
Two practices make the file defensible: keep pricing sealed from technical evaluators until technical scoring is complete, and require a written justification for scores at the extremes. See our guide to weighted scoring for how to build the matrix itself.
8. Award, notify and debrief
Award against the published criteria, notify the successful supplier, and notify the unsuccessful ones promptly. Offer debriefings and take them seriously: a supplier who understands why they lost is far less likely to file a challenge than one who suspects they were never really in it.
Post the award notice where your bylaw or the applicable agreement requires. For many entities that is the same system the tender was posted on.
9. Keep the file
Retain the complete record for the period your records retention schedule prescribes: the solicitation as issued, every addendum, the questions and answers, the submissions, the individual and consensus scores, the conflict declarations, the award decision and its rationale, and the notifications.
The purpose is not compliance theatre. It is that a challenge or an audit typically arrives long after everyone involved has moved on, and the file has to speak for itself. A system that logs each of these as it happens turns that from a reconstruction exercise into a query — which is most of what running Canadian procurement in software is actually for.
This article describes general practice and is not legal advice. Your own bylaw, provincial legislation and applicable trade agreements govern.