Skip to content

Reports and Exports

Reports turn daily activity into usable business records. They should help the office answer what happened without rebuilding the day from messages.

AdminsOwnersCoordinatorsCustomers receiving records
Use this when

How SiteRun reports and exports support job completion records, evidence packs, worker activity and operational summaries.

SiteRun reports screen showing operational summaries, exports and practical records for office admins.
A job record can combine client, site, time, notes, evidence and activity into a printable closeout pack.

Workflow

  1. Review the job detail for missing notes, photos or sign-off.
  2. Generate the job completion report after closeout requirements are met.
  3. Use operational summaries for weekly review and follow-up.
  4. Export timesheet or worker activity data when the office needs a broader view.
  5. Keep exported records consistent with the business record and privacy requirements.

Operational notes

  • Reports should be generated server-side so mobile devices do not carry heavy processing.
  • PDF and email variables must be escaped and sanitised before rendering.
  • Exports should be practical: completion packs, evidence, timesheets and exceptions.

Common mistakes to avoid

  • Exporting before required closeout evidence is present.
  • Using reports as a replacement for good onsite notes.
  • Treating CSV exports as customer-facing documents.

Ready to try this workflow?

Open SiteRun, create one real job record and test the steps with the crew member who will use it onsite.