How to use it
Fill in the four header facts exactly as they appear — or should appear — at the top of your document, then paste the full procedure text, one paragraph or step per line where you can. Read the result in fix-first order: header gaps first, then long paragraphs, then warnings buried in text, then a missing stop point. Fix the source document, paste it again, and only convert it when the score stops moving.
Your procedure
The example is a short fictional procedure written for this tool — not a real customer document. Your text never leaves this device.
The ten checks, in plain English
- 1. Title is named. The header names the procedure exactly, so the checklist that comes out of it can be matched back to its source.
- 2. A person owns it. The header names one owner — a person, not a department — who can approve a change.
- 3. Version is labelled. A version label (for example v3 or Rev. 2026-02) tells everyone which copy is current.
- 4. A date is present. An effective or last-review date in the header itself, not only in a calendar or an email.
- 5. Ordered steps can be found. Numbered lines, or lines that start with an action verb, in the order the work happens. A converter — human or software — needs a sequence it can follow.
- 6. Paragraphs are short enough to split. No paragraph over about 60 words. A long paragraph usually hides two or three steps, plus reference material that belongs in a note, not a step.
- 7. Warnings stand alone. WARNING, CAUTION or DANGER lines sit on their own line immediately before the step they protect — not buried inside a paragraph after the action.
- 8. Steps name a checkable outcome. Numbers, ranges, recorded names, photos, or a visible state a second person could verify — not only effort words like check or inspect with nothing to check against.
- 9. Vague words are rare. Properly, correctly, appropriate, adequate, as needed and similar words hide the standard. Each one needs a number, a name or a visible test next to it.
- 10. A stop or escalation point is stated. The document says when to stop and who to call — a supervisor, a named role, a phone or a ticket — instead of leaving a stuck reader to improvise.
Prerequisites get a separate look in the result: if the text never names the tools, materials, access or records needed before step one, the fix list will say so — a checklist that starts mid-air fails on its first run. The method behind these checks is in our free guide, How to Turn an SOP into a Checklist Anyone Can Follow. After conversion, the Checklist Quality Checker scores the steps that come out, and the SOP Review Scheduler tracks when the source is due for its next review.
Source ready? Convert it.
The free OniLens app converts raw instructions and SOPs into ordered, checkable lists right in your browser — no account, no credit card, up to 50 saved checklists. Prefer not to do it yourself? Assisted Conversion turns up to 10 procedures into finished browser and PDF checklists for $29 one-time, and Team & Operations covers larger sets with branding and shared links for $49 one-time.
Pro license $39/year removes the free app limits; Family is $79/year. 30-day refund policy on paid plans.
Frequently asked questions
What does the SOP Conversion Readiness Checker do?
You paste the text of a procedure you have not converted yet, and add four header facts — title, named owner, version and date. The tool runs ten plain checks on that source text in your browser: header completeness, whether ordered steps can be detected, whether paragraphs are short enough to split into steps, whether warnings stand alone, whether steps name checkable outcomes, how many vague words appear, whether prerequisites are named, and whether a stop or escalation point is stated. It returns a 0–100 readiness score and a fix-first list, so you repair the source before anyone converts it.
How is this different from the Checklist Quality Checker and the SOP Review Scheduler?
This checker works before conversion, on the raw SOP. The Checklist Quality Checker works after conversion, scoring checklist steps you already have. The SOP Review Scheduler works one level up, tracking which procedures exist, who owns them and when each is due for review. Readiness, step quality and review dates are three different jobs.
Is my procedure text uploaded anywhere?
No. The checker runs entirely in your browser. Your text is never sent to, seen by, or stored by OniLens. You can disconnect from the internet after the page loads and the tool still works.
Does a high readiness score mean my procedure is correct, safe or compliant?
No. The score measures whether the document is structured so it can be converted cleanly — not whether its content is correct, complete, safe or compliant. A qualified person must review the content before anyone runs the procedure, especially for safety-critical, medical or regulated work. This tool is not a compliance certification and is not legal or safety advice.
What should I fix first if my score is low?
Fix the header first — a procedure with no named owner, version or date will drift no matter how good its steps are. Then split any paragraph longer than about 60 words into separate lines, pull warnings onto their own lines before the step they protect, and add the stop or escalation point if there is none. Those four fixes usually move the score the most.
What do I do once the source is ready?
Convert it. The free OniLens app turns the repaired text into an ordered, checkable list in your browser, with no account and no credit card. If you would rather not convert documents yourself, Assisted Conversion and Team & Operations are done-for-you options described below.