UK Shortlists home UK Shortlists

Evidence ledger

Dash cams evidence ledger

This ledger explains the evidence boundaries for UK Shortlists dash-cam routes. It covers consumer route choice by setup, channel coverage, recording constraints and ownership caveats; it does not claim legal, insurance, safety or incident-proof guarantees.

View decision map Dash cams hub Claims we do not make

Source types used

  • manufacturer product pages, manuals and support notes for product identity, power, mounting, app, storage and feature descriptions
  • retailer listings for visible product details and merchant-context checks already captured in existing route evidence
  • route evidence summaries, review-basis metadata and Micro-Proof signals already present in the repository
  • independent expert reviews only as corroborating context where they help explain footage, setup or ownership caveats
  • official or manufacturer support material where it clarifies hardwire, firmware, memory-card or app requirements

Source types still needed

  • more consistent official support captures for firmware, app reliability, card compatibility and hardwire requirements
  • route-level source packs for specialist routes involving night driving, parking mode, company cars, motorway use or new-driver contexts
  • clearer legal and insurance-boundary caveats before any wording could be read as legal protection or claims-process advice

Supportable claims

  • which existing dash-cam route is the better starting point for broad, budget, front-and-rear, 4K or specialist-use decisions
  • published-feature and setup checks such as camera channel layout, storage requirements, hardwire needs, app friction and mounting constraints
  • evidence-strength bands and caveats already exposed by shortlist evidence summaries and Micro-Proof signals
  • claim-boundary reminders that dash-cam shortlists are consumer buying routes, not legal, insurance or safety guarantees

Unsupported claims

  • guarantees that footage will capture every incident, number plate, road condition or insurance-relevant detail
  • legal advice, insurance advice, evidential admissibility claims, collision-prevention claims or driver-safety guarantees
  • hands-on testing, lab testing, road testing, night testing, long-term reliability testing or firmware testing unless a route explicitly documents that basis
  • live price, stock, delivery, rating, review-count, merchant or warranty availability claims

Route coverage summary

Coverage is limited to existing shortlist routes. This ledger does not create routes, change product choices or change rankings.

Known limitations

  • Some specialist dash-cam routes should remain cautious until source packs capture official setup, storage, app and legal-boundary details.
  • Footage usefulness depends on installation, weather, lighting, speed, camera settings, windscreen position and local context; route-level evidence cannot guarantee outcomes.
  • Micro-Proof signals summarise route support and caveats; they do not verify live merchant state or create direct test evidence.

Review and update state

Use route-level reviewed/updated dates and evidence-summary fields as the current source of truth. The first-wave freshness dashboard identifies missing or stale signals that should be handled before stronger proof-depth upgrades.

Refresh should be triggered by route content changes, major model or app changes, source-pack updates, or any wording that could be read as legal, insurance, safety or incident-outcome advice.

Micro-Proof interpretation guidance

Micro-Proof signals are public-safe summaries of evidence support, freshness and caveats. For dash cams, treat a signal as routing guidance only: it can help decide which shortlist to read first, but it is not a road-test badge, legal/insurance assurance, incident-capture guarantee or live merchant-state check.

For claim boundaries across all clusters, use Claims We Do Not Make.