Order-to-delivery: role and approval matrix
This matrix says who may prepare, who may approve and what proof must exist at every decision between accepting an order and handing it over. Owners use it to stop orders being promised, changed or released by whoever happens to be nearby. Order desk, planning and dispatch staff use it to know when they can act and when they must wait.
When to use it
Write it when you first set up the order process, and revisit it when a role changes, someone leaves, or a mistake shows that nobody was clear about who could say yes. Pin the agreed version where the order desk and dispatch team can see it.
The template
| Decision | Prepared by | Approved by | Proof needed | Cover if approver is absent | If rejected |
|---|---|---|---|---|---|
| Accept and validate a new order | Order desk | Planning supervisor | Sales order, customer's order message | Owner | Hold the order and ask the customer to clarify |
| Change a confirmed order | Order desk | Planning supervisor | Revised sales order, customer's written request | Owner | Continue on the original order and tell the customer |
| Give a promised date | Planning supervisor | Dispatch or service lead | Schedule, stock and capacity check | Order desk lead | Offer the next date that can be met |
| Book a slot, shift or machine | Dispatch or service lead | Planning supervisor | Job card | Order desk lead | Rebook and update the job card |
| Sign off completed work against the promise | Order desk | Planning supervisor | Quality check sheet, job card closure | Dispatch or service lead | Rework and recheck before dispatch |
| Release for handover | Dispatch or service lead | Order desk lead | Invoice or dispatch note, quality check | Planning supervisor | Hold at the premises and record the reason |
| Reschedule after a failed handover | Dispatch or service lead | Order desk lead | Call log, delivery note | Owner | Keep the original date and escalate |
How to fill it
- Decision: name the event, not the department. Add a row for any decision your business makes that is not listed, such as a discount on a late order.
- Prepared by and Approved by: use job titles, and make sure they are different people. A person who prepares should not also approve.
- Proof needed: the document the approver must see before saying yes.
- Cover if approver is absent: one named fallback, so work does not stop.
- If rejected: the next step, so a "no" has a clear route and the order does not sit in limbo. Where you add a money limit for any approval, set the amount yourself and write it in the row.
Example row
| Decision | Prepared by | Approved by | Proof needed | Cover | If rejected |
|---|---|---|---|---|---|
| Change a confirmed order | Meena (order desk) | Suresh (planning supervisor) | Customer message dated 13/11/2026 raising quantity from 40 to 51 racks, ₹23,760 extra | Owner | Continue at 40 racks and tell the customer |
Review and sign-off
- The owner reviews and signs the matrix, with the date, when it is created and at each change.
- Review it every quarter and whenever someone joins, leaves or changes role.
- Escalate to the owner when an order is found to have moved past a decision without the named approver or the named cover.
Keeping up to date
- Keep each signed version for the period your CA or the law requires, and mark the older one as replaced.
- Update names and cover arrangements first when people go on leave.
- Share the current version with everyone named in it, and ask them to confirm they have read it.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →