Seven national metrics · six divisions · forty-eight regions · July 2026 to June 2027
Help DWR track the effectiveness of our programs, give regions and divisions their percent-to-goal against targets, and identify where additional regional support is needed.
Terminology is reproduced verbatim from the client outline. No measure below is a decision.
The purpose statement and the objectives are two different problems. The percent-to-goal half is built — it is the Dashboard and the Map. The objectives are the work of the call.
Seven objectives, each expressed in the goal structure already used for the FY27 individual staff goals — objective, metric, measure of success, source. The useful question for each: would you act differently if this number moved?
Role stability
Consistency across regions is the stated aim, so the measure has to be about coverage and continuity, not activity.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| Share of regions with the DWE(S) position filled | Staffing roster | Region | Measurable now |
| Median time in role | Staffing roster | Region | Measurable now |
| Positions changing occupant during the fiscal year | Staffing roster | Division | Measurable now |
| Days a position sits vacant before it is filled | Staffing roster | Region | Needs a field or a report |
Watch out: This is the one objective that is already a number. Everything else needs a decision first.
Role stability
A plan is a deliverable, not a percentage. Track that it exists, then track whether people complete it.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| Onboarding plan written and approved | Program milestone | National | Milestone first |
| New DWEs completing onboarding within 90 days | Learning record system | Region | Needs a field or a report |
| Time from start date to first independent assignment | Volunteer Connection | Region | Needs a field or a report |
Watch out: Milestone first. A completion rate means nothing until there is a defined plan to complete.
Role stability
Two different things: a one-time refresh, and an ongoing currency measure.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| Revised curriculum published | Program milestone | National | Milestone first |
| DWEs whose required training is current | Learning record system | Region | Measurable now |
| Course completion rate for the role curriculum | Learning record system | Region | Measurable now |
| Post-training feedback score | Survey | National | Needs a field or a report |
Watch out: Currency is the durable metric. Completion spikes once and then flatlines.
Capacity building · Steady State
The role does not exist yet, so there is nothing to count until it does.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| National Volunteer Lead identified and in place | Program milestone | National | Milestone first |
| Regions with an identified volunteer leadership counterpart | Volunteer Connection | Region | Needs a field or a report |
| Regions engaged by the national lead each quarter | Contact log | Division | Needs a field or a report |
Watch out: Coverage is the honest measure once the role is filled. Contact counts reward activity, not effect.
Capacity building
This one already has a working tracker. Priority-position gaps are measured today.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| Fill rate for priority positions | Volunteer Connection | Region | Measurable now |
| Gap size by position group | Volunteer Connection | Region | Measurable now |
| Recruitment cycle time for priority positions | Volunteer Connection | Region | Needs a field or a report |
| Regions with a joint volunteer-services recruitment plan | Program milestone | Region | Needs a field or a report |
Watch out: The responder-intent tracker already reports gaps by region and position group. Reuse it rather than building a second one.
Capacity building · Grey Skies
Countable in principle, but only if tier is actually recorded somewhere.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| Promotions from T-3 to T-2 in the period | Volunteer Connection | Region | Needs a field or a report |
| T-3 candidates identified against promotions completed | Volunteer Connection | Region | Needs a field or a report |
| Median time held at T-3 before promotion | Volunteer Connection | Division | Needs a field or a report |
Watch out: Open question for the call: is tier stored as a field today, or inferred from deployment history?
Capacity building
Understanding is not directly measurable. Its proxies are training and applied planning.
| Candidate measure | Where it would come from | Level | Readiness |
|---|---|---|---|
| DWEs completing Community Mobilization training | Learning record system | Region | Measurable now |
| Regions with a capacity plan aligned to Community Mobilization | Program milestone | Region | Milestone first |
| Priority communities with an assigned mobilization approach | Community Mobilization tooling | Chapter | Needs a field or a report |
Watch out: Beware proxy drift: a training completion rate measures attendance, not understanding.
Every region in the division, with the national line for context.
Own numbers against target, and where it sits among peers.
Only where a measure genuinely exists at chapter level. Most do not.
One link that rescopes, plus a print view that becomes the handout.
Decide before building: whether a region sees other regions' numbers. That is a governance choice, not a technical one, and far cheaper to settle now.
Reproduced exactly as written and deliberately not expanded — guessing at a role acronym in front of regions is worse than leaving it short. Anything a reader outside the program would not recognise on first read should be spelled out before publication.