Using a Standard, from Start to Finish
Learn about Using a Standard, from Start to Finish in WaymakerOS.
A Standard is a written rule for how your business does something: a procedure or a policy. You write it once in One. Commander then lets people make documents from it, and each document is checked against it. This page takes you through the whole loop, from choosing a Standard to publishing a document made from it. It covers procedures and policies. Skills work differently: see The Standards Library.
1. Adopt a Standard from the Library
Start with a ready-made one. The Standards Library explains what the Library holds and how to adopt an entry. Adopting makes a private draft of your own.
2. Make it yours
Open the Standard in One. Its draft is further down the page, under a heading that reads Version N (draft), where N is the version number. You see the draft if you own the Standard or it has been shared with you as an editor.
In the draft you can:
- Change the Name.
- Change a section's heading and its text. Each section has its own text box.
- Tick Required on a section so that every document made from the Standard must have it. A required section cannot be removed until you untick Required.
- Add a section with Add a section.
- Set Review every to the number of days between reviews. Enter a whole number from 1 to 1095, or leave it empty if documents need no regular review.
- Choose who approves it, under Who signs it off. The list shows how many people hold each role. If nobody holds the role, sign-off shows as Not checked until someone does.
- Write the Instructions for AI: what an AI must do with documents made from this Standard.
Then choose Save draft. The button is greyed out until the Name is filled in and Review every holds a valid number. Saving keeps your changes. The Standard stays a draft until it is published.
If Waymaker has changed the entry you adopted, the draft may show differences to decide first. Publishing waits until each one is decided and saved. The Standards Library explains how.
3. Publish it
Near the top of the Standard's page, below the three counts, choose Publish. If a version is already in force, the button reads Publish version N, where N is the draft's version number. While Library differences are open the button is greyed out, and a line under it says: "Resolve the differences with the Library first: decide each one in the draft below, then save it."
Publishing a Standard is its approver's sign-off. Only someone who holds the role chosen under Who signs it off can publish. If you chose yourself as the approver and you do not own the Standard, someone else in the role publishes it. Share the Standard with them as an editor so they can.
A published version does not change. To change it later, choose Edit (starts version N), where N is the next version number. That starts a new draft. When it is published, it takes the place of the old version.
4. Say where it applies
A Standard applies nowhere until it is published, so do this after step 3. Under Where it applies, open Choose a workspace… and pick a workspace. To apply the Standard to one project inside it, pick that project from the second list. Leave the second list on The whole workspace to cover the whole workspace. Then choose Apply here.
Applying a Standard to a workspace covers every project in it. To stop applying it somewhere, choose the cross at the end of that place's row. You can only choose places you can open yourself.
Commander offers a Standard only where it applies, and only once it is in force.
5. Make a document from it in Commander
There are three places to do this.
- Documents page: choose From a Standard in the page header. In New document from a Standard, choose a Workspace, then optionally a Project. The default is No project (the workspace itself). Then choose the Standard's name from the list.
- A workspace's home page: under the From a Standard heading, choose the Standard's name. The heading only appears when a Standard applies to that workspace.
- A project's home page: choose Add a tool. The Standards that apply are listed under From a Standard at the top of the menu.
Choosing a Standard makes the document and opens it. The document takes the Standard's name as its title and starts with the Standard's sections, each under its heading. If no Standard applies in that place, Commander says: "No Standard applies here yet. In One, open a Standard and choose where it applies."
6. Sign it off and mark it reviewed
A document made from a Standard shows a bar under its header, starting with Made from and the Standard's name. The bar holds two checks:
- Sign off is for someone who holds the role the Standard names as its approver. If you do not hold that role, Commander tells you which role does.
- Mark reviewed is for anyone who can edit the document. It means you have read it and it still stands.
Each check reports its result on the bar. For example, after Sign off it says "Signed off." followed by "Meets" or "Differs from" and the Standard's name.
If a document differs from its Standard when you Sign off or Publish, a box opens with the title This differs from and the Standard's name. It lists what differs. You can choose Fix it to go back and change the document. Or you can write a reason under Go ahead, because… and choose Go ahead. Mark reviewed never opens this box.
Sometimes the box says This does not meet the Standard's name, with the line "The Standard does not allow going ahead with this. Fix it first." In that case there is no Go ahead. Fix the document, then check again.
A sign-off is for the text as it stood. If someone edits the document afterwards, the sign-off no longer counts, and the approver must sign it off again before it can be published.
7. Publish the document
While a document is private, its bar shows Publish. Only people who can edit the document see the button. The bar says "Not in force until it is published. When it is ready, the approver signs it off, then it can be published."
Publishing needs a current sign-off first. If there is none, or it was cancelled by an edit, Commander says who needs to sign it off, and nothing is published. If the document differs from its Standard, the box from step 6 opens.
8. The register, and the three states
On a Standard's page, the Documents section lists every document made from it. Each row shows the document's state and has an Open in Commander link. Three counts sit above the list, one for each state.
- Current means the document meets its Standard.
- Slipped means the document differs from its Standard. If someone agreed an exception, the row says so, and the document stays Slipped.
- Not checked means it could not be measured, so nobody knows whether it matches. A document that is not published is Not checked. So is a published document nobody has checked yet, or one with a part that could not be checked. A Standard is Not checked when it is not published, applies nowhere, or has nothing made from it.
Not checked is never shown as Current. A Standard is only Current when everything made from it is Current. A skill is never shown as Current, because it has no checks.
When a count cannot be known, the tile shows a dash, not 0. Counts are not known when nothing has been made from the Standard yet, when some documents are filed where you cannot open them, or when there are too many to read at once.
9. The daily check
A document is checked when it is published, signed off or reviewed, and again after it is edited. Its Standard's page lists these checks under Recent checks.
Published documents are also re-checked once every day. If a document's last review is older than the Standard's Review every days, it shows as Slipped, and a check named Review date checked appears under Recent checks. Marking the document reviewed, or signing it off, puts it right.