Reports and notifications
Export operational reports and notify teams when field work completes.
Audience: Admin · Supervisor
Chekku separates historical reporting (pull data on demand) from event notifications (push alerts when something happens). Both reuse the same visit and form data model.
Reports module
Standard reports
Prebuilt reports cover common operational views:
- Visits — volume, duration, by user/team/place/type.
- Forms — answer tables and aggregates (Reports from forms).
- Tasks — open vs. completed follow-ups.
- Tracking — distance or time summaries when GPS module is enabled.
Open Reports, choose a template, set filters, then preview.
Filters that matter
Always constrain reports with explicit context:
| Filter | Why |
|---|---|
| Date range | Performance and export size |
| Team / user | Accountability |
| Place | Customer or route analysis |
| Visit type | Avoid mixing incompatible activities |
| Form / version | Stable columns after form changes |
Exporting without visit type is a common mistake—see Common mistakes.
Export formats
Most reports support:
- Excel (.xlsx) — analysis, pivot tables, client deliverables.
- PDF — printable snapshots with current filters baked in.
Scheduled or emailed exports depend on plan; check your subscription or ask Chekku support.
Widgets and dashboards
Some reports offer widgets (charts, KPI tiles, maps). Widgets respect the same filter bar as tables. Pin frequently used layouts for supervisor dashboards.
Notifications
Notifications fire on events, not on a schedule:
| Channel | Typical use |
|---|---|
| Supervisor digest, client proof-of-service | |
| In-app | Task assigned, comment mention |
| Customer alert when visit completes |
Configure notification rules from form settings, visit types, or Workflows—not only from the Reports module.
WhatsApp requirements
WhatsApp notifications use your company's WhatsApp Business API credentials. Chekku connects to the channel you configure; Meta account ownership, template approval, and compliance remain with your organization. Test with internal numbers before customer-facing templates.
Email best practices
- Use clear subjects: place name + visit type + date.
- Include deep links back to Visit control detail when possible.
- Avoid attaching large photo bundles—link to the visit record instead.
Reports vs. notifications
| Reports | Notifications | |
|---|---|---|
| Timing | On demand / scheduled | Real time on event |
| Audience | Analyst, client, finance | Supervisor, customer |
| Content | Wide tables, exports | Short summary + link |
Use reports for audits; use notifications for immediate action.
Tips
- Document filter presets supervisors reuse weekly.
- After form key changes, validate export columns (Field keys and API).
- Pair WhatsApp alerts with a form that captures customer sign-off.
- For automation on submit, prefer Workflows over custom webhook mailers (Automations on form submit).