Run the checker first for magnetic body camera mount and body camera magnetic mount / body camera magnet mount / body worn camera magnet mount / body camera with magnetic mount / boblov body camera magnet mount decisions, then use the report layer for boundary, risk, and procurement confidence.
Start with the checker first, then use the report layer to validate confidence, boundaries, and procurement direction. This canonical page handles primary and alias intent, including body camera magnetic mount and body camera magnet mount and body worn camera magnet mount and boblov body camera magnet mount and body camera with magnetic mount. Related Axon phrasing variants, including axon magnetic body camera mount, are mapped in the selector, summary, and FAQ so teams keep one decision log instead of fragmented pages.
Published on . Reviewed on . Evidence refresh point: April 26, 2026.
Review cadence target: every 90 days, or earlier when vendor specs, policy floors, or accessory availability changes.
These conclusions are intended to drive decisions, not add glossary-style filler.
The method layer makes each recommendation auditable by model context, garment stack, and motion assumptions.
| Model / Source | Published spec used | Mount decision signal | Date marker |
|---|---|---|---|
| Axon Body 4 (official product card) | 13+ hour battery, 3400 mAh, IP68 camera, pre-event configurable up to 120 sec, -20°C to 50°C, 1.8 m drop, MIL-STD-810G | Use as primary camera-context source, but do not treat camera durability specs as mount-retention certification. | Reviewed April 26, 2026 |
| Axon Body 4 (official live product page) | 4300 mAh claim, 20% charge in 30 min, 160° FOV, IP68 wording | No explicit publication date shown on page; treat as a live source that may diverge from PDF card revisions. | Reviewed April 26, 2026 |
| Motorola V300 (official datasheet, 08-2023) | 6.8 oz combined weight, IP67, -20°C to +60°C, pre-event options from none to 10 min | Published accessories include magnetic camera mount and heavy jacket magnetic mount, indicating stack-specific mount lanes. | Reviewed April 26, 2026 |
| Motorola official mount product pages | WGP02798C $86.25 (0.63 in thickness), WGP03085B $120.00 (1.00 in), WGP03088 $98.75, WGA00668 $98.75 | All four sampled pages were temporarily unavailable during this review; use these as dated MSRP and geometry signals only. | Reviewed April 26, 2026 |
| BOBLOV M7 official product page | 13-15 hour recording claim, 3400 mAh battery, 127° FOV, and 1080P framing | Use as Boblov model-context baseline, but it does not publish a universal magnetic-retention force benchmark. | Reviewed April 26, 2026 |
| BOBLOV M5 official product page | IP67, 2 m drop resistance, and conflicting battery values (4200 mAh and 4500 mAh) on one page | Treat runtime planning as pending confirmation until Boblov publishes a consistent model-revision value. | Reviewed April 26, 2026 |
| BOBLOV accessory catalog + magnetic mount pages | Accessory catalog lists 28 items with model-specific lanes; magnetic mount listing claims “for all body camera models”, 6 magnets, and 45° adjustment at a sold-out $20 snapshot | Treat this as discovery and budget signal only; run model-specific fit validation before procurement lock. | Reviewed April 26, 2026 |
| Axon Store mount taxonomy (Body 2/3/4 compatible) | Magnet Flexible Reinforced RapidLock: retention force Low; Jacket RapidLock: non-magnetic jacket path | Retention-force labels are vendor classes, not universal Newton pull-force values; use for lane selection, then pilot. | Reviewed April 26, 2026 |
| DHS body-camera comparative matrix (public release) | Axon Body 4 listed as IP67 and pre-event 30 sec-18 hrs; Motorola V300 listed as IP67 and pre-event 0-120 sec | Useful for cross-vendor baseline, but the report explicitly states performance was not independently verified. | Report release 2024-02-29; reviewed 2026-04-18 |
| IEC 60529 (IP code scope) | IP code grades enclosure resistance to dust/liquids and hazardous-part access | Useful for enclosure interpretation only; it does not certify garment-specific magnetic retention under motion. | IEC page reviewed 2026-04-18 |
| DHS Policy Statement 045-07 | Requires >= 30 sec pre-activation recording, end-of-shift upload, anti-tamper handling, and agency policy updates within 180 days of implementation | Mount rollout should be checked against policy-floor settings, storage workflow, and anti-tamper controls. | Policy signed 2023-05-22; reviewed 2026-04-18 |
| DOJ Deputy Attorney General BWC memo (06-07-2021) | Requires component policy submissions within 30 days, annual prosecutor training updates within 90 days, and explicit buffering/access/retention handling in policy language. | Treat federal policy controls as operational requirements: mount selection should be tied to activation scope, buffering defaults, and evidence workflow ownership. | Memo dated 2021-06-07; reviewed April 26, 2026 |
| FBI Policy Notice 1216N (07-16-2022) | Mandatory BWC use for planned arrest/search operations, with stated exceptions and direct safety-priority override language. | Do not evaluate mount readiness only on retention; include tactical safety overrides and operation-type scope checks. | Policy notice date 2022-07-16; reviewed April 26, 2026 |
| USMS Policy Directive 2.11 (updated 08-22-2022) | Defines BWC scope exclusions (for example fixed surveillance, dash cameras, UAS payloads) and requires annual privacy/civil-liberties review. | Use this as a policy-boundary signal: deployment governance and review cadence can block rollout even when hardware fit passes. | Directive updated 2022-08-22; reviewed April 26, 2026 |
| BJA-hosted body-worn video technical guidance | FOV baseline 70°-130° (SD) / 120°-170° (HD), minimum 2-3 hr recording capacity, and 10-min file-size bands (100-300 MB SD, 350-500 MB HD, 1000-1500 MB 4K) | Use this as deployment-planning guidance for positioning, battery/storage budget, and anti-displacement checks; do not treat it as a product certification standard. | Guidance PDF reviewed April 26, 2026 |
| FBI CJIS Security Policy v6.0 | Version 6.0 dated 12/27/2024; control mapping includes SC-8, SC-28, and AU-6 references used for evidence workflow governance. | Treat older v5.9.5 control checklists as potentially stale and re-baseline evidence workflow controls before production sign-off. | Version dated 2024-12-27; reviewed April 26, 2026 |
| FDA magnet precaution guidance | Recommend >= 6 in (15 cm) distance from implanted medical devices | Deployment SOP should account for staff or public implanted-device safety contexts. | Published/updated 2021-05-13; reviewed 2026-04-18 |
| American Heart Association device-interference guidance | Pacemaker/ICD guidance includes keeping magnets at least 6 in away and avoiding prolonged close contact. | Use AHA guidance as a clinical corroboration layer and route unresolved cases to provider/device-manufacturer instructions. | AHA page reviewed April 26, 2026 (no explicit publication date shown) |
| Medtronic electromagnetic compatibility FAQ | Manufacturer FAQ states keeping magnets >= 15 cm (6 in) from implanted cardiac devices and highlights high-field products that should not be used. | Treat 6 in as a conservative baseline, then check device-manufacturer specifics before allowing magnetic mount lanes. | Medtronic FAQ reviewed April 26, 2026 (live page without explicit publication date shown) |
| NIJ Mark + Compliant Product List scope | NIJ Mark applies only to specific listed armor models on the NIJ CPL and requires CTP/FIT evidence. | Do not treat “just like” armor claims or unlabeled variants as equivalent when evaluating vest-hole or semi-permanent mount installs. | NIJ Mark page reviewed April 26, 2026 |
| NIJ personal armor fit assessment (ASTM E3003-15) | NIJ publication documents ASTM E3003-15 fit workflow and notes overlap/coverage checks around side closures and motion. | After mount hardware changes that affect carrier geometry, rerun fit and coverage checks before rollout approval. | Document 251599 reviewed April 26, 2026 |
| BJA implementation lifecycle-cost guidance | BJA implementation guidance separates capital, operational, and replacement costs and explicitly lists mounting kits plus ongoing evidence-management workload. | Treat mount MSRP as one input only; lock lane decisions with lifecycle budget and staffing assumptions. | Implementation page reviewed April 26, 2026 |
| BJA Implementation Checklist & Toolkit Guide (v6 PDF) | Defines six policy areas (capture, viewing, use, release, storage, process/data audits), plus monthly compliance reports and 3-month post-implementation assessments. | Treat launch as a governance process: hardware fit pass should map to explicit policy ownership, compliance cadence, and post-launch review checkpoints. | v6 PDF reviewed April 26, 2026 (no explicit publication date shown in sampled pages) |
| Motorola mounting options guide (docs portal) | Warns shirt/heavy-jacket mounts use very strong magnets, includes 65 pounds snap-pressure signal, and cautions magnets can affect electronics and magnetic media. | Use this as a dual safety boundary: implanted-device screening plus handling rules for nearby electronics/cards/media and lens-orientation checks. | Last modified 2026-03-12; reviewed April 26, 2026 |
| Axon help: mounting options (Flex 2 docs) | Outerwear magnet mount notes potential LTE impact in low-coverage areas and marks Respond compatibility as not recommended; page last modified 2026-03-18. | Treat outerwear magnetic lanes as dual-check decisions: retention fit plus connectivity/Respond compatibility checks. | Last modified 2026-03-18; reviewed April 26, 2026 |
| Axon Resource Center: choosing the correct mount | Mount taxonomy publishes Low/Medium/High/Very High retention classes and dependency notes (for example wing-clip thickness limit, anchor-mount vest-hole requirement, Tilt Mount requires a primary RapidLock mount, and Slim Mount may slide/crease fabric). | Higher retention class does not guarantee lower rollout risk; some lanes require prerequisite hardware or add wearability side effects that must be piloted. | Reviewed April 26, 2026 (resource page with no explicit publication date shown) |
| NIJ/OJP primer on BWC technologies | States a single set of body-worn camera technical requirements does not exist; discusses mount-position tradeoffs and obstruction risk. | Use as a legacy federal boundary reference, then lock final choices on current vendor model docs and pilot telemetry. | Document 250382 (received 2016-11); reviewed April 26, 2026 |
| Cross-vendor universal speed standard | N/A (public evidence insufficient) | Treat speed/impact thresholds as product-specific unless a verifiable standard is cited. | Pending confirmation as of April 26, 2026 |
| Axon Body 4 battery signal (official-source check) | Axon product page: 4300 mAh; Axon product card PDF: 3400 mAh | Treat as source-vintage conflict and lock procurement on the latest vendor revision instead of averaging claims. | Both sources reviewed April 26, 2026 |
| Public mount pull-force value disclosure | N/A (reliable Newton pull-force values not publicly listed) | Do not back-calculate deployment safety from qualitative “Low/High retention force” labels alone. | Pending confirmation as of April 26, 2026 |
Use this section when you need a concrete path to choose magnetic, hybrid, or non-magnetic retention approaches.
| Mount option | Best for | Tradeoff | Fails when | Next action |
|---|---|---|---|---|
| Low-profile magnetic plate (front/back pair) | Thin uniform stack and patrol movement with moderate mass | Fast to deploy, least operational friction | Thick outer carrier, high-impact movement, or unstable substrate | Add tether backup or move to heavy-jacket/clip path |
| Heavy-jacket magnetic mount | Jacket and soft-armor layers where standard plate loses margin | Higher retention margin but still magnetic-dependent | Non-magnetic substrate or severe high-impact without backup | Add tether or mechanical backup and run pilot |
| BOBLOV universal magnetic mount listing | Boblov pilot setups that need quick magnetic placement and angle adjustment | Vendor page advertises broad compatibility but does not publish model-specific retention-force evidence. | Exact camera model or housing revision is not validated before ordering | Lock model list first, then run retention and comfort pilot before scaling procurement |
| BOBLOV model-specific clip/strap accessories | Known model fleets that can map each device family to dedicated accessories | Lower cross-model interchangeability compared with one universal SKU assumption | Program expects one accessory SKU across mixed Boblov models | Split purchase plan by model family and maintain substitution options by SKU |
| Outerwear magnetic mount (Axon lane) | Heavy coats and tactical outerwear where thicker fabric requires a stronger magnetic stack | Can introduce LTE/Respond compatibility caveats in low-coverage conditions | Workflow depends on Axon Respond in low signal areas or team cannot accept connectivity uncertainty | Run field connectivity tests and switch to non-magnetic/clip fallback when Respond reliability drops |
| Wing clip (medium-retention lane) | Users who need quick repositioning with less hardware complexity than anchor installs | Axon guidance notes fit can degrade on very taut or very thick materials | Carrier stack is too tight or too thick for stable clip engagement across shifts | Validate on real uniform variants and escalate to heavier retention lane if slippage appears |
| Tilt mount (Axon dependent lane) | Programs that already use a compatible RapidLock base and need angle correction for evidence framing | Not standalone; requires a primary RapidLock mount and adds integration complexity | Procurement treats tilt hardware as a complete retention solution without base-mount validation | Lock the primary mount first, then validate angle stability and attachment integrity in pilot |
| Slim mount (high retention, low-profile lane) | Uniform layouts with tight space where higher retention is needed and MOLLE/wing options are not feasible | Axon guidance warns it may be difficult to attach, may slide during use, and may crease uniform fabric | Programs optimize only for retention class and skip wearability and fabric-impact checks | Run wearability pilot with shift-length comfort and slippage logging before scaling |
| Anchor mount (very-high retention lane) | Bulletproof-vest workflows where repeated high-motion events require high retention | Can require vest holes and semi-permanent installation, which increases governance and installation cost | Program needs no-drill deployment or armor-governance approval is unavailable | Secure equipment-manager approval and pilot vest-modification workflow before broad issue |
| Non-magnetic jacket mount lane | Thick jacket or fabric workflows where magnetic reliability is inconsistent | Reduced convenience versus magnetic quick placement; requires user retraining for position habits | Mount geometry conflicts with uniform policy or body-worn gear | Pilot as fallback lane when magnetic path produces repeated reseat events |
| Magnet + tether/lanyard | Vehicle + foot pursuit mixed duty where backup matters | Slightly higher setup complexity for better fault tolerance | Tether routing interferes with duty equipment or policy limits | Review routing and clip points in pilot before scale |
| Clip or MOLLE primary retention | Thick carrier and higher-impact activity profiles | Lower mount convenience, higher mechanical stability | Carrier geometry or policy constraints block compatible clip path | Escalate to equipment manager and compatible mount audit |
| Hard mount or custom bracket path | Boundary conditions where magnetic path repeatedly fails | Highest integration cost and longest validation cycle | Program needs temporary no-drill setup only | Use only when policy and deployment constraints permit |
| Risk | Impact | Probability | Mitigation |
|---|---|---|---|
| Non-magnetic or mixed substrate misread | High | Medium | Run physical magnet check on actual mounting zone before purchase. |
| Thick garment stack with magnetic-only retention | High | High | Use heavy-jacket mount class and add tether or clip backup. |
| High-impact movement without secondary retention | High | Medium to High | Treat as boundary and require policy-approved backup retention. |
| Payload underestimated by excluding accessories | Medium | High | Use full assembly mass and center-of-gravity notes in the checker. |
| Overgeneralizing one vendor claim to all SKUs | Medium | Medium | Tie each decision rule to source type and model-specific evidence. |
| Assuming BOBLOV “for all models” claim covers every revision | High | Medium | Cross-check exact Boblov model families against model-specific accessory lanes before procurement. |
| BOBLOV runtime planning based on conflicting page values | Medium | Medium | Treat conflicting 4200/4500 mAh listings as open conflict until vendor confirms active revision. |
| BOBLOV manual links used without revision logging | Medium | Medium | Capture manual link ID, retrieval date, and local evidence copy to prevent version-trace gaps in audits. |
| Treating IP/MIL/NIJ labels as retention proof | High | Medium | Use each standard only within its published scope and require mount-specific pilot retention evidence. |
| Policy-config mismatch on pre-event buffer and data handling | High | Medium | Set policy-floor pre-event values first, then verify storage, upload, and review workload capacity. |
| Cross-agency policy scope copied without local crosswalk | High | Medium | Crosswalk DHS/DOJ/FBI/USMS scope rules to your own agency SOP before using policy floors in procurement or training plans. |
| Rollout launched without post-go-live compliance cadence | High | Medium | Adopt BJA v6 checklist cadence with monthly compliance reports and 3-month post-implementation assessments. |
| Safety-critical operations conflict with default camera activation assumptions | High | Medium | Apply written safety-override rules and document supervisory exception handling before declaring mount workflow production-ready. |
| Long pre-event + high-resolution profile without runtime sizing | High | Medium | Model battery and storage impact with profile-level pilot telemetry before locking default recording settings. |
| Loose placement or pointing drift masked by wide-angle lens assumptions | High | Medium | Run shift-start placement checks and anti-displacement checks; do not assume FOV alone protects evidence quality. |
| CJI evidence path missing transmission/at-rest control mapping | High | Medium | Map upload and storage architecture to CJIS controls (SC-8, SC-28, AU-6) before production rollout. |
| Evidence hashes generated only after upload, not at collection | High | Medium | Follow NIST IR 8387 guidance: hash as close to collection as possible and store hash records outside handler-modifiable paths. |
| Closed/proprietary evidence format selected without open-format strategy | Medium to High | Medium | Preserve native files for forensic fidelity and add open-format exports for cross-party playback, discovery, and long-term access resilience. |
| Police-prosecutor workflow lacks explicit BWC release/redaction ownership | High | Medium | Define written policies for officer/witness review, disclosure, redaction, audit-trail access, and post-adjudication retention decisions before rollout. |
| Evidence checklist still pinned to superseded CJIS version | High | Medium | Re-baseline evidence workflow controls to CJIS v6.0 and document version-delta approval before launch. |
| Ignoring cross-source spec conflicts before procurement | Medium | Medium | Track source versions with dates and request current vendor confirmation when values conflict. |
| Treating internal checker thresholds as certification limits | High | Medium | Label thresholds as triage heuristics and require pilot evidence for final deployment decisions. |
| Pre-event setting mismatch between policy and firmware profile | High | Medium | Export camera profile settings and verify they satisfy policy floor and storage capacity assumptions. |
| Accessory availability shock after technical selection | Medium | Medium to High | Validate SKU availability and substitution paths before rollout dates are committed. |
| Outerwear magnet lane selected without LTE/Respond validation | High | Low to Medium | Test low-coverage connectivity in pilot and switch lanes if Respond reliability drops with the selected mount. |
| Very-high retention mount chosen without vest-modification approval | High | Medium | Secure armor-governance approval for anchor-style installs that can require vest holes before committing to large-scale rollout. |
| Armor fit not revalidated after vest-hole or semi-permanent install changes | High | Medium | Run NIJ/ASTM-style post-install fit and coverage checks before approving deployment beyond pilot. |
| Mount lane approved from MSRP-only budget | High | Medium | Use lifecycle budget controls (capital + operational + replacement) so storage, redaction, and replacement load are funded before rollout lock. |
| Ignoring implanted-device magnetic caution contexts | High | Low to Medium | Combine FDA >= 6 in (15 cm) precaution with Motorola strong-magnet warning and switch to non-magnetic/clip paths when compatibility is uncertain. |
| Applying one generic magnet-distance rule without device-manufacturer review | High | Low to Medium | Treat 6 in as baseline only, then follow provider/device-manufacturer instructions or route to non-magnetic retention when guidance is unclear. |
| Strong-magnet handling force underestimated in field fitting | Medium | Medium | Train handlers on snap-force pinch risk (65 lb signal in Motorola docs) and require controlled fitting steps during pilot setup. |
| Strong magnets staged near electronics or magnetic media | Medium | Medium | Keep magnetic mounts away from phones, computers, hard drives, credit cards, and other magnetic media during fitting/storage workflows. |
| Tilt mount selected without confirming primary RapidLock dependency | Medium | Medium | Treat tilt hardware as an accessory layer and lock primary-mount compatibility before order approval. |
| Wearability validation skipped for high-retention slim lanes | Medium | Medium | Add wearer feedback checkpoints for comfort, fabric impact, and slippage before moving from pilot to scale. |
This round adds only verifiable increments: Axon dependency-bound mount constraints (Tilt/Slim), Motorola electronics/media magnet-safety boundaries, BJA v6 post-go-live governance cadence, NIJ/CPL armor-identity and fit-recheck boundaries, AHA + device-manufacturer medical constraints, and CJIS version-drift actions.
| Gap found in previous revision | Why it matters | Stage1b fix |
|---|---|---|
| No explicit cost delta between mount lanes | Users could pick a path that fits technically but misses budget assumptions. | Added public MSRP comparison with date markers and “contract pricing may differ” caveat. |
| Conflicting ingress values were not called out | Procurement teams may treat IP67 and IP68 as equivalent even when source vintages differ. | Added an evidence-boundary row showing Axon official IP68 camera wording vs DHS 2024 matrix IP67 listing. |
| Evidence confidence was implicit, not explicit | Readers could over-trust secondary comparison reports as certification sources. | Added DHS “not independently verified” caveat to source chain and boundary table. |
| Operational uptime signal under-documented | Charging-cycle assumptions affect pilot design and spare-device planning. | Added Axon official fast-charge signal (20% in 30 min) as a dated data point. |
| Standards scope was easy to over-interpret | Teams can incorrectly treat IP68, MIL-STD, or NIJ references as direct mount-retention proof. | Added explicit IEC and NIJ scope boundaries so certification claims stay in-range. |
| Policy-floor requirements were detached from mount decisions | A technically valid mount setup can still fail audit if pre-event buffer and storage controls are misconfigured. | Added DHS policy constraints (>= 30 sec pre-event, authorized systems, anti-tamper handling) into baseline and boundary tables. |
| Official-source battery conflict was not disclosed | Conflicting 3400 vs 4300 mAh claims can distort runtime assumptions and spare-battery planning. | Added a source-conflict boundary row and quick stat requiring vendor revision confirmation before lock. |
| Uniform seasonality and placement variance underexplained | Mount fit can degrade when agencies change from summer uniforms to winter jackets without repositioning controls. | Added BJA toolkit-derived placement and accessory considerations into source chain and FAQ guidance. |
| Checker mass thresholds looked like external standards | Teams could incorrectly treat 240 g/320 g gates as certified limits and skip pilot validation. | Labeled thresholds as internal screening heuristics in tool copy, uncertainty text, and disclosure blocks. |
| Pre-event range conflicts were not summarized as one decision risk | Policy and storage planning can break if teams mix values from different source vintages. | Added boundary rows and conflict table for Axon product card, Axon live page context, Motorola datasheet, and DHS comparative matrix values. |
| Retention-force wording lacked concept boundaries | Vendor labels like Low/High are easy to overread as absolute pull-force measurements. | Added Axon mount taxonomy evidence and explicit N/A disclosure for cross-vendor Newton pull-force data. |
| Availability risk was buried in source notes | A technically valid path can fail schedule commitments when selected SKUs are temporarily unavailable. | Added quick stat, risk row, and scenario row for sampled mount availability constraints. |
| Pre-event profile load was not quantified | Teams could meet policy settings but still miss battery and upload-capacity assumptions at shift level. | Added BJA data-load and runtime planning bands plus new risk/scenario coverage for upload overrun. |
| Evidence-system security controls were implied, not mapped | A mount can pass physically while evidence handling fails CJI control expectations. | Added CJIS control references (SC-8, SC-28, AU-6), boundary notes, and FAQ actions for deployment gating. |
| Mount-position quality cues were under-specified | Wide-angle lens assumptions can hide placement drift and degrade usable evidence capture. | Added BJA pointing and anti-displacement guidance into boundary, risk, and FAQ sections. |
| Vendor-level strong-magnet warnings were not explicit | Teams may apply only generic FDA distance advice and miss product-specific handling and implanted-device cautions. | Added Motorola mounting-guide evidence (medical-device warning + 65 lb snap-force signal) and a boundary action for non-magnetic fallback paths. |
| Evidence security baseline did not reflect latest CJIS revision | Using superseded v5.9.5 mappings can leave production controls out of date when audits reference v6.0. | Updated source chain and boundary rows to CJIS v6.0, while keeping v5.9.5 as a comparison baseline for transition risk. |
| “No universal BWC requirement set” lacked primary-source citation | Without a first-hand federal source, readers can mistake this as an internal opinion. | Added NIJ/OJP primer citation (document 250382) and linked it to boundary guidance on model-specific validation. |
| Federal policy scope boundaries were under-specified | Teams could treat one agency policy floor as universal and miss operation-specific scope or governance constraints. | Added DOJ/FBI/USMS primary policy rows plus decision boundaries for scope crosswalk before rollout. |
| Safety-override governance was missing in mount guidance | Hardware fit can pass while operational policy requires documented exceptions when safety and camera use conflict. | Added FBI policy-based safety override signal into risk, scenario, FAQ, and evidence-boundary sections. |
| High-retention mount install constraints were not explicit | Programs may over-index on retention class and miss vest-modification approvals or installation burden. | Added Axon mount-selection evidence for wing-clip thickness limits and anchor-mount semi-permanent/vest-hole requirements. |
| Outerwear magnetic lane side effects were hidden | Respond-dependent workflows can fail if connectivity impacts are discovered only after procurement. | Added Axon help-doc LTE/Respond caveat to quick stats, comparison matrix, risk rows, scenarios, and boundary table. |
| Boblov alias intent lacked primary-source model evidence | Alias traffic could be answered with generic mount guidance only, without Boblov model-level context. | Added Boblov M7/M5 product-page baselines, Boblov accessory catalog evidence, and model-specific decision rules into summary, baseline, risk, and conflict layers. |
| Universal magnetic language had no explicit compatibility boundary | Teams could overread “for all models” marketing text and skip model-by-model fit validation. | Added boundary, risk, scenario, and FAQ actions that require exact model lock plus pilot validation before procurement approval. |
| Boblov battery/runtime source consistency was untracked | Conflicting 4200 vs 4500 mAh values can distort runtime, spare-device, and upload-window planning. | Added Boblov M5 source-conflict rows and a “pending confirmation” rule to prevent premature runtime assumptions. |
| Boblov manual revision traceability was not surfaced | Audit and procurement teams may not be able to prove which manual revision was used for decisions. | Added download-portal traceability risk with an explicit action: record manual link ID, retrieval date, and evidence copy in the decision log. |
| Very-high retention install decisions lacked explicit armor-fit reassessment criteria | Anchor or semi-permanent mount changes can pass quick pull checks but still degrade armor coverage and movement fit. | Added NIJ/ASTM fit-assessment evidence (ASTM E3003-15 workflow) and a boundary action requiring post-install fit checks before rollout approval. |
| Armor compliance identity checks were implied, not explicit | Teams can assume a “similar” armor setup remains compliance-equivalent even when model identity and NIJ mark/CPL listing are unclear. | Added NIJ Mark + CPL source rows and decision boundaries so vest-related mount changes trigger model-level compliance verification. |
| Hardware MSRP was over-weighted versus lifecycle program cost | A low accessory price can still fail deployment when storage, redaction, admin time, and replacement cycles are under-budgeted. | Added BJA lifecycle-cost evidence and risk/scenario actions to separate capital, operational, and replacement planning. |
| Cost-pressure discussion lacked national baseline percentages | Without agency-level prevalence data, teams can under-prioritize storage and maintenance costs during budgeting. | Added BJS 2016 adoption and non-adoption barrier percentages (47% acquisition; 77/74/73 cost barriers) as dated macro context for procurement planning. |
| Chain-of-custody integrity controls started too late in the pipeline | Hashing only after upload weakens defensibility if ingestion or transfer integrity is later challenged. | Added NIST IR 8387 evidence and boundary rows requiring hash-at-collection plus protected hash-record storage. |
| Closed-format evidence interoperability risk was under-specified | Closed BWC ecosystems can shift playback/access costs to prosecutors, defense, and courts over time. | Added NIST guidance to preserve native files and add open-format exports where feasible, with new risk/conflict/FAQ controls. |
| Prosecutor-side disclosure and redaction governance was implicit | Hardware-ready deployments can still fail legal workflow requirements if review, release, and retention ownership is undefined. | Added BJA prosecutor-guideline evidence into source, boundary, scenario, and FAQ layers for actionable governance checks. |
| Implanted-device magnet boundary relied on one regulator source only | One generic 6 in rule can hide device-specific cautions and product-class exclusions that appear in manufacturer guidance. | Added AHA and Medtronic corroboration rows and a stricter decision rule: 6 in is baseline, then apply provider/device-manufacturer-specific constraints. |
| Accessory dependency constraints were under-specified | Teams can mistakenly order dependent accessories (for example tilt lane) as standalone mounts and block rollout. | Added Axon dependency evidence (Tilt requires primary RapidLock mount, Slim wearability caveats) across quick stats, baseline rows, boundaries, scenarios, and FAQ. |
| Strong-magnet collateral risk focused on medical context only | Ignoring electronics/magnetic-media impact can create preventable handling incidents during staging and field fitting. | Added Motorola evidence for phones/computers/hard drives/cards/media caution and mapped it into risk, scenario, boundary, and FAQ controls. |
| Post-launch compliance cadence was not explicitly anchored | A rollout can pass pilot checks but still drift without scheduled governance and evidence-control reviews. | Added BJA v6 implementation-checklist signals for monthly compliance reporting and 3-month post-implementation assessments. |
| Wearer-validation evidence was too implicit in vendor screening | Retention-only selection can fail when comfort, slippage, or uniform side effects are discovered after procurement. | Added BJA technology-topic wearer-evaluation signal and converted it into scenario/risk actions before procurement lock. |
| Decision dimension | Verified signal | Counterexample or limit | Decision action | Date marker |
|---|---|---|---|---|
| Ingress rating and source vintage | Axon official materials state Body 4 camera IP68, while Flex POV accessory is IP67. | DHS 2024 market matrix lists Axon Body 4 as IP67 and is a secondary compilation. | Lock procurement against the latest vendor revision and keep source version in the decision log. | Axon pages reviewed 2026-04-18; DHS report dated 2024-02-29 |
| IP code scope vs retention certification | IEC states IEC 60529/IP ratings grade enclosure resistance to dust/liquids and define enclosure test methods. | IEC IP scope does not certify wearable magnetic mount retention under dynamic movement. | Use IP ratings for enclosure risk only; run mount-specific retention pilots for deployment decisions. | IEC IP ratings page reviewed 2026-04-18 |
| Body armor standards vs camera attachment | NIJ 0101.07 specifies ballistic-resistance requirements for torso body armor used by law enforcement. | NIJ ballistic standards do not evaluate camera-mount magnetic coupling or retention in motion. | Use NIJ level for armor procurement and run separate attachment validation for camera mounting. | NIJ page published/updated 2025-12-01; reviewed 2026-04-18 |
| Garment thickness vs mount lane | Motorola heavy-jacket magnetic mount is described as stronger and intended for thick jackets/vests. | This is vendor-specific accessory guidance, not cross-vendor retention certification. | Use it as lane-selection evidence, then validate on your actual garment stack and motion profile. | Motorola store pages reviewed 2026-04-18 |
| BOBLOV universal magnetic claim vs model-specific lanes | BOBLOV magnet mount page advertises “for all body camera models” and a 6-magnet/45° adjustable design. | BOBLOV accessory catalog also lists model-specific accessory lanes (for example model-only clips and mounts), so one SKU cannot be assumed to fit every model revision. | Treat “universal” as a discovery claim only; lock exact model list and validate each model lane before purchase approval. | BOBLOV catalog and magnet page reviewed April 26, 2026 |
| BOBLOV M5 battery signal consistency | BOBLOV M5 page includes a 4200 mAh battery value in one spec section. | The same page also states 4500 mAh in another section, creating a live runtime-planning conflict. | Keep runtime and staffing assumptions provisional until vendor confirms the active revision in writing. | BOBLOV M5 page reviewed April 26, 2026 |
| BOBLOV manual revision traceability | BOBLOV download center provides model manual links for camera lines. | Download portal does not provide one consolidated public revision matrix for all linked manuals. | Record link ID, retrieval date, and local evidence copy in the project decision log before policy/procurement lock. | BOBLOV download page reviewed April 26, 2026 |
| BOBLOV mount listing status vs procurement certainty | BOBLOV magnet mount listing exposed a sold-out status and public list-price snapshot. | Public catalog status is volatile and does not guarantee procurement lead-time or contract availability. | Treat e-commerce status as a signal only and keep alternate retention lanes ready in sourcing plans. | BOBLOV magnet mount page reviewed April 26, 2026 |
| Policy pre-event floor vs storage burden | DHS policy requires BWCs to automatically record at least 30 seconds before activation. | Longer pre-event settings (V300 supports up to 10 minutes) can increase storage, upload, and review workload. | Lock minimum policy settings first, then budget data handling and staffing for the selected buffer profile. | DHS policy signed 2023-05-22; V300 datasheet reviewed 2026-04-18 |
| Pre-recording and optional features vs runtime budget | BJA technical guidance notes pre-recording and optional features can increase battery consumption and cites 2-3 hours as a minimum recording-capacity baseline. | This guidance is not model-specific certification; runtime changes with firmware profile and battery health. | Validate target profile (resolution, pre-event seconds, feature set) in pilot telemetry before rollout lock. | BJA technical guidance reviewed 2026-04-18 |
| Video profile vs storage and upload load | BJA guidance estimates 10-minute files at 100-300 MB (SD), 350-500 MB (HD), and 1000-1500 MB (4K). | Actual file size depends on codec and scene complexity; use these as planning bands only. | Size storage, docking, and shift-end upload windows against tested profile output before policy sign-off. | BJA technical guidance reviewed 2026-04-18 |
| Evidence-system security vs hardware-only readiness | CJIS v6.0 (12/27/2024) includes SC-8, SC-28, and AU-6 control references used for evidence-security mapping. | These controls govern CJI systems and do not validate magnetic retention under motion. | Treat production readiness as dual-gate: hardware fit pass plus evidence-system control attestation. | CJIS v6.0 dated 2024-12-27; reviewed April 26, 2026 |
| Collection-stage hashing vs post-upload integrity checks | NIST IR 8387 advises hashing data as close to collection as possible and notes LE should hash all evidence at collection for chain-of-custody confidence. | Some workflows hash only after ingestion into evidence systems, which can leave early transfer integrity questions unresolved. | Require collection-time hash capture and keep hash records in protected storage that evidence handlers cannot overwrite. | NIST IR 8387 published 2022-09; reviewed April 26, 2026 |
| Native proprietary format vs cross-party playback access | NIST IR 8387 notes many LE video systems are sold as closed platforms and warns proprietary formats can push downstream costs to justice stakeholders. | Open-format conversion can lose vendor-specific metadata if done as a full replacement of native files. | Preserve native evidence for forensic fidelity and publish controlled open-format copies for disclosure/review workflows when feasible. | NIST IR 8387 published 2022-09; reviewed April 26, 2026 |
| Prosecutor workflow completeness vs hardware go-live | BJA prosecutor guidance calls for explicit policies on officer/witness viewing, dissemination controls, chain of custody, and retention/disposition after adjudication. | Mount and camera pilots can pass while release/redaction/audit responsibilities remain undefined across agencies. | Do not mark rollout ready until prosecutor-facing disclosure/redaction and retention ownership is documented with audit-trail access controls. | BJA prosecutor guidance published 2023-08-01; reviewed April 26, 2026 |
| CJIS version drift in evidence checklists | FBI policy moved from CJIS v5.9.5 (07/09/2024) to v6.0 (12/27/2024). | Internal SOPs and audit checklists can remain pinned to v5.9.5 unless explicitly re-baselined. | Run a documented control crosswalk to v6.0 before production approval so security attestations are not version-stale. | v5.9.5 and v6.0 compared April 26, 2026 |
| Lens width vs mount-placement reliability | BJA technical guidance states extreme wide-angle lenses do not remove the need to point the camera correctly and limit mount displacement. | Guidance text is process-oriented and does not certify specific mount SKUs. | Add shift-start placement checks and anti-displacement checks to pilot acceptance criteria. | BJA technical guidance reviewed 2026-04-18 |
| Camera durability vs retention outcome | V300 datasheet lists IP67 and MIL-STD-810G references for the camera platform. | Those ratings do not provide a universal public speed/impact retention standard for every mount setup. | Keep high-impact + magnetic-only in boundary unless a backup retention method is present. | V300 datasheet reviewed 2026-04-18 |
| Axon battery capacity source conflict | Axon live product page states a 4300 mAh battery for Axon Body 4. | Axon Body 4 enterprise product card PDF lists a 3400 mAh battery value. | Treat as source-vintage conflict and obtain current vendor revision before runtime assumptions enter procurement. | Both sources reviewed April 26, 2026 |
| Axon collateral edition variance (same model) | Axon Body 4 enterprise EN_GB card lists 3400 mAh and 13+ hours. | Axon Body 4 EN_AU card shows 4300 mAh and full-shift battery wording. | Record the exact regional collateral and revision date before using runtime claims in procurement calculations. | EN_GB and EN_AU cards reviewed April 26, 2026 |
| Magnet proximity safety | FDA advises keeping relevant high-field consumer magnets at least 6 in (15 cm) from implanted devices. | Guidance is general magnet-interference safety, not a body-camera-specific policy framework. | Include this distance in SOP and training where implanted-device exposure can occur. | FDA page updated 2021-05-13; reviewed April 26, 2026 |
| Strong-magnet vendor warning vs distance certainty | Motorola mount documentation warns shirt and heavy-jacket magnetic mounts are very strong magnets and notes 65 lb snap pressure for the shirt mount. | The vendor page does not publish a numeric safe-distance threshold for implanted medical devices. | Use FDA >= 6 in (15 cm) as a conservative baseline and move to non-magnetic/clip lanes when medical compatibility is uncertain. | Motorola docs page last modified 2026-03-12; reviewed April 26, 2026 |
| Strong magnets vs nearby electronics and magnetic media | Motorola mounting guidance warns strong mounts can affect electronics and magnetic media (for example phones, computers, hard drives, credit cards). | Many SOP drafts focus only on implanted-device distance and do not explicitly cover staging/storage controls for non-medical magnet-sensitive items. | Add handling controls for staging kits and training zones: separate strong-magnet mounts from magnet-sensitive electronics/media by default. | Motorola docs page last modified 2026-03-12; reviewed April 26, 2026 |
| Generic magnet-distance rule vs device-specific contraindications | AHA guidance reinforces the >= 6 in baseline for pacemaker/ICD users and advises avoiding close/prolonged magnet contact. | Implanted-device manufacturer guidance can add product-specific exclusions (for example some high-field products are not recommended) beyond a generic distance reminder. | Treat 6 in as minimum baseline, then require provider/device-manufacturer confirmation or switch to non-magnetic retention when uncertainty remains. | AHA and Medtronic pages reviewed April 26, 2026 |
| Pre-event recording range alignment | Axon product card states configurable pre-event up to 120 sec, and Motorola V300 datasheet lists options up to 10 min. | DHS 2024 comparative matrix lists Axon Body 4 pre-event as 30 sec-18 hrs and explicitly notes performance was not independently verified. | Treat pre-event settings as a configuration-control task: verify live firmware profile export before storage and policy assumptions are approved. | Axon card and Motorola datasheet reviewed 2026-04-18; DHS report dated 2024-02-29 |
| Federal policy scope mismatch risk | DOJ and FBI policy artifacts frame activation requirements around planned arrest/search operations, while DHS policy applies to DHS component implementations with agency policy-update windows. | These federal artifacts are agency-specific and not a single universal local-department mandate. | Run a written policy crosswalk and lock activation scope to your governing agency policy before rollout. | DOJ memo dated 2021-06-07; FBI notice dated 2022-07-16; DHS policy signed 2023-05-22 |
| Safety-priority override vs default activation expectation | FBI policy states that in situations where safety priorities conflict with body-camera policy, safety priorities should prevail. | The policy still expects activation in its defined operation scope unless approved exceptions apply. | Document supervisory exception process and after-action notes so safety-driven deviations remain auditable. | FBI Policy Notice 1216N dated 2022-07-16; reviewed April 26, 2026 |
| BWC policy scope vs other camera systems | USMS directive states the policy does not apply to fixed surveillance cameras, dash cameras, or cameras integrated into unmanned aircraft systems. | Hardware teams can mistakenly assume one BWC policy controls every camera workflow in mixed fleets. | Separate BWC mount decisions from non-BWC camera governance and keep policy owners explicit in project documentation. | USMS Directive 2.11 updated 2022-08-22; reviewed April 26, 2026 |
| Retention-force class vs measurable pull force | Axon mount pages expose qualitative retention-force classes (for example, Low on SKU 71026) and separate magnetic vs non-magnetic jacket paths. | Public pages do not provide a reliable cross-vendor Newton pull-force benchmark that maps directly to duty-impact tolerance. | Use retention-force labels for first-pass lane selection only, then validate with pilot retention event data on real garment stacks. | Axon mount pages reviewed 2026-04-18 |
| Outerwear magnetic lane vs Respond connectivity | Axon help documentation notes the outerwear magnet mount may impact LTE performance in low-coverage areas and is not recommended for Respond use. | The warning does not provide a universal signal-strength threshold, so impact must be validated in local field conditions. | Treat outerwear magnetic selection as conditional: pass retention tests and connectivity tests before deployment approval. | Axon help page last modified 2026-03-18; reviewed April 26, 2026 |
| Very-high retention path vs installation governance | Axon mount-selection guidance describes anchor mounts as very-high retention and notes they can require holes in body armor/vests with semi-permanent installation. | Higher retention class can increase installation burden and may conflict with no-modification equipment policies. | Require equipment-owner approval and installation workflow validation before selecting anchor-style retention at scale. | Axon mount-selection guide reviewed April 26, 2026 |
| Accessory dependency vs standalone retention assumption | Axon mount-selection guidance states Tilt Mount requires a primary Axon RapidLock mount option (for example wing clip or MOLLE). | Treating tilt hardware as standalone creates incomplete retention stacks and procurement mismatches. | Validate dependency stack in BOM and pilot: primary mount first, tilt accessory second, then confirm angle + retention behavior. | Axon mount-selection guide reviewed April 26, 2026 |
| High-retention class vs wearability side effects | Axon guidance describes Slim Mount as high retention but warns attachment can be difficult and may slide or crease uniform fabric. | Retention class alone does not predict comfort, fabric impact, or long-shift usability. | Require wearer-feedback checkpoints (comfort, slippage, fabric impact) before scaling high-retention slim lanes. | Axon mount-selection guide reviewed April 26, 2026 |
| Vest modification vs armor fit integrity | NIJ fit-assessment publication documents ASTM E3003-15 checks, including fit posture/movement checks and coverage overlap expectations. | Passing a mount pull test does not prove armor fit and coverage remain acceptable after semi-permanent mount-related changes. | After any vest-hole or geometry-changing install, run and record post-install fit assessment before rollout approval. | NIJ document 251599 reviewed April 26, 2026 |
| Armor model identity vs assumed compliance equivalence | NIJ Mark scope is model-specific and ties compliance to listed armor models on the NIJ Compliant Product List. | “Equivalent” or unlabeled variants are not automatically NIJ-compliant just because they look similar to listed armor. | Verify NIJ mark/model identity on the exact armor configuration before approving vest-related mount modifications. | NIJ Mark page reviewed April 26, 2026 |
| SKU availability vs rollout schedule | Motorola sampled mount pages published public MSRP and dimensions for standard, heavy-jacket, clip, and MOLLE options. | All sampled mount pages were temporarily unavailable during review, so current procurement lead time cannot be inferred from list pages. | Add sourcing fallback lanes and timeline buffers before operational launch gates are finalized. | Motorola store pages reviewed 2026-04-18 |
| Accessory price vs lifecycle program cost | BJA implementation guidance separates BWC costs into capital outlay, operational costs, and replacement costs. | A low mount MSRP can still fail deployment if storage, redaction/admin workload, and replacement cycles are not budgeted. | Approve mount lanes only after lifecycle budget and staffing assumptions are documented with the same rigor as hardware fit. | BJA implementation page reviewed April 26, 2026 |
| Policy-area completeness in rollout governance | BJA Implementation Checklist & Toolkit Guide v6 lists six policy areas: capture, viewing, use, release, storage, and process/data audits. | Hardware-first rollouts often define capture/storage rules but under-specify viewing/release/audit responsibilities. | Do not treat rollout as ready until policy ownership is explicit across all six areas and evidence controls are mapped. | v6 checklist PDF reviewed April 26, 2026 (no explicit publication date shown in sampled pages) |
| Post-go-live compliance cadence | BJA Implementation Checklist & Toolkit Guide v6 calls for monthly compliance reporting and 3-month post-implementation assessments. | Pilot pass alone does not prevent process drift without scheduled monitoring and corrective loops. | Assign compliance owner, schedule monthly reports, and run 3-month reassessment before full-scale procurement lock. | v6 checklist PDF reviewed April 26, 2026 (no explicit publication date shown in sampled pages) |
| Tool thresholds vs external standards | This checker uses explicit mass thresholds for triage consistency (for example, ready-window and boundary-window bands). | No public standard in the reviewed source set certifies those exact bands as universal retention limits. | Keep threshold bands as internal pre-qualification logic and require pilot evidence for final deployment approval. | Inference logged April 26, 2026 |
| Universal BWC requirement-set assumption | NIJ/OJP primer states a single set of body-worn camera technical requirements does not exist. | The primer is a legacy baseline (2016) and does not replace current model-specific vendor documentation. | Use this as a boundary principle, then lock deployment decisions on current vendor docs plus local pilot telemetry. | NIJ/OJP document 250382 (received 2016-11); reviewed April 26, 2026 |
| Retention path | Public MSRP signal | What improves | Tradeoff or limit | Best-use lane |
|---|---|---|---|---|
| Standard magnetic mount (WGP02798C) | $86.25 (snapshot; temporarily unavailable) | Fast placement on shirt/vest for low-standoff setups; 0.63 in listed thickness profile. | Less tolerance for thick jackets and larger garment gaps under higher motion. | Thin uniform + patrol movement + moderate payload. |
| Heavy-jacket magnetic mount (WGP03085B) | $120.00 (+39% vs standard; snapshot; temporarily unavailable) | Stronger heavy-clothing fit intent with 1.00 in listed thickness and explicit heavy-jacket positioning language. | Higher hardware cost while still remaining magnetic-dependent in high-impact contexts. | Jacket or soft-armor layers with backup retention controls. |
| Heavy-jacket clip (WGP03088) | $98.75 (snapshot; temporarily unavailable) | Mechanical hold path on coat/jacket when magnetic confidence is weaker; listed dimensions 1.00 x 2.56 x 4.00 in. | Clip geometry and gear layout can limit placement options; still requires compatible placement with V300/V700/SVX workflows. | Thick coat workflows where magnetic-only is unstable. |
| MOLLE locking mount (WGA00668) | $98.75 (snapshot; temporarily unavailable) | Mechanical lock on MOLLE webbing for higher-stability attachment; listed dimensions 0.63 x 2.50 x 4.75 in. | Requires compatible loop geometry and placement planning across V300/V700/SVX device carriage. | Carrier/webbing setups with recurring high-motion movement. |
| BOBLOV body camera magnet mount | $20.00 (snapshot; sold out) | Vendor page positions it as a quick magnetic lane with 6 magnets and 45° adjustment. | Public page does not provide model-specific retention-force data or impact-tested duty limits. | Limited pilot with locked Boblov model list and explicit fallback retention options. |
| BOBLOV universal magnetic suction back clip | $34.99 (snapshot) | Catalog-level universal magnetic back-clip option for early budget comparisons. | Compatibility and availability still require model-level checks because the same catalog includes model-specific accessory lanes. | Pre-procurement budgeting before selecting model-specific magnetic or mechanical lanes. |
| Axon reinforced flexible magnet RapidLock (71026) | Price unavailable (public page snapshot) | Magnetic lane with versatile placement and breakaway option; listed dimensions 4.17 x 3.55 x 0.44 in. | Listed as Low retention force class and does not publish cross-vendor Newton pull-force values. | Lower-standoff magnetic path where teams can pilot and inspect frequently. |
| Axon thick-outerwear magnet RapidLock (74021) | Price unavailable (public page snapshot) | Outerwear-oriented magnetic lane with breakaway option; listed dimensions 4.00 x 2.28 x 0.35 in. | Remains magnetic-dependent and public pages do not provide a cross-vendor Newton pull-force benchmark. | Outerwear magnetic workflows with explicit backup retention planning. |
| Axon non-magnetic jacket RapidLock (11704) | Price unavailable (public page snapshot) | Explicitly non-magnetic path for thick fabric uniforms; listed dimensions 3.38 x 3.13 x 0.69 in. | Convenience and placement flexibility can differ from magnetic mounts and may require user retraining. | Fallback lane when magnetic stability is weak or substrate reliability is uncertain. |
| Conflict signal | Source A | Source B / counter-signal | Current decision rule | Status |
|---|---|---|---|---|
| Axon Body 4 battery capacity | Axon product page: 4300 mAh | Axon Body 4 product card: 3400 mAh | Treat runtime planning as provisional until vendor confirms current revision in writing. | Open - vendor revision confirmation required |
| Axon product-card regional collateral | Axon EN_GB enterprise card: 3400 mAh, 13+ hours | Axon EN_AU card: 4300 mAh, full-shift wording | Treat regional collateral as non-interchangeable until procurement locks the exact market/revision source. | Open - regional collateral variance |
| BOBLOV M5 battery value on one official page | BOBLOV M5 spec section: 4200 mAh | BOBLOV M5 copy block: 4500 mAh | Treat runtime sizing as provisional and request dated vendor clarification before capacity planning is approved. | Open - same-page source conflict |
| BOBLOV universal mount claim vs catalog model constraints | BOBLOV magnet mount listing: “for all body camera models” | BOBLOV accessory catalog includes model-specific accessories labeled for particular camera families | Do not assume universal fit; lock model list and run model-specific fit validation before procurement. | Open - model-level compatibility validation required |
| BOBLOV manual links vs revision traceability | BOBLOV download portal publishes model manual links | No single public revision matrix is shown for all linked manuals on the portal | Capture manual link IDs, retrieval dates, and local evidence copies in the procurement/policy decision log. | Open - documentation traceability control required |
| Axon Body 4 ingress rating | Axon official sources: camera IP68 | DHS matrix: Axon Body 4 listed as IP67 | Use latest manufacturer revision for procurement and keep DHS listing as secondary context. | Open - source-vintage mismatch |
| Pre-event recording range (Axon Body 4) | Axon product card: configurable up to 120 sec | DHS matrix: 30 sec-18 hrs | Verify live camera profile export before approving policy, storage, and review-load assumptions. | Open - profile verification required |
| Mount pull-force in Newtons (cross-vendor) | Axon/Motorola public mount pages provide qualitative positioning and dimensions | No reliable public cross-vendor Newton pull-force benchmark found | Use lane selection + pilot retention event data instead of fabricated force conversion. | No reliable public data |
| Policy floor vs evidence workload envelope | DHS policy requires >=30 sec pre-event and end-of-shift upload cadence | BJA guidance notes pre-recording/features increase battery use and larger files at higher quality bands | Treat as an operational fit check: lock profile only after pilot confirms runtime and upload capacity. | Open - operational telemetry validation required |
| Mount MSRP vs lifecycle deployment cost | Public mount pages publish accessory pricing and dimensions (capital signal) | BJA implementation guidance requires operational and replacement cost planning beyond hardware purchase | Do not approve procurement from MSRP alone; require lifecycle budget ownership (storage/redaction/admin + replacement cycle). | Open - lifecycle-cost validation required |
| Collection-time hashing vs post-upload hashing only | NIST IR 8387 recommends hashing as close to collection as possible and indicates LE should hash all evidence at collection | Some operational workflows rely on platform-side hash generation after ingest | Require collection-stage hashing plus protected hash-record storage before evidence workflow sign-off. | Open - integrity workflow control required |
| Closed-system convenience vs long-term disclosure interoperability | NIST IR 8387 notes many LE systems are sold as closed platforms and proprietary formats can create downstream costs | Programs may prefer single-vendor workflow simplicity and skip open-format disclosure planning | Keep native evidence for forensic integrity and add controlled open-format exports for prosecution/discovery workflows. | Open - interoperability governance required |
| Hardware readiness vs prosecutor disclosure governance | Mount/camera pilots can pass operational checks and still be marked deployment-ready | BJA prosecutor guidance requires explicit policy on officer/witness review, dissemination, chain of custody, and post-adjudication retention | Do not approve rollout until prosecutor-facing release/redaction and retention responsibilities are assigned and auditable. | Open - legal workflow ownership required |
| Federal activation policy scope alignment | DOJ/FBI materials emphasize planned arrest/search operation scope and defined policy exceptions | DHS policy language is component-policy-driven and can be interpreted as a broader baseline by teams | Do not merge scopes by assumption. Crosswalk governing policy by agency and operation type before rollout. | Open - policy crosswalk required |
| Outerwear magnet retention vs Respond reliability | Axon outerwear magnet lane improves heavy-coat fit positioning | Axon help docs warn possible LTE impact in low coverage and mark Respond compatibility as not recommended | Treat as dual-gate validation: retention pass is insufficient unless connectivity also passes in local pilot zones. | Open - field connectivity validation required |
| Generic magnet-distance baseline vs device-manufacturer contraindications | FDA/AHA guidance supports >= 6 in baseline for magnet proximity | Medtronic guidance includes product-class exclusions and device-specific cautions beyond a single distance reminder | Treat 6 in as minimum baseline and require provider/device-manufacturer confirmation when implanted-device contexts exist. | Open - medical-safety verification required |
| CJIS evidence-control baseline version | CJIS v5.9.5 (07/09/2024) legacy checklist baseline | CJIS v6.0 (12/27/2024) current policy baseline | Update control crosswalk to v6.0 before launch so evidence-security attestations are current. | Open - compliance version migration required |
| Strong-magnet safety scope in SOP language | Motorola docs include warnings for electronics/magnetic media impact in addition to implanted-device caution | Many deployment checklists only document implanted-device distance without electronic/media handling controls | Treat magnetic-safety scope as dual-track: medical compatibility + electronics/media handling controls in rollout SOP. | Open - SOP scope update required |
| Accessory dependency assumptions (Tilt Mount lane) | Axon mount guide states Tilt Mount requires a primary RapidLock mount option | Procurement summaries can treat tilt hardware as independent retention when BOM dependencies are not explicit | Keep tilt lane in review until primary-mount dependency is validated and tested as one stack. | Open - dependency validation required |
| Pilot pass vs long-term governance cadence | BJA v6 checklist calls for monthly compliance reports and 3-month post-implementation assessments | Hardware-focused rollout plans may stop governance tracking after initial pilot acceptance | Release only with assigned compliance owner and scheduled post-go-live review cadence. | Open - governance cadence assignment required |
Each scenario includes preconditions and escalation paths so teams can operationalize the output.
| Scenario | Preconditions | Expected output | Escalation path |
|---|---|---|---|
| Axon Body 4, thin uniform, patrol shift | Mounted mass around 220 g, magnetic backing valid, routine movement | Ready: low-profile magnetic path with documented inspections | Escalate if movement profile shifts to high-impact or stack thickness increases |
| Motorola V300, jacket + soft armor, vehicle + foot transitions | Mounted mass around 250 g, mixed movement profile, magnetic substrate valid | Review/Ready with heavy-jacket path plus tether backup | Boundary if team insists on magnetic-only retention |
| Unknown model, thick external carrier | Model not locked, standoff high, accessory mass uncertain | Review: lock model and test with full stack before procurement | Move to clip/MOLLE if retention pilot fails |
| BOBLOV alias request assumes one “universal” mount across mixed models | Fleet includes multiple Boblov models but procurement plan uses one magnetic SKU without model-level validation | Review: keep compatibility unapproved until each model lane passes fit and retention checks | Split accessory plan by model family and approve only pilot-validated lanes |
| BOBLOV M5 page conflict appears during runtime planning | Planner reads both 4200 mAh and 4500 mAh values on the same official page | Review: freeze runtime assumptions until a dated vendor revision is confirmed | Request written spec confirmation and rerun runtime/storage calculations before rollout lock |
| High-impact operational context | Frequent abrupt movement, potential grappling or strong impacts | Boundary for magnetic-only; requires backup retention path | Policy + pilot sign-off before scale |
| Nonferrous mounting area detected | Plastic or non-magnetic plate near intended mount zone | Boundary: exit magnetic path | Switch to clip, MOLLE, or bracket strategy |
| Policy requires 30 sec pre-event but config is set to none | Agency follows DHS-style policy floor while default camera profile is underconfigured | Review/Boundary until pre-event setting and storage workflow are corrected | Apply minimum pre-event configuration, then rerun storage and operational workload checks |
| Program copies another federal policy scope without local mapping | Team imports DHS/DOJ/FBI language but does not map local operation types, exception flow, and evidence-governance owner | Review/Boundary: policy crosswalk required before rollout can be approved | Run agency policy crosswalk and capture legal + operational sign-off before procurement lock |
| Outerwear magnetic mount selected for low-coverage Respond workflow | Axon outerwear magnet lane selected while deployment relies on Respond and LTE coverage is inconsistent | Review: verify connectivity in pilot before confirming this mount lane | Switch to non-magnetic or clip path if connectivity drops below operational target |
| Anchor mount requested without vest-modification authorization | Very-high retention target selected, but armor governance has not approved hole-making/semi-permanent installation | Boundary: hold deployment until equipment-governance approval exists | Escalate to armor program owner and document installation workflow before pilot expansion |
| Anchor install passes retention check but armor-fit coverage is not reassessed | Vest-hole or semi-permanent install completed, but no documented post-install fit movement/coverage assessment was run | Boundary: hold rollout until armor fit and coverage are validated after install changes | Run NIJ/ASTM-style fit checks and attach results to equipment-governance sign-off before production approval |
| Long pre-event + HD profile causes shift-end upload overrun | Operational profile uses longer pre-event windows and high-resolution capture while upload bandwidth is fixed | Review: rebalance profile, docking bandwidth, or upload staffing before scale | Use pilot telemetry and evidence-system owner sign-off before final profile lock |
| Mount retention passes but CJI security controls are not attested | Hardware pilot passes while storage/upload path lacks documented SC-8 or SC-28 enforcement and AU-6 review workflow | Boundary for production evidence workflow despite acceptable mount fit | Escalate to security officer and evidence administrator for control attestation before launch |
| Pilot retention passes but evidence pipeline hashes only after upload | Program relies on platform-side hashing and does not document collection-time hash capture or hash-record immutability | Review/Boundary for evidentiary confidence until collection-stage integrity controls are documented | Implement hash-at-collection workflow and store hash records in a protected location before production evidence sign-off |
| Deployment plan omits prosecutor-side disclosure and redaction workflow | Mount and camera profiles are selected, but no written policy assigns review, redaction, release, and audit-trail responsibilities | Review/Boundary: rollout governance is incomplete despite hardware readiness | Adopt a prosecutor-aligned BWC policy package covering witness/officer review, disclosure, redaction, and retention triggers before go-live |
| Axon battery source mismatch in procurement review | Live product page claims 4300 mAh while product card PDF lists 3400 mAh | Review: keep model in decision hold until current revision is confirmed | Request dated vendor clarification and attach it to the procurement decision log |
| Procurement team treats 240 g as a hard certification limit | Checker output used without reading uncertainty and evidence-boundary notes | Review: reclassify the value as a triage heuristic and schedule pilot validation | Document pilot criteria and decision owner before approving rollout |
| Selected mount SKU is temporarily unavailable at ordering time | Public product page shows temporary unavailability for preferred mount path | Review: compare substitute lane (tether/clip/MOLLE/non-magnetic jacket) against duty profile | Escalate to sourcing lead with alternates and updated timeline impact |
| Procurement locks on low mount MSRP but lifecycle budget is not staffed | Budget review includes accessory price but excludes operational storage/redaction/admin load and replacement cycle costs | Review/Boundary: pricing decision is incomplete until lifecycle cost ownership is documented | Apply BJA lifecycle-cost breakdown and update staffing/storage assumptions before procurement sign-off |
| Security review still references CJIS v5.9.5 controls only | Evidence workflow checklist was written before CJIS v6.0 (dated 2024-12-27) and lacks version-delta review | Review/Boundary until the control crosswalk is refreshed and approved by the security owner | Update SC-8/SC-28/AU-6 mappings to the current policy baseline and capture sign-off before production launch |
| Implanted-device concern appears during magnetic mount fitting | User or nearby subject reports pacemaker/programmable device context while strong magnetic mounts are planned | Boundary/Review: move to non-magnetic or clip lane unless medical compatibility is explicitly cleared | Follow provider/device-manufacturer guidance and keep magnet-adjacent electronics/media risk controls in SOP notes |
| Generic 6-inch magnet rule conflicts with device-manufacturer restrictions | Team SOP uses only FDA baseline distance but case-level manufacturer guidance adds stricter contraindications | Boundary: pause magnetic lane and re-evaluate with provider/device-manufacturer instructions | Escalate to medical-safety owner and switch to clip/non-magnetic retention unless case-specific clearance is documented |
| Tilt mount is ordered without a compatible RapidLock base | Procurement selects Tilt Mount SKU but primary mount dependency was not captured in the bill of materials | Review/Boundary: treat as incomplete retention stack until base mount compatibility is validated | Update BOM with required primary RapidLock mount, then rerun fit and wearability pilot before release |
| Strong magnetic mounts are stored near phones, cards, or magnetic media | Mount kits are staged with electronic devices, storage media, or payment cards during setup/training | Review: apply magnetic-field handling controls beyond implanted-device screening | Separate staging/storage zones and add handling instructions to rollout SOP and training materials |
| Go-live approved without monthly compliance reporting and 3-month review | Pilot passed hardware checks but no post-launch governance cadence was assigned to policy/evidence owners | Review/Boundary: rollout governance is incomplete despite acceptable retention tests | Assign compliance owner, schedule monthly reports, and book 3-month post-implementation assessment before scale |
| High-retention slim lane deployed without wearer feedback loop | Retention class is prioritized but pilot lacks structured user feedback for comfort, slippage, and fabric impact | Review: fit confidence is incomplete until wearer evaluation confirms real-shift usability | Run officer wearability review, collect issue logs, and adjust mount lane before procurement lock |
| Officer safety conflict occurs during a planned operation | Activation requirement exists but immediate tactical safety needs conflict with normal camera-use sequence | Review/Boundary: safety-priority exception process must be followed and documented | Apply supervisor-approved exception path and preserve post-incident documentation for policy audit |
Known unknowns are shown directly as N/A with reasons; no fabricated values are inserted.
| Source type | Source | Used for | Date marker |
|---|---|---|---|
| Official product card (PDF) | Axon Body 4 Product Card | Runtime, ingress scope split (camera IP68 vs Flex POV IP67), pre-event up to 120 sec, operating temperature, drop test, and 3400 mAh battery claim. | Reviewed April 26, 2026 |
| Official product page | Axon Body 4 product page | Fast-charge signal (20% in 30 min), 4300 mAh battery claim, and camera/accessory ingress wording. | Reviewed April 26, 2026 (live page; no explicit publication date shown) |
| Official product card (regional variant PDF) | Axon Body 4 Product Card EN_AU | Regional collateral variant with 4300 mAh and “full shift” battery wording; used to surface cross-collateral variance against enterprise card values. | Reviewed April 26, 2026 (regional collateral comparison) |
| Official datasheet (PDF) | Motorola V300 Body-Worn Camera Datasheet | Combined weight/dimensions, IP67, storage baseline (128 GB with 23-hour 1080p claim), pre-event options up to 10 min, and magnetic accessory lane definitions. | Datasheet date 08-2023; reviewed April 26, 2026 |
| Official accessory product pages | Motorola V300 mount SKUs (WGP02798C, WGP03085B, WGP03088, WGA00668) | List-price signals, dimensions for each mount lane, and compatibility scope (V300/V700/SVX); public pages showed temporary unavailability during review. | Reviewed April 26, 2026 (public MSRP snapshot) |
| Official vendor catalog page | BOBLOV body camera accessories collection | Catalog count signal (28 listed accessories), universal magnetic suction back clip listing ($34.99 snapshot), and multiple model-specific accessory labels used for compatibility-boundary analysis. | Reviewed April 26, 2026 |
| Official accessory product page | BOBLOV body camera magnet mount | Public listing signal: sold-out snapshot at $20, “6 strong magnets”, “45° adjustable”, and “for all body camera models” claim used for compatibility-risk and stock-risk mapping. | Reviewed April 26, 2026 |
| Official product page | BOBLOV M7 body-worn camera page | 13-15 hour recording claim, 3400 mAh battery, and 127° wide-angle signal used for model-level baseline context. | Reviewed April 26, 2026 |
| Official product page | BOBLOV M5 body camera page | IP67 + 2 m drop claims and conflicting 4200 mAh vs 4500 mAh values on one page used for runtime-confidence and revision-control boundaries. | Reviewed April 26, 2026 |
| Official download portal | BOBLOV download center | Manual links are distributed via external file links without a unified public revision table; used as documentation-traceability risk signal. | Reviewed April 26, 2026 |
| Official mount taxonomy pages | Axon Store mounts (71026 reinforced magnetic, 74021 thick-outerwear magnet, 11704 non-magnetic jacket) | Published retention-force labels (for example, Low on magnetic mount SKU 71026), mount type boundaries (magnetic vs non-magnetic), compatibility scope, and dimensions. | Reviewed April 26, 2026 (price not publicly visible) |
| Official mount taxonomy pages | Axon thick-outerwear magnet mount (SKU 74021) | Magnetic outerwear mount dimensions and breakaway-style positioning language for jacket workflows. | Reviewed April 26, 2026 (price not publicly visible) |
| Official mount taxonomy pages | Axon non-magnetic jacket mount (SKU 11704) | Non-magnetic high-retention jacket path used as counterexample when magnetic paths are unstable. | Reviewed April 26, 2026 (price not publicly visible) |
| Official mounting guide (vendor help docs) | Axon Flex 2 mounting options help page | Mount compatibility notes including outerwear magnet caveat (possible LTE impact in low coverage and not recommended for Respond) plus guidance freshness marker. | Last modified 2026-03-18; reviewed April 26, 2026 |
| Official mount selection guide (vendor resource center) | Choosing the correct Axon body-worn camera mount | Retention taxonomy and prerequisites: outerwear mount Respond caveat, wing-clip thick-material limits, anchor-mount vest-hole requirement, Tilt Mount dependency on primary RapidLock mount, and Slim Mount slide/crease caveats. | Reviewed April 26, 2026 (resource page with no explicit publication date shown) |
| Federal policy (PDF) | DHS Policy Statement 045-07 on Body Worn Cameras | Minimum 30-second pre-event buffer, end-of-shift upload rule, anti-tamper obligations, and 180-day agency policy-update window. | Signed 2023-05-22; reviewed April 26, 2026 |
| Public comparative report (PDF) | DHS body-worn camera matrix | Cross-vendor battery, pre-event buffer, and Axon Body 4 IP row; includes explicit caveat that product performance was not independently verified. | Report release 2024-02-29; reviewed April 26, 2026 |
| Public assessment report (PDF) | DHS automatic-activation assessment report | Agency-selection framing around capabilities, limitations, and operational fit used for decision-process guidance. | Report date 2023-10-19; reviewed 2026-04-18 |
| Federal policy memo (PDF) | DOJ Deputy Attorney General memo on body-worn cameras | Policy implementation timing (30-day component policy submission, 90-day prosecutor-training timeline), buffering requirement, and policy-content obligations. | Memo dated 2021-06-07; reviewed April 26, 2026 |
| Federal agency policy notice (PDF) | FBI Policy Notice 1216N (Body Worn Cameras) | Planned-operation activation scope and explicit statement that safety priorities can override camera-use expectations. | Policy notice date 2022-07-16; reviewed April 26, 2026 |
| Federal agency directive (PDF) | USMS Policy Directive 2.11 Body-Worn Cameras | Scope exclusions (fixed cameras, dash cameras, UAS payloads) and annual privacy/civil-liberties review obligation. | Directive updated 2022-08-22; reviewed April 26, 2026 |
| Federal implementation toolkit | BJA BWC Toolkit FAQs | Uniform seasonality, mount-position guidance, and accessory requirements for secure attachment. | Reviewed April 26, 2026 |
| Federal implementation toolkit topic page | BJA BWC Toolkit technology topic | Uniform variability by season, accessory requirements for secure positioning, and wearer-involved mount evaluation examples (including LAPD pilot evaluation process). | Reviewed April 26, 2026 (no explicit publication date shown on page) |
| Public technical guidance (PDF) | BJA-hosted Technical Guidance for Body-Worn Video | FOV baselines, 2-3 hour recording-capacity guidance, battery-impact caveat for pre-recording/optional features, 10-minute file-size bands, and anti-displacement mounting guidance. | Guidance PDF reviewed April 26, 2026 (legacy technical guidance; use as baseline, not certification). |
| Official user guide (docs portal) | Motorola mounting options guide (SVX / V300 accessory lane) | Strong-magnet warning for shirt/heavy-jacket mounts, implanted-device caution, 65 pounds snap-pressure signal, warning that magnets can affect phones/computers/hard drives/cards/magnetic media, plus lens-orientation guidance. | Last modified 2026-03-12; reviewed April 26, 2026 |
| Federal security policy (PDF) | FBI CJIS Security Policy v6.0 | Version baseline (6.0, 12/27/2024) and control references for SC-8, SC-28, and AU-6 used in evidence-security mapping. | Version 6.0 dated 2024-12-27; reviewed April 26, 2026 |
| Federal security policy (superseded baseline) | FBI CJIS Security Policy v5.9.5 | Previous baseline retained only for version-drift comparison in existing internal checklists. | Version 5.9.5 dated 2024-07-09; compared April 26, 2026 |
| Federal guidance | FDA magnets and implanted medical devices guidance | >= 6 inch / 15 cm precaution used in risk and policy notes. | Published/updated 2021-05-13; reviewed April 26, 2026 |
| Clinical association guidance | American Heart Association pacemaker/ICD interference guidance | Used to corroborate the >= 6 in magnet-distance baseline and the “avoid prolonged close contact” handling boundary. | AHA page reviewed April 26, 2026 (no explicit publication date shown) |
| Implanted-device manufacturer guidance | Medtronic electromagnetic guide FAQ | Device-manufacturer-specific context for >= 15 cm / 6 in magnet spacing and examples of high-field products that are not recommended. | Medtronic FAQ reviewed April 26, 2026 (live page without explicit publication date shown) |
| Federal body-armor compliance signal | NIJ Mark and Compliant Product List scope | Used to enforce model-specific armor identity checks (CTP/FIT + NIJ mark) before treating vest-related mount changes as compliance-neutral. | NIJ page reviewed April 26, 2026 |
| Federal fit-assessment publication (PDF) | Personal Armor and Fit Assessment publication | ASTM E3003-15 fit workflow and overlap/coverage checks used to define post-install fit reassessment boundaries after mount-geometry changes. | Document 251599 reviewed April 26, 2026 |
| Federal implementation guide | BJA body-worn camera implementation guide | Lifecycle cost framing (capital, operational, replacement) and mounting-kit context used to prevent hardware-only budgeting decisions. | Implementation page reviewed April 26, 2026 |
| Federal implementation checklist (PDF) | BJA Implementation Checklist & Toolkit Guide (v6) | Procurement-governance structure: six policy areas (capture/viewing/use/release/storage/audits), full life-cycle costing in vendor selection, and post-go-live cadence (monthly compliance + 3-month assessments). | v6 PDF reviewed April 26, 2026 (no explicit publication date shown in sampled pages) |
| Standards body scope note | IEC IP ratings and IEC 60529 scope summary | IP ratings define enclosure protection and test framing; used as a scope boundary against over-claiming retention certification. | IEC page reviewed April 26, 2026 |
| Federal standard scope (body armor) | NIJ Standard 0101.07 page | Scope states ballistic resistance requirements for torso body armor; used to avoid treating NIJ levels as camera-mount retention certification. | Published/updated 2025-12-01; reviewed April 26, 2026 |
| Federal technical primer (NIJ/OJP PDF) | A Primer on Body Worn Camera Technologies | Legacy federal baseline that states a single set of BWC technical requirements does not exist and outlines mount-position tradeoffs. | Document 250382 (received 2016-11); reviewed April 26, 2026 |
| Federal digital-evidence guidance (NIST IR) | NIST IR 8387: Digital Evidence Preservation | Used for collection-time hashing guidance, secure hash-record storage, proprietary-format downstream cost risk, and recommendation to preserve native plus open-format evidence copies where feasible. | Published 2022-09; reviewed April 26, 2026 |
| Federal statistics release (BJS) | Body-Worn Cameras in Law Enforcement Agencies, 2016 | Used for adoption baseline (47% of agencies acquired BWCs; 86% had policy/draft among adopters) and top non-adoption cost barriers (77% storage/disposal, 74% hardware, 73% maintenance/support). | Released 2018-11-16 (2016 survey); reviewed April 26, 2026 |
| BJA-sponsored prosecution guidance (PDF) | Body-Worn Camera Policies and Procedures: Guidelines for Prosecutors | Used for policy requirements on officer/witness video review, dissemination controls, chain-of-custody/audit-trail expectations, and post-adjudication retention/disposition rules. | Published 2023-08-01; reviewed April 26, 2026 |
| Federal publication record | BJA Library entry for NCJ 307378 | Used to validate publication provenance and date metadata for the prosecutor guideline reference set. | BJA metadata reviewed April 26, 2026 |
| Internal keyword dataset | camera-mount-magnet broad-match triage set | Canonical/alias demand and CPC snapshots used in quick stats and SEO framing. | Snapshot March 25, 2026 |
| Inference disclosure | Cross-vendor retention-speed and pull-force benchmark set | Inference from all listed public sources: no single cross-vendor retention-speed certification standard or reliable Newton pull-force dataset is publicly available. | Inference logged April 26, 2026 |
| Uncertainty disclosure | Cross-vendor magnetic retention-speed certification | Marked as N/A due to insufficient public universal standard evidence. | Pending confirmation as of April 26, 2026 |
FAQ answers are grouped by fit, risk, and procurement decisions rather than pure glossary terms.
Every path should end with an executable action, whether the result is ready, review, or boundary.
Disclosure: This page is a decision-support and pre-qualification layer, not a universal retention certification. Always validate against your real uniform stack, policy constraints, and pilot evidence.
Canonical policy: Alias intent for body camera magnetic mount, boblov body camera magnet mount, body camera magnet mount, body worn camera magnet mount, body camera with magnetic mount, axon magnetic body camera mount, axon camera magnet mount, axon body camera mount magnet, and axon body camera magnetic mount resolve to /products/magnetic-body-camera-mounts to maintain one authoritative URL.