TemplateYear-1 Impact Report
The year-end account of what changed, covering results against baseline by department, adoption, autonomy, governance and how ready your team is to run it.
#What this is for
This is the record of the year. It answers the question your board and leadership will ask: what did we get? It shows results against the baseline in every live department, how far autonomy has progressed, how adoption held, what governance looked like under real use, and whether your own team is ready to run the program. It also sets up the Year-2 decision with evidence instead of impressions.
#When to use it
Assemble it in the last month of the engagement year and present it at the Month 12 quarterly business review, together with the Year-2 Roadmap. A short version (sections 1, 2 and 7) becomes the sponsor's year-end message to the company.
#Who's involved
- Solutions Partner writes and presents.
- Business owners validate department results.
- Finance lead confirms the value method.
- InfoSec lead confirms the governance record.
- CoE lead presents the self-sufficiency assessment with us.
#How to fill it in
- Compare actuals to the Year-1 Success Metrics set in Month 1, target by target (section 2). Do not change definitions.
- Complete department results (section 3) using the same sources as each baseline.
- Estimate value with Finance using your own cost rates and method (section 4).
- Summarize adoption, autonomy and governance (sections 5–7).
- Assess self-sufficiency with the CoE lead (section 8).
- Capture lessons (section 9). Write the executive summary last.
#The template
#1. Executive summary
| Field | Entry |
|---|
| Engagement period | Day 1 – Day 365 |
| Departments live | 7 of 7 planned |
| Clones in production | 21 |
| Workflows at Execute with approval or higher | 58% |
| Hours given back per week (run rate) | 410 |
| Governance incidents above agreed severity | 0 |
| CoE in place since | Day 252 |
| Headline | Seven departments run with AI teammates inside agreed limits; your team now runs intake, builds and governance. |
#2. Year-1 targets scorecard
| Target (set in Month 1) | Goal | Result | Met? |
|---|
| Departments live | 6–8 | 7 | Yes |
| Productivity or cost gain in each department vs. baseline | Defined per department | 6 of 7 met or exceeded | Partly |
| Workflows at Execute with approval or higher | 50% | 58% | Yes |
| Governance incidents above agreed severity | 0 | 0 | Yes |
| Champion coverage in live departments | 100% | 100% | Yes |
| Center of Excellence in place by Month 9 | Month 9 | Day 252 | Yes |
#3. Results by department
| Department | Live since | Key metric | Baseline | Year-end | Change | Target | Confidence |
|---|
| Customer Support | Day 55 | Median first-response time | 9.5 hrs | 1.4 hrs | −85% | 3 hrs | High |
| Finance | Day 105 | Days to close | 9 | 5 | −4 days | 5 | High |
| HR | Day 130 | Days to provision new hire | 4 | 1.5 | −2.5 days | 1 | Medium |
| | | | | | | |
#4. Value
Method agreed with Finance: ______________
| Value type | How measured | Year-1 total | Annualized run rate at year end |
|---|
| Hours given back | | | |
| Cost avoided | | | |
| Revenue gained or protected | | | |
| Risk reduced | | | |
Where the capacity went:
| Department | Hours / week | Redeployed to |
|---|
| Support | 120 | Proactive account reviews; complex case team |
#5. Adoption
| Department | Users in scope | Weekly active % | Avg Power Rating | Trend (last quarter) | Champion |
|---|
| | | | | |
Training: __ executives fluent · __ Champions certified · __ users trained · __ builders certified
#6. Autonomy progression
| Level | Workflows at Day 90 | Day 180 | Day 270 | Day 365 |
|---|
| 1 Assist | | | | |
| 2 Recommend | | | | |
| 3 Execute with approval | | | | |
| 4 Execute within limits | | | | |
| 5 Orchestrate | | | | |
Promotions approved __ · declined __ · demotions ____ (with reasons in appendix)
#7. Governance record
| Item | Year 1 |
|---|
| Connections approved by InfoSec | |
| Audit log reviews completed (of planned) | |
| Overrides and override rate | |
| Incidents by severity | |
| Risks opened / closed / open at year end | |
| Skill changes through change control | |
| Audit evidence packs produced | |
InfoSec statement (2–3 sentences):
#8. Self-sufficiency assessment
| Capability | Owned by client team? | Evidence | Gap |
|---|
| Intake and prioritization | Yes | CoE ran intake since Day 300 | |
| Building skills in SkillForge | Mostly | 6 skills shipped by client builders | Complex ERP skills still paired |
| Promotion evidence and reviews | | | |
| Audit log review and evidence | | | |
| Training and Champions | | | |
| Optimization reviews (Power Rating, cost) | | | |
| Runbooks complete and verified | | | |
#9. Lessons
| What worked | What we would change | Advice for Year 2 |
|---|
| | |
#Good looks like
- Every Month-1 target is reported, including the ones missed, with the reason.
- Value uses your Finance team's method and is signed by Finance.
- Department results use the same metric definitions and sources as the baseline.
- Governance and self-sufficiency get as much space as results. Durable value depends on both.
- The capacity story is concrete: hours, and what people now do with them.
- Common mistake: a highlight reel. Leaders make better Year-2 decisions from an honest picture.
#How Clone helps
The Project Clone compiles the report from a year of portal data: success metrics, adoption, autonomy history, decisions and deliverables. The GRC Clone prepares the governance record. The Enablement Clone supplies training and Champion figures and turns the approved summary into the sponsor's year-end message. The report is stored in the portal as the Year-1 Impact Report deliverable and linked from the Year-2 Roadmap.
#Sign-off
| Role | Name | Date | Decision |
|---|
| Executive sponsor | | | Accepted |
| Finance lead | | | Value method confirmed |
| InfoSec lead | | | Governance record confirmed |
| CoE lead | | | Self-sufficiency assessment agreed |
| Solutions Partner | | | Issued |