Skip to content

Downloading reports

Finished monthly SLA reports live in the report archive in your console. The archive is not just storage — it's the delivery point and your pre-flight check before anything reaches a client.

Reading the archive

Each row is one client's report for one month. At a glance you get:

  • Period — the month the report covers.
  • Client — who it's for.
  • Uptime badge — the month's uptime, shown green when the client's SLA target was met. Scanning this column is the fastest way to see which clients had a clean month and which need a conversation.
  • Incidents — how many incidents the month contained.
  • Coverage — the measurement coverage percentage, the same figure disclosed inside the report. A low number here tells you, before you open the PDF, that part of the month went unmeasured — a monitor added mid-month, or one that sat paused. See What's in a report for why this number matters.
  • Status — Generated when the PDF is ready, or Failed with the reason when generation didn't complete. A failed row tells you why, so you find out from the archive — not from a client asking where their report is.
  • Download — fetches the PDF.

Getting the report to the client

Say it plainly: forwarding the report to the client is a manual step today. UpAll does not email reports to anyone, and clients cannot see reports in their portal — the portal shows live status, not documents (see Client portal overview). The report exists only in this archive until you download it and send it on.

Most teams fold that into a monthly routine that takes a few minutes:

  1. Early in the month, open the archive and scan the badge column — green across the board is most months.
  2. For any client that missed their target, open the PDF and read the incident log before the client does, so your covering note explains the month rather than reacting to it.
  3. Check the coverage column; if it's low, be ready to say why (new systems onboarded mid-month is the usual honest answer).
  4. Download and attach each PDF to your own monthly service email, under your name and your relationship.

That last point is why the manual step is not a gap to route around: the report carries your branding and measures your SLA commitment, and it lands better inside your email, with your commentary, than it would arriving cold from a platform address.

If a client's report is missing

Reports generate on the 1st of the month for the previous month, on paid plans only, and only for clients whose systems were monitored and actually checked during that month. A brand-new client, a client with no monitored systems on their sites, or a workspace on a plan without reports produces none. Language and time settings that shape the PDF itself are covered in Report language and timezone.