Skip to content

The monthly report

Reports builds one month for a client group or for the whole workspace. Nothing is asked of a site to make it: every figure on the page was recorded as it happened, by the monitoring that watches the sites, by the record every tool writes, and by the jobs that ran.

  1. Open Reports.
  2. Pick the month and the client group, or leave the group as every site in the workspace.
  3. Press Show the month.

The top of the Monthly report page: Print, Download CSV and JSON buttons, a Month picker set to August 2026, a Client group picker set to every site in this workspace, and a Show the month button, above a panel naming the workspace and the month with a line saying everything on the page was recorded as it happened and nothing was asked of a site to make the report.

Sites. Every site in the report with its address, its group, how many checks it answered this month, how many days it was down, how many updates are waiting, and where it stands now. Counts rather than a percentage, on purpose.

The Sites section of a monthly report: five sites in a table with their addresses, client groups, checks answered this month, days down, updates waiting and a state pill, with a note explaining that answered counts the looks the site replied to and days down counts the days it did not reply at all or refused the key.

What was done. The jobs that ran, when, who queued them and how each landed, then a count of every change by the tool that made it, split by whether it was a person, an AI app or a job.

The What was done section: two jobs with what ran, when, who queued them and their per-site results, then a row of counts for people, AI apps, jobs, done, failed and sites touched, and a table of what was done by tool name with how many times each ran and how many failed.

What happened on the sites. The changes the sites’ own people made in wp-admin, counted by each site itself and collected by the scheduled checks: pages edited, sign-ins, plugins and themes changed, settings changed, media uploaded. Who did each one is on the site’s own log, not on this report.

Needs attention now. This is how the sites stand today, not how they stood during the month the report covers. The section says so in as many words, because a client reading it in October should not think it describes August.

The Needs attention now section of a report, marked one site. A note says this is how the sites stand today, not how they stood during the month. Under a site’s name, two lines: PHP reached end of life on a named date and no longer gets security fixes, and three plugin updates are waiting.

Refused calls. The calls a wall stopped before they ran, with the code and how many times. A refused call never reached the site, so it changed nothing, and the report says so.

  • Print is the report without the dashboard around it. It is a real print stylesheet, so it prints to PDF and reads on paper.
  • Download CSV goes into a spreadsheet.
  • JSON goes into whatever you already send clients.

The same rows sit behind all three.

Changes are kept 400 days, a day’s checks 400 days, and a day’s counts of what happened on a site 400 days. Any month you have history for can be picked.

Only changes are recorded. Reads are not.

A client group’s report can go to the client’s own people, on the first of the month, wearing your name instead of ReDock’s. See Reports in your own name.


Open Reports in ReDock Web.