What is a change flag in annual site compliance monitoring?
If you run brand standards for a network of fuel or quick-service sites, you already know the two things an audit is supposed to tell you: is the site in spec, and has anything changed since the last time someone looked. A change flag answers the second question.
Change flag, defined
A change flag is a marker on a specific site record saying something is different now compared to the prior pass: a new awning color, a repainted pylon sign, a canopy panel swapped out, a demo trailer parked where the air pump used to be, landscaping grown over a sightline. It doesn't say whether that difference is good or bad against spec. It just says: this location looked one way last year and looks another way now, go check it.
That's a narrower job than people assume. A change flag points to where the site has moved since the prior pass, nothing more. Whether the new condition passes brand standard is a separate call, usually made by a human who already knows the spec for that market and that site tier.
Change flag vs deviation report
A deviation report compares a site against the written brand standard: approved colors, signage package, canopy lighting, pump wrap, required signage counts. It's a spec check. Pass or fail against a rulebook.
A change flag compares a site against itself, one year back, a delta check measured against last year's read rather than against the written standard.
The two overlap often enough that people conflate them, but they catch different things. A site can deviate from spec in year one, stay exactly that way in year two, and generate zero change flags, because nothing moved. It's still out of compliance. The deviation report would catch it. The change flag won't, because there's no delta to flag.
Conversely, a site can change in a way that's completely fine. A franchisee repaints the building the approved color after years of fade. That's a change flag. It's also the opposite of a problem. The flag just tells you to look; it doesn't tell you what you'll find.
Run both and you get the full picture: what's wrong against spec, and what moved since you last checked. Run only one and you're missing half the story, either blind to a standing violation or blind to new activity at a site nobody's flagged in years.
What a prior-pass comparison actually needs
Generating a change flag you can trust takes two things lined up: this year's condition read and last year's, for the same site, close enough in angle and resolution that you're comparing like to like. A photo from a different season, a different time of day, or a different camera height can manufacture false flags from shadows and lighting rather than actual site change. That's the part that's easy to get wrong with ad hoc photo audits: someone snaps a phone photo at noon this year and the comparison is against a cloudy-morning shot from last fall, and now you're chasing a "change" that's really just light.
Imagery captured at consistent resolution and a consistent annual cadence avoids that trap. Same vantage, same time of year, same ground sample distance, run back to back. The comparison holds up because the inputs match.
Why this matters for a brand standards team covering hundreds of sites
Nobody has the headcount to re-walk every site in the network every year just to find out which five changed a sign panel and which two let the landscaping overgrow the pylon. A change flag does the triage for you: it tells you where to send the limited field time you do have, instead of spreading it evenly across a network where most sites didn't change at all.
Franchise Compliance Audit is built around exactly that comparison, a per-site condition read against the prior pass, so the sites that moved get flagged and the ones that didn't stop eating your audit budget. The offer is early access to that annual review, ahead of general release, for brand standards teams who'd rather see what changed than guess.