Where do I create a client report?
Open Reports, choose Client reports, then Create report pack. The Reports area also keeps Analytics and Recurring exports available. Existing recurring export schedules are separate from client report packs.
Choose the client name, pack name, reporting month and time zone. Select only the monitors that belong in this report and give them client-facing names. Saved monitor IDs define the scope; adding another monitor to a tag does not add it to a saved pack automatically.
What can I brand and write?
Add an agency name, accent color and optional logo, then choose report sections. Work completed and next actions are your own reviewed text. PageLantern does not infer work you performed or copy internal incident comments into the report.
PDF text currently supports Latin characters and common Western European accents. Unsupported characters are identified before generation instead of being silently replaced. Logos must be PNG or JPEG, up to 1 MB and 2048 pixels on each side.
Report packs support HTTP, API, TCP, browser, SSL and domain monitors. Client-facing names replace raw monitor URLs. Keep confidential information out of the names and narrative you deliberately add. Browser screenshots, credentials, internal owners and recipient addresses are excluded from the client report.
How do preview and approval work?
Generate a preview and wait for the edition to finish. Check the period, selected monitors, data notices, narrative and PDF before approving. Approval accepts that exact version of the report. If another person changes it while you review, reload and review the new version before approving.
Approved editions do not change when monitors, labels or pack settings change. Correct an approved report by creating a new revision and approving it again. Draft downloads are marked as drafts; approved downloads and outgoing attachments use the saved approved PDF.
How does the client receive it?
Review the recipients and choose Send approved edition. Each recipient gets a separate email with the approved PDF attached, so recipients do not see one another’s addresses. PageLantern uses its configured sender. You can verify an optional agency reply-to address so client replies reach your mailbox.
Accepted by provider means the mail provider accepted the message, not that it reached the inbox. Retry failed recipients only. Delivery uncertain means the provider may have accepted a message before the connection ended; investigate before deliberately sending another copy.
The client opens the attachment without a PageLantern account. There is no public report link. Downloaded and emailed PDFs cannot be recalled.
What does monthly preparation do?
A monthly schedule prepares the previous calendar month as a draft on the first day of the month at 09:00 in the saved time zone. Review and approve each edition before sending. Saving a pack or schedule sends no client report. Pause monthly preparation before changing the report time zone, then re-enable the schedule.
After missed runs, the scheduler prepares the latest missed month once. Older months can be generated manually when they are within your monitoring-history retention. Requests outside available retention are rejected instead of silently shortened.
If preparation fails, access changes or a workspace is restored, the schedule may pause with an explanation. An owner or admin reviews the pack, resolves the problem, then enables and saves the schedule again. A restored workspace never resumes client mail automatically.
What do the numbers mean?
Successful checks is successful divided by successful plus failed conclusive primary availability checks for the selected HTTP, API, TCP and browser monitors. It is weighted by check count, not an average of monitor percentages. Renewal warnings and secondary-location evidence are not counted as availability failures.
No observations displays Not measured. Days with observations do not prove uninterrupted coverage; where scheduling history is unavailable, the report says Coverage history unavailable. Incident time is a monitoring event window, not verified customer downtime. An incident closed by pausing a monitor is not described as recovery.
Renewal information is a snapshot as of report generation, not a claim about the historical month end. Estimated P95 uses latency histogram buckets; browser journeys and simple requests are separate populations.
Who can use it, and what are the limits?
Client report packs require Team access. Owners and admins can create packs, review drafts, approve and send. Members and viewers can read approved editions in their workspace. The limits shown in the application take precedence over these standard defaults: 100 monitors per pack, 10 recipients per send and a 10 MB PDF.
Stored report artifacts expire 90 days after generation by default. Artifact lifetime is separate from monitoring-history retention. A downgrade pauses generation and sending; authorized users can still download existing approved editions until they expire.