How to Delegate Work Without Losing Accountability
For leaders and managers, a practical guide to delegating work with clear decision authority, checkpoints and escalation routes. Use a working agreement to preserve accountability without reapproving routine decisions.
On this page
Consider an illustrative handover: a founder asks a delivery manager to “prepare next week’s schedule”, but still approves every staffing change. The manager has received a task, not much authority. A different handover authorises the manager to allocate qualified staff within agreed capacity, while reserving changes to client commitments for the founder.
To delegate work without losing accountability, agree the outcome, the decisions each person can make and how exceptions will reach someone authorised to resolve them. Put those agreements into a short delegation contract with checkpoints. The aim is usable discretion, not a new approval process for every routine action.
Decide what you are delegating#
Choose one recurring responsibility, such as delivery scheduling. Write down what successful work must achieve and how you will recognise acceptable completion.
Then identify the decisions hidden inside it. Allocating a qualified consultant to an assignment is different from moving another client’s promised delivery date. “Own the schedule” does not distinguish them.
Use these working definitions:
- Responsibility: the work or obligation assigned to someone.
- Authority: the decisions and commitments they may make.
- Accountability: what they must answer for, including their decisions, results and adherence to agreed boundaries.
These are operating terms, not universal legal definitions. Retained ownership and assigned accountability can coexist. The US Government Accountability Office’s 2025 Green Book, paragraphs 3.07 and 5.01–5.03, says key role-holders retain ownership of their overall responsibilities when assigning internal-control responsibilities, while personnel are held accountable for their assigned responsibilities. Its scope is US federal internal control; it is not a universal legal rule for private businesses. (gao.gov)
For this handover, make the division explicit: the manager answers for scheduling and timely exception reporting; the founder answers for retained commitments, adequate resources and reserved decisions.
Build a delegation contract with checkpoints#
Here, “contract” means a working agreement, not a legal instrument. The template below is a proposed practical method; its scheduling details are illustrative.
Complete it together using the current workflow, client commitments, staffing availability, competence requirements and restrictions. First settle the outcome and authority boundary. Then agree the information, escalation arrangements and checkpoints needed to support them.
Copy the table and replace the examples with your own specifics—including actual names wherever a role is shown.
| Field | What to agree | Illustrative scheduling example |
|---|---|---|
| Outcome and acceptance standard | What must be achieved, by when, and what counts as acceptable work? | Publish next week’s schedule by Friday noon, covering agreed assignments with qualified staff, within available hours and existing client commitments. |
| Accountability on each side | What must the delegate and delegator each answer for? | Manager: accurate allocations, current records and timely risk reporting. Founder: resource adequacy, reserved commitments and decisions on escalated conflicts. |
| Permitted and reserved decisions | What can the delegate decide independently? What requires approval? | Manager may rearrange qualified staff within agreed capacity, without further approval. Founder approval is required for changes to scope, price, promised dates or additional spending. |
| Readiness and support | What competence, capacity, access and help are required? | Confirm scheduling competence and protected time; grant edit access; arrange a supported first cycle and a contact for qualification questions. |
| Required information and location | Which records govern the work, and who keeps them current? | Manager maintains the shared schedule. Account leads maintain client commitments; staff update availability. Link those records rather than create competing copies. |
| Exception triggers | What makes a decision request necessary? | No feasible qualified allocation; a promised date is at risk; or the solution requires a reserved decision. Escalate when identified, not only after delivery fails. |
| Escalation route and response deadline | Who can decide, through which channel, by when, and who is the authorised backup? | Send the founder a flagged request in the shared work record. Agree a response within four working hours, or an earlier deadline where needed. If unavailable or the deadline is missed, contact the named director with authority over that decision. |
| Safe action while waiting | What may continue, and what must not happen? | Flag affected work, continue unaffected scheduling and make no promise about a revised client date. If neither approver responds, keep the blocker visible; do not treat silence as approval. |
| Checkpoints and evidence | When will progress be reviewed, and what will be inspected? | During the first two weekly cycles, review the schedule, capacity conflicts, outstanding decisions and delivery results at an agreed weekly meeting. Escalate urgent exceptions separately. |
| Review and authorised revision | Who may change the agreement, and how will changes be recorded? | Founder and manager review after two cycles. Record approved changes to authority, support or escalation arrangements, including who authorised them and when they take effect. |
Written permission is only part of the handover. In their 1997 theoretical paper, Formal and Real Authority in Organizations, Philippe Aghion and Jean Tirole distinguish the formal right to decide from effective control over decisions. (people.duke.edu) For this agreement, check that the colleague can obtain the necessary information and genuinely exercise the discretion granted.
This guide proposes a four-part test for escalation: specify what triggers a request, who can decide, when a response is needed and what remains permitted meanwhile. Add an authorised backup where absence would leave the work stranded.
Before starting, both people should be able to distinguish:
- Act: make a decision within the agreed boundary.
- Report: record or communicate information without waiting for permission.
- Seek approval: request a decision outside that boundary.
If they disagree about a likely situation, repair the agreement. Missing capacity, access or authority is a readiness problem, not something a completed table resolves.
Work through an exception before the handover#
Rehearse one difficult situation before transferring the workflow.
In the scheduling example, a qualified consultant becomes unavailable. The manager checks other allocations, but covering the affected assignment would require moving another client’s promised delivery date. That is outside the manager’s authority.
The decision request might read:
Decision needed by noon: The qualified consultant for Client A’s Thursday assignment is unavailable. Reallocating the consultant from Client B would put B’s Friday delivery at risk. No other qualified internal capacity is available.
Options: Authorise additional qualified capacity, subject to availability and cost; or approve approaching one client about a revised commitment.
Recommendation: Explore additional capacity first. Please confirm the maximum spend I may commit if suitable cover is available.
Meanwhile: I have flagged both assignments, continued unaffected scheduling and made no revised promise to either client.
If the founder is unavailable or misses the agreed response deadline, the manager uses the backup route. The backup must hold the relevant authority; being reachable is not enough.
If neither approver responds, the affected work remains visibly blocked and the manager continues only what the agreement permits. Their authority does not silently expand. The founder must also fulfil their side of the agreement: respond, route the decision appropriately or arrange authorised cover.
The rehearsal is complete when both parties know the next action—not merely that they should “communicate”.
Review outcomes without taking the work back#
Separate scheduled oversight from event-triggered escalation. A weekly review can inspect delivery and recurring problems; a threatened commitment may need a decision before then. The example’s two-cycle review period is a starting proposal, not a universally optimal cadence.
Review delivery results, unresolved exceptions and decisions made outside the boundary. Do not routinely reapprove choices already delegated. Examine what each person could control before deciding whether a problem reflects judgement, missing support or a delayed reserved decision.
To assess the handover, consider tracking:
- Time spent obtaining routine approvals.
- Avoidable referrals: requests already answerable within the agreed authority and available information.
- Time from exception request to authorised decision.
- On-time accepted delivery against the original promised date, with authorised revisions recorded separately.
Do not count appropriate escalation as failure. Fewer reports could mean clearer decisions—or problems going unreported. Compare similar work and note changes in workload, complexity, staffing and support before attributing improvement to the agreement.
At review, retain, widen or narrow the authority based on what happened. Record the authorised change rather than leave the next person to infer it.
Choose one consequential recurring responsibility and complete the agreement with the intended delegate before the next handover. Start with a bounded scope they can genuinely own, including the decisions they may make without asking again.
