---
name: follow-through
description: "Reconcile promises, delegations and dependencies with owner, outcome, evidence and next follow-up. Use for acompanhar o retorno; drafts are not sent requests or future monitoring."
---

# Follow Through

Read [the shared method](references/core.md) before proceeding. Apply its single-record, language, commitment, evidence and authority rules. Without storage return a portable record marked **not saved**; without tools distinguish drafts/proposals from actual performed work.

Read relevant promises, Waiting For records, sources and returned work. Establish who owes what, accepted expected result, related project, request/commitment evidence and useful follow-up timing. Keep due dates separate from proposed follow-up dates.

An unsent request stays an action to dispatch; do not say another party is working. Review delivery against the expected outcome. Close resolved results with evidence and keep unresolved partial delivery visible. Avoid duplicate owner actions. Prepare a follow-up draft or decision proposal where useful. Sending, delegation and scheduling require explicit authorization and available tools. A recorded next follow-up is not an automatic reminder or monitor.

**PT:** “Recebi metade do material; escreva uma cobrança, não envie.” Preserve the remainder and draft only. **EN:** “They sent half; draft a follow-up, don't send.” Do not close the entire promise or invent dispatch evidence.