Two people in a business handle the same case, and each does it differently. While both are around, nobody notices. The first time one calls in sick, the customer does: a query sits untouched because it landed in the wrong inbox.
The reflex is a document. A written procedure gets created and filed away, and three months later everyone is back on their own variant. Bureaucracy does not come from standards, it comes from standards nobody asked for. There is little room anyway: according to a Market institute survey for the Austrian economic chamber WKO, businesses spend an average of 9.4 hours a week on bureaucracy, and small and medium sized firms 19.3 hours. 72 percent of those smaller firms told the WKO survey that this effort had grown strongly over the previous three years.
How do you standardise processes in a small business without creating bureaucracy?
Settle on one variant per recurring case, write it where the work happens, and name one person allowed to change it. What sits inside the tool costs nobody time. A document in a folder costs time every week.
The difference from documentation is the moment the decision gets made. Documentation records how work is done. A standard sets how it is done from Monday on. Three written variants record the disagreement and nothing else. How to capture workflows without extra effort is covered in our post on documenting processes.
What is a standard in a workflow?
A standard is the agreed order of steps for a recurring case, valid until a named person changes it. One page is enough, and it has to carry five things.
- Trigger: how you know the case has started. A mail in the shared inbox, a call, a deadline in the calendar.
- Steps: the actions in order, numbered. Reasons belong in the conversation, not on the page.
- Ownership: one person by name. A department is nobody.
- Exception: who may deviate and who gets told. Without that line, every deviation becomes a quiet second standard.
- Date: when it last changed. Without it, nobody knows whether the standard is older than the program it names.
Which workflows should you standardise first?
The cases that come up every week, that more than one person carries out, and where a mistake costs money or trust. A process map shows which cases exist at all; without it, a business standardises whatever went wrong most recently.
- Taking in enquiries: phone, mail and web form arrive in one place, with the same first reply and the same deadline.
- Following up quotes: a fixed interval, one person responsible, one place to read off the current state.
- Invoices and receipts: who records, who checks, where the file ends up.
- Onboarding: a new colleague's first week is the hardest test for any standard, because she knows nothing and asks everything.
Where does a standard belong?
Where the work happens. A template in the mail client, a required field in the CRM, a checklist in the task list, a form that will not submit without the missing entry: each carries the standard without anyone having read it. A case one person handles four times a year needs no standard, only a note where she looks next time.
A standard as a document is a request. A standard inside the tool is the shortest route through the work. Where the correct path is the easiest, nobody needs training.
Where does the law already prescribe the standard?
In several places, and there you adopt it rather than invent it. Three duties concern cases running in every Austrian business.
- Working time: under Section 26 of the Austrian Working Time Act, the employer keeps records of the hours worked. Where a fixed schedule is agreed in writing, Subsection 5a makes a confirmation at the end of each pay period sufficient, with only deviations recorded as they occur.
- The penalty sits in the same act: Section 28 provides 72 to 1,815 euro where records are missing, 145 to 1,815 euro for a repeat offence, and under Subsection 8 separately per employee where working time cannot be established.
- Records: Section 132 of the Federal Fiscal Code requires seven years of retention from the end of the calendar year, with faithful reproduction guaranteed at any time where data carriers are used. A standard therefore says where the photo of a receipt goes, not only who takes it.
- Data: Article 30 GDPR requires a record of processing activities, with purposes, categories of data subjects and recipients, retention periods and the protective measures. Article 30(5) exempts organisations with fewer than 250 employees, but not for processing that is not occasional. Whether it holds is a legal question in each case.
Anyone certified to ISO 9001 has a second frame. According to Austrian Standards, the standard appeared in a new edition on 16 September 2026; existing quality management systems need no fundamental redesign for it, and certified organisations have three years to switch. According to the certification body DQS, certificates under the 2015 edition stay valid until 30 September 2029. For a business without a certificate that changes nothing: a standard needs no norm to apply.
How do you spot a standard that only exists on paper?
By three signs. The exception comes up more often than the rule. New colleagues learn the case by asking rather than reading. And the date of the last change is older than the program the standard names. Two of the three are reason enough to rewrite it.
- 1.Pick a case that comes up every week and that more than one person carries out.
- 2.Lay the variants side by side. Half an hour with the people doing the work shows where they diverge.
- 3.Settle on one variant. Do not vote: the person answerable for the outcome decides, after listening.
- 4.Anchor the standard in the tool and write it on one page, with trigger, steps, ownership, exception and date.
- 5.After four weeks, ask which step got skipped, then change the standard instead of reprimanding people.
As a guide, each case takes half a day to a day, depending on how many people and how many programs it touches. In practice, five to eight settled cases cover most of the week in a ten person business.
Standardising takes no freedom away. It answers a question once, so that it is not asked again every week, and leaves the exception explicitly allowed. How we capture workflows, agree new ones with the team and anchor them in daily work is on our page on process design and optimization.