One of the smallest requirements in a service pathway can cause the largest delay. A support letter may occupy a single line on a form, yet obtaining it can require another appointment, another professional relationship and another telling of a story the applicant has already explained.
A government may recognize a right, announce a new program or commit new funding. The announcement matters. So does the law behind it. Yet somewhere between that public commitment and the person it is meant to serve, a form asks for one more letter. A procurement template defines the service according to yesterday’s model. An approval process quietly recreates the barrier the reform was meant to remove.
The right still exists on paper. Access to it does not.
This is the last mile of reform: the administrative distance between a public commitment and a person’s lived experience of it. Governments tend to invest heavily in the first mile. They debate legislation, negotiate agreements, announce funding and establish broad policy direction. Those are necessary steps. But implementation is not clerical work that begins after the important decisions have been made. Implementation is where many of those decisions are made again, in smaller and less visible forms.
Canada’s work on Indigenous child and family services makes this especially clear. The federal Act respecting First Nations, Inuit and Métis children, youth and families affirms that the inherent right of self-government recognized and affirmed by section 35 of the Constitution Act, 1982 includes jurisdiction in relation to child and family services. In 2024, the Supreme Court of Canada unanimously upheld the Act as constitutionally valid. Ontario’s long-term reform agreement, implemented in 2026, centres First Nations-led services, prevention, joint governance and accountability.
Those developments matter. They also raise a practical question: do the surrounding systems make the new direction possible?
I ask that question from a limited but useful vantage point. I am not Indigenous, and I do not speak for First Nations, Inuit or Métis communities. My work has been in legal stewardship, policy implementation, accreditation and organizational compliance within an Indigenous-led human-services organization. From that position, I have seen how institutions can support Indigenous leadership. I have also seen how an ordinary requirement, including a support letter or a procurement condition, can become the point at which a sound policy stops working as intended.
The problem is rarely a single dramatic act of resistance. More often, it is accumulation. A service definition does not match the program communities are building. A referral pathway assumes a professional intermediary must validate a person’s need. A reporting requirement measures activity but misses whether the support was timely, culturally grounded or useful. A contract funds direct service but leaves no realistic room for the governance, training and quality systems needed to deliver it well.
Each requirement may have a history. Some were created to manage risk. Some were copied from another program. Some have simply outlived their original purpose. Together, however, they can turn a right into an obstacle course.
The answer is not to abandon documentation, oversight or public accountability. Public money must be governed carefully, and services affecting children, youth and families require rigorous safeguards. The better question is whether each control is connected to a real risk, proportionate to that risk and tested for its effect on access.
That calls for a different approach to implementation.
First, governments should conduct a barrier review before launching or renewing a program. This review should follow the experience of a person seeking support from beginning to end. What proof is required? Who can make a referral? How many approvals are involved? Which parts of the process depend on an institution that may not be accessible or trusted? A policy team can read a form and see neutral language. A service provider or community member may see a delay that has appeared in three previous systems under three different names.
Second, procurement should be treated as part of policy design. The request for proposals, contract, funding schedule and reporting template are not administrative attachments. They determine which organizations can participate, what work is recognized, how quickly providers can respond and which outcomes matter. If the policy promises flexibility but the contract rewards standardization, the contract will usually win.
Third, implementation tables should include the people who understand delivery. Legal counsel, finance and procurement belong there, but so do Indigenous leadership, program operators and people with direct experience of the service pathway. Consultation at the vision stage cannot compensate for exclusion at the design stage.
Fourth, accountability must look in both directions. Service organizations should be able to show that they meet clear standards and use public resources responsibly. Governments and funders should also be able to show that their own processes are timely, intelligible and aligned with the policy they claim to advance. A provider cannot implement a responsive model through a funding mechanism built for delay.
Finally, governments should create a disciplined way to remove requirements that no longer serve a legitimate purpose. Administrative rules often enter a system with a rationale and remain after the rationale is gone. Every recurring form, approval and reporting obligation should have an owner, a stated purpose and a review date. If nobody can explain what risk a requirement controls, that is a reason to examine it, not a reason to preserve it.
Implementation failures are often described as gaps, as though policy and practice simply drifted apart. Frequently, the distance is built into definitions, eligibility rules, timelines, evidence requirements and contracts. That matters because a barrier created by design can be examined and redesigned.
Rights-based reform asks more of institutions than good intentions. It asks them to examine their own machinery. The promise is made in legislation and policy, but it becomes real in the ordinary encounter: the form that can be completed, the referral that can be made, the agreement that funds the actual work and the decision that arrives while it can still help.
A reform has reached the public only when the pathway reflects the promise. Until then, the work is unfinished.

