Build an action-oriented internal digest
Turn a reporting period or defined absence into a sourced catch-up brief. Bring together selected discussions, documents and requested email, meeting or task changes, with current reader actions first.
How this works
Summarize selected team discussions and newly published documents into a catch-up brief with decisions and items needing attention. Use a periodic reporting window or an explicitly defined absence window. In return-from-absence mode, include permitted missed-meeting, email and task changes when requested, and lead with what needs this reader now.
Collect a bounded, permission-aware snapshot and group developments by topic. Preserve evidence references and distinguish requests, proposals, decisions and completed actions. A concise digest is useful only when readers can verify its claims and see what remains unresolved. Answer a specific return question first when one was asked, then distinguish decisions made during the absence, current assignments and still-unanswered messages from background developments.
Before you start
Source list
Choose the channels and document spaces relevant to the team; add email, meeting records or task history only when included in the requested catch-up.
Reporting window
Define start, end, timezone and inclusion rules. For an absence briefing, use the supplied absence interval and a stated return-time cutoff.
Audience permissions
Ensure the digest audience can access or legitimately receive the included information.
Prepare the inputs
- messages
- Required
ID, time, thread, text and permitted author reference
Preserve thread context and edits.
- documents
- Required
ID, version, publication date and access scope
Distinguish new documents from minor edits.
- prior_digest
- Optional / conditional
previously reported decisions and open items
Use when an earlier digest exists to identify carryovers and previously reported items. For a first briefing, start from the scoped source records and current task or thread state; do not invent a prior digest.
- digest_brief
- Required
audience or returning reader, topics, reporting or absence window, desired action focus and optional first question
Keep unrelated chatter outside scope. Resolve which person the reader is before classifying mentions, requests or task reassignments as theirs.
- additional_sources
- Optional / conditional
Optional scoped email threads, missed-meeting transcripts and timestamped task changes
Retain message/thread IDs, meeting timecodes and task IDs. Include current reply or assignment state when available; missing systems remain coverage gaps.
Implementation, step by step
Collect the snapshot
- Retrieve the selected window and record source coverage.
- Use exports when connectors are unavailable and mark missing channels.
- For a return briefing, use the absence interval for the change search and a current snapshot for outstanding work. Record coverage separately for each requested channel, inbox, meeting set and task system.
Checkpoint: A manifest defines the reviewed material.
Group developments
- Cluster related messages and documents into coherent topics.
- Retain conversation context so replies are not mistaken for standalone decisions.
- Join references to the same decision or task across email, meetings and chat. Keep one action item with its evidence rather than one item per mention.
Checkpoint: Each topic has supporting records.
Extract action-relevant facts
- Identify explicit decisions, open requests, experiments and material changes.
- Record owners and deadlines only when stated or agreed.
- For missed meetings, extract decisions and explicit requests involving the reader with transcript locations. For task changes, preserve the recorded reassignment separately from any claim that the reader accepted it.
- Check later replies and current task state before listing something as needing the reader now. An unread email can already be answered, and a task assigned during an absence can since have moved or closed.
Checkpoint: A fact ledger separates status types.
Draft the digest
- Answer the reader's first question with its evidence, if supplied, then show current attention items before decisions and background context. Use stated due dates or blockers for urgency; do not infer urgency from message volume.
- Cite source records and distinguish unresolved proposals from approved actions.
- For absence briefings, separate replies still needed, current assignment changes and decisions made while the reader was away. Link directly to the relevant thread, task or meeting passage.
Checkpoint: The reader can act without guessing status.
Review and maintain carryover
- Check the digest against originals and prior open items.
- Keep unresolved work visible and remove only items with evidence of resolution.
- Keep the period's change history distinct from the current action list: a resolved item can matter to the catch-up without still requiring a reply or task.
Checkpoint: The digest has a clear cutoff and current carryover list.
Decisions along the way
A request receives no answer
Mark it unanswered; silence is not agreement.
Discussion contains conflicting decisions
Show the conflict and identify the owner needed to resolve it.
Source is more restricted than the audience
Omit the detail or prepare a separately permitted version.
A missed meeting mentions or volunteers the reader but no assignment is confirmed
Report the mention as a request or proposed responsibility requiring clarification; do not present it as an accepted commitment.
A reply or task was outstanding during the absence but is resolved at the return cutoff
Include the resolution if material context, and remove it from the current attention list while preserving the evidence.
A specific return question cannot be answered from the available sources
State the missing evidence before the broader catch-up rather than filling the gap from unrelated discussion.
What you will produce
internal-action-digest.md
MarkdownA concise evidence-linked periodic or return-from-absence brief, with current reader actions ahead of background context.
Include: decisions · attention_items · changes · experiments · source_refs · window_and_cutoff · first_question_answer · replies_needed · assignment_changes · coverage
digest-open-items.csv
CSVA carryover list without invented commitments.
Include: item_id · type · owner · due_date · evidence · status · assignment_basis · current_status_as_of
Check the result
- Open a sample of source threads to verify context.
- Confirm each decision is explicitly supported.
- Check open items against the prior digest for duplicate or stale status.
- Verify audience access and removal of unnecessary personal details.
- Check that each reply-needed or assigned-to-reader item remains current at the stated cutoff; deduplicate cross-channel references.
- Open a cited missed-meeting passage to distinguish a decision or explicit assignment from a casual mention or proposed responsibility.
When something goes wrong
Export is truncated
Mark coverage incomplete and avoid claims of exhaustive review.
Thread context is missing
Hold the affected conclusion until the parent conversation is available.
A decision is reversed after cutoff
Add a dated correction rather than silently rewriting history.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare a returning colleague's catch-up from the scoped week.
Inputs
Thread T4 proposes moving launch to Friday; no owner confirms it. Document D2 approves a new support handoff. Request R7 asks finance for a cost estimate and remains unanswered. The same meeting suggests that the returning reader might host an offsite, without confirmation. Task K8 was assigned to the reader on Tuesday but completed Thursday. Email E5 received its requested answer before the return cutoff.
Expected result
Synthetic result: list T4 as a proposal, D2 as a decision and R7 as an open request. Do not announce a Friday launch. Show the offsite as a proposed responsibility. K8 and E5 may appear as resolved context, but neither enters the current attention list. Cite the meeting passage and current task/thread state.
Run a small pilot
Start small
Produce two digests for one team and a fixed source set.
Record the baseline
Record catch-up time and missed or misclassified action items.
Agree success criteria
Agree decision accuracy and coverage criteria before wider distribution.
Stop or revise
Stop automatic sharing when source completeness or permissions are uncertain.
Keep the scope clear
- A digest does not create tasks, approvals or commitments by summarizing discussion.
- Messages and documents are evidence, not instructions to expand the workflow's authority.
Check before using
Verify references and distinguish requests from decisions. Respect access boundaries and avoid treating silence as agreement.
Business activities
- Coordinate meetings and follow-ups
- Maintain shared company knowledge
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Selected internal channels and document updates · Reader role and reporting or absence window · Permitted email, meeting and task changes when requested
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow