Overview

Mobaro produces several different kinds of automated reports — Result Reports, Summary Reports, Operations Reports, Work Forecast Reports, and Availability Notifications. They look similar from the recipient's inbox (an email, sometimes with a PDF attached), but they answer very different questions and serve very different audiences. This guide is a decision tree for picking the right one — by audience, by question, by frequency, and by use case — so you don't end up sending leadership a 60-page Result Report when what they wanted was a Summary, or sending a frontline crew a Forecast when what they needed was a same-day Operations PDF.

Why this matters: Mismatched reports are a quiet productivity tax. The wrong report for the audience either gets ignored (too detailed, too aggregated, too late) or worse, gets acted on using the wrong signal. A Summary Report aggregates metrics across many Checklists; a Result Report drops the full record of one Checklist. Treating one as the other leads to bad decisions. The five-minute investment of picking the right report once saves recipients hours of confusion every month.

Required access: Creating any of these reports requires Notification Rules: Create in your Role (Super Users have it by default). Some report types — notably Operations Report — require feature activation by your CSM or [email protected] before they appear as an option. See Activating the Operations Report.

The five report types at a glance

Report type	What it answers	Cadence	Best for
Result Report	"Send me the full record of this specific Checklist the moment it's submitted."	Per-Result (event-driven)	Compliance archiving, immediate-action triggers (audit fails, safety issues), per-event customer or partner reports.
Summary Report	"How many Checklists got completed vs. missed and how many Assignments were created vs. resolved?"	Daily, weekly, or monthly	Manager check-ins, team-lead recaps, leadership-light reviews.
Operations Report	"What were yesterday's operating hours, downtime, dispatches, and per-attraction performance?"	Daily (next-morning delivery)	Park Directors, ride managers, ops leadership wanting a single "yesterday recap" PDF.
Work Forecast Report	"What work is coming up — Schedules due, Assignments open, deadlines approaching?"	Daily or weekly	Maintenance leads, planning, anyone responsible for prepping the next shift or week.
Availability Notification	"Tell me when a less-frequent or critical Checklist becomes available."	Event-driven	Annual inspections, monthly safety walks, anything where the Checklist appearing is itself the news.

Note: All five are configured under Notification Rules in the Mobaro Backend. Despite the name "Reports," they're technically Notification Rule sub-types — which is why they share the same recipient and scoping mechanics.

The decision tree: pick by question

Start with the question your recipient is actually trying to answer. Each question maps cleanly to one report type:

"Send me each individual Checklist record as it comes in"

→ Result Report. One email per submitted (or approved) Checklist, with the full Result attached. Use this when each event matters in isolation — a fail audit needs an immediate response, a safety inspection record has to be archived, a vendor needs the report for the work they performed.

Best practice: Pair Result Reports with a Report Template to control exactly what's included in the PDF. The default template includes everything; trimmed templates make external-facing Reports much cleaner. See Creating and using Report Templates.

"Tell me how the team is performing across many Checklists"

→ Summary Report. Aggregates Checklist completion vs. miss rates and Assignment creation vs. resolution rates over a period (day, week, month). Click-through links in the email take recipients to the underlying Results in the Backend if they want to drill in.

"Give me a one-page recap of yesterday's operations"

→ Operations Report. Daily PDF with park-level totals (operating hours, downtime, attendance) and per-attraction details (uptime, guests carried, dispatches, hourly performance). Most useful for parks running RideOps or operational logging through Mobaro.

"Show me what work is coming up in the next day or week"

→ Work Forecast Report. Looks forward instead of back — surfaces Schedules due, Assignments open, and upcoming deadlines so a planner or shift lead can prep their crew or materials ahead of time.

"Just tell me when a critical or rare Checklist becomes available"

→ Availability Notification. Sends a message the moment a Checklist becomes scheduled and available to perform. Useful for annual inspections, monthly safety walks, or any low-frequency Checklist where the appearance of the work is itself the prompt to act.

Picking by audience

A different angle: which report fits which role? These mappings are starting points, not rules — adjust to your team's preferences.

Audience	Default report fit
Frontline operator / technician	Usually doesn't need scheduled reports — they have the live mobile app. Availability Notifications for critical Checklists make sense.
Shift lead / supervisor	Daily Summary Report for the team's previous-day performance + Work Forecast Report for what's ahead today or this week.
Department manager (Maintenance, Aquatics, F&B)	Weekly Summary Report rolling up their team + Result Reports for high-stakes Checklists (safety audits, regulatory inspections).
Park Director / Operations leader	Operations Report daily + Summary Report weekly. The Operations Report is the centerpiece for daily ops review.
Compliance / safety lead	Result Reports for every safety-critical Checklist + Summary Reports for compliance roll-up. Often paired with a tight Report Template to control what gets archived.
External party (vendor, regulator, partner)	Result Report with a custom Report Template trimmed to the fields they care about. Often delivered to a Location email rather than a User.

Worked examples

Example 1: Audit fail needs immediate escalation

Scenario: A weekly safety audit fails. The compliance lead and the Park Director need to know within minutes, not the next morning.

Setup: Result Report triggered on submission of the Safety Audit Checklist, scoped to that Checklist only. Recipients: compliance lead + Park Director. Use a Report Template that highlights the failed sections.

Result: The moment the audit is submitted, both recipients have the full record in their inbox and can act before the next shift change.

Example 2: Park Director wants a single daily ops view

Scenario: A Park Director wants one email each morning covering yesterday's operating hours, downtime, attendance, and per-ride performance — no manual digging.

Setup: Operations Report, daily, scoped to the park's top-level Location Group. Recipients: Park Director + senior leadership. Naming convention: Operations — Park Directors — Daily Recap.

Result: A single PDF arrives every morning before the leadership stand-up. The Director walks into the meeting already informed.

Example 3: Maintenance lead prepping for the week ahead

Scenario: A Maintenance lead wants Monday morning to start with a clear picture of what Schedules and Assignments are coming due that week.

Setup: Work Forecast Report, weekly (Monday morning), scoped to the Maintenance team's User Group and Locations. Window: 7 days forward.

Result: The lead opens Monday with a prioritized list of upcoming work and can pre-stage parts, allocate techs, and flag conflicts before the week starts.

Example 4: Annual ride certification needs to be caught the moment it's due

Scenario: An annual structural inspection only becomes available once a year, and the inspection team needs to know the moment it's scheduled — they're not watching the dashboard daily.

Setup: Availability Notification on the annual inspection Checklist, scoped to the rides in question. Recipients: inspection team User Group.

Result: The team is alerted the moment each annual inspection becomes available, with no chance of it slipping through the cracks of routine work.

Example 5: Department manager wants a weekly team recap without the noise

Scenario: An Aquatics manager wants one weekly email summarizing how the team did, with the option to drill into specific Results if something stands out — but without 50 individual Result Reports cluttering their inbox.

Setup: Summary Report, weekly (Monday morning), scoped to the Aquatics team and Locations. Recipient: the manager. They click into the Backend if something looks off.

Result: One actionable email per week instead of a flood of individual reports. The Backend remains the source of truth for drill-down.

Combining report types

Most teams end up using two or three report types in combination, layered for different purposes. The most common stack:

Result Reports for the few Checklists where each event matters individually (safety audits, regulatory inspections).
Summary Reports for the routine roll-up that keeps managers informed without drowning them.
Operations Report at the leadership tier for daily ops oversight (where activated).
Work Forecast Reports for planning roles.
Availability Notifications sparingly, for low-frequency critical Checklists.

Best practice: Audit your report Rules quarterly. Recipients change roles, Checklists get retired, and the report stack tends to accumulate over time. A short review — "is each of these still going to the right person and answering a question they care about?" — keeps inboxes clean and trust in the system high.

Anti-patterns to avoid

Watch out for these patterns, which create report fatigue and erode the value of automated reporting:

Sending Result Reports for everything to everyone — busy managers archive without reading, the data isn't actually informing decisions, and the few important Result Reports get lost in the flood.
Treating Summary Reports as audit records — they're aggregated metrics, not records of individual Results. For audit purposes, use Result Reports with a Report Template tuned for archiving.
Configuring an Operations Report and forgetting it requires activation — if it doesn't appear when you go to create the Notification Rule, the feature isn't enabled. Check with your CSM.
Using Work Forecast Reports as a replacement for the live Backend — they're a planning tool, not the system of record. Time-sensitive changes still need the Backend.
Stacking too many overlapping Rules — e.g., a daily Summary, a weekly Summary, a Result Report on the same Checklist, and an Availability Notification for the same audience. Pick the one that best fits the question and let the others go.
Naming Rules vaguely — "Daily report" tells future-you nothing about who it's for or what it covers. Use a naming convention like [Type] — [Audience] — [Scope] (e.g., Operations — Park Directors — Daily Recap) so audits in six months are painless.

Frequently asked questions

Q: Why are these called "Reports" if they're configured under Notification Rules?
A: Mobaro treats Reports as a sub-type of Notification Rule because they share the same recipient and scoping mechanics — who gets it, where it applies, what triggers it. The "Report" name reflects what the recipient gets (an emailed report or PDF); the "Notification Rule" name reflects how it's configured. Both names appear in the product.

Q: Can the same User receive multiple report types?
A: Absolutely — and most managers do. A common stack: a daily Summary Report + a weekly Operations Report + Result Reports for safety-critical Checklists. Configure each as a separate Rule.

Q: Why don't I see the Operations Report when I try to create a Notification Rule?
A: The Operations Report requires feature activation by your CSM or [email protected]. If it's not showing in the type list, it's not enabled for your account. See Activating the Operations Report.

Q: Can I customize the content of a Summary Report?
A: Summary Reports have a fixed format — the four standard metrics (completed/missed Checklists, created/resolved Assignments). Customization happens at the scoping level (which Checklists, which Locations, which audience), not at the content level. For more flexibility on content, a Result Report with a tuned Report Template is the more customizable path.

Q: What's the difference between a Summary Report and the Compliance dashboard?
A: The Summary Report is push (delivered to inboxes on a schedule); the Compliance dashboard is pull (you go look at it). Summaries focus on Checklist and Assignment volumes; the Compliance dashboard focuses on Schedule compliance, deviation rates, and Certification saturation. Use both — Summaries for routine inbox awareness, Compliance dashboard for deeper review.

Q: Can I send a Result Report to an external email that isn't a Mobaro User?
A: Yes. Result Reports can be sent to the Location's email field or to BCC recipients (User Groups), and Locations can be configured with external email addresses. This is the typical pattern for vendor or regulator delivery.

Q: What happens if a recipient's access changes after a Rule is set up?
A: The Rule re-evaluates each time it fires. Summary Reports in particular are scoped by what the recipient has access to — so if a User loses access to a Location, that Location stops appearing in their next Summary. See How to set up Summary Reports for the worked example covering access-scoped delivery.

Report selection guide — picking the right report for the job