lamp.
ResourcesPricingAbout
4 min readBy

Fault-to-fix: role and approval matrix

This matrix assigns the roles in fixing a fault: who may log it, who may repair it, who must check the repair, who can approve spending and who can close it. Owners, operations heads and team leads use it so repairs are quick but never closed by the person who did them.

When to use it

Use it when you first organise your repair and complaint handling, when a new technician or supervisor joins, and after a fault that was repaired and closed by the same person, or one that waited because nobody could approve a part. The matrix also helps a new technician: instead of asking around, they can see who to call for each kind of decision and how much they may spend before asking.

The template

Table 1: Roles and limits

RolePersonCan log faultsCan approve repair spend up to (₹)Can close faultsBackup
Front desk or line operatorNameYesNilNoName
TechnicianNameYes2,000 for minor partsNoName
Supervisor or quality leadNameYes15,000Yes, after verifyingName
Owner or partnerNameYesAbove supervisor's limitYesSecond partner

Table 2: Decisions

DecisionPrepared byApproved byRequired proofIf rejected
Accept the fault and set severityPerson receiving reportSupervisorIntake formReturned with reason, reporter told
Choose repair or replacementTechnicianSupervisorCause note, quote or part listTechnician reworks the plan
Buy parts or call outside vendorTechnicianSupervisor, or owner above limitQuote, estimateLook for another vendor, note the delay
Verify the repairTechnicianSupervisor or quality leadTest reading, photo, trial runFault reopened, original fixer told
Close the fault and inform customerSupervisorOwner for faults with credit or safety impactVerification note, update messageClosure withdrawn, reason recorded

How to fill it

  • Can approve repair spend up to (₹): set one amount per role and say if repeat purchases within a week count together.
  • Can close faults: only a person other than the repairer should hold this.
  • Backup: one named person who has the same limit as the person absent.
  • Prepared by and Approved by: different people in every row.
  • Required proof: name the document or photo.
  • If rejected: state what happens next, so rejection is a step in the process and not a dead end.
  • Urgent cases: add a line for what happens at night or on a holiday, naming who can approve emergency spend and how it is reported to the owner the next morning.

Example row

DecisionPrepared byApproved byRequired proofIf rejected
Replace gearbox on mixer 2, quote ₹21,500Mahesh (technician)Rajesh (owner), since it is above the supervisor's ₹15,000 limitVendor quote dated 3 Nov, cause noteMahesh asks a second vendor for a quote by 5 Nov

Review and sign-off

  • The owner signs the matrix and its dated changes.
  • The operations head checks it every quarter against closed faults, looking for faults closed by their own repairer or spend above limit.
  • Escalate to the owner the same day when spend crosses a limit without approval or when no approver or backup is reachable for an urgent fault, and record what was done in the meantime.

Keeping it up to date

  • Revise limits when repair costs or staff change, and keep the older versions with their dates.
  • Test the backup arrangement once in a while by asking the backup to approve a real case, so you learn before an emergency whether they know the limits and the proof required.
  • Keep the matrix and the approvals it governs 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 →