Ten extra hours can be a sensible investment in a strategic customer. Ten extra hours every month because nobody knows whether the founder's permission expired is a different decision.
A founder override decision process should make that distinction visible. Record the normal rule, why the founder is departing from it, the maximum exposure, the responsible operator and the review date. When permission expires, the choice returns to the normal approval process unless the founder explicitly renews it.
That is the editorial rule developed here from Arron Bennett's published positions on reducing key-person dependence and turning financial insight into execution. It is not presented as an existing Bennett policy or a client case.
Making decisions includes deciding when permission ends
Founders have reasons to grant exceptions: a critical launch, a customer recovery or a promising relationship. A useful process leaves room for judgment. It also gives the team a clear answer when someone asks for the same exception again.
The CEO should identify exactly what is being overridden. An ordinary pricing approval is different from a temporary service concession. An operational exception cannot casually waive security requirements, legal obligations or contractual conditions; route those considerations to the appropriate responsible person and advisers.
An authority map explains the wider distinction between delegating a job and granting authority. An override needs its own narrow boundary inside that map.
The key question is whether people can run the business on Tuesday without reconstructing what the founder meant on Friday.
Give the operator enough data to carry out the job
Write a short record before the team begins the exceptional work:
The normal rule and the specific departure being approved.
The business reason and information available at the time.
The hours, cash or other exposure allowed.
The person responsible for tracking usage.
The expiry date, review owner and conditions for stopping early.
Documentation should solve an operating problem. Do not create a form whose contents nobody uses. A record in the existing customer workflow is enough if the required people can find it and it preserves the approval.
The founder owns the judgment. The delivery lead owns the work boundary. Finance supplies the cost analysis. The account lead communicates the agreed scope to the customer. Co-founders should agree who may approve an extension rather than leaving employees to compare competing instructions.
Hypothetical: permission for 10 unbilled hours
Assume a founder approves up to 10 unbilled delivery hours for one strategic account during November. The fictional direct labor cost is $100 an hour. The maximum direct cost is therefore 10 × $100 = $1,000.
This is a direct-cost illustration, not a complete measure of opportunity cost, profit or customer value. Other paid work may be displaced. The delivery lead should make that consequence visible before accepting the exception.
By November 20, eight hours have been used. Two hours remain under the approval. The customer then asks for another five hours. The operator cannot treat the remaining allowance as permission for all five; three hours would exceed the boundary.
At month-end, unused permission expires. If the founder wants to cover another month, review the outcomes and grant a new approval with a fresh limit. Otherwise, the team returns to normal scope and billing rules.
When repeated concessions have become hard to trace, use the Profit & Tax Leak Check to examine the decisions behind the lost margin.
Review the exception before it becomes infrastructure
The review is a decision, not a ceremonial check. Ask whether the original justification still applies, whether the concession achieved its intended purpose and whether service quality suffered elsewhere.
There are three useful outcomes: close the exception, renew it on explicit terms, or change the underlying policy. If the exception repeatedly solves the same problem, the normal process may need revision. That requires a conscious company-level decision, not an accumulation of one-off permissions.
This matters in an established service organization as much as in a startup. Investors, mentors and outside advisers may offer ideas, but employees still need an internal owner who can accept or decline the next commitment. Tools cannot supply that ownership.
Bennett's internal controls article covers the broader control environment. Here the essential control is simply knowing when exceptional permission stops.
Leave a record the next leader can understand
Do not rely on the founder remembering the conversation. Customers may remember a concession as part of the offer, while operators remember it as temporary. Record what was communicated as well as what was approved.
The CEO decision journal offers the wider practice of preserving decision context. For an override, the record should also show what triggers the next review and who tells the customer the result.
Before approving the next departure from your ordinary rules, set its end date. If nobody can explain which current exceptions remain active, bring that uncertainty to the Leak Check and review the largest exposure first.
Frequently asked questions
Does an override always mean the normal rule is wrong?
No. A specific exception can be reasonable while the ordinary rule remains useful for other customers and circumstances.
What should the founder record at approval?
The normal rule, reason, maximum exposure, responsible operator, expiry date and review owner.
Who tracks the exceptional work?
The operator responsible for delivery should track usage, with finance supporting the agreed cost measurement.
What happens when the allowance is almost used?
Escalate the next request before accepting work that would exceed the approval. Remaining permission is not an unlimited extension.
Should unused hours roll into another month?
Only if that was expressly approved. In the proposed rule, unused permission expires at the stated date.
Can repeated exceptions justify changing a policy?
Yes, but the founder should make that company-level choice separately after reviewing the evidence and consequences.
What if a customer thought the exception was permanent?
Check what was actually communicated and involve the account owner before changing expectations. An internal expiry alone does not settle contractual questions.
Which exceptions need specialist review?
Requests involving legal obligations, security requirements or contractual rights need the appropriate specialist, beyond an operational founder approval.
Sources and context
Arron on key-person dependence and Arron on financial execution support the underlying leadership position. The expiry rule and worked example are original editorial applications.