How owners set who can approve what and up to what amount, so routine decisions can be made the same day, whether they ever sell or not.
A customer requests two additional card readers on an existing project. The change has been approved by the customer, the materials are available, and the project manager has overseen the job from the beginning. Yet the order is delayed because it still requires the owner’s signature.
This is a common challenge in growing, owner-operated businesses. Decisions that could be handled by capable managers often remain dependent on the owner, creating delays and limiting operational efficiency.
As companies prepare their plans for 2027, the fourth quarter presents an opportunity to establish clearer spending and approval authority. While the plan for next year defines what the business plans to spend, an approval authority framework establishes who can authorize those expenditures and within what limits.
In our earlier discussion of The Owner’s Week, we highlighted how routine approvals can consume an owner’s time and slow decision-making. Establishing defined approval limits for each type of decision is a practical step toward greater accountability, faster execution, and a more scalable organization.
The following framework outlines six areas where businesses can begin defining approval authority. These practices strengthen day-to-day operations and create lasting value, whether or not selling the business is part of the long-term plan.
The limits a company already has
Approval limits exist in many companies before anyone writes them down: the service manager knows roughly which purchases can go ahead without a call, the office knows which credits need a word with the owner first, and a new project manager asks about almost everything, because a new person cannot yet know where each limit sits.
In a growing company, an unwritten limit tends to settle on the owner. The careful choice is to ask, and the most careful people ask the most. For years that worked well: the owner was close to every job, and asking was the fastest way to decide. As the company grows, so does the number of questions, and they still reach the owner.
A written policy answers the question before anyone needs to ask it. Below a set amount, the manager closest to the work can approve, and the customer can have an answer the same day. Above it, the decision goes to the next level up with the facts attached, and only the largest decisions of each type reach the owner.
The limits of authority
Finance calls this policy a delegation of authority or an approval matrix. At Halo, ours is called the Limits of Authority.
Each row is a type of decision, split into tiers by size where size matters, so a standard customer contract can take one row for smaller agreements and another for larger ones. Each column is a level of the company, from the lead technicians and managers closest to the work to the owner.
A letter in each cell shows the part that level plays: R to review and recommend, A to approve, and S to sign. Approving and signing can sit at different levels, because a signature binds the company. One more column, outside the levels, marks the decisions the company’s attorney reviews before anyone signs.
Six areas are the place to begin:
- Customer Contracts & Pricing. Who can send a proposal of each size and sign the customer agreement. Standard pricing and payment terms apply to every customer alike, and this area names who can approve a documented exception, with any discount written as a percentage of the price. Nonstandard terms, such as unlimited liability or a broad indemnity, take a row of their own and the attorney’s review.
- Project Change Orders & Scope Adjustments. Added devices, added hours, or a change in scope, agreed with the customer. This area also says whether parts can be ordered before the customer signs the change order. Work done as a courtesy, one of the marks in the closeout comparison, is a decision with a cost, and it belongs in this area.
- Purchasing & Capital Expenditures. Materials within a signed job’s estimate were approved with the job, so the limits apply to orders beyond the estimate. Vendor agreements and subcontracts are split by size, the way customer contracts are, and stock for the shelf has a limit of its own. Vehicles and larger equipment have tiers of their own, a lease has a row of its own, and a long lease reaches the owner.
- Customer Credits & Write-Offs. A credit memo corrects a billing error or makes up for a service problem, and a manager who can issue one can settle a problem the day it is reported. Each credit carries its reason, and above a set amount it needs a second approval. Writing off an amount that will not be collected belongs in this area too.
- Hiring & Compensation. A position in the year’s plan can be approved by the manager who will lead the new person, and a management position goes one level higher. This area also names who can approve the pay in an offer and a change in pay. A position the plan did not include follows the next area.
- Unbudgeted Expenditures & Commitments. Spending or a commitment that the year’s plan did not include goes one level higher than planned spending of the same size.
Each area except the last has a home in one part of the company: change orders, for example, sit with project management. Spending outside the plan can start in any of them. A complete matrix also covers banking and borrowing, insurance renewals and claims, and state license filings.
Setting each limit
Start with each type of decision and find its risk point: the amount, or the kind of term, where a second look is worth the wait. Below that point, the manager who owns the work approves. Above it, the decision goes to the next level up.
The goal is that the critical items in each area cross the right manager’s desk, for visibility as much as for approval. In a week of the owner’s time, logged as in The Owner’s Week, the decisions marked “needs my approval” show where to begin: the type of decision, its usual size, and who brought it.
A few rules keep the matrix working as the company grows:
- Apply each spending limit to the full amount. That includes every payment over the term of a lease or a multi-year vendor agreement.
- Cover an approver who is away. The decision goes to the next level up or, where the company has named one, to an alternate given the same limits in writing, often the person the depth chart names as able to carry the seat tomorrow. For the owner’s own decisions, the owner names who covers. An alternate never approves a decision they brought.
- Keep each approval in writing. A signed purchase order, an email, or a note in the system lets anyone see later who approved what, and when.
Two duties need two people. Whoever approves a purchase does not also pay the invoice, and whoever approves a credit does not also post customer payments, so every payment and credit is seen by two people. In a smaller office, where one person holds several of these duties, the owner or another manager who does not hold them can review payments and credits each month instead.
Decisions above a limit
The manager who brings a decision up brings the amount, the reason, and a recommendation: the R in the matrix. A recommendation keeps the manager in the decision, and it usually makes the approval quick. It helps to agree how quickly an answer comes back, so a decision above a limit does not hold up a job.
Once a month, look at what came above each limit. If the same routine decision comes up frequently, the limit may sit below the ordinary work in that area.
Review the whole matrix at least once a year, when the year’s plan is set, and whenever someone joins, leaves, or changes roles. A matrix written for a company of twenty people seldom fits the same company at fifty.
What a serious reader sees
A written matrix, with the approvals on file beside it, answers a question lenders and accountants ask in some form: who can commit the company’s money and up to what amount? It shows a team making decisions every day within limits the owner set. A successor or a partner would see the same thing: a company that already decides at every level.
Where we stand
Written approval authority is trust extended in advance: the company telling the people closest to the work which decisions are theirs before the next one arrives. We built Halo Service Partners on the conviction that in commercial security, trust is the product, and it begins inside the company, with the people trusted to make its decisions. Continuity is the center of how we partner, because the trusted local company is the thing worth protecting. The name stays, the team stays, and the customer relationships stay. What changes is what stands behind them: shared resources across the network, finance among them, so an owner setting approval limits is not doing it alone, and a company can take the step it has been weighing. Founders choose their own path forward: step back, stay on to lead, or take a larger role across the network.
ProTech Security and Verified Security both run under their own names today, with the leaders and teams who built them still serving the customers who know them.
If you’re thinking about the future
If you own a commercial security company and you are thinking about its future, in any direction, we are glad to compare notes: on how companies like yours share decisions as they grow, on the market, and on what your next chapter could look like. A first matrix can start with one row: the type of decision that reaches you most often in an ordinary week, with an amount and the level that approves it.