Why multi-city programmes break without a shared log
Field reporting is not a photo dump at 23:00. It is a structured, location-wise update while the campaign is live: what ran, what failed, what the next city should change. When Mumbai files “good turnout” and Bengaluru sends twenty unlabelled images, the brand cannot decide whether to restaff, move a wall, or kill a format. Cities that do not share a template are not a programme. They are three separate jobs pretending to be one.
Clogik’s field reporting product is built for that loop—same fields, issue flags, a cadence ops can watch. We do not invent footfall or project counts. If a sensor was down for two hours, the wrap says so.
What every city must file
- Venue ID that matches the recce record—not a new nickname
- What actually ran (wall playlist, check-in, sampling beat) versus the plan
- Issues: power, NOC, queue spill, hardware, network
- Counted metrics only—sessions, check-ins, opt-ins—not estimated aisle
- Observation the next city can act on (shift time, backup court, spare sensor)
Recce first, report while live, wrap once
Reporting cannot fix a stand that was never recce’d. Power, height, and load-in still belong in the Recce Management System before fabrication. After go-live, field reporting is how you catch the things recce could not: a neighbour overbuild, a wall driver that fails at 11:00, a badge printer without overnight power.
Interactive installs add a second stream. An interactive wall should log sessions; event registration logs check-ins. Field reporting is the overlay: issues and observations across cities, tied to those systems so the account team does not merge photo shares with plays into one fake “engagement” number. Expo stands use the same discipline—see exhibition tech.
Cadence that agencies can staff
Daily is the default for a live weekend. Mid-day flags for blockers (no power, court closed). End-of-day for the comparable row. Do not wait until Friday to discover Thursday’s Hyderabad court was blocked. The point of multi-city reporting is to change Friday’s plan, not to decorate a slide.
WhatsApp versus a campaign OS
| Without structured reporting | With field reporting |
|---|---|
| Each city invents columns | One template; cities stay comparable |
| Issues found in the wrap | Issues flagged while the show is live |
| Photo ZIP as “proof” | Counted sessions or check-ins plus honest downtime |
| Next city repeats the same failure | Observation carries forward before travel is booked |
How this sits on Clogik’s stack
The wedge is recce → registration → interactive + data → field reporting. Reporting is not a BTL staffing pitch. On-ground teams exist as enablement when the brief needs people. Do not hire a reporting product if you only need promoters. Do not skip reporting if you are running walls and gates in four metros.
Named work (MGL India Energy Week, Sting F1, Vislook, IPL Fan Park) lives in industry use. We do not attach invented scale to this guide. AR/VR honesty: if the floor is a headset farm, that is a catalog supplier; if it is a playable wall, report plays, not “immersive impressions.”
Takeaway
Treat multi-city as one programme with one log. Recce before load-in, count what the software counted, flag issues the same day, and carry observations to the next city. That is field reporting—not a late-night gallery.
Plan reporting before the first city goes live
Share cities, cadence, and whether walls, registration, or enablement sit on the same stack.
WhatsApp Clogik ↗Frequently asked questions
What is field reporting for activations?
A structured, location-wise update while the campaign is live—issues, counted sessions or interactions, and observations—so cities stay comparable.
Why do multi-city programmes need one reporting template?
If each city invents its own columns, the brand cannot compare Mumbai to Bengaluru. One checklist, one status, one Monday artefact.
How does field reporting sit with recce and walls?
Recce is before load-in. Walls and registration log sessions and check-ins. Field reporting carries issues across cities while the programme is live.
Should field reports invent footfall?
No. Report what was counted or flagged. If a sensor was down or a court was blocked, say so.
Is field reporting only for sampling teams?
No. Expo stands, mall walls, and dealer meets need the same discipline. Sampling is enablement when the brief needs people.