The Process Nobody Wrote Down: The First Holiday Is the Audit
The person who knows how the business works is the hardest to replace. What happens on their first holiday, why documenting a process is mostly finding decisions nobody made explicit, and a worked example of a return going wrong.
Every business has a person who knows how it actually works. Not how it is supposed to work — how it works. They know which customer always pays late and what to do about it, which return is fine and which needs a phone call first, which discount gets refused and which gets waved through, which step in the day-end routine exists only because something went wrong once and nobody cleaned it up. Ask them to write it down and they will say yes, and produce something that is thirty per cent right, because the process is not in a document. It is in a hundred judgements they have never had to make explicit.
Then they take eleven days off, and the business finds out which parts of that knowledge were a process and which parts were a person. This article is about that fortnight. It is also about why documenting a process turns out to be mostly the opposite of writing: you sit down intending to transcribe what someone does, and you discover that a third of the steps have no decision behind them at all. Somebody has been making a judgement call, quietly, for years, and nobody — including them — had noticed there was a decision to make.
The first holiday is the audit
Nobody volunteers for a holiday as a test. The absence arrives and the coverage is improvised, and the improvisation is the measurement. If the process was written down, the person covering can follow it and the difference will be small. If it was not, the person covering does the part they understand, skips the part they do not know exists, and the skip is invisible until a customer notices or a number moves.
There is a reason this is more dangerous than an ordinary mistake. An ordinary mistake is corrected when it is found. A skipped step is not obviously a mistake at all — the work looks done, the invoice looks issued, the day closes. What you lose is the ability to tell the difference between the work that was done properly and the work that was done the way the covering person guessed. That difference is exactly what you would need in order to answer a question in three months.
A process failing in a specific, believable way
Here is a worked example. All figures are constructed and the arithmetic is shown so you can check it. A retail business sells a category of goods that may be returned within 21 days, with a restocking deduction of 10% of the sale value where the packaging is opened. The shop manager knows both rules because they wrote them down in a training note two years ago. The person on the counter this year has never seen the note. Nobody is at fault; the note lives in a shared drive under a filename that describes the products and not the rule.
Worked example, constructed for this article — the arithmetic.
Original sale, invoice IN-208, dated 4 August:
- Taxable sale value: ₹18,500
- GST at 18% of the sale value: 18,500 × 0.18 = ₹3,330
- Invoice total: 18,500 + 3,330 = ₹21,830
Return presented on 13 September:
- Days since the sale: August has 31 days, so 31 − 4 = 27 days to the end of August, then 27 + 13 = 40 days
- The return window is 21 days, so the return is 40 − 21 = 19 days past the window
The credit note actually issued, at the full sale value with no restocking deduction:
- Taxable credit: ₹18,500
- GST at 18%: 18,500 × 0.18 = ₹3,330
- Credit total: 18,500 + 3,330 = ₹21,830
The credit note the policy would have produced, with the 10% restocking deduction:
- Restocking deduction: 18,500 × 0.10 = ₹1,850
- Taxable credit: 18,500 − 1,850 = ₹16,650
- GST at 18% of the reduced value: 16,650 × 0.18 = ₹2,997
- Credit total: 16,650 + 2,997 = ₹19,647
The difference the skipped rule made:
- 21,830 − 19,647 = ₹2,183
- Check it another way: 1,850 × 1.18 = ₹2,183. Same number.
The 18% GST figure is used here only so that every line can be checked by hand. Whether a restocking deduction, a return window, or a tax treatment is right for your business is a question for your own chartered accountant — and so is the question of whether a credit note may reduce an invoice that has already had a payment allocated against it.
Three things went wrong on 13 September and only one of them is obvious. The return was outside the window, and nobody checked. The restocking deduction was skipped, and nobody noticed. And the credit note was issued with no reference to a return being authorised, because the step that required a manager to look at the goods does not exist as a record — it existed as a habit, in one person, who was not on shift. The ₹2,183 is the visible cost. The invisible cost is that the credit note now reads as a correction of a pricing error rather than a return outside policy, and six weeks later nobody can tell which it was.
Documenting a process is mostly deciding things
Ask someone to write down a process and the first draft is always the sequence, not the judgement. It will read like this: receive the return, check the item, issue the credit. That is not a process. It is a list of verbs. The process is the part in the middle: check the item against what — the invoice date, the 21-day window, the packaging, the customer's history, the manager's judgement, and in what order, and what happens when two of those disagree.
So the drafting session will stall, repeatedly, on the same thing. Someone has to say: when a return is six days past the window and the customer is a long-standing account, is it accepted? There is no fact to look up. It has been decided, implicitly, dozens of times, and each time slightly differently. That is the real output of documenting a process. Not the sequence — the sequence was never the problem. The problem is the decisions that were made so quietly that nobody noticed they were being made.
Worked example, constructed for this article — the arithmetic.
A team writes down the returns process step by step. The written process has 14 steps.
- Steps that turned out to be mechanical, with no judgement attached: 5. These were things everybody already did the same way.
- Steps that required the writer to invent a rule, because no rule had ever been stated: 14 − 5 = 9.
- Of those 9, the ones with a real financial consequence: 4 — return window, restocking deduction, who authorises, and what happens when the invoice already has a payment against it.
So two thirds of the writing was not documentation. It was decision-making, done in an afternoon, by people who had been making the same decisions informally for years. Two thirds is not a complaint about the team. It is the normal shape of an undocumented process, and it is the reason the exercise is worth doing: those nine decisions now exist in a form that can be argued with, and the four with financial consequences now exist in a form that can be checked.
Start from the tasks that already exist
A project in NoxOrigin holds tasks and task lists, and they are the closest thing most small businesses have to a written process: a named piece of work, assigned, with a state. The temptation with tasks is to use them as a to-do list and stop there. The better use is as the skeleton of the process, with the decision written into each task instead of living in the assigner's head. "Issue credit note" is a task. "Return is within 21 days of the invoice date and packaging is unopened, so issue the credit note at the full value" is a task somebody else can pick up on a Friday and get right.
The same applies to a recurring routine. A day-end or month-end sequence is a list of tasks with a recurrence, and the person who currently does it in their head can be asked a narrower question than "write the process": what do you always do first, and what do you never do until the first thing is done? Those two answers are the parts that matter, and they are the parts that survive a holiday.
A drafting session that produces decisions rather than verbs
- Start from one process someone does often enough that a mistake would be noticed — returns, credit limits, month-end, onboarding a new customer.
- Write the sequence first, then mark each step: mechanical, or a decision. Be strict about the second category. Most steps that feel obvious are decisions.
- For every decision step, write the threshold as a number, not an adjective. "Large" and "suspicious" are not thresholds.
- For every decision step, write what happens when the threshold is crossed, and who is allowed to make that call. If the answer is a person, write their role rather than their name, so the process survives their leaving.
- Name the person who can override the process, and what the override leaves behind. An override that leaves nothing behind is indistinguishable from the process not existing.
- Turn the sequence into tasks so the covering person has something to work from, and attach the decision text to the task itself.
- Re-read it after the next holiday, when somebody has followed it without the author in the room. That is the cheapest and most honest review available.
The last point is the one most teams skip, and it is the only one that tells you whether the work succeeded. A process document written by the person who knows the business is their opinion, however carefully recorded. A process document that somebody else has followed without them present is evidence. The difference between the two is exactly the difference between a process that exists and a person who exists, and the only way to get from one to the other is to let somebody else run it once while you watch what they ask.
Frequently asked questions
Does NoxOrigin have a process or SOP documentation module?
No. There is no SOP builder and no knowledge base. What exists is the records a process leaves behind — quotes, projects, tasks, invoices, payments, credit notes, stock movements — and a per-user activity trail. A documented process in this platform is a sequence of those records with the decisions written into the tasks.
How do I document a process when the person who knows it is on leave?
You do not, and that is the point. The first absence is the cheapest audit you will ever get: the steps that get skipped are the ones that were never written down. Cover for the holiday, note every question the covering person had to ask, and turn those questions into the decision text on the tasks. You will learn more in eleven days than in an afternoon of interviewing.
What about processes that depend on hours, expenses, or payroll?
NoxOrigin has no timesheet record and no payroll module, and expenses live in Nox-Billings rather than in the unified app. Purchasing sits in Commerce, and shift close and day-end reconciliation are assisted-setup maturity rather than self-serve switches. Any process you document that depends on those needs a named person to set it up.
Is the 18% GST in the return example a rule I should apply?
No. It is there only so the arithmetic can be checked line by line. Whether a return, a restocking deduction, or a credit note treatment is correct for your business depends on your registration and your circumstances — ask your own chartered accountant, and note that a credit note against an invoice that already has a payment allocated against it is a situation where you want their answer in writing before you process it.