# Local Proof Refresh System

Use this system when the business has proof, but the public trust layer is getting stale.

## Proof Refresh Objective

The objective is not to create more proof for its own sake. The objective is to keep the business looking active, trusted, and current across the surfaces buyers actually inspect.

## Proof Inventory

Track every proof type the business can refresh:

- recent reviews
- review-response quality
- team photos
- service photos
- before/after evidence
- case outcomes
- awards, memberships, certifications
- operator bios and headshots
- local news or partnership mentions
- frequently asked questions with direct answer text

Each asset should be tagged by:

- freshness
- location relevance
- service relevance
- approval status
- current public usage

## Capture Windows

Most proof is easiest to capture during natural operating moments:

- immediately after a successful job or milestone
- during onboarding completion
- after a problem is resolved
- after a strong review or referral moment
- after a service-area expansion or new hire

If the team waits for a “content day,” proof capture usually gets delayed or forgotten.

## Refresh Rhythm

### Weekly

- collect one new proof item from the field
- review review-response backlog
- identify one stale photo or page module to replace

### Monthly

- refresh the homepage or primary service page with one proof cue
- refresh one location or listing surface
- update one authority asset or downloadable with fresher examples

## Location-Specific Proof

If the business serves multiple cities or offices, assign proof carefully:

- local reviews stay local
- local team photos stay local
- city-specific wins should not be disguised as company-wide proof
- corporate proof can reinforce the brand, but it should not erase local specificity

## Publishing Rules

When adding fresh proof:

- connect it to a decision point
- use plain labels and dates where helpful
- avoid hiding it too deep in a gallery
- reuse it across the site, listings, proposals, and downloadable assets where appropriate

Proof is strongest when it is close to the place a buyer is asking, “Can I trust this?”

## Measurement Loop

Track:

- review velocity
- proof freshness on top revenue pages
- CTR or conversion lift after proof refreshes
- rage-calculator starts from proof-heavy pages
- booked-call quality when proof modules are strengthened

Not every proof asset needs a direct attribution line, but the system should still be measured.

## Owner Assignments

Assign one owner for each function:

- review collection
- review response
- photo collection
- proof publishing
- monthly audit
- approval for sensitive case or client references

Without owners, proof refresh becomes “important” but not real.

## Failure Modes

- only refreshing one proof type, such as reviews, while everything else looks stale
- publishing proof with no connection to the buying decision
- mixing markets and locations carelessly
- letting old bios and old photos quietly undermine newer growth claims
- capturing proof but never routing it into pages, listings, or assets

## Quarterly Review

Quarterly, ask:

1. what trust signals look obviously stale?
2. which markets or service lines have the weakest proof coverage?
3. which proof assets are helping conversion most?
4. what needs to be retired, replaced, or upgraded?

The refresh system should get sharper as the business grows, not heavier.