Proof of service, in their inbox.

The customer never logs in. They get a report with the work they're paying for, the observations you chose to include, and the photos from the job.

What goes out

A report the property can forward

Staff compose it, staff send it. A draft can be prepared automatically; sending is a person. A customer-facing email is not something you want a cron to surprise anyone with.

  • Observations and finished-work photos on the customer copy
  • One building or a whole portfolio, from the contacts you pick
  • Upcoming scheduled work can ride along, with staff exclusions

One building or a portfolio

Pick the contacts, and the buildings they should see come with them. Upcoming scheduled work can ride along for a 7, 30, 90 or 365-day window, with staff exclusions if something shouldn't be listed.

Observations with photos

Attach the finished-work photos and notes that belong on the customer copy. Photo links in the email last thirty days. Resend a sent report to refresh those links without changing the original sent date.

Who received it is visible

When there's more than one recipient, the email names everyone it was sent to — names, not addresses — so a property manager can see that their colleague got it too.

Locked once sent

Draft, then Sent or Cancelled. There is no separate customer-approval step on the report. The quote is where the customer approves money; the report is where you show the work.

A Tuesday

From the job photos to their inbox

The photos are already on the job

The crew attached them in My Day. You are not hunting a group chat for the before-and-after.

Staff send it

A draft can be prepared automatically. Sending is a person. Pick the contacts, the buildings, the window of upcoming work.

The property forwards it

No portal. Names of who received it are on the email. Resend if a photo link ages out.

See it on your buildings

Early-access demos, with a person. We'll say plainly whether it fits how you work.

Request a demo