Setup Daily Triage Practice

What follows is a start to refine your process. It translates the concept into a repeatable management practice. It takes triage out of abstraction and places it into the daily rhythm of planning, delegation, communication, review, and continuous improvement. Used consistently, it helps a team connect the day’s work to the year’s priorities, and the year’s priorities to the wider growth and health of the business.

Purpose

This is the daily process for triaging work so that effort is aligned to strategic objectives, the annual plan, KRAs, operational delivery, and capacity building. Its purpose is to ensure that work is not handled merely in the order it arrives, but in the order that best serves value, risk, continuity, and growth.

Scope

This applies to managers, team leaders, project leads, and any staff member responsible for planning, prioritising, delegating, or reviewing work. It is intended for daily use, and for adaptation into weekly and monthly review rhythms where required.

Core Principle

All work is to be triaged against consequence, value, risk, dependency, and available capacity. Priority is not determined by noise, habit, or personal preference alone. Priority is determined by what most needs attention in order to protect delivery, build capability, and serve the wider direction of the business.

Reference Points

Before triaging work, the person responsible must interpret tasks in relation to the following reference points:

Strategic Objectives, including the wider Theory of Growth of the business.

Organisational Objectives, including the Annual Plan and key projects.

KRAs, KPIs, role accountabilities, and immediate operational commitments.

Existing promises, deadlines, dependencies, and stakeholder commitments.

Definitions

Operational Business refers to work that supports current delivery, continuity, servicing, execution, production, and immediate commercial activity.

Building Capacity refers to work that develops future capability, including people development, systems improvement, documentation, process reliability, infrastructure, leadership capability, and training.

Triage refers to the disciplined sorting of work according to value, risk, urgency, dependency, and available capability.

Promise refers to a clear commitment stated as who is doing what, for whom, by when.

Roles and Responsibilities

The Manager or Team Lead is responsible for ensuring that triage occurs, that priority is clear, that delegated items are refined into promises, and that follow-up rhythms are maintained.

The Team Member is responsible for maintaining visibility of assigned work, surfacing breakdowns early, and renegotiating commitments when required.

The Project Lead, where applicable, is responsible for ensuring that project priorities, dependencies, and deadlines are visible and incorporated into daily triage.

Procedure

Step 1, Capture the Work

At the start of the day, or at the agreed triage time, list all current actionable items. This includes tasks, requests, issues, decisions, follow-ups, delegated work, and pending commitments.

Only actionable items should appear on the list. Vague concerns or unclear requests must first be clarified before being prioritised.

Step 2, Check Alignment

Review each item against role responsibilities, strategic objectives, annual priorities, KRAs, and immediate delivery obligations.

If an item is unclear, out of scope, misdirected, duplicated, or no longer relevant, it must be clarified, redirected, deferred, or removed before further triage takes place.

Step 3, Sort the Work into Two Categories

Each item must be placed into one of the following categories:

• Operational Business
• Building Capacity

This distinction must be made deliberately. Capacity-building work is not to be ignored simply because operational work feels more immediate.

Step 4, Assess Value

• Assess the value of each item. Consider whether it:
• Advances a strategic objective
• Supports an annual priority or KRA
• Protects or generates revenue
• Strengthens delivery quality
• Builds people, systems, or capability
• Removes friction, waste, or repeated breakdowns
• Improves client, stakeholder, or team outcomes
• Record whether the value is high, medium, or low.

Step 5, Assess Risk

• Assess the risk associated with each item. Consider:
• Deadline pressure
• Client consequence
• Dependency on other work
• Compliance, safety, or legal implications
• Reputational exposure
• Operational disruption
• Impact of delay or non-completion
• Record whether the risk is high, medium, or low.

Step 6, Set Priority

• Prioritise work using combined value and risk judgement.
• Items with high value and high risk are to be handled first.
• Items with high value and lower immediate risk are to be scheduled deliberately and protected.
• Items with high risk but lower value are to be contained, escalated, or resolved as appropriate.
• Items with low value and low risk are to be deferred, batched, delegated, or removed.

Where judgement is uncertain, the manager should test the task against the question, “What most affects delivery, growth, trust, or future capability if left undone?”

Step 7, Decide the Mode of Action

For each prioritised item, determine whether it should be:

• Done personally
• Delegated
• Scheduled for later in the day or week
• Escalated
• Declined or removed

This decision must take into account skill, authority, workload, development opportunity, and deadline.

Step 8, Refine into a Promise

Any item that is prioritised for action or delegation must be converted into a clear promise:

Who is doing what, for whom, by when.

Where useful, the promise should also include the required quality standard, relevant dependencies, and the check-in point.

No delegated item should remain vague.

Step 9, Communicate and Calendar

Communicate delegated or shared commitments clearly. Enter key actions, deadlines, and check-ins into the calendar or agreed task system.

Communication rhythms should be short, regular, and purposeful. This may include daily check-ins, weekly one-to-ones, project reviews, or brief status updates.

The purpose is to maintain visibility, surface risk early, and protect deliverability.

Step 10, Review at End of Day

At the end of the day, review:

• What was completed
• What remains incomplete
• What changed in value or risk
• What breakdowns occurred
• What must be renegotiated

Any incomplete promise must be accounted for explicitly. Silence is not acceptable as a form of managing missed commitments.

Step 11, Renegotiate Where Required

Where a commitment cannot be fulfilled as promised, the responsible person must communicate early and renegotiate the promise.

This renegotiation should include:

• What changed
• What impact this creates
• The new proposed commitment
• Any support or decision required

Step 12, Improve the System

At the close of the day, or during the weekly review, reflect on the triage process itself.

Consider:

• What repeatedly gets left too late
• What work should be systemised
• What recurring issues suggest a capacity gap
• What delegation failures indicate unclear expectations
• What meetings, rhythms, or structures need improvement

Use these insights to strengthen future triage and overall management hygiene.

Daily Output Standard

At the end of the triage process, the responsible person should have:

• A clear prioritised list
• A visible distinction between operational and capacity work
• Named owners for each key item
• Clear promises for delegated work
• Scheduled review or check-in points
• A basis for end-of-day accountability

Escalation Rule

If a task has high strategic consequence, high operational risk, or cross-functional dependency beyond the authority of the person triaging it, it must be escalated promptly to the appropriate manager or decision-maker.

Review Rhythm

This should be applied daily.

A weekly review should be used to identify patterns, recurring bottlenecks, overdue capacity-building work, and opportunities to strengthen systems, capability, and delegation.

Expected Outcome

When followed consistently, this SOP creates a more mature work pattern. Teams become less reactive, more aligned, and more trustworthy. Daily work gains a clearer connection to strategic direction. Delegation becomes cleaner. Breakdown management improves. Capacity-building work stops being endlessly postponed. Over time, the organisation moves from coping through effort to performing through design.

Daily Triage SOP

1. Capture all actionable work.
2. Check each item against strategic objectives, annual plan, KRAs, and operational commitments.
3. Sort each item into operational business or building capacity.
4. Assess value and risk for each item.
5. Prioritise using combined value and risk judgement.
6. Decide whether to do, delegate, schedule, escalate, or remove.
7. Convert priority items into promises, who is doing what, for whom, by when.
8. Communicate clearly and calendar deadlines and check-ins.
9. Review progress at day’s end.
10. Renegotiate any incomplete promises and capture learning for improvement.