Compare the outdoor play record with the delivery actually bought

Translate the booking into a measurable obligation

Broadsign describes share of loop as a time-based allocation rather than a simple repetition count. Its documentation illustrates why changing content lengths can affect the relationship between the two. This is a platform capability, not a universal definition of what an advertiser has bought.

Read the approved booking with the media owner. Record screen identities, eligible dates and operating hours, spot duration, contracted delivery unit and any permitted aggregation. Determine whether the obligation applies to every screen, a network total or specified dayparts. A weekly total cannot establish compliance with an hourly minimum. Preserve any unresolved wording for the commercial owner rather than silently choosing the interpretation easiest to calculate.

Build a compatible expected-delivery calculation

Use the agreed loop or time-allocation model to calculate the expected quantity. In a deliberately simplified fixed loop, one ten-second play every sixty seconds during an hour implies sixty plays and six hundred seconds of content. That arithmetic is a planning illustration, not a claim that real networks always run fixed loops or uninterrupted hours.

Show assumptions alongside the calculation: partial opening hours, permitted interruptions, dynamic slot lengths and excluded inventory. Do not apply an audience multiplier to solve a missing-play question. If a supplier has changed the loop structure, ask for the actual scheduling basis and the approved contractual treatment. Keep planned allocation, scheduled opportunity and reported playback as separate columns so a shortfall can be located rather than hidden inside one percentage.

Qualify the actual play evidence

Broadsign's POP documentation distinguishes daily exports from near-live reporting and defines successful playback for that system. Obtain the corresponding definition for the supplier's implementation. Ask whether rows represent individual events, aggregates or multiple screens, and identify the report timezone, date range and creative version.

Match records to the booked screen list before summing. Inspect duplicate rows, partial intervals, unexpected creative identifiers and screens missing from the export. A disconnected player may upload records later; an empty report therefore needs a status investigation rather than an immediate declaration that the screen was dark. Conversely, a player log alone does not prove that a physical panel was powered, unobstructed or noticed. Keep those evidentiary limits explicit.

Resolve the difference without erasing its location

Prepare a reconciliation by the smallest commercially relevant unit: perhaps screen and day, or market and hour. Label confirmed delivery, pending telemetry and unexplained variance separately. Ask the supplier for the particular missing evidence instead of requesting another unqualified campaign total. Preserve the original report before incorporating corrections.

If delivery differs from the agreement, send the factual bridge to the authorized commercial owner for interpretation and any permitted remedy. Do not invent a makegood formula or automatically trade missed peak hours for cheaper hours elsewhere. Record the eventual disposition and its scope. The useful result is an explainable account of where the agreed service was delivered, where it remains uncertain and what decision follows, not a cosmetically perfect dashboard.

Make the reasoning concrete.

A fictional museum buys one ten-second slot in each minute on two indoor screens for an agreed hour. A supplier file shows 120 plays, but all rows belong to one screen and include two creative versions.

The museum requests the missing screen records and excludes the unrelated creative from its provisional bridge. It does not infer audience exposure or announce a contractual breach from the first file.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Obligation

   What delivery unit and aggregation level does the order actually specify?

2. Expected

   Which loop and operating-hour assumptions produce the planned amount?

3. Record

   What does one reported row represent, and when is it available?

4. Variance

   Which screen, interval or creative accounts for the difference?

5. Decision

   Who interprets the agreement and approves any corrective arrangement?

Watch for the wrong conclusion.

• Treating a play as a person who noticed the ad.
• Using total network volume to hide screen-specific obligations.
• Calling missing telemetry confirmed downtime.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not supplier implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Supplier controls, contracts and local requirements can change; verify the actual placement and current provider guidance before implementation.

• Broadsign Control: Share of Loop →Primary platform documentation · Supports: Supports the distinction between time-based loop allocation and repetition-based allocation; contractual interpretation and reconciliation workflow are editorial.
• Broadsign Control: Broadsign POP Log →Primary platform documentation · Supports: Supports platform-specific successful-play definition and distinction between daily POP exports and real-time POP.