---
name: generate-knowledge-capture-note-within-24-hours
description: Save one real lesson in a short note while the facts are fresh.
category: Knowledge System Maintenance
stage: —
definitive_article: /knowledge-system-maintenance
status: needs-work
---

# Generate Knowledge Capture Note within 24 hours

Save a useful lesson while the facts are fresh. This guide turns one real finding into a short note your team can use. Start with the source and write the note within 24 hours.

## Inputs
- A real new lesson from a call, campaign, audit or completed step, plus when it was learned.
- The [four-field note form](https://local-service-spotlight.github.io/task-library/?task=provide-knowledge-capture-note-template#task-provide-knowledge-capture-note-template) and shared capture location.
- A source link or retained record, the affected guide or task, and permission to save the note.

## First-run prompt
> Use our four-field form to capture this lesson: [source, finding and time learned]. State the source, insight, destination and priority. Separate observed facts from guesses. Save it in [capture location] within 24 hours of the finding and record the actual save time. If the deadline passed, report that honestly.

## Steps
1. Confirm there is a lesson worth keeping: a new fact, a useful example, or evidence that a method needs to change. Record when it was learned so the 24-hour clock has a real start.
2. Open the shared four-field form. Add the dated source and the person or system that supplied it. Keep private proof in the authorized location.
3. Write the insight in one to three sentences. Explain what is newly known and what the source actually proves. Label uncertainty; do not turn a guess into a result.
4. Name the current guide or task that should receive it. If the destination is unclear, record the uncertainty for the routing owner instead of creating a competing article.
5. Set priority from the work affected. A finding blocking current work needs prompt attention; a useful future example can wait for the normal review.
6. Save the note in the shared location within 24 hours. Reopen it and check the source link. Record the actual save time and any missed deadline rather than backdating.
7. Hand the note to the routing task. Capturing a lesson does not mean the shared procedure has been changed.
8. If missed capture deadlines keep happening, record the pattern and pass it to [Add knowledge capture to existing workflows](https://local-service-spotlight.github.io/task-library/?task=add-knowledge-capture-to-existing-workflows#task-add-knowledge-capture-to-existing-workflows). That task owns the workflow change; this note does not set up a schedule.

## Definition of done (QA checklist)
- [ ] Exactly four fields are filled: source, insight, destination and priority.
- [ ] The insight is one to three sentences, and its factual claims match the source.
- [ ] Time learned and actual save time show whether the 24-hour target was met.
- [ ] The saved note opens in the shared location; its proof is accessible to the authorized receiver.
- [ ] The routing owner has the note or a visible queue entry; unresolved destination/access is explicit.

## Example(s)
**Fictional teaching example, not a real client run.** A shop owner learns at 10:00 on Tuesday that a campaign report used the wrong date range. By 10:30 the note says: Source: the Tuesday report and its dated export. Insight: the report covered two weeks while its title said one week; compare dates before comparing totals. Destination: the weekly reporting guide. Priority: before the report is sent. The measured delay is 30 minutes. A real note must link the actual source, not this example.

## Handoff
[Route the saved lesson](https://local-service-spotlight.github.io/task-library/?task=route-notes-to-sop-update-protocol-or-directly-to-articles#task-route-notes-to-sop-update-protocol-or-directly-to-articles) decides whether it belongs in an article as evidence or in a proposed process change. The author remains available to clarify the source.

## When it runs
Run after each useful new finding, with a 24-hour capture target. This is an event in the work, not proof of a configured timer. Add a reminder only through the team’s agreed workflow.

## Using this guide with AI
A guide is a set of steps. Ask an AI worker to use it with the files for this job. Confirm it can read the files and save the result where the next owner can find it. Use the existing authority for the work; identify the exact missing grant before an action outside that scope.

For repeat work, agree on the trigger, time zone, runtime and receiving owner. Check one run before relying on the schedule. The guide itself does not create a schedule, access or shared memory.

Record the actual work in a [meta article: the run record and its proof](https://blitzmetrics.com/meta-article-prompt/). Keep one execution ID for the same run and its retries. A teaching example does not add a completed run.



<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 2/5 `●●○○○` — frequency 2, revenue 1, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links
- Method: [How the knowledge system learns](https://blitzmetrics.com/knowledge-system-maintenance/)
- [This exact Task Library task](https://local-service-spotlight.github.io/task-library/?task=generate-knowledge-capture-note-within-24-hours#task-generate-knowledge-capture-note-within-24-hours)
- [Writing and visual guidelines](https://localservicespotlight.com/article-guidelines/)