Audit · Webgardenpath

Match-day observation

One home fixture, from the first push to the last replay clip, read from a guest login rather than from an admin panel.

Format
One fixture, written note, short debrief
Duration
Ten days around one home match
Where
Remote from a guest login; optional concourse hour
Fee basis
Fixed fee from RM 4,200

Some desks do not need a four-week season audit. They need a named person to live with the app on one home Saturday and write down the sequence: first alert, team news, ticket wallet, half-time clip, full-time table.

The observation starts two days before kick-off, when the fixture reminders usually go out, and ends when the last replay is posted. The note is shorter than a season reading — typically four pages — and the debrief is forty-five minutes rather than ninety.

We still work from a guest login. Sitting in the admin panel during the match tells you what the vendor thinks happened; sitting in the supporter view tells you whether the half-time blog was under a shop banner.

If rain delays kick-off, we stay with the app through the delay. That is often when duplicate alerts pile up. The fee does not change for a delay. A postponement to another week is re-booked; the deposit holds the new date if it falls within 30 days.

Prepare the same guest access you would for a season audit, plus a note of any match-day campaign (a shirt drop, a ticket lottery, a player vote) so we know which screens were meant to carry the afternoon.

Ask for this reading

Name the club, the app, and the next fixture week you want observed.

Write to the desk