Design-to-launch: role and approval matrix
This matrix settles who decides what during a product or service launch: starting the project, changing the specification, buying trial material, releasing a pilot batch, approving the price and giving the final go. Owners and project leads use it so that decisions are made by the right person, on time, and with a record.
When to use it
Prepare it at the start of any launch and keep it with the project folder. Revisit it when a decision was delayed because nobody was sure who could approve, or when someone new joins the design, quality or purchase team.
The template
| Decision | Proposed by | Reviewed by | Approved by | Limit in ₹ | Record kept |
|---|---|---|---|---|---|
| Start the project | Requester | Accounts lead | Owner | Design and trial budget of ₹ __ | Signed request form |
| Fix the specification | Design lead | Quality lead and sales head | Owner | Not applicable | Specification with version and date |
| Change after specification is fixed | Anyone on the project | Design lead and accounts lead | Project lead, or Owner if cost or date changes | Above ₹ __ extra cost | Change log entry |
| Buy trial material | Purchase lead | Design lead | Project lead | Up to ₹ __ per order | Purchase order |
| Release a pilot batch | Operations head | Quality lead | Owner | Batch above ₹ __ | Pilot release note |
| Set the selling price | Sales head | Accounts lead | Owner | Price below the minimum in the brief | Price approval note |
| Launch go or no-go | Project lead | Quality, accounts, operations leads | Owner | Not applicable | Launch approval note |
| Stop or withdraw the product | Quality lead or Owner | Accounts lead | Owner | Not applicable | Dated written decision |
How to fill it
- Decision: add any decision particular to your product, such as a trial at a customer site.
- Proposed by, Reviewed by and Approved by: use role titles with a name beside each, and make sure the approver is never the only reviewer.
- Limit in ₹: fill the blanks with figures that match your margin and cash. Keep them in numbers, and review them once a year.
- Record kept: the exact document that shows the decision, so it can be found years later.
- Where a decision involves regulated labelling, licences or tax treatment, check the current rule on the official portal or with your CA before acting.
Example row
| Decision | Proposed by | Reviewed by | Approved by | Limit in ₹ | Record kept |
|---|---|---|---|---|---|
| Buy trial material | Anil (Purchase lead) | Ritu (Design lead) | Project lead | Up to ₹ 12,000 per order | PO 2201 for 40 kg of resin dated 18 Oct 2026 |
Review and sign-off
- The owner signs and dates the matrix at the start of the project and shares it with everyone named.
- Review at each launch, and during the project if a decision stalls.
- Escalate when a decision is taken without the named approver, when reviewers disagree on a safety or quality point, or when spending would cross the project limit.
Keeping it up to date
- Keep each version with its date, so you can show who was allowed to approve at any point.
- Update limits and names the same day roles change, and tell the team.
- Retain the matrix and the records it points to for the period your CA or the law requires.
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 →