Boundaries of this review
1. What this review covers — and what it does not
A remote review rests on two sources: what the people running the process say, and what the documents record. That is enough to see where the process breaks, and not enough to see how people actually work.
| What was done | What it shows | What it does not show |
|---|---|---|
| A 60-minute conversation with the owner and the production manager | The picture of the process as held by those who run it | Not how the process actually runs — only how it is described |
| Study of documents: production order forms, the stock ledger, a month of order exports | Verifiable traces: what is recorded, where, and at what moment | Not what happens between those recordings |
| Reconciling the description against the documents | Divergences between how the process is described and how it is recorded | No substitute for watching the cycle and interviewing the people doing the work |
This is a limit of the method, not a disclaimerEverything that follows rests on the conversation and the documents. Claims that cannot be checked without being on site are not included — instead, the questions that remain open are listed at the end.
Observations
2. Where the process breaks
Each observation below rests on a specific trace in the documents rather than on a general impression from the conversation.
| Break | How it was found | What follows from it | Priority |
|---|---|---|---|
| Stock is only known at dispatch | The order export contains deferrals and refusals on line items that the stock ledger shows as available on the same date | The outlet is promised what is not there; the order is renegotiated after confirmation | Critical |
| The production order is raised after the shortage | Production order dates consistently fall after the refusal dates on the same line items | Production runs in catch-up rather than replenishment | Critical |
| The purchase requisition follows the production order | In the internal memos the requisition date falls after the date of the order the material is needed for | A material stoppage that was visible in advance | High |
| The order is rewritten between intake and dispatch | The same line items exist on two forms with different wording and units | Transcription errors and disputes about order contents | High |
| Piece-rate pay is assembled by hand | The monthly roll-up is not derived from closed production orders: its totals do not reconcile with output per order | Recalculation and disputes about hours and volume every period | High |
The common denominatorAll five breaks are the same phenomenon in different places: stock is not a controlling signal. It is recorded as a report about the past rather than as a condition for the next action. That is why every subsequent step learns about a shortage later than it could.
What can be closed
3. What automation can close, and how
Below is what can be closed with separate, verifiable steps. Each one can be tested across a single month of work without waiting for the others.
| What | How it works | What is needed from you |
|---|---|---|
| Reservation against the order | Stock is checked at intake, goods are committed to the specific order, and a shortage is visible immediately | A current list of line items and a threshold for each |
| Production order from a stock threshold | When the threshold is crossed the order is raised automatically, with quantity and material required | Approved thresholds and a decision on who may change them |
| Purchase requisition from the production order | Material missing against an order becomes a requisition to purchasing with no separate paperwork | Consumption norms and lead times for the key materials |
| Documents from the action | Invoice and delivery note arise in the same action that creates the order | Templates, company details and a numbering rule |
| A basis for piece-rate settlement | Output, the workers involved and the rate are settled when the production order closes; the monthly roll-up stops being separate work | Current rates and a rule for who closes an order |
The order mattersStart with the reservation against the order. It is the cheapest of the five and it makes the other four measurable: as soon as stock becomes a condition of intake, it becomes visible how many times a month the process stalled on its absence.
Limit of a tool
4. What needs the “Operations system” tier
Part of what was found cannot be closed by a single tool. Not because the task is harder, but because it touches several departments at once — and introduced across only part of the chain it moves the manual reconciliation to the boundary rather than removing it.
| What | Why it cannot be closed piecemeal |
|---|---|
| A single order record from intake to purchase requisition | It touches sales, the store, production and purchasing at once. Partial rollout moves the manual reconciliation to the seam with the department left out, rather than removing it |
| A state model with an owner for each step | It requires agreement on who decides, and on what data. That is organisational work no configuration replaces |
| Rules and deadlines with an escalation target | They work only if they cover the whole order path. Across part of it they create the appearance of control: an exception enters the queue and leaves it into the un-automated part |
| Management reporting from operational data | It only comes together once the three points above stand. Before that, any consolidated report remains manual assembly, however it looks |
What that requiresThis cannot be designed remotely: the state model and the distribution of ownership are derived from watching the cycle and interviewing the people doing the work. That is the scope of the “On-site process immersion”, not of this review. The present document shows that such a step is justified; it does not replace it.
Decisions and next step
5. What you do not need to do, and what comes next
Some of the obvious-looking solutions make this situation worse. We name them directly, because they are usually where people start.
| What you do not need to do | Why |
|---|---|
| Introduce a general-purpose CRM | It settles over the break between order intake and stock and records it as a tidy funnel. The problem is not deal tracking; it is that the commitment is made before the stock level is known |
| Start with the outlet account | Self-service over unsynchronised stock increases the number of manual checks: more orders arrive and the ability to confirm them is unchanged |
| Digitise the stock ledger as it stands | That is an exact copy of a faulty mechanism. Stock must follow from reservation and issue, not be a separate record somebody maintains |
| Optimise delivery routes | While stock is unreliable, what gets optimised is randomness. Returning to this makes sense once reservation works |
| Roll out all five points at once | Each is testable separately across one month. A simultaneous start removes your ability to tell which one actually worked |
Questions that remain open at a distance
These are not gaps in the review but what by definition cannot be read from documents. Each of them changes the scope of the work.
- How far the stock ledger diverges from what is actually in the store — verifiable only by stocktake or by watching goods-in.
- How much of a shift is spent rewriting the order — visible only when the cycle is observed.
- Who actually decides to ship when stock is short — the documents show the outcome, not the decision.
- Which consumption norms are applied in practice, and whether they match the approved ones.
- What your accounting software accepts and in what format — that needs access to it, not to exports.
Recommended next stepTake the first point in section 3 — reservation against the order — and test it across one month. It requires no change in other departments and gives a measurable answer: how many times a month an order stalled on missing stock. If an unbroken chain from order to purchasing is needed after that, the next step is capturing the process on site.
This document demonstrates the structure and level of detail of the deliverable of the “Process review — remote” service, the format without a site visit. It is based on the mechanics of a delivered, anonymised platform for beverage production, is not legal, tax or industry advice, and contains no confidential client information. Maturity scores, role analysis and the state model are not part of this format: they require watching the cycle and interviewing on site.