A client update should not start with screenshots
At the end of a month, an agency often has the information it needs scattered across monitor histories, incident notes and its own work log. Turning that into a clear client update takes another round of copying, formatting and checking.
Client report packs bring the monitoring evidence into a branded PDF for a chosen client. You select the monitors, add context about work completed and next actions, then review the exact edition before it leaves your workspace.
Choose the scope and make it recognizable
In Reports → Client reports, create a pack with a client name, completed reporting month and time zone. Select the relevant monitors and give them names the client recognizes. Saved monitor IDs define the scope, so adding a monitor to a tag later does not silently add it to the report.
Add your agency name, accent color and optional logo. Work completed and next actions are your own reviewed writing. PageLantern does not infer work you performed or copy internal incident comments into the client narrative.
Review once, approve that exact edition
Generate a preview and check the reporting period, selected monitors, data notices, narrative and PDF. Approval accepts that specific version. An approved edition remains unchanged when a monitor label or pack setting changes later; corrections require a new revision and approval.
Send the approved edition to reviewed recipients. Each receives a separate email with the PDF attached, without seeing other recipients’ addresses. Clients do not need a PageLantern account. An optional verified agency reply-to lets their responses reach your mailbox.
Prepare next month without sending it early
A monthly schedule prepares the previous calendar month as a draft on the first day at 09:00 in the saved time zone. It does not email the client automatically. You still review, approve and choose when to send each edition.
This makes recurring reporting easier without turning an unfinished note or unexpected data gap into a client communication. Existing recurring exports remain a separate workflow, available alongside client reports in the Reports area.
Keep the numbers and limits understandable
No observations means Not measured. Successful-check percentages describe recorded checks, not a guarantee of uninterrupted coverage. Reports identify unavailable coverage history, estimated latency percentiles and incident event windows instead of presenting them as exact customer downtime.
Report creation and sending require Team access and an owner or admin role; members and viewers can read approved editions. Stored PDFs expire after 90 days by default. There is no public report link, and emailed or downloaded copies cannot be recalled.