Picture a routine equipment order waiting for an MSP owner's approval. Before a decision rights framework, the team has a task and an unanswered message. After the owner assigns authority, the purchasing owner can approve a standard order within the agreed budget and report the result. An exception follows a named escalation route.
The useful change is permission to make a defined decision, with its limits and reporting understood. Calling the same approval queue empowerment doesn't change who can act. I'd start with a recurring decision that the business already knows how to judge.
Separate Doing the Work From Deciding
List the decisions that still reach the owner. For each, identify what the owner actually supplies: a budget check, a client commitment, technical judgment, or approval of an exception. That tells you whether the next step needs a documented rule, training, information, or retained owner authority.
Keep responsibility for the task separate from authority to decide it. A technician may prepare the equipment order without being authorized to approve a nonstandard purchase. A purchasing owner may approve the standard order without being authorized to promise a client a different service scope.
The MSP model puts purchasing and billing administration in the operations role. It keeps service supervision in delivery and account responsibilities distinct. Use your actual roles when assigning decisions; don't send every cross-team question to the service lead because that person is nearby.
For a smaller MSP, the same person may fill several roles. Record which role they are acting in and what authority comes with it. A title alone doesn't settle the boundary.
Write the Decision, Limit, and Report Together
Use a compact record for each delegated decision. State what can be decided, who owns it, which inputs must be checked, and the boundary beyond which approval is needed. Add where the decision is recorded and who reviews the result.
| Decision Area | Authority to Define | Escalation and Record |
|---|---|---|
| Standard purchasing | Approved catalog, budget, supplier terms, and required client approval | Purchasing owner escalates exceptions and records the order basis |
| Desk scheduling | Work allocation within skills, coverage, and existing commitments | Service lead escalates uncovered demand and records changed priorities |
| Invoice correction | Documented billing error and approved correction method | Billing owner escalates disputed scope or an exception and preserves the reconciliation |
| Proposal scope | Approved service offer and pricing rules | Commercial owner seeks approval for unsupported scope and records the revised offer |
| Technical exception | Defined technical authority and service requirements | Technical owner records the departure, approval, and follow-up responsibility |
Choose financial and operational limits from your own commitments and cost records. The model doesn't supply a universal purchase threshold, credit limit, or acceptable error count. A convenient round number isn't evidence that the decision fits the role.
Keep the model's pricing rules inside the commercial boundary. It rejects discounting monthly recurring revenue to win a client. Giving a salesperson more authority doesn't require authorizing a concession that the pricing model prohibits.
Test the Rule With a Representative Decision
Return to the illustrative equipment order. The purchasing owner checks the item against the approved catalog, the available budget, the supplier commitment, and any client authorization needed. If those conditions match, that role approves the order and records the evidence.
If the item falls outside the catalog or creates a different service responsibility, it follows the exception route. The owner receiving that escalation gets the specific unresolved question and the proposed action. They don't need the whole purchasing process resubmitted as an approval request.
Have the person who will use the rule walk through a representative case before making it routine. Ask what they can decide, what would stop them, and what they must record. Their unresolved question identifies a boundary the framework hasn't explained.
Then check actual work capacity. Authority doesn't create time to compare quotes, investigate a billing difference, or supervise a difficult ticket. Remove or reprioritize work where the new responsibility otherwise has nowhere to fit.
Remove Approvals You Don't Need to Keep
Here's what I'd cut: an owner approval after a delegated decision already met every agreed condition. Keep the report and the review. If the owner still has to approve each instance before work starts, describe it honestly as a prepared recommendation rather than a delegated decision.
Set a route for the owner to question a decision without silently taking the whole category back. Establish whether the person exceeded authority, lacked information, or followed a rule that produced the wrong result. Those require different corrections.
If the rule was followed and the outcome was poor, examine the rule. If the role needed a skill it didn't have, address training or change the assignment. If the person knowingly crossed a boundary, handle that through the responsible management process rather than rewriting every routine request as owner-only work.
A stronger lead-generation campaign can't remove an approval step you still require the owner to complete. More demand may make that queue more visible. Check delivery decisions and coverage alongside the growth plan instead of expecting marketing to repair them.
Keep Exceptions From Becoming the Normal Route
Write down why a decision was escalated. Separate a genuine exception from a normal decision whose owner lacked access, information, or confidence. Repeated normal requests returning upward can identify a missing input or a boundary that isn't clear enough.
Name the backup for an unavailable decision owner. State when the backup can act and where the decision is recorded. Otherwise an absence can restore the owner as the default approval route without anyone deliberately changing the plan.
Keep client commitments visible. A scheduling decision inside the desk may affect an agreed delivery date or a client update. The framework should identify who can change that commitment and who communicates it, rather than assuming internal authority includes permission to alter the agreement.
Measure Decisions Completed Within the Boundary
Record the request, decision owner, waiting time, outcome, and any escalation or reversal in the decision log. Compare those records with the previous process for similar work. Count decisions completed within authority alongside decisions returned for correction.
Agree the review standard before judging the results, using your actual service and financial requirements. If waiting time falls but rework or reversals exceed that standard, I'd narrow or revise the rule. A larger count of independent decisions isn't enough to call the change successful.
Check what happened to the owner's time too. Record the approval work removed and the work that replaced it. Fewer messages don't establish that the business gained usable capacity if the same decisions now require an unrecorded conversation.
The model treats recurring, profitable revenue without owner reliance as part of building enterprise value. A decision record can help identify work that no longer depends on the owner; it doesn't establish a sale value. Keep that broader goal separate from the result you can actually observe.
Choose a recurring decision, assign authority with a clear boundary, and test it with the person who will act. Keep the report, exception route, and review attached. The next step is a decision the team can make from the agreed information without waiting for permission they already have.
mspoutpost.com/articles/build-a-decision-rights-framework-your-msp-team-can-use
Written by Owen Gallagher
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.