Answer
Reduce founder dependence by identifying recurring decisions, assigning qualified owners and documenting when they must escalate. Give each owner the evidence and authority needed to act, then review exceptions and returned decisions. Delegation is incomplete if the founder still needs to approve every ordinary action informally.
A founder can delegate a job title while remaining the actual approver for discounts, staffing, design priorities and customer exceptions. Start with the decisions that return to the founder, rather than drawing another organization chart.
This is a management worksheet for solar businesses. It proposes ways to organize decisions; it does not establish professional authority, legal delegation or a guaranteed business outcome.
1. Record which decisions interrupt the founder
Capture the question, requester, available evidence and reason it reached the founder. Separate genuinely exceptional decisions from routine requests that lack a clear owner. Do not classify a necessary safety or technical escalation as a failure of delegation.
2. Write a normal route for recurring questions
Choose one recurring decision. Describe when it can proceed, which evidence is required and which conditions require escalation. Avoid a rule that merely says the owner should “check with management.”
An intake-priority decision, for example, needs criteria that the operations owner can apply without guessing which salesperson the founder would favor.
3. Give the owner an explicit authority boundary
State what the person can approve, return or decline. Separate authority over commercial terms from authority over technical design. A managerial title does not replace qualifications or responsibilities attached to a professional decision.
Confirm that the person has access to the relevant records and the time to review them.
4. Require evidence with an escalation
| Escalation field | Purpose |
|---|---|
| Decision requested | Makes the question answerable |
| Current evidence | Shows what is known now |
| Options and consequences | Makes tradeoffs visible |
| Owner’s recommendation | Reveals the reasoning already completed |
| Missing information | Distinguishes uncertainty from disagreement |
| Decision deadline | Shows what becomes blocked and when |
Urgent exceptions may arrive before every field is complete. Record what is missing rather than inventing certainty to satisfy the format.
5. Separate scheduled exception review from urgent escalation
Group non-urgent recurring questions for a regular review. Keep a clear immediate route for issues whose consequences cannot wait. The schedule should fit the business; a meeting cadence is not a substitute for a response owner.
6. Teach the reasoning with examples
Have the founder explain a routine approval and an exception using the evidence available at the time. Ask the delegated owner to apply the rule to a different case and explain the result.
Illustrative example: an operations lead can reorder design work within an agreed queue, but a request that would displace a contractual milestone needs escalation. The point is the boundary, not a universal priority rule for solar projects.
7. Record changes to the authority rule
When an exception changes the normal process, update the written instruction and tell the affected roles. Retain the earlier version so a past decision can be understood in its original context.
NASA’s configuration-management guidance describes keeping information consistent with controlled changes. It is not a management standard for solar businesses, but it provides a useful reference for maintaining versioned instructions.
8. Review decisions that still return unnecessarily
Ask whether the owner lacked evidence, permission, confidence, capacity or a usable rule. Each calls for a different response. Repeating “take ownership” will not fix a missing authority boundary.
Use a handoff worksheet to record the requested decision and escalation conditions. Measure whether routine decisions can proceed within the agreed boundary while necessary exceptions still reach the right person.
Frequently asked questions
Which decisions should remain with the founder?
Define this from the business’s authority structure, risk and professional responsibilities. Strategy or unusual commitments may need executive judgment, while routine work may be delegated within an agreed boundary. A universal list would ignore how the business operates.
What if an employee keeps asking for approval?
Check whether the employee has the authority, information, qualifications and capacity to decide. Ask which part of the rule remains unclear. The repeated question may reveal an incomplete delegation rather than unwillingness to act.
How can we test delegation?
Review actual decisions after introducing the rule. Check whether ordinary cases moved, exceptions escalated correctly and later reviewers could reconstruct the reasoning. Do not measure success only by fewer messages to the founder.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.
