When to use this
- Bond cleans — agent asks for evidence of inclusions completion. Reply with the PDF rather than a 14-paragraph email.
- Strata — monthly proof-of-service to the strata manager (PICA, Bright & Duggan, etc.).
- Commercial contracts — quarterly evidence pack to the facility manager.
- Medical / healthcare — accreditation surveyor requests a 6-month evidence snapshot.
The email-PDF action handles the entire workflow without leaving the dashboard.
Step 1 — Complete the scope items
On /dashboard/jobs/[id]/scope, work through the checklist:
- Tick items complete (or skip with a reason)
- Attach photo evidence per item (📷 Before / 📷 After buttons capture directly from the camera)
- Add notes where context matters
The scope can be partial — the PDF generates whatever state the scope is in. But typically the operator emails after completion.
Step 2 — Tap "✉ Email PDF"
At the top of the scope page, next to ↓ PDF, tap ✉ Email PDF.
A popover opens with:
- Recipient email — the agent / facility manager / strata manager's email
- Optional message — your cover note, e.g., "Hi Sarah, please find the bond clean evidence attached. Happy to discuss any items via reply."
Step 3 — Send
Tap Send. The action:
- Fetches all the scope items + linked photo evidence
- Generates a branded PDF in-process (same as the ↓ PDF download — single source of truth)
- Photo thumbnails embedded inline (up to 2 per item; remaining show as a count chip)
- Sends via the platform's Resend email infrastructure with the PDF as a 1-2MB attachment
- Audit log records the send for compliance
The popover shows a success message and auto-closes after 2.5 seconds.
What the recipient sees
- From: your business name, with reply-to set to your business email
- Subject: "Scope-of-work summary — Job #XXX · Customer Name"
- Body: your optional message + a brief explanation of the PDF contents
- Attachment: branded PDF with header, status summary, per-zone items with status badges, embedded photo thumbnails
Tips
- Reply-to is your business email (not the platform). When the agent replies, it lands in your inbox.
- Idempotency: avoid clicking Send twice rapidly. The infrastructure has built-in retry but doesn't dedupe explicit re-sends from the operator side.
- Multi-recipient: send to one recipient per action — copy-paste BCC isn't supported in this flow. For multi-stakeholder distributions, send once per recipient (the audit log keeps a clean per-send record).
- Email-not-configured fallback: if Resend isn't set up on your tenant, the action returns "Email not configured" — use ↓ PDF instead and attach manually in your email client.