Daily check-in: why a written plan beats a status meeting
A daily check-in that starts with a written plan keeps remote teams honest without a status meeting. Here is how the daily commitment works in DailyPulse.
A good daily check-in answers the question most status meetings exist for: what is everyone doing? That question is worth asking. A meeting is a costly way to ask it, especially when your team works in different cities and different hours.
A check-in that starts with a written plan does the same job. It takes a short moment, it is easy to read later, and nobody has to be online at the same time. This post explains the idea we build DailyPulse around: the daily commitment.
A daily check-in built on a commitment
Every morning you answer two questions about your work:
- What did you do yesterday?
- What will you do today?
The second answer is your commitment. It is a plain sentence about what you intend to do, per project. It is not a contract and it is not a score. It is a note to your team, and to yourself, that says: this is where my day is going.
There is a third box for blockers, and it is optional. Leave it empty when nothing is in your way.
Why writing beats talking
A spoken update fades. A written one stays put. That has a few quiet benefits.
- You think before you commit. Writing “finish the invoice export” forces a choice. “Working on some billing stuff” in a meeting does not.
- Everyone gets the same information. People in other time zones read the plan when their day starts. Nobody learns the news second hand.
- Nobody has to perform. Some people talk well in meetings and some do not. A written answer treats them the same.
- It costs less. A check-in takes about 30 seconds. A meeting takes everyone’s time, at the same moment.
Yesterday’s plan is answered by today’s question
Here is the part that makes the commitment more than a to-do note.
The plan you wrote yesterday is the answer you owe today. When you write “what did you do yesterday?”, you are looking at what you said you would do. You do not need a manager to ask. The two questions are two ends of one thread.
The pairing follows your check-ins, not the calendar. If you wrote your plan on Friday, it is answered on Monday. The weekend does not count as a missed day. A day you skipped is stepped over, not treated as a broken promise.
DailyPulse is careful about what it does not do here.
- It does not compare the two texts. “Shipped the API” and “finished the endpoint” can mean the same thing. Software cannot tell, so it does not try.
- It does not give you a score. There is no “kept” or “missed” tally.
- A blank is not a promise. If you leave “today” empty, there is no commitment to answer to.
The pairing feeds your own AI insight, which is written for you and shown on your own check-in. It is a way to see your own pattern, not a report card for someone else.
Say how sure you are
Plans change. A plan you wrote at 9:00 may look different at 11:00. The honest thing is to say so early, and the daily check-in makes that easy.
Next to each project’s plan there is an optional question: How sure are you today’s plan gets done? You pick one:
- On track
- At risk
- Won’t make it
If you choose at risk or won’t make it, you can add what would help. That is the most useful sentence in the whole check-in. It turns “I’m behind” into something a teammate can act on: a review, a decision, an hour of someone’s time.
The confidence is about the work, not about you. It sits apart from the mood question, which is about how you feel.
There is also a single checkbox, I have room to help today. It is for the days when your plan is light and you would like to be useful.
The Today board
Those signals land on one page, the Today board. It answers a simple question: who is at risk or blocked on today’s plan, and who said they have room to help?
It has three lists:
- Needs help: people whose plan is at risk or won’t make it.
- Can help: people who said they have room today.
- Blocked: people who named a blocker.
A leader can read it in a minute and see where a short conversation would matter. A teammate can see that someone has room and ask. When the lists are empty, they say so: Nobody has said so today.
That is the whole point. Nobody is chasing for a status. People say what they know, and the board puts it where it can be used.
How to start
You can run this with any tool, or even a shared document. A few habits make it work.
- Write the plan first. Do it before the first meeting or message of the day.
- Keep it small. One or two sentences per project is plenty.
- Use the confidence question honestly. At risk is not a confession. It is early information.
- Treat “what would help” as a request. Leaders, answer it the same day.
- Never use the answers as a stick. The first time someone is punished for writing “at risk”, they will stop writing it.
Try it in DailyPulse
DailyPulse is built for this routine: the daily commitment, the optional confidence, and the Today board. It is invite-only for now. If you would like to try it with your team, talk to us at hello@dailypulse.ai. If you have already been invited, open the app at app.dailypulse.ai.