Reviewed 31 August 2026 · next review 28 February 2027
Writing guides: what makes a procedure readable, and how to check it
Every guide states the principle, shows the failing sentence, gives the neutral edit, and links to a checker you can run on your own text without an account.
Last updated · Written and reviewed by Jonatan Tensetti · Tensetti Tools
Method 1.0.0 · reviewed 31 August 2026 · next review 28 February 2027
These pages describe the reasoning behind the checks: why an actorless instruction slows a reader down, why three names for one part costs a support ticket, and why a warning works better when the hazard comes before the avoidance. Nothing you paste is sent anywhere — the analysis runs in your browser.
Showing 11 of 11 guides
- Technical writing· ExplainerTechnical writing style guideThe rules behind clear procedures, written as principles you can adopt today.
- Technical writing· ExplainerReadability checker for documentationWhy generic readability scores miss procedure-specific clarity problems, and what to review instead.
- Technical writing· ExplainerPlain language checkerPlain-language principles applied to technical documents, with a deterministic clarity check.
- Technical writing· ExplainerSimplified Technical English contextWhat STE-style writing asks for, and what this independent tool does and does not do.
- Technical writing· ChecklistInstruction clarity checkerOne main action per step, an identifiable actor and an observable result.
- Technical writing· ExplainerControlled language checkerApproved terms, controlled variation and consistent sentence patterns.
- Technical writing· ExplainerPassive voice in technical writingWhen passive voice hides the actor, and when it is a deliberate technical choice.
- Technical writing· ExplainerTerminology consistencyFind competing names for the same component or concept and decide which variation is legitimate.
- Technical writing· ChecklistSafety warning wordingReview hazard, possible consequence and avoidance action without automating safety approval.
- Technical writing· ComparisonSimplified Technical English vs plain languageTwo clarity approaches compared without reproducing or claiming conformity to either standard.
- Technical writing· ComparisonFree alternative to technical writing softwareCompare transparent deterministic checks with grammar tools and enterprise authoring suites by actual workflow need.
ClearSpec uses an independent proprietary clarity method. It is not affiliated with ASD/STEMG, is not an ASD-STE100 checker or certification service, and does not certify ISO 24495-1 conformance.
22 checks, no account, and the text is analysed in your browser.
ClearSpec reports automated heuristics from method version 1.0.0. The clarity indicator is not a measure of technical accuracy, usability, legal sufficiency, safety or standards conformance. A competent person must decide the final wording, especially for safety content.