Company procedures: how to write short work rules that people actually follow
Management9 min read
Company procedures in plain words: types, structure and an example, how to write them briefly, how to roll them out and why to build them into the task.

A company procedure is a document that describes how a particular piece of work is done: who is responsible for it, what steps must be taken, by when, and what the result should be. Its purpose is to make results repeatable, so that a deal, a client booking or a purchase goes equally well no matter who is working today.
A procedure in a minute
| Block | What to write | Example for handling an inquiry |
|---|---|---|
| Goal | Why the process exists | Every inquiry gets a reply and a next step |
| Scope | When it applies | All incoming inquiries from messengers, the website and platforms |
| Roles | Who takes part | Administrator, manager, head of department |
| Steps | What to do, in order | Reply, clarify the request, offer options, schedule a meeting |
| Deadlines | When to do it | First reply within 15 minutes during working hours |
| Result | What counts as done | The client has a reply, the CRM has a card and a task with a deadline |
| Exceptions | What to do in non-standard cases | If the request is out of scope, politely decline and close it with a reason |
Why companies need procedures
While a company has five people, everything runs on agreements. Everyone knows who does what. Once there are 15–20 people, problems appear:
- everyone does the same work their own way, and quality swings;
- a newcomer spends a month figuring out "how things are done here";
- when an employee leaves, their knowledge leaves with them;
- the manager constantly answers the same questions;
- it is unclear who is to blame when something goes wrong.
Procedures solve these problems if they are short, clear and tied to real work.
Types of procedures
| Type | What it describes | Example |
|---|---|---|
| Business process procedure | The sequence of steps from start to result | Handling an inquiry, closing a deal, receiving a patient |
| Job description | The duties and rights of a specific position | Duties of a salon administrator |
| Interaction procedure | How departments hand work to each other | Passing an order from sales to the warehouse |
| Service standard | How to communicate with a client | Greeting, reply times, tone of correspondence |
| Security procedure | Access, data, working with documents | Who can see the client database, how passwords are shared |
How to write a procedure: 7 steps
1. Choose a process
Don't start with "we need to document everything", but with the process that breaks most often or affects money the most. Usually this is handling inquiries, closing deals, issuing invoices and working with repeat clients.
2. See how the work is done now
Don't invent an ideal process at a desk; ask the people who carry it out. It is best to look at real examples: 10–20 inquiries or deals from the last month.
3. Define the result
What should be achieved at the end? "The client got a reply" is too vague. "The client got a reply within 15 minutes, a card with budget and timing was created in the CRM, and a next step was set" is clear and verifiable.
4. Describe the steps
Each step is one action with a clear result. If a step can't be checked, it is poorly worded.
5. Assign owners
Each step has one role responsible for it. "Everyone is responsible" means "no one is responsible". A responsibility matrix helps.
6. Set deadlines
Deadlines for each step and for the whole process. Without deadlines, a procedure turns into wishes.
7. Describe exceptions
What to do if the client doesn't reply, if a discount larger than standard is needed, if the request is out of scope. Exceptions are the most useful part of a procedure: they are where employees make the most mistakes.
Procedure example: handling an incoming inquiry
Goal: every incoming inquiry gets a fast reply and a clear next step.
Applies to: all inquiries from messengers, the website and listing platforms.
Steps:
- First reply — the manager replies within 15 minutes during working hours. Outside working hours, an AI operator or an auto-reply states when the manager will respond.
- Clarifying the request — the manager finds out the budget, timing and key requirements. The data is recorded in the client card.
- Offer — the manager sends 2–3 suitable options and explains why they fit.
- Next step — a meeting, call, viewing or commercial proposal with a specific date. A task with a deadline is created.
- Closing — if the client declines or doesn't respond after three attempts, the inquiry is closed with a stated reason.
Deadlines: steps 1–4 within one working day.
Result: the client has a reply and a date for the next contact, and the CRM has a completed card and a task.
Exceptions: request out of scope — polite refusal and closing with the reason "not our profile"; client asks for a discount above 10% — approval from the manager.
This example fits on one page. That is exactly the length a procedure should have for people to read it.
Why procedures don't get followed
- Too long. Nobody reads a 40-page document past the table of contents.
- Outdated. The process changed, the procedure didn't. Employees see the mismatch and stop trusting it.
- Detached from the work. The procedure sits in a folder on a drive, while the work happens in messengers and the CRM. At the moment of action, nobody remembers it.
- No control. If nobody checks whether the procedure is followed, it quickly becomes a formality.
- Written "from above". A procedure invented without the people who carry it out often ignores real constraints.
A procedure in the task, not in a folder
The most reliable way to make a procedure work is to build it into the place where the work happens. Instead of a document on "how to close a deal", use a process template in which:
- the deal stages are already created in the right order;
- each stage has an owner and a deadline;
- inside the stages there are checklists with specific actions;
- the move to the next stage is visible to the whole team.
The employee doesn't read the procedure — they simply go through the steps, and skipping something important becomes hard. For more on how to describe and improve processes, see the article on business process automation.
How to roll out procedures
- Start with one process. Describe it, test it for a month, fix it.
- Discuss with the people who do the work. People follow rules they helped write more willingly.
- Build it into the system. Task templates, checklists, mandatory steps.
- Train. A short walkthrough at a team meeting with real examples.
- Review. Once a quarter, check whether the procedure matches reality.
Procedures in different industries
| Industry | Which procedures are needed first |
|---|---|
| Sales | Handling inquiries, closing deals, handling objections and discounts |
| Clinics | Booking a patient, preparing for the appointment, repeat visit, handling complaints |
| Salons and fitness | Booking, cancellation and rescheduling, selling memberships |
| Real estate agencies | Taking on a property, viewing, deposit, closing the deal |
| Service and repair | Taking an order, technician visit, warranty cases |
| Wholesale and manufacturing | Taking an order, agreeing deadlines, shipment, handling debts |

How it works in Mestra
In Mestra, a procedure lives not in a document but in the work itself:
- Process templates. You create a process once — for example, "Handling an inquiry" or "Apartment deal" — with stages, deadlines for each step, assignees or groups of assignees, and files. For each new task, the process is launched from the template.
- Stages the whole team can see. The task moves through steps, each with an owner and a deadline; if needed, you can go back to the previous step.
- Checklists and comment templates. Inside the task is a list of specific actions to tick off.
- Loss reasons. If a deal falls through, a reason is chosen from the company's list — this is part of the procedure that later turns into analytics.
- Action history. Who changed a status or completed a step, and when, is visible in the task history.
- AI launches processes itself. AI can create a task from a conversation and start the right process from a template.
Frequently asked questions
How is a procedure different from a job description?
A job description sets out the duties of one position. A procedure describes a process in which several people and departments may take part: who does what and in what order.
How long should a procedure be?
The shorter the better. For most processes, 1–2 pages is enough: goal, roles, steps, deadlines, result and exceptions.
Who should write procedures?
The process owner — usually the head of the department — together with the people who carry it out. The owner approves key procedures, especially those involving money and clients.
How often should procedures be updated?
Review them once a quarter, and always when the process, product or team structure changes.
How do I make sure a procedure is followed?
Make it short, discuss it with the people who do the work and build it into your working system: task templates, stages, checklists and deadlines that can't be skipped unnoticed.
Summary
A good company procedure is short, verifiable and built into the work. It describes the goal, roles, steps, deadlines, result and exceptions, and helps the work get done equally well no matter who does it. Procedures that sit in a folder stop working after a couple of months; procedures in the form of process templates are followed every day.
In Mestra, a procedure becomes a process template with stages, deadlines, owners and checklists that is launched for each task. Try Mestra free for 15 days at mestra.chat.


