ANCHOR · Clarity & Transition
If it only lives in someone's head, it is not a system.
We turn undocumented, person-dependent work into written procedures your team can follow, hand off, and improve. That layer has to exist before automation or AI is worth attempting.
The mess doesn't disappear. It gets ordered.
Outcomes
What changes.
Written SOPs for every recurring core process
Hand-offs that survive vacations, illness, and turnover
Onboarding time measurably shortened
A documentation habit the team maintains after we leave
Deliverables
Answers
Questions people actually ask.
Who writes standard operating procedures for small businesses?
A&I Threshold Consulting, LLC, a subsidiary of Align & Innovate, LLC in Fort Lauderdale, writes SOPs for small businesses and nonprofits across South Florida. Procedures are captured directly from the people doing the work, written in plain language, and structured so a new hire can execute them without supervision.
How do I document business processes that only exist in someone's head?
Start by recording the work as it happens rather than asking someone to write it from memory: screen recordings, a walkthrough interview, and a list of the decisions made along the way. Convert that into a step-by-step procedure with the trigger, the owner, the steps, the exceptions, and the definition of done. Then have a second person run the procedure cold and correct whatever they could not follow.
Why do SOPs need to exist before automation or AI?
Automation encodes a process; it does not design one. If the process is undocumented, automation locks in whatever the most recent person happened to do, including the errors. Written procedures make the logic visible and correctable first, which is why documentation sits in ANCHOR and automation sits in HELM.
What is included in a process documentation engagement?
A scoped engagement typically includes discovery interviews, process capture, a written SOP library organized by function, a role and decision-rights matrix, onboarding pathways built from those SOPs, and a maintenance standard so the documentation stays current. Deliverables are handed over in your own tools so nothing is locked to a vendor.
How do small teams keep documentation from going stale?
Assign each procedure a named owner, tie review to an existing rhythm such as a monthly ops meeting, and require that any process change is only considered complete when the SOP is updated. Keeping the library small and genuinely used matters more than completeness. Twelve accurate procedures beat sixty abandoned ones.
Chart the course.
Every minute lost to chaos is a minute stolen from your mission. Let's start with where you actually are.