By Toddrick Bowens · 2026-10-12
When I look at a small recovery program, I see a clinical service surrounded by a lot of other work. Someone has to answer inquiries. Someone tracks approvals. Someone follows up on a missing document. Someone remembers the application that has been waiting for a reply.
In a small organization, those responsibilities can all land with the owner. The eight-desk framework is my way of making that work visible. It gives each kind of task a place, a responsible person, and a boundary.
Follow the work through the program
Intake and admissions is the first desk. It covers how an inquiry becomes an organized next step. Authorizations and approvals is the next: dates, packets, missing information and evidence of filing. A clinician keeps assessment and level-of-care decisions.
Documentation and compliance deals with requirements and the evidence behind them. Billing and money deals with exceptions that need to be resolved before or after billing. These desks are connected, but a flag in a system is not a clinical judgment and it is not a promise that a claim will be paid.
Credentialing and staff covers application work, credentials and renewals. Marketing and referrals covers the public website, approved content and the relationships that need follow-up. Both need someone to do the work after the draft exists.
Programming and curriculum organizes materials for the people qualified to approve and deliver them. The owner’s office brings the operation together: priorities, meeting notes, policy work and a report that makes decisions easier to see.
Give the system a bounded job
A system can organize facts, draft a packet, check supported requirements and remind someone that an item needs attention. The job needs a defined input and a way to show when evidence is missing.
I do not want a confident answer where the source is absent. I want a visible gap. That tells the operator what needs to happen next and keeps a reviewer from mistaking a polished draft for a complete record.
The current operating framework is built in part. A demonstrable compliance core exists on synthetic data. Other workflows need to be scoped and built for the organization using them. An operating diagram does not make all its boxes live.
Put a person behind the queue
My role is the follow-through: work the list, ask for the missing item, explain the exception and keep the owner informed. A reminder does not make a phone call. A draft does not establish an agreement. A prepared packet does not file itself.
Your people retain the responsibilities that belong to them. Clinicians sign notes and make clinical decisions. Owners adopt policies and sign filings. The authorized person presses Send. That division needs to be clear before a workflow is put into use.
Start with what the audit finds
I would not ask a program to rebuild every desk at once. The audit identifies the first useful scope and the conditions it needs. Sensitive records require the appropriate agreements and controls before they enter an AI tool.
The framework is a map for that conversation. It helps a program owner see what is already supported, what still needs building, and where a person remains responsible. The purpose is to give the work a structure your team can actually use.