A delegation matrix is a table of the decisions your business makes every week, who makes each one, what they can decide on their own and when they have to call you. It’s how you hand over decisions, not just tasks, so the person you delegated to stops calling you for permission.
This guide shows why handing over a task often isn’t enough, the five levels of authority you can give, what goes into each decision, and two worked examples from a contractor’s week. At the end there’s a template you can copy.
Why “you handle the scheduling” doesn’t work
Example: an owner tells the office coordinator, “From now on, you handle the scheduling.” Two days later:
- A customer asks to push their start by a week. The coordinator calls the owner: “Is that OK?”
- A crew finishes early. “Should I pull the next job forward?”
- A job needs a specialist who’s booked. “Can I give it to the other crew?”
The coordinator isn’t being difficult. The owner handed over the task (putting jobs on the calendar) but kept every decision (what to do when something changes). Scheduling is mostly changes, so the calls kept coming.
| A task | A decision |
|---|---|
| Enter the job on the calendar | Move a job when the customer asks |
| Order materials for next week | Switch to a different supplier when one is out of stock |
| Write up the change order | Approve the extra work on site |
| Send the invoice | Agree to split the payment |
To get a task off your desk for good, you have to hand over the decisions that come with it, with limits.
Five levels of authority
Delegating a decision isn’t all or nothing. You can hand it over in steps:
| Level | What the person does | Example |
|---|---|---|
| 1. Do as asked | You decide, they carry it out | You pick the new date, they call the customer |
| 2. Recommend | They look into it and suggest; you decide | “Thursday works for crew 2. Should I book it?” |
| 3. Decide, check before acting | They decide, tell you and act unless you object | “I’m moving it to Thursday unless you say otherwise” |
| 4. Decide and act, tell you after | They act and let you know | “Moved Henderson to Thursday, crew 2. Customer confirmed.” |
| 5. Decide and act | They act; you see it in your regular review | Nothing reaches you. It shows up on the weekly job review |
Most handoffs should start at level 3 and move to level 4 after a few weeks of good decisions. Level 5 is for decisions that are routine, low risk and well understood. When someone keeps calling you about a decision you thought you’d handed over, check which level you actually gave them. Often it was level 2 without anyone saying so.
What goes into each decision
For each decision you hand over, write down seven things. In this guide we call that a decision agreement: one row of your delegation matrix.
- The decision: in plain words. “Move a scheduled job to a new date.”
- Who owns it: one person, by role. Not “the office.”
- Level: from the table above.
- Information they use: what they need to decide well, and where it lives.
- They can decide alone when: the limits. Be specific: days, amounts, job types.
- They call you when: the escalation triggers. Anything outside the limits, plus the situations that are risky even inside them.
- How it’s recorded and shared: who needs to know and where the decision is written down, so the office and the field see the same thing.
Add a review date, two to four weeks out, when you’ll look at how it went together.
Example 1: rescheduling, handed to the office coordinator
A remodeling company with two crews. The limits are an example. Set your own.
| Part | What the owner and the coordinator agreed |
|---|---|
| Decision | Move a scheduled job to a new date, or swap jobs between crews |
| Owner | Office coordinator |
| Level | 3 for the first two weeks, then 4 |
| Information | The shared schedule, which crew can do which work, typical job durations, who’s off |
| Can decide alone when | The move is 3 working days or less; the customer agrees; a crew with the right skills is free; the price doesn’t change |
| Calls the owner when | The move is longer than 3 working days; it affects an inspection or a subcontractor’s date; it needs overtime; the customer is upset or talks about cancelling |
| Recorded and shared | Updated on the schedule the same day; the crew lead gets told before the end of the day; a note on the job saying why it moved |
| Review | Two weeks from today |
Look at what’s missing: the owner. A customer who wants Thursday instead of Tuesday, with crew 2 free, never reaches the owner’s phone again.
Example 2: small change orders, handed to the crew lead
The customer asks for an extra outlet while the crew is on site. Without a rule, the crew lead calls the owner, or does the work without documenting it and the extra never gets billed.
| Part | What the owner and the crew lead agreed |
|---|---|
| Decision | Agree to extra work the customer asks for on site |
| Owner | Crew lead on the job |
| Level | 3 for the first five change orders, then 4 |
| Information | The price list, the approved scope, the change order process |
| Can decide alone when | The extra is on the price list; it’s under $500 (the owner’s chosen limit in this example); it doesn’t change the schedule by more than half a day |
| Calls the owner when | It’s over $500 or not on the price list; it touches structure, permits or inspections; the customer disputes the price |
| Recorded and shared | Change order written, priced and signed by the customer before the work starts; the office is told the same day so it gets invoiced |
| Review | After the first five change orders |
How do you choose a limit like $500? There’s no right number for every business. Pick an amount you could absorb if the decision went wrong, that covers the small extras that come up most often, and that fits the person’s experience. Start lower and raise it once you’ve seen a few weeks of good calls. How to handle change orders without losing the client covers the customer side.
Delegation matrix template
Copy this table into a spreadsheet and fill in your own rows. Start with three or four decisions, not twenty. The rows are examples, not recommendations for your business.
| Decision | Owner | Level | Can decide alone when | Calls the owner when | Recorded where | Review |
|---|---|---|---|---|---|---|
| Move a scheduled job | Office coordinator | 3 → 4 | ≤ 3 working days, customer agrees, crew free | Longer move, inspection or sub affected, unhappy customer | Schedule + job note | In 2 weeks |
| Approve a small change order | Crew lead | 3 → 4 | On the price list, under your limit | Over the limit, structural, disputed | Signed change order | After 5 change orders |
| Order materials for a scheduled job | Office coordinator | 4 | Approved supplier, matches the estimate | Over the estimate, supplier out of stock on key items | Purchase order on the job | Monthly |
| Approve a day of overtime | Crew lead | 3 | Job finishes that day, customer deadline at risk | More than one day, or a second crew affected | Timesheet note | Monthly |
| Send the invoice for a finished job | Office coordinator | 5 | Closeout checklist complete | Unbilled extras, disputed items | Invoice + job record | Weekly review |
| Offer a discount to close a sale | Estimator | 2 | Never alone: recommends | Every time | Note on the proposal | Quarterly |
The last row matters as much as the others. A delegation matrix also says clearly what doesn’t move, so nobody guesses.
How to hand over a decision safely
- Write the agreement together. Sit down with the person and fill in the seven parts. They’ll spot gaps you can’t see from the owner’s chair.
- Walk through three real cases from the last month: “What would you have done here?” If their answers match yours, the limits are clear. If they don’t, fix the wording.
- Start at level 3. For the first two weeks, they decide and tell you before acting. Most of the time, you just say “OK.”
- Review the exceptions, not every decision. At the review date, look at what was escalated and anything that went wrong.
- Raise the level when the calls have been good. Write the new level down.
When they make a call you wouldn’t have made
If the decision was inside the limits, let it stand, even if you’d have done it differently. Then ask yourself whether the limits need to change, and change them for next time. If you reverse decisions made within the rules, you’ve changed the rules without telling anyone, and the person will go back to asking you about everything.
If the decision was outside the limits, talk about it privately and go back over the agreement. Was the limit unclear, or was it ignored? Those need different fixes.
Tell everyone who decides now
A decision agreement only works if the people around it know about it. Tell the office, the crews and anyone else who used to come to you: “Moving jobs is the coordinator’s call now.” Then, when someone calls you anyway, send them to the coordinator instead of answering. The first few times feel slower. That’s how the new habit forms.
Your next action
- Take the responsibility you picked in the previous lesson.
- Write one decision agreement for it with the person who’ll own it: all seven parts and a review date.
- Walk through three recent real cases together.
- Tell the office and the field who decides now.
What to review on the review date:
- Decisions made within the limits: these are the ones that no longer reached you.
- Escalations that didn’t need you: if there are many, the limits are too narrow or unclear.
- Decisions that should have reached you but didn’t: the limits are too wide, or the triggers are missing.
Next lesson: Know Where Every Job Stands Without Calling Your Crew. Once decisions move, you need a way to see the results without asking.
Where MotionOps helps
Delegated decisions need the right access and a record everyone can see. In MotionOps:
- Customizable Roles & Permissions: each team member gets a role, and you can change it as they take on more.
- Change Order Requests: field technicians start the change order with the customer inside the work order, so the extra gets documented and billed.
- PriceBook: your items, prices and margins in one place, so every proposal is priced from the same list, not from memory.
- Push & Email Notifications: staff and clients get notified about important appointment and work order updates.
See plans and pricing, or book a MotionOps demo.
Contractor Scaler Hub: Get Out of the Owner Bottleneck, lesson 3 of 5
- Previous lesson: Work On Your Business, Not In It: What a Contractor Should Keep and What to Hand Off
- Next lesson: Know Where Every Job Stands Without Calling Your Crew
- Course toolkit: Get Out of the Owner Bottleneck toolkit (PDF)
- All courses and lessons: Contractor Scaler Hub
