Write the rule in English.
Walter checks every spec against it.
Every firm has standards it never writes down — the rub count below which a fabric will not survive a lobby, the grade of casegood you will actually sign off, the lead time past which a plan stops being a plan. They live in a principal’s head and they get enforced when someone remembers. Type one into Workroom as a sentence, and Walter reads every product specification against it.
Or just tell Walter — “add a standard: all casegoods must be AWI Premium Grade.”
Five sentences. Every product specified from here on gets read against all of them.
Trusted by the studios doing the work
It is in someone’s head, and they are on site
Ask a principal what their standards are and you will get a fluent, specific answer — rub counts, grades, finishes they will not use again, the vendor whose lead times they no longer believe. Ask where those standards are written and the answer is a look.
So enforcement is a person. It happens when that person reviews the schedule, and it does not happen when they are on a plane, when the work went out on a Friday, or when the junior who specified it did not know the rule existed. The failure surfaces at install, which is the most expensive place it could possibly surface.
- Write it once, in the words you would use out loud
- Scope it to a category, or apply it to everything
- Applies to work specified by anyone on the team
- Add one mid-project and it checks what is already there
A standard added in conversation is the same record as one added on the form — and it shows up in Your standards either way.
One rule, three hundred rooms
On a single residence a bad fabric is an apology and a re-order. On a hundred-and-forty-key hotel or a build-to-rent block it is the same wrong fabric in every unit, discovered after installation, priced accordingly.
- Hospitality — brand standards manuals are already written in exactly this language. Rub counts, flame spread, contract ratings, cleanability. You are transcribing a document you were handed, not inventing a policy.
- Multi-family and build-to-rent — the durability floor is the whole business model, because everything specified gets used harder than a home and replaced on a schedule.
- Spec and production building — the package repeats, so a standard that catches one line catches it across every plan carrying it.
The junior still specifies it. You still hear about it.
Hard validation is how good software becomes hated software. Block a field and the first genuine exception — the approved substitute, the client’s own fabric, the piece that is technically out of spec and completely right — turns into a support ticket and a workaround.
A standard produces a finding. The product is specified, the work continues, and the flag sits on the record where the person reviewing it will see it. You keep the judgement; you just stop needing to remember the rule.
- Severity set per standard when you write it
- Findings collected in their own tab for review
- Nothing is blocked and nothing is silently changed
- Exceptions stay exceptions instead of becoming precedent
Four fields. That is the entire mental model — which is the point, because a standard nobody can be bothered to write is a standard that does not exist.
“The standards were always in my head. Writing them down once meant I stopped being the only person who could catch a bad spec.”
Brand standards, specifically answered
Do I have to learn a rules syntax?
No. A standard is a name, a sentence, an optional category and a severity. You write the rule the way you would say it to a colleague — “all guestroom fabrics must be at least 100,000 double rubs” — and Walter reads product specifications against it.
What does Walter actually read?
The product’s own specification fields — material, finish, pattern, dimensions, model number, lead time and the rest of the record. It is checking the specification you captured, not a tag somebody remembered to apply.
Does a failing product get blocked?
No. It produces a finding. The product is still specified and the work continues; the flag sits on the record for whoever reviews it. Hard blocks are how legitimate exceptions turn into workarounds, and a workaround defeats the standard entirely.
Can a standard apply to only one category?
Yes. Set a category and the rule only applies there — a rub count against textiles, a grade against casegoods. Leave it blank and it applies across every category.
Can I add a standard by talking to Walter?
Yes. “Add a standard: all casegoods must be AWI Premium Grade” creates the same record the form does, and it appears in Your standards alongside the rest.
Who can see and change standards?
Standards live in settings, so access is governed by the permission set on each team member — the same mechanism that decides who can approve a bill or see a budget. Permissions →
Tell us one rule you enforce by memory.
We will write it into Workroom on the call as a sentence, and run it against a schedule you already have — which is usually the moment it stops being a preference and starts being a standard.