Docs
The process, where the work is.
A written process is worth having only if the people who run it can find it and you can tell who has read it.
The screen
Docs
Docs, wikis, processes and contracts.
WorkPlannerAITalkTeamsDocsTablesGoalsSettings
NONorthwind OpsSample workspace
Library
SOPs
SOPs
CClient onboarding v4
CClient reporting
SSupplier onboarding
Contracts
BBluefin Foods v2
HHarbour Mills v1
Docs›SOPsSearch or jump toMD
Client onboarding v4
Owner: Sam OkaforKRA: Client onboarding runs on timeShare
1Confirm the signed agreementOnboarding lead
2Create the client recordOnboarding lead
3Kick off internal onboardingOnboarding leadOnboarding cycle time
4Confirm the reporting cadenceOnboarding lead
5Collect finance sign offFinance
6Schedule the kickoff callOnboarding lead
7Hand over to the account teamOnboarding lead
SLA 10 days from the signed agreement.
What you get
Everything below ships today.
- Four kinds, four editorsA written procedure, a checklist, a decision flow and a recorded walkthrough. The editor matches the kind rather than making every process a wall of text.
- Acknowledgement that closesAssign an SOP, see who has acknowledged the current version and who has not, and export the list. It is a record, not a certification.
- Version historyPublish a new version and the acknowledgements reset to it. The old version stays readable, attached to the period it governed.
- Owned by a roleAn SOP points at the KRA it serves, so the process and the result area are the same conversation. Today the owner shown on the doc is the person who created it.
- Steps, with ownersA step names the job title that owns it. Run the SOP and each step marked to create a task becomes a task for the person holding that title, linked back to the step.
- Policies and contracts beside themThe same block holds policies with their own acknowledgement ledger, and contracts with their clauses, so the paperwork is not a separate product.
Questions
Straight answers.
Does an SOP step create the task by itself?
When you run the SOP, yes. Give a step of a step-by-step SOP a job title and mark it to create a task. Running the SOP creates the task for the person holding that title who is available soonest, and when nobody holds it the task is created unassigned with a note saying so, never guessed.
Can I see who has not read the current version?
Yes. The compliance view lists acknowledged and outstanding per SOP and per person, and exports to CSV.
Is this an audit trail I can hand to an auditor?
It is a record of who acknowledged what and when. Whether that satisfies a given auditor is between you and them: we hold no certification and we are not going to imply one.