Certification
Writing Your Policy & Procedure Manual
How to write the ~24-policy manual certification expects — the Policy/Procedure two-part pattern, what each section covers, and how to keep it a living document instead of a binder nobody opens.
Every NARR certification level requires a written policy and procedure manual, and most operators dread it because they picture a hundred pages of legalese. The real thing is simpler: for each area of house life, a short POLICY (what we commit to and why) and a PROCEDURE (the numbered steps staff actually take). Two paragraphs and a list, times roughly two dozen topics. This guide is generalized from a state affiliate's full manual template.
The two-part pattern
Every section uses the same skeleton. Policy is one paragraph of commitment: "It is the policy of this residence to maintain a safe, structured, recovery-supportive environment…" Procedure is the steps a brand-new staff member could follow tonight without asking anyone. If a section can't be executed by someone who started yesterday, it isn't a procedure yet — it's a wish.
The sections certification expects
- Identity: mission statement, vision statement, your code of ethics — plus the NARR Code of Ethics itself, which every person associated with the operation signs, and which obligates each signer to REPORT unethical conduct; your manual should say to whom.
- Information handling: confidentiality (collect only need-to-know information, store it securely, release it only with consent or as law requires) and a social media policy (residents' privacy and anonymity protected; nobody posts another resident, ever).
- The resident lifecycle: screening criteria and what happens when someone is ineligible (connect them to an alternative, don't just decline); orientation (what's covered, who signs what, within how many days); house rules WITH consequences; program format including phases and what earns advancement; discharge — administrative, unsuccessful, and successful — written to the same defensible-documentation standard as the discharge guide in this library; and recurrence of use, covering immediate safety, the documented offer of a higher level of care, and how someone is welcomed back afterward.
- Daily operations: good neighbor policy, including parking courtesy — neighbor relations fail in driveways before they fail anywhere else; contraband and searches (what's prohibited, who searches, with what witness); medication storage and use; drug and alcohol testing (who, when, how observed, what happens on refusal); maintenance requests on a standardized form; hazardous items.
- Safety and rights: emergency policy and procedures; infectious disease; a sex-offender acceptance OR denial policy — several states restrict where registrants may live, so this section must match the statute that applies in YOUR state; resident rights; and the grievance policy — fast written resolution, no retribution, escalation past the person complained about (see "Handling Resident Grievances").
- Money and work: financial obligations (rent, fees, refunds, what happens on nonpayment) and policies about paid work by residents — anything residents do FOR the operation gets extra scrutiny from affiliates.
- Recovery support: how participation in recovery plans is documented — meeting sheets, sponsorship, employment, volunteering.
Writing it without drowning
- Write the five you enforce most first: house rules, drug testing, discharge, grievances, financial obligations. Those five are where disputes actually happen.
- Steal from your own practice. If your house already handles recurrence of use well, write down what you actually do — don't invent an aspirational version you won't follow, because the gap between written policy and real practice is what gets operators in trouble.
- Match the manual to your records. Where the manual says "incidents are documented," your incident reports are the evidence; where it says "grievances are resolved in writing," your grievance records are. A reviewer who sees software enforcing the manual believes the manual.
- Version it. Date each revision, have staff sign the current version, and re-sign on material changes. An unsigned manual proves nothing about what staff knew.
Keeping it alive
Re-read one section at each staff meeting and ask "is this what we actually do?" — twenty-plus sections a year means every section gets reviewed annually with no dedicated review day. When practice and policy disagree, change one of them on purpose.
Affiliate templates differ state to state, and some sections (sex-offender policy especially) turn on your state's statutes — use your own affiliate's template where one exists, and have the finished manual reviewed. Operational guidance, not legal advice.
The software that builds these patterns in
Anchor & Ascent turns this guide's paper trail into the path of least resistance — incident reports, documented alternatives, discharge records, and the audit packet assemble themselves as you work. Questions? support@anchorandascent.app — a real person replies within one business day.