Updated
2026-06-15Recheck before live launchSource operating SLA
Freshness windows before Brighton claims go live.
Operational freshness and publication gates for Good Morning Brighton source checks before live sends, public posts or sponsor claims.
Internal prep only. This file does not fetch sources, send subscriber email, publish posts, contact sponsors or enable payments.
Cadence lanes
6Freshness windowsClaim gates
5Publication blockersLive actions
0No sends, posts or outreachCadence rules
Use these windows to decide whether a source is fresh enough for issue copy, public social copy or sponsor-safe claims.
Government and records / Planning
Council, planning, licensing and consultations
Freshness: Same morning for dated claims; 72 hours for static route checks.
Publish gate: Block civic claims unless the original public record is open, dated and linked in the issue or operator notes.
Travel
Travel, roads and disruption
Freshness: Same morning, and again within 2 hours for disruption-led copy.
Publish gate: Block disruption, cancellation or delay claims if the source route is stale, failed or only backed by local media.
Weather
Weather and warnings
Freshness: Same morning before the issue is approved.
Publish gate: Use Met Office or official warning routes for warning language. Do not infer warning status from generic forecasts.
Events
Events and visitor economy
Freshness: Within 7 days for evergreen listings; same day for time, venue, ticket, cancellation or access claims.
Publish gate: Block dated event guidance if the organiser or venue source cannot be reopened.
Local media
Local media discovery
Freshness: Same day for discovery; never enough alone for civic claims.
Publish gate: Treat as lead generation for the briefing. Confirm risky facts against original records before publication.
Advertising / Prospects
Sponsor and commercial claims
Freshness: Same day before outreach approval, payment link creation, placement or campaign report.
Publish gate: Block sponsor names, offers, prices, availability and claims until current advertiser-site proof is captured.
Claim gates
Minimum proof rules before risky claims enter the daily issue or any commercial workflow.
Claim gate
Planning application, appeal, licensing or road closure
Minimum proof: Original authority record URL, record reference where available, checked date/time and one-sentence neutral summary.
Stop rule: No original record, no claim.
Claim gate
Travel disruption or service status
Minimum proof: Operator or official disruption page opened on the morning of publication.
Stop rule: If only a social post or third-party article is available, downgrade to 'check before travelling' with source link.
Claim gate
Weather warning or safety advice
Minimum proof: Official forecast or warning page, area match and issue time.
Stop rule: Do not use warning language when the source only shows routine weather.
Claim gate
Event listing, opening or ticket availability
Minimum proof: Organiser, venue or ticketing source with current date, location and cancellation/accessibility notes where relevant.
Stop rule: If current details cannot be checked, publish only a broad discovery note or omit.
Claim gate
Sponsor offer, booking, price or endorsement
Minimum proof: Advertiser URL, CTA URL, terms/expiry, approval owner and proof-ledger row.
Stop rule: No outreach, checkout, issue slot or public sponsor claim without editorial approval.
Operator checklist
Run this after source fetches and before approving the draft issue.
- Run the source fetch and open /source-quality/report.json before approving a daily issue.
- Resolve every core failure related to a claim in the issue, or remove that claim.
- For each weak navigation-heavy source, open the manual recovery route and capture only date-specific or record-specific items.
- Check the coverage area page for the story location before adding sponsor fit or neighbourhood context.
- Record stale, blocked or corrected source routes in the recovery playbook so the next build loop can harden them.
Linear proof
Track this against MY-2577 and related issue MY-2571, MY-2572.
- Generated /source-sla/ page in website build output.
- Checks page links to the source SLA route.
- Standard issue and website validation gates pass.
- Commit pushed to GitHub with scoped Brighton source-operations changes.