A support-letter requirement can look entirely reasonable from inside an institution. It asks a professional to confirm that a person needs the service. The requirement feels familiar, cautious and easy to defend.
From the other side of the process, the same line on the form may mean finding a professional who knows the applicant well enough, securing an appointment, explaining a painful situation again and waiting while the need continues. Some applicants will complete those steps. Others will disappear from the pathway, and the file will record only that their application was incomplete.
I have worked on removing a support-letter requirement that no longer justified the barrier it created. The useful part of that work was not simply deleting a line. It was identifying the decision the letter was supposed to support, examining whether the information could be obtained more directly and preserving the safeguards that still mattered. That is the kind of administrative review access systems need more often.
Documentation serves legitimate purposes. It helps confirm eligibility, protect public funds, support consistent decisions and create a record for review. In services involving children, youth and vulnerable adults, careful documentation can be an essential safeguard. The question is not whether evidence is necessary. It is whether the evidence required is connected to the decision, proportionate to the risk and reasonably obtainable.
Systems rarely create barriers through one dramatic rule. They create them through accumulation. An application requires identification, a referral, a support letter, proof of residence and confirmation from another program. Each requirement may have an explanation. Together, they can make access depend on time, transportation, literacy, professional connections and the ability to repeat one’s story to several institutions.
The people most in need of support may be least able to assemble a perfect file. That should be treated as information about the process, rather than proof that the need is absent.
This problem is sometimes framed as a conflict between access and accountability. That is too simple. Poorly designed documentation can weaken accountability as well. It directs staff toward collecting material that does not improve the decision, creates inconsistent workarounds and hides the true reason people abandon an application.
A better approach starts by identifying the decision each document supports.
If the decision is whether a person meets an age requirement, reliable proof of age is relevant. If the decision concerns the urgency or type of support, a lengthy professional letter may add little beyond information the person and service provider can supply directly. If a third-party confirmation is required mainly because “we have always asked for it,” the requirement needs a fresh rationale.
Evidence should also be calibrated to risk. A decision involving significant legal consequences or safety concerns may require strong verification. A low-risk, reversible service decision may justify a simpler process, with later review if circumstances change. Treating every decision as though it carries the highest risk creates delay without necessarily producing better judgment.
Organizations should examine who can obtain the required evidence. A rule may appear neutral and still have unequal effects. People in rural or remote communities may not have prompt access to the designated professional. A young adult leaving care may not possess conventional proof of residence. A person whose trust in institutions has been damaged may reasonably hesitate to approach another authority for validation.
In Indigenous services, documentation requirements can also carry the weight of a long history in which institutions demanded proof, controlled recognition and made decisions about Indigenous families without them. As a non-Indigenous lawyer, I do not speak for Indigenous people or communities. I do believe governments, funders and service organizations have a responsibility to examine their own rules with humility and to ensure accountability processes do not reproduce unnecessary control.
Five practical tests can improve documentation design, although they do not need to become another form.
The purpose test: What exact decision does this document support? If the answer is vague, the requirement may be serving habit rather than accountability.
The necessity test: Is the information available from a simpler source? Could a declaration, direct conversation or existing record provide reliable evidence?
The proportionality test: Does the burden match the risk and consequence of the decision?
The access test: Who is likely to have difficulty obtaining this document, and what alternative path is available?
The review test: How will the organization know whether the requirement is causing delay, exclusion or repeated exceptions?
These tests should be applied across the whole pathway, not one form at a time. Five individually reasonable requirements can create an unreasonable process. A journey review follows the applicant from first contact through decision, service and renewal. It counts handoffs, repeated questions, approvals and dependencies on outside institutions.
Data can help. Organizations should track incomplete applications, processing time, requests for additional information and the point at which people leave the process. They should also ask applicants and front-line staff where the process becomes difficult. A spreadsheet can show that files are incomplete. A conversation may show why.
Staff need discretion for unusual circumstances, but discretion must be governed. The organization should identify who may accept alternative evidence, what factors guide the decision and how it is recorded. Otherwise, flexibility may depend on which staff member happens to receive the file.
Privacy is another reason to reduce unnecessary collection. Every additional document contains information that must be stored, protected, retained and eventually destroyed. Collecting information because it might someday be useful creates its own legal and operational risk.
Funders and regulators should participate in this review. Service providers often collect information because a contract or reporting template requires it. If a provider cannot explain the value of a document but cannot remove it, the barrier may sit higher in the system. Accountability should include a route for challenging obsolete requirements.
Evidence remains necessary. So do trust, professional judgment and proportionate verification. The work is to decide deliberately which one the situation requires.
Before asking for another document, an institution should be able to say what it will learn, why that knowledge matters and whether a fairer source is available. When the answer is unclear, the requirement deserves review. A process should not become more defensible on paper by becoming less reachable in practice.
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 →