Lessons Learned Quality

Last Updated:

On this page

Prepare Your Assessment

Purpose: Score the lessons learned section of a report for actionability, generalizability, and evidence basis. Paste the lessons learned to assess whether they will be useful beyond this program.

Materials: The report or section, linked findings and underlying evidence, methods and limitations, and documented authority, capacity and timing for recommendations.

Stage: State the stage and intended decision. Assess a plan by its documented provisions; completed work requires actual records.

Use: Read the criteria and record located evidence, applicability, ratings and priority revisions. Request missing records. Check AI quotations, source locations, requirements, and scores against the sources; missing evidence does not justify a low score.

Limits: Document quality does not establish readiness, authorization or compliance. Scores remain provisionally checked.

Adaptation and Comparability

Presentation and answer-language changes generally preserve meaning. Changing criteria, anchors, scale or strictness can change the assessment: label it adapted and do not compare its totals with the original rubric. Short mode removes two anchors and requires interpolation. Missing evidence calls for a request for records, not removal of the criterion. These scoring bands are provisionally checked, not practitioner-validated.

AI Prompt Templates

Add your material in the same chat. Context is optional; completed records must come from you.

Assess supplied evidence, report blockers and gaps, and give located findings and priority revisions. Incomplete evidence means no total.

7,111 characters
Adapt this rubric
Establish the document purpose, design, stage, applicable requirements, and available source evidence before rating. Distinguish N/A with a reason, not evidenced, unresolved conflicting evidence, and observed inadequate performance. Missing records do not prove an activity did not occur. Missing records alone justify evidence requests and a deferred readiness decision, not an inferred failure or mandatory repeat activity. Do not invent documentary, signature or approval requirements. Cite document locations for every finding. Keep supported facts separate from proposals, assumptions, and illustrative examples. Never invent completed fieldwork, validation, consent, approval, values, dates, quotations, or assigned ownership. Label unconfirmed owners and proposed revisions for confirmation. Report blocking ethics, safety, confidentiality, measurement-validity, or inference failures first regardless of scores. Give a total and band only when all five dimensions are applicable and sufficiently evidenced with no unresolved evidence conflict; otherwise show the dimension profile, coverage, and evidence requests without a total, band, or rescaled equivalent. A documentation score never authorizes use, fielding, compliance, or approval.

You are an expert evaluator and learning specialist. Score the lessons learned section I will provide using the rubric below. Treat the lessons learned as a standalone product: a useful lessons learned section should help readers in similar programs make better decisions, not just summarize what this team did.

SCORING RUBRIC - Lessons Learned Quality
Rate each applicable, evidenced dimension 1-5. Choose the highest anchor fully supported by the evidence; a material defect takes precedence over a favorable element count. An absent required feature in a complete submitted artifact is an observed documentation defect; an unavailable source or record is not evidenced, not proof the underlying activity failed.

DIMENSION 1: Evidence Basis
- Score 5: Every lesson cites the specific finding, data point, or event it draws from. The reader can trace each lesson back to evidence in the report. Where multiple findings support a lesson, all are cited. Lessons that contradict surface-level data acknowledge what was reconciled and how.
- Score 4: At least 80 percent of lessons cite their source finding or evidence. The remainder are plausible inferences from the body of the report but the link is implied rather than stated.
- Score 3: Roughly half of lessons are traceable to findings. The rest read as the author's general impressions. Some lessons appear consistent with the report but no direct link is shown.
- Score 2: Most lessons appear to reflect author opinion without documented evidence. Citations to findings are rare or absent. The section reads as commentary detached from the analysis.
- Score 1: Lessons are untraceable to anything in the report. No evidence basis is shown.

DIMENSION 2: Specificity
- Score 5: Every lesson is specific to a context, mechanism, or condition. Each lesson names the population, sector, intervention type, or operating condition it applies to. No lesson could be cut and pasted into an unrelated program report and still make sense.
- Score 4: At least 80 percent of lessons are specific in this sense. A small number drift toward general statements but the bulk are anchored.
- Score 3: Roughly half of lessons are specific. The rest read as generic ("partnerships matter," "context is important," "data quality is critical") without naming what made them apply here.
- Score 2: Most lessons are generic platitudes that could be lifted into any program report. Specificity is rare.
- Score 1: All lessons are platitudes with no specificity at all.

DIMENSION 3: Generalizability
- Score 5: Every lesson explicitly states its scope of applicability. The reader knows whether a lesson applies only to this program, to similar programs (and what makes them similar), or to the sector broadly. Boundary conditions are named where they matter.
- Score 4: At least 80 percent of lessons state their scope. A small number leave scope implicit but the surrounding context makes it inferable.
- Score 3: Some lessons name their scope; others do not. The reader has to guess whether a lesson is a one-off observation or a broader principle.
- Score 2: Scope is rarely addressed. Lessons are presented without any signal about whether they generalize.
- Score 1: No lesson states its scope. The reader cannot tell which lessons might apply elsewhere.

DIMENSION 4: Counter-Lessons
- Score 5: Learning is balanced against the supplied record. Documented failures, difficulties, unintended effects, and choices to retain or change practice are treated proportionately. Where no counter-lesson is supported, explain the evidence coverage rather than inventing a failure.
- Score 4: Relevant counter-lessons are meaningfully reported; a minor framing or evidence detail remains.
- Score 3: Some supported difficulties appear but their interpretation or implications are incomplete.
- Score 2: Documented difficulties are minimized, reframed without evidence, or detached from lessons.
- Score 1: Known failures or negative consequences are concealed or contradicted by the lesson account. There is no minimum count of counter-lessons.

DIMENSION 5: Action-Oriented Framing
- Score 5: Every lesson is framed so that a reader can derive an action or decision from it. Lessons name what to do differently, what to keep doing, what to stop, or what to test. Verbs and decisions are visible.
- Score 4: At least 80 percent of lessons are action-oriented. A small number remain observational but the bulk are decision-ready.
- Score 3: Roughly half of lessons are action-oriented. The remainder are passive observations that leave the reader unsure what to do with the information.
- Score 2: Most lessons are passive observations or descriptive statements. Few suggest action.
- Score 1: Lessons are descriptive only. No action framing is present.

OUTPUT FORMAT:
Return your assessment as a table followed by a summary:

| Dimension | Score (1-5), N/A, or Not Evidenced | Evidence | Priority Revision |
|-----------|-------------|----------|-------------------|
| Evidence Basis | | | |
| Specificity | | | |
| Generalizability | | | |
| Counter-Lessons | | | |
| Action-Oriented Framing | | | |

First report blocking issues, unresolved conflicts, applicability and evidence coverage. Only if all five dimensions are applicable and sufficiently evidenced with no unresolved source conflict, report **Total: X/25** and **Band:** Strong (22-25) / Adequate (17-21) / Needs Revision (11-16) / Substantial Revision (5-10), as a secondary documentation summary. Otherwise omit both total and band; report the dimension profile and evidence requests without rescaling.
**Single Most Important Revision:** [One specific sentence]

For any dimension scored 1 or 2, add a brief explanation and a concrete revision example using one of the lessons from the document.

LESSONS LEARNED TO SCORE:
[Paste your lessons learned section here]
Open it, with the prompt already in:ChatGPTClaude
Or paste it into:GeminiCopilot

Gemini and Copilot open empty. Copy the prompt, then paste it in.

Governing evidence and applicability rules (take precedence over aggregate bands): establish the document purpose, design, stage and available evidence before rating. A fit-for-purpose single-method design can earn the highest applicable rating; do not require complexity, mixed methods or two sources for every finding. Distinguish applicable, not applicable with reason, not evidenced, and observed inadequate. Report applicable coverage and the raw denominator. If any dimension is N/A or not evidenced, report the profile and gaps without a 25-point band or an unvalidated rescaled equivalent. Never interpret missing documentation as proof no activity occurred. Use source-linked historical facts only; keep proposed work and illustrative examples separate. Preserve unresolved source conflicts. Do not invent baseline values, quotations, fieldwork, pilots, validation, consent or approvals to improve a score. A serious consent, confidentiality, safeguarding, measurement-validity or unsupported-inference failure is a blocking issue regardless of the total, including 22/25. High document-quality scores do not establish legal compliance, instrument readiness, field authorization or donor approval. Accountable human review against the applicable protocol is separate. A well-documented failed pilot may score 25/25 for documentation while remaining not ready for fielding.

Use This Rubric

Bring: the proposed lessons, parent findings and source references, relevant context, contrary evidence, and intended decisions.

Stage: State whether this is a proposed design, a draft, or a report of completed work. Assess planned procedures as plans; require records before claiming they occurred. A complete submitted document can have an observed documentation defect even when the underlying activity is unknown.

Limits: Apply requirements to the stated purpose, methods, population, and risk. Do not impose extra methods or sensitive data collection solely to increase a score. These editorial anchors are provisionally checked, not practitioner-calibrated.

Scoring Criteria

Evidence Basis
5Excellent

Every lesson cites the specific finding, data point, or event it draws from. The reader can trace each lesson back to evidence in the report. Where multiple findings support a lesson, all are cited. Lessons that contradict surface-level data acknowledge what was reconciled and how.

4Good

At least 80 percent of lessons cite their source finding or evidence. The remainder are plausible inferences from the body of the report but the link is implied rather than stated.

3Adequate

Roughly half of lessons are traceable to findings. The rest read as the author's general impressions. Some lessons appear consistent with the report but no direct link is shown.

2Needs Improvement

Most lessons appear to reflect author opinion without documented evidence. Citations to findings are rare or absent. The section reads as commentary detached from the analysis.

1Inadequate

Lessons are untraceable to anything in the report. No evidence basis is shown.

Specificity
5Excellent

Every lesson is specific to a context, mechanism, or condition. Each lesson names the population, sector, intervention type, or operating condition it applies to. No lesson could be cut and pasted into an unrelated program report and still make sense.

4Good

At least 80 percent of lessons are specific in this sense. A small number drift toward general statements but the bulk are anchored.

3Adequate

Roughly half of lessons are specific. The rest read as generic ("partnerships matter," "context is important," "data quality is critical") without naming what made them apply here.

2Needs Improvement

Most lessons are generic platitudes that could be lifted into any program report. Specificity is rare.

1Inadequate

All lessons are platitudes with no specificity at all.

Generalizability
5Excellent

Every lesson explicitly states its scope of applicability. The reader knows whether a lesson applies only to this program, to similar programs (and what makes them similar), or to the sector broadly. Boundary conditions are named where they matter.

4Good

At least 80 percent of lessons state their scope. A small number leave scope implicit but the surrounding context makes it inferable.

3Adequate

Some lessons name their scope; others do not. The reader has to guess whether a lesson is a one-off observation or a broader principle.

2Needs Improvement

Scope is rarely addressed. Lessons are presented without any signal about whether they generalize.

1Inadequate

No lesson states its scope. The reader cannot tell which lessons might apply elsewhere.

Counter-Lessons
5Excellent

Learning is balanced against the supplied record. Documented failures, difficulties, unintended effects, and choices to retain or change practice are treated proportionately. Where no counter-lesson is supported, explain the evidence coverage rather than inventing a failure.

4Good

Relevant counter-lessons are meaningfully reported; a minor framing or evidence detail remains.

3Adequate

Some supported difficulties appear but their interpretation or implications are incomplete.

2Needs Improvement

Documented difficulties are minimized, reframed without evidence, or detached from lessons.

1Inadequate

Known failures or negative consequences are concealed or contradicted by the lesson account. There is no minimum count of counter-lessons.

Action-Oriented Framing
5Excellent

Every lesson is framed so that a reader can derive an action or decision from it. Lessons name what to do differently, what to keep doing, what to stop, or what to test. Verbs and decisions are visible.

4Good

At least 80 percent of lessons are action-oriented. A small number remain observational but the bulk are decision-ready.

3Adequate

Roughly half of lessons are action-oriented. The remainder are passive observations that leave the reader unsure what to do with the information.

2Needs Improvement

Most lessons are passive observations or descriptive statements. Few suggest action.

1Inadequate

Lessons are descriptive only. No action framing is present.

Score Interpretation

Report blockers, the dimension profile, and evidence coverage first. Use these aggregate bands only when all five dimensions are applicable and sufficiently evidenced with no unresolved evidence conflict. Otherwise give no total, band, or rescaled equivalent. High documentation quality does not establish readiness, legal compliance, or approval.

Total (out of 25)BandNext Step
22-25StrongStrong documentation profile only. Resolve blocking issues and obtain the applicable human review; this score does not authorize use.
17-21AdequatePrioritize source-linked revisions in the weakest dimensions. Request missing records before proposing additional activity; confirm the need for any new work from evidence.
11-16Needs RevisionUse located findings as a revision brief. Distinguish reporting gaps from demonstrated design or implementation failures and label proposed work for confirmation.
5-10Substantial RevisionRework the evidence-backed weaknesses with accountable review. A low documentation profile alone does not establish that the underlying activity failed or must be repeated.
Did this page help?