Policy language tells us what a public program hopes to achieve. The contract tells a provider what it is actually allowed and funded to do.
Governments may describe a program in language of flexibility, prevention, innovation and community leadership. The procurement documents often tell a more concrete story. They define the eligible provider, the funded activity, the required evidence, the payment schedule and the consequences of departing from the model.
Those details do more than purchase a service. In practice, they shape it.
Procurement is often treated as the stage that follows policy design. Officials determine what government wants to achieve, then procurement professionals find a compliant way to buy it. That sequence understates procurement’s power. The request for proposals and resulting agreement can preserve the policy’s purpose, narrow it or quietly replace it.
Consider a program intended to provide individualized support. The policy may emphasize responsiveness to each person’s goals. If the contract funds only pre-defined activities, requires identical service hours and measures success through volume alone, providers will be pulled toward standardization. The policy says individual. The purchasing mechanism says uniform.
The same tension appears in community-led and culturally grounded services. A government may commit to partnership and local authority while using contract terms designed for conventional vendor relationships. The agreement may place decision-making far from the community, impose short renewal cycles that undermine continuity or recognize direct-service hours while ignoring the governance, relationship-building and cultural work that make the service effective.
This is particularly important in Indigenous child and family services. Canada’s legal and policy landscape has moved toward recognition of Indigenous jurisdiction, prevention and First Nations-led reform. As a non-Indigenous lawyer working within an Indigenous-led organization, I do not presume to define what communities should build. My concern is narrower: public institutions must ensure their own purchasing systems do not obstruct the leadership they have committed to respect.
I have worked on implementation questions where the obstacle was not the stated purpose of a program. The difficulty sat in the surrounding machinery: what a procurement document recognized as an eligible activity, what evidence had to be supplied and whether the purchasing structure reflected how the service would actually operate. That experience made procurement impossible for me to treat as administrative cleanup at the end of policy design.
Several parts of procurement deserve particular scrutiny.
Definitions can freeze an old model in place. If eligible services are described too narrowly, a new approach may be excluded before its value is considered. Definitions should protect the program’s purpose and safeguards without assuming there is only one valid delivery model.
Eligibility rules can favour administrative scale over community connection. Financial capacity and governance controls matter, but requirements should be proportionate to the contract. Otherwise, smaller or community-rooted organizations may need to fit themselves into structures designed for large institutional vendors.
Evidence requirements can become access requirements. A contract may require a particular referral, letter or professional confirmation before support is funded. Each document may appear reasonable on its own. Together, they can delay service or make access depend on another system that is difficult to reach. Evidence should be linked to a clear decision and calibrated to the risk involved.
Payment design can distort delivery. Reimbursement models may require organizations to carry significant costs. Unit pricing may discourage the patient work needed in complex situations. Short agreements can make it difficult to retain staff and sustain quality systems. Funding architecture is operational policy.
Reporting can reward what is easiest to count. Number of contacts, hours and completed activities may be useful, but they do not necessarily show continuity, trust, cultural safety or progress toward a person’s own goals. If the contract values only volume, organizations will feel pressure to organize their work around volume.
None of this means procurement rules should be loose. Fairness, transparency, value and accountability are essential. The solution is to bring procurement expertise into policy design early and to bring implementation knowledge into procurement.
Before an opportunity is released, the policy and procurement teams should test the documents against the intended experience. Can the proposed provider deliver the model described in the policy while complying with the agreement? Does the payment schedule support the staffing and governance required? Are reporting measures connected to meaningful outcomes? Do approval steps protect against an identified risk, or are they inherited from another program?
Contracts need room for learning as well. New programs reveal things that could not be known at the drafting table. Agreements should include a disciplined mechanism for reviewing requirements, sharing implementation evidence and making lawful amendments. Without that mechanism, everyone may recognize a barrier and still feel bound to preserve it until the next procurement cycle.
Finally, accountability should be mutual. Providers must meet standards, use funds properly and report honestly. Public purchasers should make timely decisions, maintain coherent requirements and respond when contract design is undermining policy goals. Partnership cannot mean that only one side is expected to learn.
Procurement choices produce operational consequences. A model that rewards volume, limits discretion and funds instability will predictably pull services toward standardization and fragility. A model that supports clear outcomes, proportional safeguards, continuity and community authority gives policy a better chance of becoming real.
That is why procurement belongs at the policy table from the beginning. By the time the contract reaches a provider, many of the program’s most consequential decisions have already been made.
Lorraine Mlambo
Lorraine Mlambo is Managing Director and In-house Counsel at Nitanis Group. Her work spans organizational leadership, governance, policy implementation, compliance, accreditation and systems advocacy. She writes from the perspective of a non-Indigenous lawyer working in support of Indigenous-led human services.
Read Lorraine’s profile →