SOP compliance, for a small business, is four claims that each need evidence: the procedure is written and approved, the people who do the task follow it, each run leaves a record, and the procedure is reviewed on a date or when the process changes. An auditor, a customer or a regulator reads the evidence, not the claim. The tools on this site size the procedures and the record; RunbookDesk Pro keeps the evidence.
Written and approved: the version with a signature
The evidence is the current version with the approver's sign-off and the date, and the retired versions with theirs. A procedure with no version is not evidenced as written; one with two current versions is not evidenced as standard.
Followed: the training sign-off
The evidence that people follow the procedure starts with the record that they read the current version and signed that they had, and continues with the runs. Five people at twenty-five minutes per procedure is the training load the SOP development cost calculator prints, and the sign-offs are the record.
Recorded: the run leaves a mark
A procedure run with no record is, to the reader of the evidence, a procedure not run. The checklist cut from the procedure, with who ticked what and when, is the record; the SOP example builder on this site prints how many runs a week a procedure produces.
Reviewed: the date and the change
The review date on the cover page and the record of the review, with what changed, is the evidence that the procedure is current. A procedure last reviewed before the system changed is not compliant with anything; RunbookDesk Pro reminds the owner and keeps the record.
Questions people ask about sop compliance
Is SOP compliance a legal requirement?
In regulated activities, written procedures and records are often required; outside them, customers and auditors ask for the same evidence. Either way the evidence is the same four records.
What is the weakest link in most small businesses?
The review. Procedures are written in a burst and then decay, and a stale procedure is evidence against the business rather than for it.
Does software make a business compliant?
No. It keeps the evidence that the business did the four things; the doing is the business's.