The problem
Procedures exist but nobody opens them mid-task. Quality depends on who does the work, and senior people spend time fixing avoidable mistakes.
How it works
- Each task type is linked to its SOP so the procedure appears next to the task.
- When a task starts the model drafts a first pass using the task details and the SOP.
- The team member edits and completes starting from a draft that already follows the process.
- Edits are captured so SOPs and prompts improve over time.
What it needs from you
- Written SOPs for your repeat tasks (we can help write them)
- A task tool your team already uses
- An owner for each SOP
Why it's built this way
Putting the procedure in front of people at the moment of work is what makes SOPs actually get used.
Drafts grounded in your SOPs are more consistent than generic AI output.
How it stays under control
- Every draft reviewed by the assignee
- SOP version linked to each draft
- Edit tracking to improve prompts
- No external sending from the draft step
The path to autonomy
Drafts always go through a person. Over time, simple task types may need only a quick check.