Use this as a working artifact, not a reading assignment. First check whether the problem matches your situation. Then copy the template structure into the tool your team already uses. If you use AI, give it approved source material and keep a human review step before making decisions.
- A clearer version of the problem this template is meant to solve.
- A first draft you can review with the requester, reviewer, leader, or owner.
- A short list of missing information, assumptions, and next actions.
Measurement stays thin when the team starts with available data instead of the decision that needs evidence.
Measurement gets stronger when we start with the decision the evidence needs to support. Completions can be part of the story, but they should not be the whole story.
- What decision would this evidence help a leader make?
- What would someone do differently if the learning worked?
- What signal is credible enough for the stakes of this program?
This sets up the evidence layer of the system. We are deciding what proof is useful before launch, so measurement becomes part of the design instead of a report we scramble to build later.
- A leader asks whether training worked, but the team only has completions.
- The team needs evidence tied to readiness, behavior, adoption, manager feedback, or workflow impact.
- A program needs a realistic measurement plan before launch.
- The program goal or business question leaders are asking.
- The behavior, task, or workflow the learning is supposed to improve.
- Any data the team can realistically collect before and after launch.
Start small enough that the work can move today.
- Write the decision the evidence needs to support before choosing data.
- Choose one behavior signal and one readiness signal.
- Name what the evidence can prove and what it cannot prove.
- Decide when the team will review the evidence after launch.
Use this when you need the words.
- We can report completions, but that will not answer the whole question.
- Before we build the measurement plan, what decision are we trying to make with the evidence?
- Once we know that, we can choose the smallest credible signal instead of building a dashboard nobody trusts.
Use the answers to choose the next move.
Use completion, access, and a lightweight confidence check.
Use scenario practice, role play, scorecards, or manager observation.
Use behavior signals, workflow data, manager feedback, and follow-up evidence.
Start with value evidence: readiness, behavior, adoption, and workflow impact.
Choose a smaller credible proxy and name the evidence limit.
- The team has not agreed what decision the evidence should support.
- The program is too early for measurement design and still needs problem discovery.
- The only available data would create a false sense of proof.
Copy this structure into the tool you already use.
Paste this into the tool next to the work.
Blank version
# Measurement Planning Worksheet
| Field | Notes |
| --- | --- |
| Decision | |
| Behavior | |
| Readiness | |
| Adoption | |
| Workflow impact | |
| Evidence limit | |Completed example
# Measurement Planning Worksheet example
| Field | Example |
| --- | --- |
| Decision | Decide whether new hires are ready to handle quote exceptions without manager intervention. |
| Behavior | New hires identify the exception path and choose the right approval route. |
| Readiness | Scenario scorecard for three quote exceptions during onboarding. |
| Adoption | Usage of the job aid during first-week quote tasks. |
| Workflow impact | Fewer approval reroutes and fewer manager corrections on first submitted quotes. |
| Evidence limit | This cannot prove revenue impact by itself. It can show readiness and cleaner first-pass work. |Write the decision first: what will we do differently if the evidence says this is working or not working?
Use Forms, Excel, Sheets, Power BI, Looker Studio, or a shared scorecard to collect one behavior signal and one manager observation.
Use AI to draft evidence options, manager observation questions, role-play scoring criteria, and a short results summary from approved source data.
Use these when AI can help shape the first draft.
Use these as starting points, then adjust them to your approved tool, source material, and review standard.
Draft evidence options and limits
Use this when a leader asks whether training worked and the team needs better options than completions alone.
I am planning measurement for an L&D program.
Program context:
[paste context here]
Help me choose practical evidence.
Return:
1. The decision the evidence could support
2. Three possible readiness signals
3. Three possible behavior signals
4. One manager observation question
5. One workflow-impact signal
6. What this evidence can prove
7. What this evidence cannot prove
8. A simple 30-60 day follow-up plan
Rules:
- Do not claim ROI unless the source data supports it.
- Keep the plan realistic for a busy L&D team.
- Mark any missing source data as "Needs confirmation".Validation checklist
- The evidence connects to a decision, not just a dashboard.
- The plan includes at least one signal beyond completion.
- The evidence limit is stated clearly.
- The collection method is realistic for the team to maintain.
- Check every fact against an approved source.
- Mark anything AI guessed, inferred, or could not confirm.
- Remove private, sensitive, or customer-specific details that should not be in the working file.
- Confirm the right human owner approves the final decision.
- Review tone, accessibility, and learner impact before anything goes live.
Platform-specific starters
ChatGPT GPT-5 family
Use an outcome-first prompt with the job, source material, constraints, and the exact artifact you want back.
I am using the Measurement Planning Worksheet for an L&D workflow.
Goal: Help me turn the rough notes below into a practical first draft of the template.
Context: Measurement stays thin when the team starts with available data instead of the decision that needs evidence.
Use these template fields: Decision, Behavior, Readiness, Adoption, Workflow impact, Evidence limit.
Rules:
- Ask clarifying questions if the notes are too thin.
- Do not invent facts, policy details, metrics, or source material.
- Separate what is known from what needs human confirmation.
- Keep the output practical enough to review in a working meeting.
Rough notes:
[paste notes here]
Return:
1. Completed first draft
2. Missing information
3. Risks or assumptions to review
4. One recommended next actionClaude 4 family
Use clear XML-style sections so Claude can keep context, task, constraints, and output format separate.
<context>
I am using the Measurement Planning Worksheet for an L&D workflow.
Measurement stays thin when the team starts with available data instead of the decision that needs evidence.
</context>
<source_notes>
[paste notes here]
</source_notes>
<task>
Turn the source notes into a practical first draft using these fields: Decision, Behavior, Readiness, Adoption, Workflow impact, Evidence limit.
</task>
<constraints>
Do not invent facts, policy details, metrics, or source material.
Separate what is known from what needs human confirmation.
Flag anything that changes scope, ownership, risk, or decision rights.
</constraints>
<output_format>
1. Completed first draft
2. Missing information
3. Review risks
4. Recommended next action
</output_format>Gemini 3 family
Use a structured task with an example pattern. For Obsidian context, use approved excerpts, Drive exports, Google Docs, or NotebookLM.
Task: Complete a first draft of the Measurement Planning Worksheet from the notes provided.
Template fields:
- Decision: What decision does the evidence need to support?
- Behavior: What behavior should change in the work?
- Readiness: What practice, scenario, or check shows readiness before live work?
- Adoption: What signal shows people are using the workflow or support?
- Workflow impact: What operational signal might move if this improves?
- Evidence limit: What can this evidence not prove?
Example pattern:
Field: Decision
Good answer: Decide whether new hires are ready to handle quote exceptions without manager intervention.
Rules:
- Use only the notes provided.
- If information is missing, write "Needs confirmation".
- Keep the output concise and reviewable.
- End with the next best action.
Notes:
[paste notes here]Microsoft 365 Copilot
Use goal, context, expectations, and source. For Obsidian context, use approved excerpts, Word summaries, OneDrive files, SharePoint pages, Teams context, or Outlook threads.
Goal: Create a first draft of the Measurement Planning Worksheet.
Context: Measurement stays thin when the team starts with available data instead of the decision that needs evidence.
Source: Use the selected document, meeting notes, request thread, or pasted notes as the only source.
Expectations:
- Fill these fields: Decision, Behavior, Readiness, Adoption, Workflow impact, Evidence limit.
- Keep uncertain items marked as "Needs confirmation".
- Do not add facts that are not in the source.
- Summarize the top three review questions for the team.
Output: Return the completed draft, missing information, and one recommended next action.