Knowella
TemplatesGuide

Writing and design conventions

The rules that keep 825 templates reading as though one person wrote them.

Language

1
No em or en dashesAnywhere. Commas, full stops or a rewrite instead.
2
Plain wordsUtilise becomes use. Prior to becomes before. Commence becomes start.
3
Say the thingHelp text states the actual failure mode rather than restating the field label. Dull knives need more force is useful. Ensure knives are sharp is not.

Template descriptions

Every description follows the same shape: what the template does, when it is raised, who completes it, and why it matters. Descriptions never claim the platform acts on its own, because it does not. A template does not open a case or become a work order. A person does that, and the description says so.

Info blocks

Info blocks carry the reason, not the instruction. They exist because a form that only asks questions teaches nobody anything. Roughly one in three templates opens with one, and they are the place where operational judgement is written down.

Field naming

  • Questions read as statements to confirm, not as questions with a question mark.
  • IDs always end in ID and carry their format in the help text.
  • Anything linking to another template names that template in the link.

Scoring positions

Where the library scores something zero it is taking a position. Retraining as the sole corrective action, convenience sampling, assumed energy savings, job rotation as a primary control, and lifting technique training as a substitute for redesign all score zero. That is deliberate, and it is where the library carries an opinion about what good practice looks like.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.