Standard operating procedure (SOP) writing
Write standard operating procedures a competent stranger could run. We observe the work, document the exact steps with screenshots, cover the exceptions and test each draft on someone who was not in the room, so your processes are written down in a form others can follow.
Most SOPs only make sense to the person who wrote them
Most SOPs are written by someone who already knows the process, which is often where the problems begin. They skip steps that seem obvious, overlook rare exceptions and leave out screenshots because the system is familiar to them. The document makes perfect sense to its author, but a new user reaches the first decision and doesn’t know what to do. We use a more practical test: could a capable person complete the process using the SOP alone, even if they had never done it before? Every SOP we write must meet that standard.
How we handle SOP writing for your processes in NetSuite
Senior consultants oversee our SOP writing services, and you can see progress as it happens. Approvals and decisions stay with your team.
- Watch-the-work captureWe document the procedure by watching it happen, rather than relying on memory. That way, we capture the steps people complete automatically but often forget to mention.
- Step-accurate authoringWe write numbered actions with the exact clicks, fields and values, giving a newcomer precision at the grain they need.
- Screenshot anchoringEach decision point gets an annotated screenshot, kept current and refreshed whenever the UI moves.
- Exception coverageThe if-this-happens branches, such as the credit hold, the failed match and the missing field, are documented as first-class paths rather than footnotes.
- Stranger testingA competent non-expert runs the draft, every stumble becomes an edit and sign-off follows the clean run.
- Ownership and review datesEach SOP has an owner, a review date and a change trigger, so the procedure tracks the process as it evolves.
SOPs promised but never written?
We write the standard operating procedures your auditors and new starters need. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.
What handing it over buys you
Absence cover works from the document
Tested SOPs mean someone else can run the process from the document when a colleague is on holiday.
Training has a written basis
New starters onboard against written procedures rather than word of mouth.
Exceptions are handled consistently
Documented branches mean a credit hold is handled the same way each time.
Audits meet written practice
The walkthrough follows the SOP, so paper matches practice.
How the writing lands
Watch & capture – the process is observed at the desk where it runs.
Draft to standard – steps, screenshots and exceptions are written to the house standard.
Stranger-test – a clean run by an uninvolved person precedes sign-off.
Own & maintain – review dates and change triggers keep each SOP current.
What to know before you hand it over
- !Process owners approve the content, and the sign-off is theirs. The SOP encodes how your business runs the process, so correctness is the owner’s call while we write, test and maintain.
- !We flag broken processes instead of documenting them. If observation shows that a procedure needs to change, we send it to the improvement programme rather than turning a flawed process into an SOP.
- !Keeping screenshots current is part of the service. Interfaces change, and screenshots quickly become outdated, so we review them with each release cycle. Even one old screenshot can make users question whether the rest of the SOP is still reliable.
Standard Operating Procedure (SOP) Writing FAQs
How long should an SOP be?
Who tests the drafts?
How many SOPs does an account need?
What happens when the process changes?
Last reviewed: 21 October 2026 · Written by the Suite Generation team
Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.
