grova.
Plan a pilot
Home / Blog / GROVA Notes 01
GROVA NOTES · ESSAY 01

Why “submitted” isn’t “verified”.

A photograph arriving on a server tells you that someone submitted evidence. It does not yet tell you whether the work happened at the correct location, during the execution window, or against the required creative.

PUBLISHED BY GROVA RESEARCH · OCTOBER 2026 · 6 MIN READ

Consider an enterprise rollout of 1,000 outdoor billboards across three metropolitan regions. Two weeks into the flight, the operations team sends an executive summary claiming: “84% Complete.”

What does that number actually mean? In conventional OOH tracking software, it almost always means: 842 photographs have been uploaded into the shared cloud folder.

It does not answer whether:

  • The photographs were taken at the contracted coordinates or 400 meters away.
  • The artwork displayed matches the approved Q4 regional creative or last quarter’s expired vinyl.
  • The photo was captured live in the field or selected from a worker’s camera gallery.
  • Any duplicate photos were reused across multiple unit identifiers.

The Three Buckets of Truth

In GROVA’s data model, we reject the single “Percent Done” metric. Instead, every campaign must reconcile three independent buckets:

METRIC A 84.2% Submission Rate (842 / 1,000)
METRIC B 78.1% Verified Execution (781 / 1,000)
METRIC C 92.8% Unit Pass Rate (781 / 842)

Notice the vital operational distinctions:

  • Submission Rate (84.2%): How much physical evidence has reached the server. Measures field worker velocity.
  • Verified Execution (78.1%): How many distinct contracted units have met all verification rules. Measures true commercial delivery.
  • Unit Pass Rate (92.8%): What percentage of submitted evidence passed without adverse decision. Measures vendor quality.

Keep the Reasons with the Evidence

When an automated rule flags an exception—such as an auto-rickshaw captured 42 meters outside the designated transit depot—it must not disappear into a generic “failed” column. It lands in the Review Queue with its full lineage:

  • Planned coordinate vs actual captured coordinate, visibly connected on the campaign map.
  • Accuracy circle and geofence boundary.
  • Exact capture time, device timestamp confidence, and server receipt time.
  • Image hash comparison against all previous attempts.

This ensures human reviewers can make an informed, recorded decision: approve with an operational note, request a field revisit, or reject the submission with an auditable reason.

Conclusion: Certainty is a Practice

Physical execution is messy. Weather delays mounting, GPS drifts in urban canyons, and traffic obstructs sightlines. Pretending that 100% of field submissions are flawless creates friction between brands and agencies.

By separating submission from verification, GROVA gives both parties an honest surface to work from. Certainty doesn’t come from hiding exceptions—it comes from resolving them with ground truth.