Ask a room of managers whether their organization has strong accountability and most will say yes. Ask who owns a particular obligation and the room may go quiet. Then three people answer with three different names.
That gap between what an organization believes and what it can show is where accountability often breaks down. The problem is rarely a lack of commitment. People in human services work hard and carry significant responsibility. Accountability fails when it is assumed rather than designed.
My work in governance, accreditation and compliance has increasingly focused on building systems people can use during the work, not merely describe afterward.
Begin with one clear owner
“Shared responsibility” sounds collaborative. It can also mean that everyone believes someone else is watching.
One important obligation should have one primary owner. That person does not perform every task. The owner is responsible for knowing whether the work is progressing, whether the evidence exists and whether a problem needs to be raised.
In an operating model I developed, I separated service delivery, supervision, coordination, operational management and executive assurance. The design makes an important distinction: keeping an obligation visible is different from performing it, and reviewing a control is different from operating it.
A coordinator can keep a deadline visible without silently becoming responsible for another manager’s work. Independent review also needs a boundary: someone who operates a control cannot independently assure that same work. Smaller organizations may need another reviewer or an external check to preserve that distinction.
Give recurring obligations a calendar
Human-services obligations often have time attached to them. Where screening is a prerequisite, it must be confirmed before the relevant work or client contact begins. Credentials expire. Plans require review. Reports have deadlines. Policies, contracts and licences need scheduled attention.
When these dates live in individual memory, the organization has a hidden system that leaves when the person leaves.
I designed a compliance calendar linking recurring duties to an owner, a due date, required evidence and review. Its value lies in making the next action visible. The design routes reminders to the responsible person before the deadline and unresolved exceptions to someone with authority to act.
The system can then show leaders what needs attention without requiring them to search every file. Routine work stays with the responsible role. Leadership sees exceptions, overdue high-risk items and patterns.
Make evidence part of the work
Separate reporting becomes a burden when it repeats information already recorded elsewhere. Under pressure, staff may give priority to the work and leave a second reporting system incomplete. The design should account for that pressure.
The better approach is to let the work create its own evidence. A training platform records completion. A supervision template captures the conversation and agreed follow-up. A checklist also becomes the file record. A corrective-action log keeps the issue visible until someone verifies that the change worked.
This does not mean collecting everything. Evidence should have a purpose. It may confirm completion, preserve reasons for a decision, alert another role or support trend analysis. If no one can explain how a field will be used, it may not deserve to be collected.
A checkbox can create the appearance of closure. For higher-risk obligations, completion should depend on the required evidence and, where appropriate, review by another role.
For controls requiring evidence, I design the sequence around action, evidence, review and closure. The design keeps the item open until the required record and review are complete. That does not mean the action never happened; it means the organization has not yet verified completion. If the evidence shows the action did not resolve the problem, the response needs to change. Closing an item should mean more than moving it out of view.
Escalation should be normal
People delay raising problems when escalation feels like admitting failure. A healthier system defines the route in advance.
Some exceptions can be corrected by the owner. Some require a manager’s decision. Serious, repeated or systemic concerns may need executive or governing-body attention. The route should depend on risk, authority and urgency, with a backup when the usual recipient is unavailable. Immediate safety and external reporting duties must proceed without waiting for internal approval.
Exceptions are also data. If the same workaround appears repeatedly, the organization may have a process problem rather than a people problem.
Accountability should help people succeed
Accountability should give staff a fair basis for understanding expectations and leaders a fair basis for addressing gaps. It needs to remain usable when staff change, budgets tighten and the work becomes difficult.
A good system tells people what they own, when it is due, what evidence is required and where to go when the normal path fails. It gives leaders a view of risk without pulling every decision upward. It protects role boundaries while making handoffs visible.
Behind every obligation in human services is a person who depends on it being met. Accountability systems earn trust when they help the organization keep those promises consistently, especially on the days when good intentions are not enough.
Lorraine Mlambo
Lorraine Mlambo is a lawyer and senior executive working in Indigenous human services. As Managing Director and In-house Counsel, her work spans governance, policy implementation, accreditation and regulatory compliance. She has led policy, implementation and compliance work supporting Canadian Accreditation Council accreditation. Her writing examines practical systems for organizational accountability and reliable service delivery.
Read Lorraine’s professional profile →