Catch up on every meeting you missed.
The useful question after an absence is what changed for your work. Transcripts let the AI recover how a discussion unfolded; subsequent messages help establish where it ended up.
Try it now
Copy the prompt into your AI tool of choice, then answer its questions as they come.
Paste it into any AI chat to start. For most people, this is all you need.
Everything on this page in one paste: the prompt plus the full plan, every step and what to check. Use it for longer moves, to plan ahead, to share with a colleague, or if your AI can't open links.
How it goes
What the AI will do
- Find the meetings you missed and reconstruct the discussions, decisions and issues that matter to your role, using transcripts first.
- Trace later messages and project updates so your briefing reflects what still stands.
What to have ready
- A period or set of meetings to catch up on; a calendar link or rough description is enough to start.
- Access to transcripts, calendar and relevant project correspondence is especially valuable. Without connected records, reconstruction will be difficult and incomplete.
Where you come in
- Confirm uncertain attendance and fill gaps about your role or priorities.
- Resolve important ambiguities and review what appears to need your attention.
What you'll get
A sourced catch-up briefing with current decisions, your likely follow-ups and a clear account of meetings or details that could not be reconstructed.
You're done when
You have a current, sourced briefing of the agreed missed meetings, with issues relevant to your role, possible next actions and explicit gaps wherever the record was incomplete.
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result. ### Start with the activity and the user's context Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear. Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them. ### Check the capabilities needed for this work Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit. When useful access is missing: - Explain what you cannot reach and how that material would help. - Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot. - If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response. - Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available. ### Ask focused questions and respect the answers Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful. Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements. ### Keep evidence and independent contributions distinct Distinguish evidence, inference, and missing information. Check your work against the source material. Use independent agents when your system actually supports delegation and independent investigation or review would improve the work: - Give each agent a bounded brief and the context appropriate to its role. - Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations. - Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately. ### Produce, check, and revise the result Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them. Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result. Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized. Help me catch up on meetings I missed and understand what now matters to my work. Reconstruct the record, prioritize it for my role, and deliver a briefing I can use. Ask focused questions one at a time, waiting when an answer changes the investigation or a decision represented as mine. ### 1. Establish my work and the catch-up boundary Start with any period, meeting names, project links or absence information I supplied. Inspect available calendar, transcript, document, email and chat tools with a small relevant read to establish actual access. Search project briefs, current responsibilities, my recent emails and chats, and relevant task records for my role, active projects, commitments and upcoming decisions. Include WhatsApp or other messages when available and relevant. Use project names, people and dates from these records to narrow subsequent searches. State the catch-up period and your understanding of what I need to know. Ask about a material missing priority or boundary rather than asking me to retell the project history. If an uncertainty would change which meetings you investigate, wait for my answer before that work. ### 2. Identify missed meetings and locate their records Inspect calendar events and invitations in the agreed period, including cancellations, reschedules and recurring meetings. Compare available attendance reports, transcript speakers and my own absence information. An invitation or accepted RSVP does not prove attendance; absence from a transcript speaker list does not prove I was absent. Separate confirmed missed meetings from uncertain candidates and ask me to resolve consequential uncertain cases. For each included meeting, record its date, purpose, participants, project, attendance evidence and available sources. Retrieve the transcript as the primary reconstruction source, checking whether it is complete and whether speaker labels are reliable. Link the invitation, transcript, agenda, meeting documents and notes. If a transcript is missing, use the invitation to identify participants and search their subsequent emails, chats, shared notes and task updates for references to that meeting. Look for both discussion details and outcomes. Search the relevant project and meeting terms within a sensible following period, extending it when a discovered thread continues later. A later summary can establish a reported outcome without recovering the actual discussion. If connected documentation is unavailable, explain early that this reconstruction will be very challenging and incomplete. Investigate permitted connection and export routes and request the smallest useful access action. Offer a limited interview reconstruction if records cannot be obtained, agree that fallback with me, and label recollections throughout. Do not invent discussion, attendance or chronology to fill the gap. ### 3. Reconstruct meetings in bounded assignments For several meetings, assign agents bounded meetings or related meeting series. Supply each with the actual records, source references, my role and priorities, and a required output: a concise meeting account, evidence-linked decisions and commitments, unresolved issues, possible implications for my work, and missing coverage. Keep a meeting/source coverage record. Split long transcripts into inspectable sections, retaining surrounding exchanges so proposals are not mistaken for agreements. Use successive waves if concurrency is limited. If agents are unavailable, work through manageable passes or fresh sessions with explicit source, decision and coverage handoffs. Describe shared-context checking honestly and never count an unread source as reviewed. For each meeting, establish: - What was discussed and why it mattered, including material disagreements or conditions. - Which decisions were made, by whom, and what remained a suggestion or open question. - Actual commitments, owners and dates, with unresolved ownership explicit. - Changes to assumptions, dependencies or expectations that affect my projects. Use transcript passages or timestamps for consequential findings, alongside direct document or message links. Separate recorded facts, participants' later accounts and your interpretation of relevance. ### 4. Bring the reconstruction up to date Reconcile the completed accounts across meetings. Follow decision and action threads through subsequent correspondence, project documents and task records. Distinguish the meeting date, message date and effective date. A newer mention does not automatically reverse an earlier decision: identify the actual amendment, confirmation or replacement and its authority. Prioritize what I need to address now: a decision awaiting me, a commitment attributed to me, changed work, an emerging issue, or useful background. Explain the connection to my role. If evidence conflicts on something consequential, show the conflict and ask one focused question before treating it as settled. Continue unaffected parts while waiting. ### 5. Check and deliver the briefing Give a separate reviewer the actual draft briefing, source records and agreed scope, without your explanation of what you meant to convey. Ask it to check unsupported decisions, misattributed commitments, missed reversals, relevance and incomplete meeting coverage. Use a fresh-session review when available; otherwise disclose the limits of a sequential check. Resolve material findings against the records. Deliver a short opening account of what changed, followed by the items needing my attention and concise meeting-by-meeting notes. Attach source links, current decision/action status, and a coverage list showing reconstructed, partial and unreconstructed meetings. Keep suggested actions distinct from commitments I actually made. Invite corrections and revise the briefing. Do not send messages, accept commitments or change task records as part of this catch-up. These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
View full AI instructions
Catch up on every meeting you missed.
What the AI will do
- Find the meetings you missed and reconstruct the discussions, decisions and issues that matter to your role, using transcripts first.
- Trace later messages and project updates so your briefing reflects what still stands.
What you can provide
- A period or set of meetings to catch up on; a calendar link or rough description is enough to start.
- Access to transcripts, calendar and relevant project correspondence is especially valuable. Without connected records, reconstruction will be difficult and incomplete.
Where you'll take part
- Confirm uncertain attendance and fill gaps about your role or priorities.
- Resolve important ambiguities and review what appears to need your attention.
What you'll get
A sourced catch-up briefing with current decisions, your likely follow-ups and a clear account of meetings or details that could not be reconstructed.
Activity context
The useful question after an absence is what changed for your work. Transcripts let the AI recover how a discussion unfolded; subsequent messages help establish where it ended up.
For the user
Start with the period you missed or a meeting you know you need to understand. The AI will look for your project context and meeting records before asking you to reconstruct them. You may need to confirm attendance, enable access or supply an export, and settle ambiguities that affect your next actions.
Guidance for the AI
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result.
Start with the activity and the user's context
Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear.
Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them.
Check the capabilities needed for this work
Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit.
When useful access is missing:
- Explain what you cannot reach and how that material would help.
- Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot.
- If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response.
- Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available.
Ask focused questions and respect the answers
Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful.
Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements.
Keep evidence and independent contributions distinct
Distinguish evidence, inference, and missing information. Check your work against the source material.
Use independent agents when your system actually supports delegation and independent investigation or review would improve the work:
- Give each agent a bounded brief and the context appropriate to its role.
- Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations.
- Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately.
Produce, check, and revise the result
Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them.
Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result.
Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized.
Your AI prompt
Help me catch up on meetings I missed and understand what now matters to my work. Reconstruct the record, prioritize it for my role, and deliver a briefing I can use. Ask focused questions one at a time, waiting when an answer changes the investigation or a decision represented as mine.
1. Establish my work and the catch-up boundary
Start with any period, meeting names, project links or absence information I supplied. Inspect available calendar, transcript, document, email and chat tools with a small relevant read to establish actual access. Search project briefs, current responsibilities, my recent emails and chats, and relevant task records for my role, active projects, commitments and upcoming decisions. Include WhatsApp or other messages when available and relevant. Use project names, people and dates from these records to narrow subsequent searches.
State the catch-up period and your understanding of what I need to know. Ask about a material missing priority or boundary rather than asking me to retell the project history. If an uncertainty would change which meetings you investigate, wait for my answer before that work.
2. Identify missed meetings and locate their records
Inspect calendar events and invitations in the agreed period, including cancellations, reschedules and recurring meetings. Compare available attendance reports, transcript speakers and my own absence information. An invitation or accepted RSVP does not prove attendance; absence from a transcript speaker list does not prove I was absent. Separate confirmed missed meetings from uncertain candidates and ask me to resolve consequential uncertain cases.
For each included meeting, record its date, purpose, participants, project, attendance evidence and available sources. Retrieve the transcript as the primary reconstruction source, checking whether it is complete and whether speaker labels are reliable. Link the invitation, transcript, agenda, meeting documents and notes.
If a transcript is missing, use the invitation to identify participants and search their subsequent emails, chats, shared notes and task updates for references to that meeting. Look for both discussion details and outcomes. Search the relevant project and meeting terms within a sensible following period, extending it when a discovered thread continues later. A later summary can establish a reported outcome without recovering the actual discussion.
If connected documentation is unavailable, explain early that this reconstruction will be very challenging and incomplete. Investigate permitted connection and export routes and request the smallest useful access action. Offer a limited interview reconstruction if records cannot be obtained, agree that fallback with me, and label recollections throughout. Do not invent discussion, attendance or chronology to fill the gap.
3. Reconstruct meetings in bounded assignments
For several meetings, assign agents bounded meetings or related meeting series. Supply each with the actual records, source references, my role and priorities, and a required output: a concise meeting account, evidence-linked decisions and commitments, unresolved issues, possible implications for my work, and missing coverage. Keep a meeting/source coverage record. Split long transcripts into inspectable sections, retaining surrounding exchanges so proposals are not mistaken for agreements.
Use successive waves if concurrency is limited. If agents are unavailable, work through manageable passes or fresh sessions with explicit source, decision and coverage handoffs. Describe shared-context checking honestly and never count an unread source as reviewed.
For each meeting, establish:
- What was discussed and why it mattered, including material disagreements or conditions.
- Which decisions were made, by whom, and what remained a suggestion or open question.
- Actual commitments, owners and dates, with unresolved ownership explicit.
- Changes to assumptions, dependencies or expectations that affect my projects.
Use transcript passages or timestamps for consequential findings, alongside direct document or message links. Separate recorded facts, participants' later accounts and your interpretation of relevance.
4. Bring the reconstruction up to date
Reconcile the completed accounts across meetings. Follow decision and action threads through subsequent correspondence, project documents and task records. Distinguish the meeting date, message date and effective date. A newer mention does not automatically reverse an earlier decision: identify the actual amendment, confirmation or replacement and its authority.
Prioritize what I need to address now: a decision awaiting me, a commitment attributed to me, changed work, an emerging issue, or useful background. Explain the connection to my role. If evidence conflicts on something consequential, show the conflict and ask one focused question before treating it as settled. Continue unaffected parts while waiting.
5. Check and deliver the briefing
Give a separate reviewer the actual draft briefing, source records and agreed scope, without your explanation of what you meant to convey. Ask it to check unsupported decisions, misattributed commitments, missed reversals, relevance and incomplete meeting coverage. Use a fresh-session review when available; otherwise disclose the limits of a sequential check. Resolve material findings against the records.
Deliver a short opening account of what changed, followed by the items needing my attention and concise meeting-by-meeting notes. Attach source links, current decision/action status, and a coverage list showing reconstructed, partial and unreconstructed meetings. Keep suggested actions distinct from commitments I actually made. Invite corrections and revise the briefing. Do not send messages, accept commitments or change task records as part of this catch-up.
Done when
You have a current, sourced briefing of the agreed missed meetings, with issues relevant to your role, possible next actions and explicit gaps wherever the record was incomplete.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.