Esc

↑↓ move↵ openIndex · Pagefind

Goals, alerts and reports: which one when

A dashboard only helps when someone looks at it. Analytics has four ways to bring the right number to the right person: goals, alerts, scheduled reports and insights. Here's what each one answers, how goal status is worked out, and a weekly routine that uses all four.

Workflow explainer7 min readIllustrative numbers

The short answer

Four tools, four questions

Use a goal when a number has a target and an owner. Use an alert when someone must hear the moment a number crosses a line. Use a scheduled report when a group needs the same view on a timetable. Read insights for the things nobody thought to set a rule for. All four read the same governed metrics as your dashboards, and none of them shows a person a number they couldn't already open.

Goals, alerts, reports and insights compared
ToolAnswersMade ofWhen it runsWho gets itWhat you see
GoalAre we where we said we would be?A KPI with a target, an owner and an optional due dateLive, every time someone opens Goals or the scorecardShared with company Analytics, or privateMet, At risk, Behind, Unavailable; On track only by check-in
AlertTell me the moment it crosses a lineOne metric, a threshold or percent change, a windowChecked every 15 minutes; fires once per periodUp to 50 recipients, in-app or in-app and emailLast value and last fired
Scheduled reportPut the numbers in front of people on a timetableA dashboard, pack, exploration or Project StoriesDaily, weekly or monthly, optionally only if a condition holdsUp to 50 recipients, each rendered as themselvesQueued, Delivered, Failed or skipped
InsightWhat changed that nobody set a rule for?Findings from a built-in rule set, ranked by severityEvaluated nightlyEveryone with Analytics, filtered to what they can readOpen, dismissed or resolved
Goal status

Met, At risk, Behind: a 10% band

A goal is Met when the value meets the target. It's At risk when it misses by no more than 10% of the target, and Behind past that. Example: Daily log compliance at least 95%. Ten percent of 95 is 9.5 points, so At risk runs from 85.5% up to 95%.

Goal status bands for a target of at least 95%Below 85.5% is Behind, from 85.5% to just under 95% is At risk, 95% and above is Met. Sample values: 97% is Met, 89% is At risk, 81% is Behind.BehindAt riskMettarget 95%70%75%80%85%90%95%100%97% → Met89% → At risk81% → Behind

For an "at most" goal such as TRIR at or below 1.0, the band sits above the target: At risk up to 1.1, Behind beyond. If the value can't be read for you, the status is Unavailable, never zero. On track only appears when an owner sets it in a check-in. A check-in status stays in place, marked manual, until the next check-in.

A week with all four

The routine

MON 6:00 The brief arrives

A weekly schedule sends Project Stories: one written brief per project you can see, biggest moves first, built from fixed sentence templates over the same metrics as the dashboards. Every sentence links to the query behind it. Leadership reads it before the 7:30 meeting.

MON 7:00 PMs get their own pack

A second schedule sends the Project management pack as a PDF, One per project. Each PM gets only their job, rendered with their own access. The email carries download links, not attachments.

MON 7:30 Walk the goals board

Open Goals, filter to Behind and At risk, and ask each owner for a check-in with a note: what slipped and what happens next. The Scorecard shows every goal by project. A blank cell means that viewer can't read the number. Save as CSV drops it into the meeting notes.

TUE Read insights

Insights are evaluated nightly from a built-in rule set and ranked by severity. Each has Why? evidence, a ball in court and a next step. Assign the real ones, dismiss the noise with a reason, and choose Alert me if this persists on anything you want to keep watching.

WED 14:15 An alert fires

An alert on late RFIs, set to Each project separately, crosses 10 on one job. The PM and the ops manager get an in-app notice and an email, each computed with their own numbers. It won't fire again for that project until the next period, so nobody gets the same email every 15 minutes.

FRI 14:00 The exception report

A Friday schedule on the Commitments & changes pack uses Send only if: it goes out only when open change exposure is above the line you set. Most Fridays it's skipped, and the skip is recorded. When it does arrive, people read it.

Analytics home: report packs and saved dashboards
Analytics home: report packs and saved dashboards (sample data)
Choosing

Three quick rules

  • If nobody owns it, don't make it a goal. A goal without an owner is a chart with a line on it. Tick Alert the owner when it falls behind so the owner hears about it.
  • If it can wait until Monday, schedule it. Alerts are for numbers that need action this week. Everything else belongs in a scheduled report.
  • If the email is usually boring, add a condition. Send only if turns a weekly report into an exception report.

Terms in this guide

Semantic layer · Row-level security · RFI · Daily log · Change event · Webhook

Keep going

Want this on live job data?

Analytics is in preview in os.construction. Goals, alerts, scheduled deliveries, insights and Project Stories are live, and every number runs with the viewer's own permissions.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

All figures are illustrative. Pick targets and thresholds that fit your own jobs.

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file