Replace Your Weekly Status Meeting with an Async Written Check-In
Get a reusable async check-in with a posting schedule, response deadline, short questions, a sample answer and clear rules for when a live call is still needed.
You getSchedule, check-in questions and sample answer
Prompt
You are a team operations lead who has replaced many recurring status meetings with written check-ins.
Your job: design a reusable async check-in that replaces my team's status meeting. Before writing anything, ask me these questions in one message and wait for my answers:
1. What is the meeting now (how often, how long, how many people, their roles)?
2. Where will updates be posted (Slack, Teams, email, a shared doc)?
3. What does the meeting cover, and what usually goes wrong in it?
4. Which time zones is the team in?
Rules:
- Use 3-5 questions, each answerable in under 2 minutes.
- Set a specific response deadline (day, time and time zone) plus a reminder before it.
- Every question asks for something concrete: a date, a number, a named owner or a yes/no.
- Write 3-5 rules for when a live call is still needed, each with a trigger, who calls it and a maximum length.
- Include one filled-in sample answer so people see the expected length.
Output format:
1. Schedule (post time, reminder, deadline, who summarizes and by when)
2. Check-in questions (numbered, with a one-line answer guide each)
3. Sample answer
4. When to call a live meeting (table: trigger, who calls it, max length)
5. Rollout note for the team (under 100 words)
End with one line on what could make this fail for my team and how to spot it early.Example output
Tips and common edits
Why this works
- Asking about time zones and tools first makes the deadline and posting schedule fit the real team, not a generic one.
- Requiring dates, owners or yes/no answers stops vague updates like 'making progress' that hide risk.
- Explicit live-call triggers stop async from becoming an excuse to let stalled decisions sit.
Use this in ChatGPT, Claude or Gemini when a recurring status meeting feels like a recital. Have the meeting's length, attendee count, team time zones and your chat tool ready.
Common edits
- Ask for a daily version with only 2 questions for fast-moving sprint teams.
- Request a Notion or Google Form version instead of a chat-tool post.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Turn Rough Notes into a Weekly Slack Team Update with Clear Blockers
Turns your messy weekly notes into a Slack-ready team update under 150 words, split into Shipped, Next and Blocked, with an owner and date for every blocker.
Build a Reusable Report or Memo Template Anyone on Your Team Can Fill In
Get a blank document template with headed sections, one-line guidance under each, a fully filled example, and a short pre-send checklist.
Prepare for Presentation Q&A with 10 Tough Questions and 30-Second Answers
Get 10 likely tough audience questions ranked by likelihood and difficulty, a 30-second answer for each, and clear flags where you lack evidence.
Meeting Notes to Decisions, Action Items and Follow-Up Email
Extracts decisions, owned and dated action items and open questions from meeting notes, then drafts a follow-up email.
Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged
Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.
Audit Your Calendar Week and Cut or Shorten Low-Value Meetings
Scores each meeting you paste on value and need for your presence, gives one verdict per meeting, and drafts polite decline or shorten-to-15-minutes messages.