Example

Vague LMS Report Request to Decision-Ready Report Definition

Turn a vague monthly completion request into a report definition that names the decision, audience, metric, source field, cadence, owner, and caveat.

Download PDF Use the related template All examples

The messy version

Vague report request

Can you send monthly completions for the new program? Leadership wants to know how it is going.

What to notice

Inspect the system signal before fixing the artifact.

The request asks for a metric before naming the decision.
Completion might mean assigned, launched, started, completed, passed, overdue, or current depending on the LMS.
The audience is leadership, but the action they can take is not named.
The caveat needs to travel with the report so completion is not treated as behavior proof.

The problem this shows

The messy version is usually not a writing problem.

LMS report requests sound simple until the team needs to explain what the number means and what decision it should support.

What you should take away

Look for the decision the artifact needs to support.

Write the caveat before you build the report. If the caveat feels important, it belongs on the report.

Aha moment

The shift is small, but it changes the conversation.

A report is not ready until the decision, audience, metric definition, source field, cadence, owner, and caveat are named.

15-minute meeting move

Ask what decision will change if the number is high, low, flat, or missing.

Office/workspace move

Store report definitions in Microsoft Lists, SharePoint, Excel, Google Sheets, or a data dictionary next to the report links.

Out-of-box move

Put the caveat directly on the report so people cannot separate the number from its limit.

AI-assisted move

Use AI to draft report-definition questions and spot ambiguous metric language from approved notes. Validate every field with the LMS owner.

Three ways to build it

Use the lightest setup that still changes the work.

These are not separate philosophies. They are three levels of the same operating move.

Manual version

Use one report-definition card before opening the LMS. If the decision, metric definition, source field, and caveat are blank, the report is not ready.

Microsoft 365 or Google Workspace version

Create a definition library in Microsoft Lists, SharePoint, Excel, or Google Sheets. Link each report to its definition and review date.

AI-assisted version

Ask AI to turn the request into a report definition draft, identify ambiguous metric language, and create questions for the LMS owner. Do not let AI invent source fields.

Final usable artifact

Report Definition Card

This is the artifact pattern to recreate in a document, spreadsheet, List, Sheet, or working note.

Report name	Decision supported	Audience	Action threshold	Metric definition	Includes	Excludes	Source field	Cadence	Owner	Caveat	Review date
New program readiness follow-up	Where regional leaders focus coaching	Regional leaders	Any region below 85 percent completion or below usually on manager observation	Completed assigned module and passed readiness scenario	Assigned learners in active regions	Exempt learners, archived assignments, test users	LMS completion status; readiness scenario score; manager observation scorecard	Monthly for 90 days	Learning operations lead	Completion shows exposure and readiness check result. It does not prove behavior change by itself.	2026-06-30

Copy-ready artifact

Paste this next to the work.

# Report Definition Card

| Field | Definition |
| --- | --- |
| Report name |  |
| Decision supported |  |
| Audience |  |
| Action threshold |  |
| Metric definition |  |
| Includes |  |
| Excludes |  |
| Source field or export |  |
| Cadence |  |
| Owner |  |
| Caveat |  |
| Review date |  |

Rule:
A report is not decision-ready until the definition and caveat are visible.

Prompt starters

Use AI to inspect the example, not make the decision.

These prompts work best when you provide approved notes and ask the model to separate known facts, assumptions, missing information, risks, decisions, and next actions.

ChatGPT GPT-5 family

Use an outcome-first prompt with the job, approved source material, constraints, and the exact artifact you want back.

I am working on Turn an LMS report request into a decision-ready definition for an L&D system problem.

Goal: Help me turn the notes below into a practical next move.

Context: Use this when a report request starts with a metric and needs the decision, audience, source field, cadence, owner, and caveat defined.

Use these working fields: report name, decision supported, audience, action threshold, metric definition, source field, cadence, owner, caveat.

Rules:
- Use only the source notes I provide.
- Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
- Separate known facts, assumptions, missing information, and next actions.
- Flag anything that needs requester, reviewer, leader, legal, compliance, LMS owner, or manager confirmation.
- Keep the output practical enough to review in a working meeting.

Source notes:
[paste approved notes here]

Return:
1. Report definition card
2. Known facts
3. Assumptions
4. Missing information
5. Ambiguous metric language
6. Questions for the LMS owner
7. Recommended next action

Claude 4 family

Use XML-style sections so context, source material, task, constraints, and output format stay separate.

<context>
I am working on Turn an LMS report request into a decision-ready definition for an L&D system problem.
Use this when a report request starts with a metric and needs the decision, audience, source field, cadence, owner, and caveat defined.
</context>

<source_notes>
[paste approved notes here]
</source_notes>

<task>
Turn the source notes into a practical next move using these working fields: report name, decision supported, audience, action threshold, metric definition, source field, cadence, owner, caveat.
</task>

<constraints>
Use only the source notes provided.
Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
Separate known facts, assumptions, missing information, risks, and next actions.
Flag anything that changes scope, ownership, evidence, risk, or decision rights.
</constraints>

<output_format>
1. Report definition card
2. Known facts
3. Assumptions
4. Missing information
5. Ambiguous metric language
6. Questions for the LMS owner
7. Recommended next action
</output_format>

Gemini 3 family

Use a clear task, labeled input, and one example pattern. For Obsidian context, use approved excerpts, Drive exports, Google Docs, or NotebookLM source sets.

Task: Help me make progress on Turn an LMS report request into a decision-ready definition from the notes provided.

Context: Use this when a report request starts with a metric and needs the decision, audience, source field, cadence, owner, and caveat defined.

Working fields:
- report name
- decision supported
- audience
- action threshold
- metric definition
- source field
- cadence
- owner
- caveat

Example pattern:
Field: Missing information
Good answer: Name the specific information to confirm, who can confirm it, and why it affects the next decision.

Rules:
- Use only the source notes provided.
- If information is missing, write "Needs confirmation".
- Keep the output concise and reviewable.
- End with the next best action.

Source notes:
[paste approved notes here]

Output format:
1. Report definition card
2. Known facts
3. Assumptions
4. Missing information
5. Ambiguous metric language
6. Questions for the LMS owner
7. Recommended next action

Microsoft 365 Copilot

Use goal, context, source, expectations, and output. For Obsidian context, use approved excerpts, Word summaries, OneDrive files, SharePoint pages, Teams context, or Outlook threads.

Goal: Help me make progress on Turn an LMS report request into a decision-ready definition.

Context: Use this when a report request starts with a metric and needs the decision, audience, source field, cadence, owner, and caveat defined.

Source: Use the selected document, meeting notes, spreadsheet, email thread, SharePoint file, or pasted notes as the only source.

Expectations:
- Work with these fields: report name, decision supported, audience, action threshold, metric definition, source field, cadence, owner, caveat.
- Mark uncertain items as "Needs confirmation".
- Do not add facts that are not in the source.
- Separate known facts, assumptions, missing information, risks, and next actions.
- Summarize the top review questions for the team.

Output:
1. Report definition card
2. Known facts
3. Assumptions
4. Missing information
5. Ambiguous metric language
6. Questions for the LMS owner
7. Recommended next action

What changed in the system

The artifact carries more of the operating logic.

The team stops producing numbers on request and starts treating reports as governed decision tools.

Before and after

What changes when the work becomes clearer.

Use this as a pattern. The exact wording will change, but the move is the same: name the audience, workflow, owner, evidence, or decision more clearly.

Before

Monthly completion report.

The report has a metric label, but no decision, audience action, source field, inclusion rule, owner, cadence, or caveat.

After

Readiness follow-up report for regional leaders.

Decision: where to focus coaching. Audience: regional leaders. Metric: completion plus readiness check and manager observation. Cadence: monthly for 90 days. Caveat: completion shows exposure, not behavior change.

Why this is better

The artifact starts carrying more of the operating logic.

The report has a decision and an audience action.
The metric definition can be checked against the LMS source field.
The cadence matches the follow-up window.
The caveat reduces overclaiming before the report circulates.

Use this with

Open the related resource when you want to apply it.

Field test

Try it before you rebuild the whole system.

Before building the next LMS report, ask the requester to finish this sentence: if this number changes, we will decide whether to...