Get alerted when a number crosses a line
Create an Analytics alert: pick a metric, a fixed threshold or a percent change, a window and recipients, per project if you like. How often it checks, when it fires and who receives what.
Partly in the app today. Items marked Planned are not built yet.
On this page
An alert watches one metric and tells you when it crosses a line: late RFIs over 10, weighted pipeline falling below a floor, open punch rising 25% month over month. Alerts never widen access. Each recipient is told only about numbers they could already see.
Open Analytics → Alerts at /companies/{company}/analytics/alerts, or choose Alert me… on any dashboard tile to start with that tile’s metric and filters filled in.
Create an alert
-
Choose New alert
Or use Alert me… from a tile menu, or Alert me if this persists on an insight.
-
Name and metric
Give it a Name that says the rule (“Late RFIs over 10”) and pick the Metric.
-
Condition
- Rises above or Falls below a fixed Threshold.
- Rises by % or Falls by %, a Change (%) against the previous period of the same length. Percent conditions need a window other than All time.
-
Window
Over sets the period the value is measured on. The default is last 30 days.
-
Narrow it (optional)
Only counting adds filters, such as one project or one status. Alerts started from a tile bring the tile’s filters with them.
-
Per project (company alerts)
Tick Each project separately to check up to 50 projects one by one. The alert then fires for each project that crosses the line, instead of once on the company total.
-
Delivery and recipients
Send In-app or In-app and email. Recipients defaults to you; add up to 50 people with analytics access. The form shows the rule as a sentence (“Tell me when … over …”) so you can check it before saving.
When an alert fires
- Alerts are checked every 15 minutes.
- An alert fires once per period while the condition holds, so you don’t get the same message every 15 minutes. The period follows the window:
| Window | Fires at most once per |
|---|---|
| Last 7 days | Week |
| Last 30 days, month to date | Month |
| Last 90 days, quarter to date | Quarter |
| Last 12 months, year to date | Year |
| All time | Once |
- Each recipient’s message is computed with their own permissions. If the breach isn’t visible in someone’s data, they get nothing.
- Every firing also sends an
analytics.alert.firedevent to the company’s webhook subscriptions, without metric values. You don’t configure that in the alert form.
The list shows each alert’s Condition, Last value, Last fired and Recipients, with On and Off to pause it and Delete. Analytics admins manage every alert; everyone else manages their own.
Three alerts worth setting up
Illustrative rules. Pick thresholds that fit your jobs.
| Name | Metric and condition | Why |
|---|---|---|
| Late RFIs over 10, by project | Late RFIs, rises above 10, each project separately | Catches a job whose design team has stopped answering |
| Punch growing fast | Open punch, rises by 25% | Early warning before closeout |
| Pipeline floor | Weighted pipeline, falls below $5,000,000 | Tells BD and leadership when new work is drying up |
Choose the window last, and remember it does two jobs: it sets the period the number is measured over, and how often the alert can fire. Open the metric in Explore with the same window first, so you know what the alert will actually see.
Common mistakes
Mistake: An alert on the company total that hides one bad job
In the app: Tick Each project separately (company alerts) so a single project crossing the line fires on its own.
Mistake: Percent alerts on tiny numbers
In the app: Going from 2 to 3 is a 50% rise. Use a fixed threshold for small counts, or narrow the alert with Only counting.
Mistake: Sending to people who can't see the data
In the app: Each recipient needs analytics access, and they are only told about breaches in data they can read.
Mistake: Using All time for an alert you want to hear about again
In the app: An All time alert fires once and then stays quiet. Pick a weekly, monthly or quarterly window for a standing rule.
Mistake: Expecting a repeat every check
In the app: An alert fires once per period while the condition holds. Look at Last fired to see the most recent one.
Before you save an alert
- The sentence preview reads the way you’d say the rule out loud
- Window matches how often you want to hear about it
- Per-project ticked if one job could hide inside the total
- Every recipient owns the response to this number
Terms on this page
Webhook · RFI · Punch list · Weighted pipeline · Row-level security
Next steps
- Put a target and owner on the same metric: Set goals and read the scorecard.
- Get the whole dashboard on a schedule instead: Send a report to your team every week.
- Goals, alerts and reports compared: Dashboard goals, alerts and reports.
Keep exploring
Related across os.construction
- DocsAnalytics BI guideGet started with Analytics, build a dashboard from the metric catalog, read the CRM & Pipeline pack, share and schedule results, and understand exactly which rows each person sees.
- ExplainerDashboard goals, alerts and reportsGoals, alerts, scheduled reports and insights in os.construction Analytics: what each one answers, how goal status is worked out, and a weekly routine that uses all four.
- GlossaryModel Context Protocol (MCP)An open protocol that lets an AI application discover and call tools and read data from other systems through a standard connector.
- DocsSend a report to your team every weekSchedule a dashboard, pack, exploration or the weekly Project Stories brief as PDF, Excel or CSV, daily, weekly or monthly, one file per project if you like, and only when a number says it matters.
- Blogos.construction is open for trialsThe app is live at app.os.construction. Start a 14-day free trial: project management and project financials today, with separate company accounting workflows and planned AI agents. Here's exactly what's live and what isn't.
- GlossaryGeneral ContractorThe company that holds the prime construction contract with the owner and is responsible for building the whole project, usually by managing subcontractors, suppliers and its own crews.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →