Use staged recordings to evaluate mounting, daylight and infrared video, audio, buffering, runtime, downloading, retrieval, and exports. Keep a clear acceptance record for the proposed Martel configuration.
By Martel Electronics · Updated November 5, 2026
A body camera demonstration should end with saved recordings that the department can examine. A camera that looks clear on its display or feels comfortable in a meeting room has passed only a small part of the evaluation. The complete test follows the device from assignment through recording, download, retrieval, and readiness for reuse.
This original guide uses the Martel Crime Cam as an equipment example. Its product page describes a 2-inch display, infrared operation, pre-event recording, multiple video modes, docking, and Transporter downloading software. Test the exact configuration proposed in the quote and keep a record of the conditions.
Write the task the recording must support. A useful requirement describes an observable result, such as intelligible staged conversation from the proposed worn position or successful retrieval of a specified training clip. Avoid vague requirements such as best quality or easy software without a shared definition.
Identify essential requirements separately from preferences. The department may need a particular receiving workflow or export capability that is more important than a convenient display option. Give the supplier those requirements before the demonstration so the test addresses the proposed purchase.
Use training participants and staged situations. The evaluation should not depend on recording actual incidents or sensitive members of the public. Obtain the organization’s approval for the test environment and follow its normal training arrangements.
The wearer tests mounting, controls, indicators, movement, and practical use. The receiving operator tests connections, downloading, file organization, and readiness. The reviewer tests whether a requested recording can be found and understood afterward.
Keep those roles distinct even when one person ultimately performs several jobs. A reviewer who was not present during the staged conversation is especially useful for assessing whether the recording carries enough understandable context.
Record who performed each task and where assistance was needed. A successful demonstration with constant vendor guidance may still require additional internal training before deployment. The test should reveal that need clearly.
Before filming, note the device identifier, model, supplied version where known, video resolution, quality setting, compression choice, date and time, buffer setting, mount, and receiving arrangement. Include the computer and storage destination used for the test.
Photograph the approved worn position using a training participant where appropriate. A later comparison is easier when the department knows how the camera was attached. Record clothing and equipment that might affect the lens or microphone.
Change settings deliberately and label the resulting clips. If several modes are tested, give each sequence a clear spoken or visual identifier. Avoid mixing recordings from unknown settings and then drawing a firm conclusion from the group.
Begin with ordinary posture. Check the field of view while standing, sitting, turning, and reaching. Include the clothing and equipment normally used for the assignment. Watch for a coat, strap, radio, or hand covering the lens.
Have the wearer walk at a normal pace and make routine movements in a safe training area. Check whether the mount remains attached and whether the camera angle changes. A secure mount can still point in an unhelpful direction, so review the saved view afterward.
Ask the wearer to locate and operate controls without an exaggerated demonstration posture. Record what requires looking down or using both hands. The department can then decide whether the arrangement fits the assignment and training plan.
Use representative distances and a staged subject. Include movement toward and away from the camera, a conversation from the side, and a transition near a bright doorway. Record the conditions so later comparisons use the same task.
If the department needs to capture particular detail, test that detail directly under defined conditions. A general sharp-looking image is not proof that every object or distant feature will be readable. Keep observations tied to the actual clip.
Review the saved file on the intended workstation. The camera display is useful for immediate review, but it is not the same viewing environment as the department’s archive or an authorized export. Confirm both the image and playback behavior.
The Crime Cam listing describes automatic and manual infrared operation. Ask Martel to demonstrate the supplied controls and available settings. Use a safe staged transition between ordinary interior light and a dim area, then inspect the saved recording.
Include reflective surfaces and a moving volunteer at representative distances. Record where the image remains useful for the stated task and where detail becomes insufficient. A stated night-vision range should be treated as context for evaluation rather than a guarantee of identification.
Teach reviewers to recognize the appearance of infrared footage. Do not assume colors or daytime appearance are preserved in that mode. Keep a daytime reference if it helps the department compare the same scene.
Have volunteers speak in normal voices at the positions relevant to the assignment. Include background sounds that can be reproduced safely, such as ordinary traffic noise at a training location or a radio at the normal operating level. Keep test conditions consistent.
Include walking, turning, and sitting so clothing noise is represented. The microphone may hear friction that was not obvious to the wearer. A handheld demonstration away from clothing does not answer how the worn arrangement performs.
Ask a reviewer to identify specific staged details from the saved recording without seeing a script. Record what was understandable, uncertain, or obscured. Do not claim a universal audio result from one favorable office conversation.
The Crime Cam page describes pre-recording up to sixty seconds depending on mode and quality. Confirm the available duration and conditions on the supplied unit. Ask specifically about audio in the buffered portion rather than assuming it behaves like the later saved event.
Use a known sequence with clear time markers before activation. Start recording at a documented point and inspect the saved file on the workstation. Confirm which part of the sequence was preserved and how the camera indicates its operating state.
Repeat after an ordinary restart using the supplied instructions. The department should know what must happen before buffering is available and what the wearer must still do to save an event. Keep the result with the configuration record.
Battery estimates vary with recording mode and conditions. Define the test pattern before measuring: powered-on time, active recording, infrared use, display review, and any pauses or charging. Use the proposed settings and record the environment.
Observe the low-battery indications and the supported response. Do not plan operational coverage solely from a maximum advertised number. A measured trial should inform the department’s readiness and replacement procedure.
For shared devices, test the actual turnaround between assignments. Charging opportunity and receiving time matter as much as continuous recording time. Record whether the camera meets the approved readiness condition before the next issue.
Measure the size and duration of representative training clips. Calculate gigabytes per recorded hour and retain the sample conditions. Use these observations in the storage estimate rather than treating resolution alone as a data rate.
Play the selected format on the receiving and review workstations. The Crime Cam page lists MP4 and different compression choices, so test the proposed mode. Confirm that required playback tools are available in the organization’s approved environment.
Use the storage planning guide to turn measured rates into an archive estimate. Label every retention period in that estimate as an approved agency input or an explicit planning assumption.
Connect the camera using the proposed dock or cable and the supplied instructions. Observe device recognition, software startup, destination selection, transfer progress, and completion. The operator should explain what visible evidence establishes success.
Open the saved file from its intended location. Confirm the training identifier, expected duration, picture, and sound. Do not treat a charging indicator or elapsed connection time as proof of successful receiving.
Ask Martel to explain what happens to files on the device after transfer. Demonstrate the supported behavior with disposable clips. Keep that procedure in the station instructions rather than improvising a clearing sequence.
With vendor guidance and training files, demonstrate an unavailable destination or another supported interruption scenario. Record the message and the operator’s response. Confirm how the expected files are received after the condition is corrected.
Check the destination for incomplete or duplicate items through the supported procedure. Do not delete files simply because their names look similar. The point of the exercise is to establish a known recovery method before real material depends on it.
Keep the exception test safe and limited to approved training conditions. Do not create unnecessary faults in a live archive or disrupt other work. The department should control the test environment and the recordings used.
Give the reviewer the kind of request the department expects: date, assignment, approximate time, and a short event description. Have the reviewer locate and play the correct training recording without help from the wearer.
Observe ambiguity in device assignment, folder structure, dates, and file naming. A clear recording loses practical value when staff cannot find it reliably. Update the assignment and receiving instructions where the exercise exposes uncertainty.
Repeat with an authorized employee from another shift if possible. The retrieval process should remain understandable when the person who downloaded the files is absent. This is a useful test of the written procedure as well as the equipment.
Use the organization’s proposed process to prepare a copy of a training recording. Record which source file it came from, who prepared it, and what the export is intended to contain. Keep original recordings distinct from working or prepared copies.
Play the exported file in the intended receiving environment. Confirm expected picture, sound, duration, and any required context. A file appearing in an export folder does not prove that the recipient can use it.
If a particular access, logging, redaction, encryption, or integration function is required, test it explicitly and ask for written confirmation of the supplied capability. Do not assume those functions follow from the presence of downloading software.
Use one result row per requirement: test conditions, expected result, observed result, pass or unresolved status, and follow-up owner. Attach references to the relevant training clips and configuration record. Keep preferences separate from essential failures.
A result should be specific enough for someone absent from the demonstration to understand. For example, describe the staged distance and lighting where speech or detail was checked. Avoid broad conclusions such as works everywhere or eliminates complaints.
Ask Martel to resolve essential questions in the written quote or supporting documentation. Repeat affected tests after changes. A revised mount, different recording mode, or changed receiving computer may alter an earlier result.
For small deployments, compare the 6-officer and 12-officer packages using the measured workload and assignment schedule. Larger choices are available through Martel’s police camera category.
Confirm that the final quote describes the tested configuration or explains any difference. Preserve the acceptance record with the purchase information. The department can then repeat affected checks when equipment is replaced or the workflow changes.
Give each test a short identifier and a stated purpose. Record the camera, mount, settings, date, location, participant roles, and expected outcome. Add the names or references of the training files created. A test sheet should let someone understand the conditions without relying on the person who conducted the demonstration.
Use observable outcomes. If the task is understanding a staged conversation, describe the positions, ordinary speaking level, and background conditions. If the task is retrieval, describe the information given to the reviewer and the expected recording. Avoid a pass condition based only on whether someone liked the appearance of a preview.
Separate essential requirements from preferences. A department may consider a particular receiving capability essential while treating a display preference as desirable. Preserve that distinction in the results so an attractive feature does not conceal an unresolved requirement. Purchasing should be able to trace the decision back to the agreed task.
Keep the original training recordings and configuration notes through the organization’s approved process. When a mount or setting changes, repeat the affected sequence using the same conditions where practical. A meaningful comparison depends on knowing what changed and what stayed consistent.
Choose a safe training space representative of the intended assignment. Have the wearer use the proposed clothing and mount. Place a volunteer in the position relevant to the recording task and agree on a short set of known statements, including a few names or numbers created for training. Do not use sensitive real-world information merely to make a test sound realistic.
Record the conversation at ordinary speaking levels. Include a brief turn of the wearer’s body and a short change in distance. Record the approximate positions and environment in the test sheet. The purpose is to evaluate the worn arrangement, so avoid holding the camera away from the clothing during the main sequence.
Have a reviewer who was not present listen to the saved file on the intended workstation. Ask the reviewer to identify the staged details and mark anything uncertain. Do not provide the full script first, because prior knowledge can make unclear speech seem easier to understand than it would be in an actual review.
Discuss whether the result meets the department’s stated task under those conditions. If it does not, identify a possible supported adjustment and repeat the relevant test. Keep the earlier result so the organization can see why the configuration changed rather than replacing an unfavorable clip with no explanation.
Prepare a safe walking route with ordinary movements such as standing, sitting, turning, and reaching. Use the equipment the wearer normally carries where the organization permits it in training. Make a known spoken statement at several points so the reviewer can compare the effect of movement on the saved audio.
Check the view as well as the sound. A camera can remain attached while shifting enough to obscure the intended subject. Clothing may cover the lens briefly, and a strap may touch the microphone area. Record these observations as features of the tested arrangement rather than assuming the wearable camera follows the wearer’s eyes.
Review the sequence on the workstation. Identify the movements associated with an obscured view or prominent noise. Ask whether a supplier-supported mounting adjustment could address the issue without interfering with other equipment. Repeat the same movements after an approved change to make the comparison useful.
Do not stage unsafe physical activity or imitate a real emergency merely to make the test dramatic. A controlled exercise can answer mounting and recording questions with less uncertainty. The department should choose training activities appropriate to its environment and requirements.
Choose an ordinary location where the camera moves between areas with different lighting. Record the conditions and approximate positions. Have a volunteer make a known movement or statement while the wearer passes through the transition. Keep the route safe and avoid relying on uncontrolled public interactions.
Inspect the saved sequence for the task the department defined. Note whether the relevant subject remains visible, when detail changes, and whether the transition affects the portion needed for review. A camera’s preview may adjust in a way that looks acceptable at a glance, while the saved file deserves a slower examination.
Keep the result specific. A pass in one doorway under one lighting arrangement does not establish performance in every building or every hour. If the assignment regularly involves different lighting, add representative sequences and retain the conditions for each one.
Use the result to ask focused product questions. A department can request clarification about supported modes and controls or ask to repeat the demonstration using another proposed setting. Avoid translating a general feature description into an untested guarantee about every scene.
Ask Martel to show how the supplied camera indicates and controls infrared operation. Record whether the trial uses automatic or manual operation and the relevant settings. Choose a safe training area that represents the organization’s low-light recording task, with distances and lighting noted in the test sheet.
Use a volunteer or staged object appropriate to the stated task. Include normal movement and any representative reflective surfaces. Review the saved result on the intended workstation and distinguish general scene visibility from the ability to resolve a particular detail. Those are related but different observations.
If an approximate range is listed on a product page, treat it as information for planning the trial. Do not describe it as a promise that every face, object, or marking will be identifiable at that distance. The conditions and recorded task determine the usefulness of the result.
Keep a daytime reference where it helps reviewers understand the same location. Explain that infrared footage can look different from ordinary daytime video. The acceptance record should show what was actually captured and what the department concluded about the defined test.
Prepare a sequence with clear training markers before and after the intended activation point. Record how long the camera has been operating and which pre-event setting is selected. Use the supplied instructions to establish the relevant ready state rather than assuming buffering begins immediately after any power action.
Activate recording at a known marker and complete the sequence. Receive the file through the proposed workstation and inspect its beginning. Identify which markers appear before activation and whether audio is present in that portion. Record the observed duration and behavior for the tested setting.
Repeat where a different proposed recording mode changes the available buffer. The Crime Cam page describes pre-recording as dependent on resolution and quality, so the acceptance result should remain tied to a known configuration. A maximum listed duration should not silently become the assumed behavior of every mode.
Have the wearer explain the distinction between powered on, buffering where supported, and saving an event. This checks training as well as the feature. Any required activation policy remains the department’s responsibility; the equipment test establishes the control actions and recorded result.
Record a representative training sample using the proposed standard mode. Keep every original file that belongs to the sequence, including segments if the device divides recordings. Measure the total size and duration using the organization’s approved tools and consistent units.
Calculate the observed gigabytes per recorded hour and retain the arithmetic beside the sample conditions. Repeat with a different representative scene if file sizes vary. Explain the planning rate selected from those observations rather than choosing the smallest result merely because it supports a smaller storage purchase.
Use the result in the storage worksheet with the expected camera count, recorded hours, and approved retention assumptions. Add longer-held material, reserve, growth, and recovery needs separately. The storage planning guide gives worked calculation examples.
This exercise is not a benchmark claim about every Crime Cam or every deployment. It is evidence about the supplied configuration under recorded training conditions. Keep that limit in the purchasing record and revise the estimate when actual operating data becomes available.
Use the number of cameras expected to return together and the proposed docks, cables, computer, software, and destination. Record the amount of training material on each device. Have the normal operator perform the routine while an observer records the actions and outcome.
Check whether the operator can identify each camera and its assignment. Observe transfer status and the procedure for a device needing attention. Confirm the required saved-file verification and charging status separately. A row of connected cameras does not by itself describe which work has finished.
Record the time needed for the tested batch and any assistance required. Do not predict a larger fleet’s performance by multiplying a short single-camera result without testing the shared arrangement. Computer, connection, storage, and staff workloads may change when several devices are handled together.
Have an alternate employee take over using the station instructions and status record. That person should identify unresolved work and understand the next approved action. This checks whether the proposed receiving process survives a normal staff handoff.
Choose an exception exercise with Martel and responsible technical staff. Use disposable training recordings and an isolated approved test setting where needed. The purpose is to learn supported behavior, not to disrupt live archives or manufacture a failure in operational equipment.
Record the visible symptom and software message before changing anything. Ask the operator to identify the affected device, preserve its status, and follow the supplied instructions. Keep the distinction between an observation and a diagnosis clear in the test record.
After the condition is resolved through the supported process, verify the expected training material at the intended destination. Record any incomplete or duplicate items and the approved handling procedure. Do not resolve unfamiliar file states by deleting things solely because their names appear similar.
The outcome should include both technical recovery and staff understanding. The operator should know when to continue and when to seek support. If instructions were unclear, improve them and repeat the relevant training exercise before ordinary deployment.
Give an authorized reviewer a request containing the information normally available in the organization: assignment date, approximate time, relevant device or wearer reference, and a short staged-event description. Keep the expected answer separate. Do not begin by handing the reviewer a direct link to the exact file.
Observe how the reviewer connects the assignment record to the saved material. Note uncertainty in time conventions, folder names, camera reassignment, or file segmentation. Ask the reviewer to identify the expected beginning, end, picture, and sound through the approved review procedure.
Repeat with a different training event or staff member where useful. A successful result should show that retrieval is understandable from the documented process, not merely that one employee remembers the recording. Improve instructions where verbal help was necessary.
This exercise is especially useful when several cameras or recording sources relate to one staged event. The department should understand how its records identify the relevant files without assuming the equipment automatically creates a shared event relationship.
Use a training recording and the organization’s proposed authorized-copy process. Record the source reference, preparation method, intended content, and destination environment. Keep originals distinct from prepared working copies according to the organization’s requirements.
Open the resulting copy in the intended receiving environment. Check picture, sound, duration, and any required accompanying information. Confirm that the selected compression mode can be played using the organization’s approved software. A file extension alone does not guarantee identical support on every computer.
If the department requires redaction, logging, encryption, or another specialized function, include it as a separate demonstrated requirement. Do not assume downloading software provides a feature simply because it is associated with evidence handling. Ask for written confirmation of the actual supplied capability.
Record failures and unresolved questions in the acceptance sheet. A reviewer should be able to see whether the issue concerns the original recording, export preparation, playback environment, or another stage. That makes follow-up more useful than a general note saying the video did not work.
Where an agency evaluates body cameras and police in-car video together, define the expected viewpoint from each system. A body camera moves with the wearer while a vehicle camera remains mounted or is used in its specified portable role. Create a safe staged sequence that shows where each view helps and where it does not cover the task.
Martel’s DC7 and MDP6 pages describe different vehicle-recording arrangements. Use the current quoted configuration and supplied instructions in the trial. Keep body-camera and vehicle files identifiable through the organization’s process, and ask a reviewer to retrieve the expected portions afterward.
Confirm any required synchronization or integration explicitly. Shared activation, common event identifiers, automatic pairing, and a single review application should not be inferred from complementary equipment. An acceptance test should demonstrate the exact relationship the department needs.
Use the results to refine the quote and training plan. The trial may show that an additional view, a different approved mount, or a clearer source-reference procedure is needed. Record the requirement and repeat the affected test after a supported change.
For every essential requirement, retain the test identifier, conditions, expected result, observed result, associated training files, status, and follow-up owner. Use pass, unresolved, or another organization-approved status with a clear definition. Preferences should be documented separately from essential functions.
Avoid broad claims that exceed the evidence. A particular conversation was understandable under defined conditions is more precise than perfect audio. A reviewer retrieved a known training clip using the instructions is more useful than effortless evidence management. Specific findings help an approving official assess the actual purchase.
Have the supplier address unresolved product questions in writing and identify any difference between the tested configuration and the final quote. Repeat affected checks after substitutions or changes. The delivered equipment should be compared with the accepted arrangement before it enters ordinary service.
Keep the acceptance record with the current instructions and equipment inventory. It becomes a reference for future training, repair, expansion, and workstation changes. The value of the test continues after purchasing because staff can repeat the relevant sequence when a change affects the recording workflow.
## Check repeatability before drawing a purchasing conclusion
A useful acceptance result should be repeatable under the documented conditions. Ask another trained wearer to perform the same staged sequence using the accepted mount and settings. Have the receiving operator follow the same instructions and another authorized reviewer evaluate the saved result. Record meaningful differences instead of assuming the first trial represents every user.
Repeatability does not mean every recording must look or sound identical. Movement, voice, posture, and ordinary environmental variation can affect the result. The question is whether the documented arrangement supports the defined recording task consistently enough for the department’s requirements. The agency should determine that conclusion from its own evaluation.
If one participant needs additional instruction, distinguish that training need from an equipment limitation. If a supported mounting adjustment changes the result, retain both configurations and the reason for the change. This helps purchasing understand what must be supplied and helps training staff preserve the accepted arrangement.
An unresolved finding should identify the requirement, observed issue, relevant configuration, and requested clarification. For example, a reviewer may be unable to play the selected compression mode on the proposed review computer. The follow-up should address that actual playback environment rather than asking only whether the camera records MP4 files.
Another finding may concern receiving status. If an operator cannot identify which camera completed a batch transfer, ask for a demonstration of the supported workflow and the staff procedure needed to track it. Keep the question tied to the camera quantity and workstation arrangement intended for purchase.
For a required capability that was not available in the demonstration, ask how it would be supplied and tested. Do not record it as passed based solely on a general statement that it is possible. The final written proposal should make the equipment, selected options, and operating responsibilities understandable.
After delivery, check the supplied model, quantities, accessories, workstation, software, and storage configuration against the accepted proposal. Identify differences before relying on the system for ordinary work. A component substitution may be appropriate, but its effect on the relevant acceptance result should be understood.
Repeat the affected training sequences using the delivered equipment. Check wearable use, receiving, playback, retrieval, and any essential specialized function that changed. Preserve the results with the equipment record. The aim is to connect purchasing approval to the actual arrangement in service.
Have normal and alternate staff perform the appropriate exercises. A successful vendor demonstration is useful, while a repeat performed by the organization’s staff shows whether the operating instructions and training are sufficient for their roles. Document where assistance remains necessary and resolve essential gaps through the normal acceptance process.
The completed record should state what was tested, under which conditions, and with what outcome. It should also identify limitations and unresolved questions. That evidence supports a practical purchasing decision without promising that any camera can capture every detail in every possible event.
A final test summary should use concrete observations and identify their limits. List the supplied configuration, staged conditions, requirements demonstrated, and unresolved questions. Have the responsible staff review that summary before it accompanies purchasing approval. Keep the original training samples and current instructions through the organization’s approved process. When an affected component or setting changes, repeat the relevant exercise and update the record so the acceptance evidence remains connected to the equipment actually in service.
It should cover the representative recording tasks, return workload, charging interval, retrieval, and required exceptions. The appropriate duration depends on the assignment pattern. A short demonstration may answer control questions but leave daily turnaround untested.
Test modes that may meet the department’s needs. Compare detail, playback, file size, runtime, and transfer together. Record which mode is chosen and why so the rollout uses a known configuration.
Use staged training material for an equipment trial unless the organization has explicitly approved another process. Known training content makes completeness easier to check and keeps the evaluation independent of real case handling.
Treat the unresolved receiving requirement as part of the system evaluation. Identify whether the issue is connection, software, destination, assignment, or procedure. A successful wearable recording does not complete the overall acceptance test.
Read the buyer’s guide, docking guide, small-department guide, and recording-to-review workflow. Request a Martel quote with the test requirements and intended deployment size.
