Every team writes differently. A compliance team wants “Navigate to the Settings menu and select the Audit Log option.” An engineering team wants “Settings → Audit Log.” An onboarding guide can afford a “Nice work — you’re halfway there.”
Until now, Routinly wrote every SOP in one house style: clear, neutral, correct. Good — but not yours. Starting today, Solo and Team plans can set a custom writing tone, and every generated SOP matches it.
How it works
In your workspace settings, describe how your team writes. You can pick one of the presets or write your own instruction:
- Formal — full sentences, no contractions, precise UI terminology. Built for regulated industries and audit trails.
- Friendly — warm, encouraging, plain language. Ideal for customer-facing guides and new-hire onboarding.
- Brief — the minimum words that still get the reader through the task. Engineers love it.
- Custom — your own description, e.g. “write like our support KB: second person, short sentences, bold every UI element name.”
The tone applies at generation time, so there’s nothing to rewrite. Record your video as usual; the draft arrives already sounding like your team. Change the tone setting and future SOPs follow it — existing documents stay untouched.
Why we built it
The whole point of Routinly is that generated documentation is good enough to ship. In practice, “good enough to ship” turned out to include sounding right, not just being right — teams told us they were editing drafts not to fix errors but to fix voice. That’s exactly the kind of manual work we exist to remove.
Custom tone is live now on Solo and Team plans. Set it once in Workspace settings → Writing tone, and your next recording comes back sounding like you wrote it — in a fraction of the time.