---
name: build-into-post-project-checklist-and-weekly-routine
description: "Help your team remember to say thanks. Use this when you want a simple way to track real help and the next step."
category: Thank You Machine
stage: —
definitive_article: /thank-you-machine
status: needs-work
---

# Keep a Simple Thank-You Routine

It is easy to forget to thank people when work gets busy. This guide helps your team keep a small list and follow through. Start with real help from recent work. Finish with clear next steps and proof of what was done.

**The path:** Recent work → choose real thanks → track the next step.

**Use this when:** the team wants a repeatable way to notice good deeds after projects or during an agreed weekly review.

## Inputs

- The team’s existing project closeout checklist and recent work records.
- The gratitude log and the owner of the review.
- The chosen trigger or cadence, time zone, actual task tool and allowed communication scope.

## First-run prompt

> Add a small thank-you review to this workflow. Use real deeds, check for duplicates and name the next owner. Keep the client’s work closeout criteria intact. If a repeat is requested, configure and verify the actual schedule; otherwise save the checklist.

## Steps

1. Read the existing closeout rules and current log. Add a review prompt such as “Did someone help in a way we should acknowledge?” without making public thanks or ad spend a condition of completing unrelated client work.
2. Choose an event trigger or an agreed cadence with the team. Define who reviews, which projects are included and how much effort is useful. Do not invent a compulsory weekly quota of videos.
3. Keep one row per deed with source, person, date, intended audience, next owner and state. States can include note ready, clip checked, draft, sent, posted or no further action; require evidence for the last two.
4. Review recent work and check duplicates before planning a new message. Use [Find a Real Reason to Say Thanks](https://local-service-spotlight.github.io/task-library/?task=identify-thank-you-triggers#task-identify-thank-you-triggers) for each worthwhile event. No new deed can mean no message this week.
5. Choose the lightest suitable form: a private note, short video or approved public post. Carry the person’s preferences forward; do not turn each thank-you into a required promotion campaign.
6. If recurring work is requested, configure it in the actual task tool or agent runtime with owner, time zone, trigger, required access and failure route. Verify the saved configuration and the first actual firing. A checklist or calendar idea alone is not a running schedule.
7. At each review, read existing records before retrying a send. Check exact delivery or post evidence, identify the smallest missing item, and carry open work forward with its owner. A reminder or automated acknowledgment is not proof of human receipt.
8. Periodically check whether the routine helps: real deeds noticed, time spent, pending work and repeated-message errors. Adjust the cadence within scope; do not claim relationships or revenue improved without evidence.

## Definition of done (QA checklist)

- [ ] The thank-you prompt fits the project workflow without changing unrelated closeout criteria.
- [ ] The log has source, deduplication key, state, evidence and next owner.
- [ ] Private and public routes are chosen for the actual event.
- [ ] A requested schedule is verified, or clearly remains a proposal.
- [ ] The report distinguishes planned, sent, posted and received states.

## Example(s)

**Fictional teaching example — no client result or completed run.** A team adds a five-minute review after each project. One week has no new deed, so it sends nothing. Another week has a checked private note. The project can still close once its own agreed deliverables pass.

## Handoff and Content Factory context

Use the log to hand a chosen event to [Find a Real Reason to Say Thanks](https://local-service-spotlight.github.io/task-library/?task=identify-thank-you-triggers#task-identify-thank-you-triggers) and later record its checked output. Send project updates only within the already authorized communication scope.

This fits the [Content Factory](https://blitzmetrics.com/content-factory/): Produce a true story, Process it into useful files, Post only in the agreed places, and Promote a suitable post when its test has a budget. Each stage passes its checked files and next owner forward.

## When this runs

Use the actual agreed event trigger or cadence. Save one run record per real review and keep the same execution ID for retries of that review.

## First-run setup and continuity

Use the files and accounts this task actually needs. A skill is a written recipe; the [AI worker](https://blitzmetrics.com/build-agents/) needs suitable tools and access to follow it. This file does not install an app, connect an account or start a timer. Follow the [setup guide](https://localservicespotlight.com/install/) for the chosen app. Carry out work already covered by the user's instructions; ask only for an exact missing item or a new action outside that scope.

Save the source, current state, checked result and next owner in the project files. Check that record before retrying or handing work to another person. Configure a repeat only when requested, with its time zone, actual runtime and first successful firing. An app or model name does not prove persistence, memory or a schedule.

Keep every agent media check muted with volume zero before playback. If that cannot be verified, use captions, metadata or still frames and record the limit. Do not play sound through the user's speakers without their current request.

## Write up the real run

For each real attempt, [write the meta article](https://blitzmetrics.com/meta-article-prompt/): its task and source revision, starting point, work done, evidence, measured result, gaps and next handoff. Save one execution ID across retries and edits. Partial, blocked and failed work also gets a record. A saved draft satisfies writing while any public release is pending. Writing does not grant publication authority.

A teaching example is not a real execution. Do not count it, a repeated check or a revision as another run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the link between reusable instructions and actual work.


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

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

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, 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

- Exact task: [Keep a Simple Thank-You Routine](https://local-service-spotlight.github.io/task-library/?task=build-into-post-project-checklist-and-weekly-routine#task-build-into-post-project-checklist-and-weekly-routine)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/) — how to record one clear point.
- [Content Factory](https://blitzmetrics.com/content-factory/) — how the source becomes checked posts.
- [Dollar-a-Day guide](https://blitzmetrics.com/dollar-a-day/) — the paid test method; current platform controls still need checking.

## Review and evidence still needed

The original contributor state is preserved. Instruction review, article certification, account access and completed work are separate states.

- Source mapping needs repair: on September 6, 2026, the recorded /thank-you-machine/ hub redirected to /face-socks/, a gift-ordering guide. That live gift recipe does not certify this video workflow. Keep the task ID and contributor state; use the relevant video and process guides below until the owner resolves the canonical video hub.
- Add a dated, real execution record with the actual checked output. The example below does not fill that gap.