AG-G1Self-Assessment Guide
Is Your Work Pack Territory?
August 2026
~10 min
4 sections
Not every category of work belongs in a pack. This guide helps you determine whether a specific area of work is ready to be delegated. Work through each section and tally your answers to reach a score band. A score does not guarantee success or failure; it gives you a starting point for a conversation about where delegation is likely to go well and where you need more setup first.
1. Frequency and volume
How often does this work occur, and at what scale?
How often does this work happen?
Daily · Weekly · Monthly · Rarely
Is the volume of instances consistent enough to define patterns?
Yes · Somewhat · No
Would a human do this same task more than three times before it changed significantly?
Yes · Unlikely · No
High frequency + stable volume = strong signal. Rare or highly variable work needs a different starting point.
2. Structure and repeatability
Can the steps be written down without too many branches?
Could you write a one-page runbook for this work that a new person could follow?
Yes · With effort · No
How many decision branches does the work typically involve?
1-3 · 4-8 · 8+
Do exceptions happen more than 20% of the time?
Never · Sometimes · Regularly
Is the output format stable — the same shape every time?
Yes · Mostly · No
High structure means a pack can follow explicit steps. Low structure means the work requires judgment the pack may not have yet.
3. Data and inputs
What does the work need in order to start, and is it accessible?
Are the inputs for this work digital and already accessible in a system?
Yes · Partially · No
Does someone need to gather or interpret inputs before the work can begin?
Never · Sometimes · Always
Is the data clean — consistent field names, formats, and sources?
Yes · Mostly · No
Does the work depend on context that lives only in someone’s head?
No · Sometimes · Yes
Clean, accessible inputs are the single biggest enabler of successful delegation. Missing or ambiguous inputs stall packs before they start.
4. Stakes and review
What happens if something goes wrong, and who needs to be in the loop?
What is the cost of an error in this work?
Low · Medium · High
Does this work touch external parties (clients, vendors, public-facing content)?
No · Sometimes · Yes
Is there a human review step before anything leaves your organization?
Yes, always · Sometimes · No
If a pack made a mistake on this, could it be reversed within an hour?
Yes · With effort · No
High-stakes work is not off-limits, but it needs a clear approval gate. The proposal-gate-commit loop exists exactly for this: the pack prepares, a human approves, then it executes.
What your answers suggest
Strong fit
Most answers in column 1
This category of work is ready for a pack now. The inputs are accessible, the steps are repeatable, and the review gates are in place. Start with a narrow scope, watch the first ten cycles, then expand.
Emerging fit
Mixed answers across columns
You have enough structure to start, but some prerequisites are missing. Identify the column-3 answers first and fix the underlying gap — usually: clean inputs, a written runbook, or a defined review step.
Not yet
Mostly column 3
This work needs more scaffolding before delegation will hold. The most common blockers are tacit knowledge that has not been written down, and data that is not yet in a system a pack can read.
Next steps
If you scored Strong or Emerging, the next step is to identify which pack type fits the work. Most work in small organizations falls into one of the core packs: Operations, Client Delivery, or Admin. If your work does not map to an existing pack, Custom Build is the path.
If you scored Not Yet, the most useful action is to write the runbook first. Put the steps on paper, identify what decisions get made and why, and locate where the data currently lives. Once you can answer those questions, revisit this guide.
If you are unsure, start a conversation with us. The first thing we do in every engagement is walk through exactly this assessment with you.