Question 1

What is an SOP?

Accepted Answer

A standard operating procedure is a short written description of how a recurring process is done: who owns it, what starts it, the steps, who does each one and when it counts as done. It lets the work happen the same way without the founder or one key person.

Question 2

What makes a good SOP?

Accepted Answer

One owner, a clear trigger, a definition of done, a deadline, steps that each have a role, and a control point where mistakes usually happen. If it does not fit on one page, it is probably two processes.

Question 3

How does the readiness score work?

Accepted Answer

Basics give 40: owner, trigger, definition of done and deadline, 10 each. Steps give 60: a workable number of steps 10, a role on every step 15, at least one control point 15, and the known risks you confirm as covered up to 20. With no steps the score is 0, with fewer than three it is capped at 40, and more than five handoffs costs 10.

Question 4

What is a control point?

Accepted Answer

A step where someone checks the work before it moves on: an approval, a second signature, a match against the contract or a review of access. Put one where the process usually breaks.

Question 5

Why does the builder count handoffs?

Accepted Answer

Every time work passes to another role it can wait in a queue or get lost. Fewer handoffs mean faster, safer processes. The handoff map shows exactly where they happen.

Question 6

Can I use it for any process?

Accepted Answer

Yes. Start from a ready draft or choose Custom and write your own steps. The checks work the same way for any process.

Question 7

Is my data stored anywhere?

Accepted Answer

No. The builder runs entirely in your browser and nothing you type is sent to OptiSync. Copy the SOP into Google Docs or Notion, or download a PDF, to keep it.

Question 8

How should we roll the SOP out?

Accepted Answer

Walk the owner and the people in each step through it once, run the process with the SOP open, then fix what did not match reality. Review it every quarter or when the team changes.

Get a process out of your head and onto one page

One page your team can follow

SOPs, explained