Setting check-in schedules and frequency
The schedule controls when Dailybot asks for responses. Timezone handling matters because participants may work in different regions.
Before you begin
- You need edit access to the check-in (check-in owner or Organization Admin).
- Decide whether the whole org shares one timezone anchor or you rely on per-user overrides (see Configuring your personal timezone and reminder time).
Steps
- Open app.dailybot.com and go to Check-ins.
- Select the check-in and open Schedule (or Timing / When we ask).
- Set frequency: Daily, Weekly on selected weekdays, or Custom days depending on what your UI offers.
- Pick send time (hour and minute) for the first prompt on each scheduled day.
- Set the timezone that defines “9:00 a.m.” for the check-in configuration. This is often the org or team’s primary timezone.
- If the UI shows a collection window or deadline, configure how long participants have before the report compiles. Shorter windows produce tighter reports; longer windows catch late time zones.
- Save work days or holiday behavior if your check-in links to org work-day settings (see Work days and check-ins if configured).
- Click Save and confirm the summary matches what you expect.
Frequency options
| Option | Typical use |
|---|---|
| Daily | Standups, habit tracking |
| Weekly | Retros, manager 1:1 prompts, light polls |
| Custom days | Mon/Wed/Fri standups, sprint boundaries |
Timezone and participants
The check-in’s configured timezone sets the default anchor for “what clock” Dailybot uses when it schedules the org-level send. Participants who set a personal timezone in their profile usually get reminders aligned to their local day so a single global send time does not land in the middle of the night.
If someone has no personal timezone, the org or check-in default applies. Mixed teams should encourage everyone to set their timezone once — see the personal settings article linked below.
Delivery window behavior
A delivery or collection window is the period in which Dailybot accepts answers before it finalizes the report batch. Late answers may roll to the next cycle or appear as updates depending on your settings; check the check-in detail page after a run to see how your org behaves.
What to expect after
The next occurrence uses the new schedule. If times still look wrong for one person, have them verify Profile timezone and reminder preferences before changing the global check-in again.