How daily team check-ins work
The check-in is the only thing Eodly asks of your team, and it is deliberately small. One short message, in the tool they already have open, once a day.
What a teammate sees
At the time you set, the Eodly bot sends each person a direct message asking what they worked on. They reply in their own words. That is the whole interaction.
- Slack and Telegram: a DM from the bot. They reply in the thread.
- Discord: they type
/checkinin any channel and fill in the box. Eodly replies privately. - Microsoft Teams: a DM from the Eodly app.
They never create an account, never see a dashboard, and never attend a meeting. If they miss the cutoff, Eodly can nudge them, so chasing people is not your job.
What makes a good check-in
Free text is fine. Eodly parses it into claims, so plain sentences work better than formatting:
Finished the billing webhook and opened the PR. Started on the retry logic, blocked on the Stripe test keys.
That gives Eodly three things: something shipped, something in progress, and a blocker. It will then look for the pull request to sit next to the first claim.
Nobody is required to type
If someone does not check in, they are not invisible. Eodly still reads GitHub and Linear, so a silent teammate who merged three pull requests shows up as having shipped. The check-in adds intent, which is what lets Eodly spot the gap between what someone said and what actually moved.
What you get
At your report time, all of it is distilled into one page: who shipped with proof, who is silent, and who is slipping. See Reading your evening report.
This is not monitoring
Eodly reads the check-ins your team chooses to write and the work systems you connect. It does not do keystroke logging or screen capture, and it never will. It is a chief of staff for you, not surveillance of them. Being straight with your team about that is usually the difference between a routine that sticks and one that quietly dies.