LFW

The engagement · Service report

A monthly statement of the work — measured, not remembered.

Most vendor reporting is a reassuring email. Yours should be a document: what was requested and how fast it was handled, what the uptime actually was, how your accessibility and performance scores moved, and what changed on the site and when.

Every number is traceable

The report is compiled from the same systems that run and monitor your site — Monitor's daily scans, Analytics' first-party traffic, Looking Glass's nightly record of what changed, and the request history in your portal. That's the difference between a vendor saying the work happened and showing it: every figure in the report can be walked back to the instrument that produced it.

What's in it

  • Requests opened, handled, and how fast — from the portal's own record
  • Uptime and incidents, if any
  • Accessibility and performance score trends, against last month
  • What changed on the site and when — pages added, content updated, links moved
  • What's queued for next month

Where it arrives

In your portal, every month, alongside the records it draws from. Nothing to compile by hand on your side, nothing to chase — and like everything else in the portal, it exports.

This is the accountability layer of the engagement.

It comes with website management — it isn't sold separately, because it's how we stay honest.

Prefer to write?

Tell us what needs to work better.

Slow, fragile, hard to edit, missing a workflow — say it plainly. You'll get a straight answer, not a ticket number.

You'll get a straight answer, usually the same day.