Works with Claude, ChatGPT, Gemini, or your own local model: paste this prompt and your AI will co-facilitate this exercise with you.

Help me prepare and run the exercise below. First ask for my participant count, time, setting, access needs and intended result. Check these against the stated limits. Use the supplied rules and materials. Explain any proposed changes before using them, and label them as adaptations. Do not invent source claims or require personal disclosure. Give me one step at a time when I say start. I manage the people, physical activity and clock; do not claim to observe the room. Ask me what happened before choosing a next step.

Reference revision: bcf05ed307190d3e356ce2d40a9e3f5790bab69881818b46a65bc22399a06c3c

# Check-in and Check-out

Team members sit in a circle to share brief progress updates, daily goals, and support requests at the start of work, then reconvene at day's end to review finished tasks.

**Time:** 15 minutes. Source recommends 10 to 30 minutes for 2 to 12 people. UWT standardizes on a 15-minute standing routine.
**People:** 2 to 12. Whole group seated in a circle, speaking sequentially.

## Choose this exercise

**Purpose:** Track daily project status and identify immediate team support needs.
**Use it when:** At the start or end of an intensive project day or sprint when a team needs quick coordination.
**Skip it when:** When team members work on entirely unrelated tracks or when an in-depth problem-solving session is required instead.

## Materials and tools

- Visible board, chart paper, or shared screen for questions and notes
- Dry-erase marker or digital document
- Timer or visible clock

## Before participants arrive

1. Arrange chairs in an open circle with clear sightlines.
2. Display the chosen questions clearly on the board or screen.

## Say this to open

We will do a quick round where everyone answers three short prompts. Keep each turn under 45 seconds so we keep momentum. You may also pass if you prefer.

## How to run it

### 1. Introduce prompts (2 minutes)

Display the questions. For a morning Check-in, use: What did you do yesterday? What will you do today? Is there something you need help with? For an evening Check-out, use: What did you finish today? What remains unfinished against the plan? Remind everyone that deep technical troubleshooting happens in breakout pairs right after this round.

### 2. Run sequential sharing (9 minutes)

Invite a volunteer to start, then proceed clockwise around the circle. Each person answers the prompts within 45 seconds. Example: 'Yesterday I completed the wireframes. Today I am drafting copy for the login flow. I need help reviewing technical constraints before noon.' The facilitator writes each person's core task commitment and any support requests on the shared board without stopping to debate solutions.

### 3. Confirm commitments and pairs (2 minutes)

Review the recorded task commitments and support requests on the board. Confirm which pairs or subgroups will meet immediately after the circle to resolve each help request.

### 4. Debrief process (2 minutes)

Ask 1 or 2 quick reflection questions to close the session: Did this format keep our daily focus sharp? Is there an additional question our team should ask tomorrow? Take up to two short responses, then dismiss the group.


## Debrief questions

- Did this format keep our daily focus sharp?
- Is there an additional question our team should ask tomorrow?

**Finished output:** A shared list of daily commitments and paired follow-up actions recorded on the board.

## Remote

Run via video conference. Post the questions in chat and display a shared document on screen. Facilitator establishes a speaking order in chat. Each speaker takes up to 45 seconds. The facilitator logs commitments and help requests live in the shared document.

## Hybrid

In-person participants sit facing the shared camera and room microphone. The facilitator alternates between in-person and remote speakers. A shared online document is projected on the room screen so all participants see the logged commitments and support pairs.

## Access and participation choices

- Participants may pass or type their updates in a shared document or chat instead of speaking aloud.
- Disclosing emotional state is optional; participants may focus strictly on task status.

## If the session gets stuck

**A participant starts a lengthy technical debate during their turn.**

Gently interrupt and say: 'Let us log that topic on our follow-up list so you two can solve it right after this circle.'

**Participants exceed their speaking limit and the meeting falls behind.**

Use a soft visible timer set for 45 seconds per person and model concise, two-sentence updates.


## Terms used here

- Time plan: The agreed schedule, milestones, or deadlines for the team's project.

## Sources and adaptation

Observed in Project of How (projectofhow.com, method HOW004), where the page attributes the entry to Emelie Askfelt.

Retained core questions, round formation, and check-in/check-out mechanics from Project of How. Added strict 45-second per-person timeboxing to guarantee completion within 15 minutes for up to 12 people, explicit facilitator capture of commitments and support pairs, and structured hybrid accommodations.

[Project of How](https://projectofhow.com/method/check-in-check-out/)

Current run sheet: https://unitedwetransform.com/exercises/check-in-check-out-project-of-how/