An ABA practice procedure explains how an authorized role performs a defined task safely and consistently. It includes purpose, scope, prerequisites, authority, safety and access conditions, ordered actions, decisions, exceptions, required records, escalation, completion evidence, references, version, training, and review. A procedure should fit the real workflow and tools. It cannot expand a person's clinical, legal, payer, or employment authority.

Define the procedure boundary and audience

Cora writes for the person doing the work at the moment of need. She separates mandatory requirements, practice choices, qualified judgments, and examples so staff know which parts can vary. The role-specific operating procedure has a named owner, purpose, audience, scope, sources, qualified decision boundaries, version, effective date, evidence, feedback route, change trigger, and retirement state.

Record usable steps, evidence, and stop rules

Cora records procedure ID and title, audience and role, purpose, trigger and scope, exclusions, prerequisites, authority and source, needed access and tools, safety and accessibility conditions, defined terms, ordered step, decision point and owner, expected evidence, exception and stop rule, escalation and contact, system and record, privacy limit, completion and quality check, linked checklist or job aid, owner and approver, version and effective date, training, superseded procedure, feedback route, and review trigger.

Keep instructions within each role's authority

Cora uses direct language and observable actions. A step says which role does what, in which system, with which source, and what proves completion. Clinical decisions link to the qualified clinician instead of being converted into a script for administrative staff. Staff can pause when required information, access, safety, or authority is missing. Exceptions name the approved route rather than telling people to use judgment without boundaries. The procedure includes enough context to prevent mechanical compliance with a clearly wrong or unsafe result.

Validate the procedure with realistic performance

Cora runs the draft with representative users, including a new user, an experienced user, a person using accessibility supports, and the roles that receive the output. They perform realistic fictional cases without coaching from the author. Observers record unclear wording, missing prerequisites, wrong assumptions, excess steps, inaccessible formats, and unsafe interpretations. Cora revises only the affected section and repeats the failed case. Production review then samples ordinary work and exceptions to confirm the procedure remains usable after system or source changes.

Publish, support, and revise the procedure

Cora formats the released procedure around the moment of action. Prerequisites appear before numbered steps, decision owners sit beside the decision, and stop conditions are visually distinct. Each system instruction names the field or record instead of relying on a screenshot that will age quickly. A short change summary tells experienced staff what moved, while new staff receive the full version. Feedback links retain the procedure ID and step number. Cora reviews repeated questions and deviations to decide whether the wording, tool, workload, training, or underlying process needs repair.

Keep the artifact family connected

Cora links the process map, state specification, procedure, checklist, job aid, runbook, training, competency record, authorization, system access, and observed-work evidence that apply. One source or workflow change identifies every dependent artifact. Owners update only affected content, preserve earlier versions for historical work, communicate the change, and remove obsolete copies from every known distribution point.

Protect client access, staff voice, and qualified authority

Cora keeps AAC, interpreters, accessible formats, accommodations, privacy, safety, and an effective reporting route within the operating design. Clients and workers can identify barriers and harmful effects. Clinical, payer, employment, privacy, security, safety, and legal decisions stay attributable to qualified roles. A procedure or checklist never delays urgent action through the authorized emergency or reporting route.

Work through Cora's fictional example

Cora reviews 18 procedures. Thirteen support correct performance with current sources, steps, decisions, exceptions, records, and completion evidence. One uses an obsolete screen, one assigns a clinical decision to operations, one lacks an accessible format, one has no stop rule, and one cannot be completed as written. Four repair. One withdraws. The scenario is synthetic. It tests source, role, version, use, evidence, and denominator logic without establishing clinical quality, legal compliance, payer approval, competence, safe performance, client satisfaction, or outcome.

Calculate the example measures

Initial procedure usability is 13 of 18, or 72.2%. Seventeen validate, or 94.4%. Procedures, users, steps, decisions, test cases, errors, and revisions retain separate counts.

Watch for steps that cannot be followed as written

Long procedures can bury the decision that matters. Cora keeps the procedure complete and moves narrow point-of-work prompts into governed job aids or checklists.

Test routine, exception, urgent, and inaccessible paths

Cora tests new user, experienced user, routine path, missing access, clinical question, inaccessible format, system change, exception, urgent stop, downtime, correction, and retirement. Each case states the source, qualified owner, user, access and safety conditions, expected evidence, exception, immediate safeguard, correction, validation, and next review.

Close review with unresolved work visible

Cora confirms source currency, qualified authority, scope, version, distribution, access, training, authorization, actual use, exceptions, feedback, validation, obsolete-copy removal, and open work. The procedure remains draft until every named reviewer completes the required review.

Place procedures within organizational guidance

Cora uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. CASP sells the detailed guidance. The public page does not prescribe this procedure, validate adoption, or grant decision authority.

Treat compliance guidance as a control framework

Cora treats the OIG General Compliance Program Guidance as voluntary and nonbinding. Its discussions of policies, training, reporting, audits, corrective action, incentives, and oversight help test process controls. Current law, payer, professional, workforce, privacy, safety, contract, and legal sources control actual requirements.

Keep general business guidance in scope

Cora uses the SBA Manage Your Business guide only as broad orientation across employees, finances, compliance, emergencies, and closure. It gives no ABA clinical, payer, privacy, safety, facility, tax, or legal authority. Each process artifact cites its actual current sources and qualified owners.

Preserve professional accountability

Cora applies the current BACB Ethics Code to covered people and professional activities. It addresses competence, responsibility, client involvement, documentation, supervision, risk, evaluation, billing, and reporting. BACB has no separate corporate jurisdiction. An artifact can route clinical judgment but cannot assign it to an unqualified role.

Include management leadership and worker participation

Cora uses OSHA's management leadership and worker participation pages as general safety-program guidance on resources, accountability, reporting, participation, response, and nonretaliation. Staff need accessible ways to report unsafe, unusable, or inaccurate procedures and tools. The pages do not create a universal ABA process-documentation method.

Limit PHI access and manage technology risk

Cora applies HHS minimum-necessary guidance to role-based PHI access when the standard covers the use, disclosure, or request. NIST Cybersecurity Framework concepts may support voluntary technology-risk management. Neither source mandates a particular process map, training tool, workflow platform, checklist, or authorization database.

Related resources

Sources