Late Start Alert
Alert type: Attendance
Schedule: Daily/Weekly Notification
Available on: Basic and above
Who can set it up: Workspace Admin
Where to find it: Admin Settings › Alerts
The Late Start alert tells which members began work after an agreed cut-off. Catching a late start while the day is still on lets you check in when it matters.
When to use this alert
A late start is often the earliest sign of a slipping routine, but it can go unnoticed in a weekly report until it is too late to act. This alert sends the names to the right people shortly after the cut-off passes.
Use it to:
- Spot late starts the same day, while a conversation is still useful.
- Apply one cut-off consistently across a team.
- Give HR and managers the same list without anyone compiling it by hand.
Example alert setup
Field | Value |
|---|---|
Alert Schedule | Daily Notification |
Alert Type | Attendance |
Alert Name | Late Start (Customer Support) |
Variable | Start Time |
Condition | greater than equals |
Compare With | Custom |
By | 10:30 AM |
Apply alert on | Custom: Monday to Friday |
Whom to monitor | Individual members, teams or the entire organisation. In this example: the Customer Support team. |
Who gets notified | Individual, Reporting Manager, All Admin, Custom |
When to send | Same day at 12:00 pm |
Note: All values in this article are examples. Times, hours and percentages are sample values to help you get started. Adjust them to your own working hours, roles and policies. They are not benchmarks or recommendations for any industry.
How to set it up
- Open the alert settings: go to Admin Settings › Alerts.
- Click "Create New" button
- Choose the Alert Schedule: Daily Notification.
- Set the Alert Type to Attendance and enter an Alert Name, for example "Late Start (Customer Support).
- Set the condition:
- Variable: Start Time
- Condition: greater than equals
- Compare With: Custom
- By: 10:30 AM
- Choose Apply alert on: Custom, then select Monday to Friday.
- Choose whom to monitor: under Applicable to, select Teams, then choose Customer Support.
- Choose who gets notified: Individual, Reporting Manager, All Admin, Custom
- Set when to send: Same day at 12:00 pm.
- Save the alert and activate it.
How the rule is evaluated
Start Time is the time a member's day begins. Because the condition is greater than equals, a start at exactly 10:30 AM also triggers the alert. In plain English: the alert lists every member of Customer Support whose day began at 10:30 AM or later.
Set the value to the team's start time plus your grace period. For a 10:00 AM start with a 30-minute grace, use 10:30 AM.
By 12:00 pm the start of the day is already recorded, so the list is complete for every member who has begun work.
Worked example
Rule: Start Time is greater than equals 10:30 AM.
Member | Start Time | Triggers? |
|---|---|---|
Priya Sharma | 09:52 AM | No |
Karan Malhotra | 10:12 AM | No |
Rohan Mehta | 10:30 AM | Yes (equals the value) |
Ananya Iyer | 10:47 AM | Yes |
Sneha Kulkarni | 11:05 AM | Yes |
What recipients receive
Recipients receive an email naming the members who met the condition.
Dear User,
Please be informed that the 'Late Start (Customer Support Team)' alert has been triggered. Currently, 10 out of 50 users have met the following criteria(s):
Start Time is greater than or equal to custom value of 10:30 AM
For a comprehensive view, please refer to the attached CSV file with detailed information. You can adjust the alert settings here.
We hope this information assists you in identifying trends, making informed adjustments, and supporting a balanced, productive environment for your team.
Best regards,
Flowace Team
Choosing recipients and timing
Field | Recommendation | Why |
|---|---|---|
Who gets notified | Individual, Reporting Manager, All Admin, Custom | The member gets a nudge, the manager can follow up, and HR and Admins see the pattern. |
When to send | Same day, 12:00 pm | Late enough that starts are recorded; early enough to act on. |
Apply alert on | Monday to Friday | The team's working week. Add other days only if the team works them. |
Reading the results: common scenarios
What you see | What it may mean | What to do |
|---|---|---|
One member listed once | An isolated late day | Usually no action; note the pattern. |
The same member on several days | A shifting routine or a schedule change | Check in. |
Most of a team on one day | A shared cause such as an outage or transport disruption | Check the cause before addressing individuals. |
A member whose tracker did not start on time | The start time reflects when tracking began | Check that the tracker is running |
Good to know
- Values are per team or role. Different teams work different hours; set a separate alert for each.
- Choose the day carefully. If every day of the week is selected, the alert also runs on weekends and holidays for everyone who was not working.
- Alerts follow your workspace settings. Working days, shifts, or the time zone configured for your workspace decide when an alert runs.
- Add a grace period. A cut-off equal to the start time lists anyone who starts a minute late.
FAQs
- Are the values in this article fixed?
No. The times, days and recipients in this article are examples. Change By, Apply alert on, Whom to monitor, Who gets notified and When to send to match your company's working hours and policies, and edit them whenever your policies change.
- Does a start at exactly the cut-off trigger the alert?
Yes. The condition is greater than equals, so a start at exactly the value is included.
- Why did the alert not list someone who started late?
Check that the day is selected under Apply alert on, that the member is within Whom to monitor, and that a start time was recorded.
- Can I send it to the member only?
Yes. Select only Individual under Who gets notified.
- Can more than one person receive the alert?
Yes. You can select several options under Who gets notified, and Custom lets you choose specific people.
Related articles
How to Set Up Custom Alerts in Flowace
Need more help? Reach out to support@flowace.ai and our team will be happy to assist.
© Flowace Technologies Pvt Ltd | flowace.ai
Updated on: 21/10/2026
Thank you!