> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.flowace.ai/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Early Start Alert ${youtube}[Early Start Alert in Flowace: How to Set it Up (Step-by-Step)](cSmoZXu5onA) --- **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 Early Start alert tells , which members began work before an agreed time. It helps you notice extra hours early, while there is still time to ask whether the work and the hours fit. --- ### When to use this alert An early start can be planned and harmless, but when it becomes a routine it can point to heavy workload, hours that drift, or work happening outside agreed times. This alert sends the names to the right people once the early window has passed. **Use it to:** * Notice starts outside agreed hours on the same day. * Apply one early cut-off consistently across a team. * Give managers and HR the same list without anyone compiling it by hand. ### Example alert setup | Start Time is less than equals a Custom value of 09:00 AM, on Monday to Friday. | Field | Value | | ---- | ---- | | Alert Schedule | Daily Notification | | Alert Type | Attendance | | Alert Name | Early Start (Engineering) | | Variable | Start Time | | Condition | less than equals | | Compare With | Custom | | By | 09:00 AM | | Apply alert on | Custom: Monday to Friday | | Whom to monitor | Individual members, teams or the entire organization. In this example: the Engineering Team | | Who gets notified | Individual, Reporting Manager, All Admin, Custom | | When to send | Same day at 10:00 AM | **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 1. Open the alert settings: go to **Admin Settings › Alerts.** 2. Click **"Create New"** button 3. Choose the **Alert Schedule**: Daily Notification. 4. Set the **Alert Type** to Attendance and enter an **Alert Name**, for example "Early Start (Engineering Team). 5. **Set the condition:** * **Variable:** Start Time * **Condition:** lessthan equals * **Compare With:** Custom * **By:** 09:00 AM 6. Choose **Apply alert on**: Custom, then select Monday to Friday. 7. Choose whom to monitor: under **Applicable to**, select Teams, then choose Customer Support. 8. Choose **who gets notified**: Individual, Reporting Manager, All Admin, Custom 9. Set **when to send**: Same day at 10:00 AM. 10. **Save the alert** to activate it. ![](https://storage.crisp.chat/users/helpdesk/website/-/6/7/1/e/671eefeed0317800/image_4svt62.png) --- ### How the rule is evaluated Start Time is the time a member's day begins Because the condition is less than equals, a start at exactly 09:00 AM also triggers the alert. In plain English: the alert lists every member of Engineering whose day began at 09:00 AM or earlier. Set the value to the team's start time minus the window you want to allow. For a 10:00 AM start and a one-hour window, use 09:00 AM. A start time does not change once it is recorded, so the list is complete as soon as the cut-off has passed. Sending at 10:00 am, when the team's day begins, puts the list in front of the manager at the start of the day. A member who has not started by then has no start time and is not listed **Worked example** Rule: Start Time is greater than equals 19:00 AM. | Member | Start Time | Triggers? | | ---- | ---- | ---- | | Arjun Reddy | 08:40 AM | Yes | | Divya Menon | 08:55 AM | Yes | | Imran Qureshi | 09:00 AM | Yes (equals the value) | | Tanvi Joshi | 09:20 AM | No | | Nikhil Bansal | 09:58 AM | No | --- ### What recipients receive Recipients receive an email naming the members who met the condition. ``` Dear User, Please be informed that the 'Early Start (Engineering Team)' alert has been triggered. Currently, 18 out of 120 users have met the following criteria(s): Start Time is less than or equal to custom value of 09:00 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 ``` | Download the sample csv: http://de9j6rhbdgsa2.cloudfront.net/sample-reports/early-start-alert-sample.csv --- ### Choosing recipients and timing | Field | Recommendation | Why | | ---- | ---- | ---- | | Who gets notified | Reporting Manager, Custom | The manager can ask about workload and hours; HR sees the pattern. Individual is left out because an early start is not a fault. | | When to send | Same day, 10:00 am | After the early cut-off has passed, as the team's day begins. | | Apply alert on | Monday to Friday | Early starts on a weekend are a different conversation; add those days only if you want to review them | **Use this alert as a prompt for a conversation.** Early Start shows a pattern worth checking; it does not explain why it happened. Tell your team which alerts exist and why, send the alert only to the people who need to act on it, and look at the pattern over several days before drawing conclusions. --- ### Reading the results: common scenarios | What you see | What it may mean | What to do | | ---- | ---- | ---- | | One member listed once | A one-off early start, such as a deadline or a call with another time zone | Usually no action; note the pattern. | | The same member on several days | Hours drifting earlier, or a workload that does not fit the day | Check in about workload and agreed hours. | | Several members of one team on one day | A shared cause such as a release or an early client call | Check the cause before addressing individuals. | | A member on a different shift or time zone | The alert applies one cut-off to the whole team | Place them in a team with its own alert | --- ### Good to know * **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. * **Values are per team or role.** Different teams work different hours; set a separate alert for each. * **Alerts follow your workspace settings.** Working days, shifts or the time zone configured for your workspace decide when an alert runs. * **Choose the window to suit the team**. A narrow window fires often; a wider one lists only clear early starts. --- ### 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 value I set trigger the alert?** Yes. The condition is less than equals, so a start at exactly the value is included. * **Why was a member who started early not listed?** 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. * **Why does the email arrive after the member started, and not at that moment?** The alert is sent once a day, at the execution time you set under When to send. * **Can I monitor only one member?** Yes. Under Applicable to, select Members and choose the member. * **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](https://help.flowace.ai/en/article/how-to-set-up-custom-alerts-in-flowace-v4qm3m/) **Need more help?** Reach out to support@flowace.ai and our team will be happy to assist. --- © Flowace Technologies Pvt Ltd | flowace.ai