Check In Meeting: The 25% Rule That Keeps It From Becoming a Status Update

By Andreas Pettersson, Founder, Leaders ADAPT

Your calendar says you ran six check-ins this week. Each person left the room feeling heard. Each of them still doesn't know what done looks like on the thing you handed over on Monday.

That's the gap a check in meeting is supposed to close, and most of them don't. They turn into status updates: a list of what got touched, read aloud, with you nodding.

The Delegation Protocol I teach fixes it with one number. Check in when the work is 25 percent done, ask about blockers, and don't ask to see the draft. A check-in is a short conversation about the state of agreed work, not a report on activity. Below: the timing rule, the four sentences, and three question sets.

What is a check in meeting?

A check-in meeting is a brief, scheduled conversation in which a manager and an employee compare the current state of agreed work against the outcome they set, surface blockers, and confirm what happens next.

Scheduled means agreed at the handoff. Blockers means your job in the room is to remove something, not inspect something.

The three kinds serve different purposes and shouldn't be mixed:

• The project check-in. One conversation, timed to the work, about a delegated outcome. The 25% Rule governs it.
• The employee check-in. A recurring weekly check-in with employees about the person: energy, priorities, what's harder than it should be.
• The team check-in. The stand-up. Blockers named in public, no solving in the room.

Most guides, including the Management Center's agenda template near the top of the results, treat all three as one warm catch-up with a question list attached, which is why the meetings feel good and change nothing.

Check-in meeting vs status update vs one-on-one: what is the difference?

A status update asks what are you doing. A check-in asks what's in your way. A calibration 1:1 asks how are you really. Three different meetings.

The one-on-one meeting builder on this site scores 1:1s against the same split. Its two most common results are the failure modes: the 1:1 that is only a check-in and the 1:1 that is a status update.

Status update 1:1s are the worse problem. I'd rather a manager ran none. They create the illusion of connection while missing everything that matters, and they train people to perform "fine" instead of telling the truth.

When should you check in on delegated work? The 25 percent rule

The 25% Rule is a delegation timing rule: check in once when delegated work is about 25 percent complete, ask about blockers rather than asking to see the work, and leave the process to the owner.

A week long project means Wednesday; a month long one, the end of week one. Set the date at the handoff, out loud.

The reasoning sits on both edges. At 25 percent a wrong direction is correctable without starting over. At 90 percent it's too late. At 5 percent the check-in is micromanagement, because nothing has happened yet.

The script has four sentences and no fifth:

1. How is it going?
2. Any blockers I can remove?
3. Anything you need from me?
4. Still on for the date we agreed?

The missing sentence is the one most managers open with: "Can I see what you've got so far?" Ask it and the meeting becomes about your approval, and the work moves back across the desk. The handoff line was "You own it, update me for visibility, not approval." The check-in has to honor it.

This is the step almost every how-to-delegate guide skips, and the cure for the hovering manager: a manager who knows the check-in is Wednesday can leave the doc closed until Wednesday.

What should you ask in an employee check-in? Three sets by purpose

The incumbents offer 52 or 103 check in questions for employees. You need about a dozen, one set per meeting.

Set 1: the project check-in (the work)

The four sentences above. If "how is it going" gets a shrug, add: "What's the one thing that's harder than it should be?"

Set 2: the employee check-in (the person)

• "What's on your mind?" Not "give me an update," which turns it into a status meeting. These employee check in questions belong in the weekly meeting.
• "What else?" Asked twice. There's always more.
• "On a scale of 1 to 10, what's your energy level right now?" Below 7 gets the follow-up: "What would it take to get you to an 8?"
• "What are you struggling with that you haven't told me about?"
• "What do you need from me before next time?"

Run this set the way a manager who coaches runs it: listen first, hand the problem back, then tell.

The energy question is the highest value item in the set. People perform "fine" to an open question. Almost nobody performs a number. A 4 from someone who's usually an 8 is the earliest signal you'll get.

Set 3: the standard check-in (what done looks like)

Run this one when work keeps coming back almost right. "Say back to me what done looks like on this, in your words." "Which part are you least sure I'll accept?" "What decision are you waiting on me for?"

If the read-back doesn't match your head, the fault is in the handoff. Clear expectations written at the handoff save more check-ins than any prompt list.

How often should you check in with employees without micromanaging?

Two clocks, and confusing them is where micromanagement starts.

The project check-in runs on the work's clock: once, at 25 percent, plus whatever the owner asks for. Four check-ins by day ten of a month long job is supervising, and the work will find its way back to you because the owner has learned you'll finish it.

The employee check-in runs on the person's clock. Frequency follows state, not title:

Gallup found that employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers don't (Gallup, 2015). Regular is the operative word, not long.

When my company grew from thirty to seventy people, managers appeared between me and the work, and my 1:1s became 1:1s about their 1:1s. I couldn't just delegate well anymore. I needed my managers to delegate well.

The fix wasn't more meetings from me. It was one line in each manager's 1:1, "What have you delegated this week, and how did you frame it," plus two skip-level conversations a month with their direct reports. By 150 people I'd cut my week from 60 hours to 45, and the check-ins below me ran without me.

One honest limit: this site's 1:1 statistics page is below its 30 completion floor as of September 22, 2026, so there's no first party figure yet on how many 1:1s are really status updates.

How long should a check-in meeting be, and what goes on the agenda?

The Async-First Rule in my system makes status updates and project updates async by default. The written update has a fixed shape: project, red-yellow-green status, progress this week, next steps, blockers, what I need from you. Thirty seconds to write, 15 to read, and it replaces a 30 minute status update meeting. Asana's Anatomy of Work Index puts the cost of skipping this at about 103 hours a year per knowledge worker lost to unnecessary meetings (Asana, Anatomy of Work Index).

With status on paper, the check-in meeting agenda has four lines and fits in 15 minutes:

1. The outcome, restated. One sentence, by the owner.
2. The color. Green, yellow or red, with one sentence of why.
3. Blockers. What's in the way, and which of those you can remove today.
4. Next check-in. The agreed date holds or you set a new one. Written down.

No walkthrough of the work. No "let me show you." Ten to fifteen minutes for a project check-in, thirty for a weekly employee check-in. If yours run longer, the status update is still in the room.

How do you run a check-in remotely?

A remote check-in loses the channel most managers rely on: reading the room. Stop reading and start asking.

• Cameras on, always. You need to see the person to read how they're doing.
• Ask for the color out loud. "I can't read your energy through a screen. Give me a color: green, yellow or red." People start volunteering it before you ask.
• Ask the energy question every single time, because remote you can't tell when something seems off.
• Follow up in writing within two hours. What you heard and what each of you committed to.

Watch for the remote version of status theater: a stand-up where everyone says "on track, no blockers" week after week. Break it by going first with your own blocker, then ask each person for the hardest thing on their plate. A remote manager who can't name each report's energy level is meeting, not calibrating.

Check in meeting FAQ

What is the purpose of a check in meeting?

The purpose of a check-in meeting is to compare the current state of agreed work against the outcome that was set, surface blockers early enough to fix them cheaply, and confirm what happens next. A project check-in does this once for a delegated piece of work. An employee check-in does it on a recurring basis for the person's priorities and energy.

How is a check-in meeting different from a status update meeting?

A status update meeting reports activity: what was done since the last meeting. A check-in meeting examines state and obstacles: whether the agreed outcome is on track and what is in the way. Status can be written in a fixed format and read in under a minute, so it rarely justifies a meeting. A check-in needs a conversation, because a blocker needs a decision.

What should a manager ask in an employee check-in?

For a project check-in: how is it going, any blockers I can remove, anything you need from me, still on for the agreed date. For a weekly employee check-in: what is on your mind, what else, what is your energy level from 1 to 10, what are you struggling with that you have not raised, and what do you need from me.

How often should a manager check in with employees?

A project check-in happens once, when delegated work is about 25 percent complete, plus any check-in the owner requests. Recurring employee check-ins follow the person's state rather than their title: weekly for new hires in their first 90 days, anyone struggling, and anyone in a transition; every two weeks for stable, experienced performers; monthly for senior leaders with a track record. A sudden change moves anyone back to weekly.

How long should a check-in meeting last?

A project check-in on delegated work runs 10 to 15 minutes when the status update was sent in writing beforehand. A recurring employee check-in runs about 30 minutes. A check-in that regularly exceeds those lengths has usually absorbed a status report, which belongs in a written update, or a problem-solving discussion, which belongs in a separate working session.

What should a weekly check in with employees include?

A weekly check-in with employees covers the person before the work. It opens with their agenda: what is on their mind and what else. It moves to calibration: an energy score from 1 to 10, with a follow-up when the score is under 7, and what they are struggling with. It closes with alignment: top priorities for the week, what they need from the manager, and what they commit to.

The check-in that keeps the work where you put it

Six check-ins a week that leave people feeling heard and nobody knowing what done looks like isn't a meeting problem. It's a handoff problem showing up in your calendar. No outcome was stated, so the check-in had nothing to check, so it filled with status.

Fix the sequence and the meeting fixes itself. State the outcome and the authority level at the handoff. Move status to a written update.

Check in once, at 25 percent, with four sentences and no request to see the draft. Run the employee check-in on the person's clock, with a number instead of "how are things."

Tomorrow morning, pick the one piece of delegated work you're most tempted to look at. Write down the date it will be 25 percent done. Put the check-in on the calendar for that date, and nothing before it.