Reports & communication

Reports are short written summaries you send to a client when there's something worth summarizing. They're operator-led: you decide when one is warranted, draft it (with AI as a starting point if you want), and send it as a PDF — usually alongside an invoice.

When to send one

There's no schedule. Send a report when the period covered actually had something to say — meaningful work shipped, an incident worth documenting, a budget that needs context. Quiet periods don't need a report. Reports are pull-not-push: you opt in per send, the client can opt out per account.

The five sections

Drafts come back in a consistent shape so clients learn to read them quickly:

• • Summary — one short paragraph framing the period.
• • Work this period — what you did, grouped by what was done rather than when.
• • Site state — uptime, anything currently flagged, software state where relevant.
• • Open items — anything still in flight or awaiting client decision.
• • Next period — what's queued or worth their attention soon.

How drafting works

From a client's profile, open the outbound composer and choose “Draft new” report. Pick a period; Field gathers the work items, time entries, findings, uptime stats, and budget activity for that window across the client's sites. If you have an AI provider configured, those signals become a draft you can edit. If you don't, you get the structured data laid out for you to write from. The output is markdown — edit freely until it reads the way you'd say it.

Sending

Reports are sent through the outbound composer as a PDF attachment on a single email — typically bundled with an invoice and a short cover note. Field renders the PDF fresh from the markdown plus your branding, so edits to either propagate without re-saving anything. Sending marks the report sent and records the recipient and subject for the per-client history.

Per-client history

Every draft and sent report appears on the client's profile in a Reports section, most recent first. Each row shows the period, status, and (once sent) the recipient and subject. The PDF is regeneratable on demand from the stored markdown — there's no archive of bytes to manage.

Client opt-out

Clients can opt out of reports on their profile's notification preferences. The toggle doesn't hard-block sending — the composer surfaces a soft warning if you attach a report to a client who's opted out, so you can make the call. The intent is to spare you from drafting reports the client won't read.

Without AI

Reports work without an AI provider configured. The composer surfaces the same structured period summary — work done, findings, budget, uptime — and you write the narrative yourself. The send and history flow is identical.