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

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

Example for: an 8-person product engineering team replacing a 45-minute Monday status call, using Slack, split between New York and Lisbon.

1. Schedule

  • Post time: Monday 9:00 ET / 14:00 Lisbon, an automated Slack workflow posts in #eng-checkin
  • Reminder: Monday 15:00 ET to anyone who hasn't replied
  • Deadline: Monday 17:00 ET / 22:00 Lisbon
  • Summary: Priya (EM) posts a 5-line digest by Tuesday 10:00 ET

2. Check-In Questions

  1. What did you ship or finish last week? Link the PR or ticket; one line each.
  2. What will you finish by Friday? Max 3 items, each with a ticket number.
  3. Are you blocked? (yes/no) If yes: what, and who can unblock you.
  4. Any date at risk? Name the deliverable and the new estimated date.
  5. Need input from someone by Wednesday? Tag them directly.

3. Sample Answer

  1. Shipped CSV export (PR #412), fixed login timeout (ENG-219)
  2. Finish billing webhook retries (ENG-233), review Marta's search PR
  3. Yes, need staging DB access, @Tomas
  4. Billing retries: Thu → next Tue, waiting on Stripe sandbox keys
  5. @Priya, approve retry limit of 5 vs 3

4. When to Call a Live Meeting

TriggerWho calls itMax length
Same blocker reported 2 weeks in a rowEM15 min
A release date slips more than 3 daysOwner of the deliverable20 min
A thread goes past 10 replies without a decisionAnyone in the thread15 min
Two people disagree on scope or approachEither person20 min
Production incident affecting customersOn-call engineerAs needed

5. Rollout Note

Starting next Monday, our status call becomes a written check-in in #eng-checkin. It takes about 5 minutes and is due by 17:00 ET. Priya will post a summary Tuesday morning. We'll still meet live when a blocker repeats, a date slips, or a thread stalls; the table above says when. We'll review after 4 weeks and keep it only if it saves time.

Risk: Lisbon replies may drift past the deadline and hide blockers; if more than 2 people miss it two weeks running, move the deadline to Tuesday 12:00 ET.

Written by AI from this prompt. Your results will vary.

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 in Productivity