Chaos in HR and sales: auditing procedures and automating

Chaos in HR and sales: auditing procedures and automating

When everything rests on people rather than on a process, one person's holiday is planned like a military operation and a new employee takes months to get up to speed. Below are five signs there is no process, and the order of work — describe first, automate second, with no exceptions.

When everything rests on people rather than on a process, one person's holiday is planned like a military operation and a new employee takes months to get up to speed. Below are five signs there is no process, and the order of work — describe first, automate second, with no exceptions.

The person left and the process stopped

The sign by which this diagnosis is made in a minute: one employee leaving paralyses an area.

He knew how it was done. He knew who to ring, where the files were, what to say in a difficult case. None of it is written down, because "everyone knows anyway". Everyone knows while he is there.

Then come the derivatives of the same thing. A new employee takes three months to get up to speed and interrupts everyone else throughout. The same task is done differently by different people. Nobody can say how long it should take. To "who is responsible for this" the answer is "well, all of us".

The company works and grows meanwhile. It is just that each new person adds not productivity but chaos.

Why written procedures usually do not help

The root cause: they get written as a document rather than as a tool.

The classic scenario: somebody was hired, spent six months writing procedures, produced a two-hundred-page volume and it went into a folder. Nobody ever opened it, because finding the right thing in there takes longer than asking a colleague.

The misconception: "we need to describe everything". You do not. You need to describe what recurs and what costs a lot when it goes wrong. The rest is wasted time on both sides.

A second misconception: "procedures exist to control people". No. A procedure exists so that a person can do the work without asking, and so that the result does not depend on who does it. The moment it is perceived as supervision, it gets sabotaged.

And a systemic layer. A procedure not built into the tools goes out of date within a quarter. A written sequence of actions that is not prompted anywhere at the moment of work lives exactly until the first change.

How the pipeline works

Step 1. A process map

Not "how it should be" but how it actually is. Assembled from interviews with people: what do you do, where does the task come from, who do you hand it to, where do you most often get stuck.

The main finding usually appears at this step already. Processes nobody commissioned turn up, along with duplication between departments and stretches where a task hangs with no owner.

Step 2. Priority by the cost of chaos

Describing every process is pointless. What gets selected is what meets at least two conditions: it recurs often, an error costs a lot, only one person has the knowledge.

The last is the most important criterion. A process only one person knows is not a process but a risk.

Step 3. Extracting knowledge from heads

The most labour-intensive stage, and the one that used not to work.

An assistant runs a structured interview with the holder of the knowledge: what do you do, in what order, what goes wrong, how do you handle exceptions. The person does not have to sit down and write — he has to answer questions, and that he can do.

The output is a draft procedure the holder checks and corrects. That is several times faster than "please write down how you work".

Step 4. A procedure people actually use

The format matters more than the content. A working procedure is short, answers a specific question in ten seconds, describes the exceptions and says who to go to if the case is not covered.

The sign of a non-working one: it cannot be read in the time the task takes.

Step 5. Automating what needs no human

After formalisation, part of the described processes turns out to be mechanical: move data across, send a notification, assemble a report, remind somebody of a deadline. That goes into automation.

The order is essential: describe first, automate second. Automated chaos is chaos that has become harder to fix.

Step 6. Assistants as prompts at the moment of work

A procedure in a folder dies. A procedure built into an assistant you can ask at the moment of the task lives.

An employee asks "what do I do if a client wants to move a deadline" and gets an answer from your procedure rather than from general notions. A new person gets up to speed in days rather than months.

Step 7. Ownership

The final step, without which the previous six fall apart: every process has one owner. Not "a department" but a person responsible for the description matching reality.

How to know it is time

Five signs. Three are enough.

A new employee takes more than a month to get up to speed. That is a direct cost: the salary is paid, the output is low, and colleagues are distracted by explaining.

The same task is done differently by different people. A client gets different service depending on who answered.

A key person's holiday has to be planned like a military operation. A sign that there is no process, only a person.

There is no answer to "how long should this take". Which means it can neither be planned nor seen to be deteriorating.

The same mistakes recur. They get discussed verbally and the discussion settles nowhere.

If you recognised three of the five, the company is growing faster than its processes, and the gap will widen by itself.

What the business gets

Separately on resistance

This is the main risk of the project, and it is not technical.

People resist having their work described for an understandable reason: being irreplaceable feels like protection. While only I know how this is done, I will not be dismissed.

One thing works: showing that a procedure takes routine off a person rather than making him redundant. Somebody who stops being asked about trivia gains time for more interesting work. Somebody who goes on holiday and comes back to a functioning area rather than a backlog feels the difference quickly.

What must not be done: promising redundancies. One mention and you will get sabotage at every step where you need people to be honest.

What does not need describing

Half of failed procedure projects are attempts to describe everything.

Do not describe what is done once a year. It is cheaper to work it out afresh each time than to keep a document current.

Do not describe the creative part. The order of work on a design or a text can be formalised up to a point; beyond that taste begins, and a procedure there does harm.

Do not describe what is about to change. A process rebuilt every quarter is too early to document.

And do not describe for the sake of completeness. A procedure exists so somebody can do the work without you. If the task is one that will not get done without you anyway, a document for it is work for the drawer.

What a process audit costs

The cost is calculated from the volume: how many processes get formalised, how many people are involved, whether automation and assistants built to your procedures are needed.

An honest caveat: the fee here is stated by our methodology from the volume of work rather than taken from market statistics — I have not measured what such work fetches on average.

What to compare it against. The cost of three months getting each new employee up to speed, and the price of one departed holder of knowledge.

What a process audit needs

AI assistants — over 200 across 14 categories, including HR, sales and analytics. Interviews, extracting knowledge, draft procedures. Chat access from Basic.

Automation templates — the mechanical part of processes. Creator plan, advanced ones Full.

Your own assistants built to your procedures — Creator+. They are what turns a document into a live prompt.

Registration is free and opens three days of Basic access — enough to run one interview and get a draft procedure for one process.

Do one thing today: write down the processes known by exactly one person in the company. The list is usually shorter than expected and more frightening. That is where you start.

What gets automated after the processes are described

The procedures are described — the question is then what to put on automatic first.

Collecting and qualifying leads from social media into a CRM — an n8n template: a lead-generation pack of eight scenarios, leads from social media are qualified and passed to a CRM. The integrator's fee is from $1 200 (as stated in this card's description in the catalogue).

Weekly report on enquiries from Google Sheets by email — an n8n template: a summary of enquiries and bookings is assembled and sent by email on its own, so the manager sees the figures without interrupting people.

Call transcription and analysis with AssemblyAI and OpenAI — an n8n template: it transcribes a call, analyses the content and saves the result to a database. It closes a standard hole: the conversation happened and there is no record.

HR data sync via API into Google Sheets — an n8n template: an employee table that updates itself. A small thing, but it is exactly why procedures diverge from reality within two months.

The order to keep to. Describe the process first, automate second — a rule with no exceptions. A ready solution saves weeks of assembly but does not remove the first step: automated chaos remains chaos.

Templates — Creator, Make, N8N and Full plans; advanced ones — Full only (or a one-off $9, or 1000 XP).

A ready corporate consulting scenario

The course “AI-Assistants”, Creator plan — system instructions for your own assistants: they are what turns a procedure into a live prompt.

Assistants for each zone of chaos, Basic plan, the catalogue:

What to implement after the audit. The automation templates section — over 3 000 ready scenarios: n8n workflows and Make scenarios. Broken down by category: mailings, CRM, scraping, document handling, AI agents, integrations. Creator plan, advanced ones Full or $9 one-off.

The income model from the section's description: you implement it, then you support and refine it monthly. That is how the model is described on the section's card; income depends on your client and is not guaranteed.

If the processes have to be built yourself — the Make and N8N plans: everything in Creator plus the course of your platform — “Automations in Make” or “Automations in n8n”.

Skills for a process audit

All of these skills are advanced: Creator and above, or a one-off $9, or 1000 XP.

What to take on the platform for this task

What to read next

AI for business owners — the same view from the decision-maker's side.

A company knowledge base as a service — what to do with the procedures once written.

AI for HR — if the chaos is in hiring.

Three automations people buy — what gets automated first.

n8n and Make automation templates — the full guide to automations.

Also on AI SKILLS