5.4 Testing Installed and Mobile Equipment

Installed versus mobile systems

A permanently installed system may integrate courtroom microphones, public address, recording computers, network storage, clerk controls, and centralized support. Its advantages include repeatable wiring and room-specific design; risks include hidden routing, shared infrastructure, permissions, and faults outside the reporter's console. Coordinate with authorized staff and do not reconfigure protected settings casually.

A mobile system travels with the reporter and may be more familiar, but every room requires assembly, cable protection, power, microphone placement, and acoustic adaptation. Components can be lost or connected differently. Use a checklist and consistent labels. Do not assume yesterday's configuration survived transport or a software update.

Closed-loop test

A reliable test follows the complete loop:

1. Identify: Confirm job, date, session, system time, participants, and required format.
2. Stimulate: Have a person speak at each actual position, including remote and interpreter paths.
3. Observe: Check input and track meters, routing, record status, error indicators, and backup.
4. Record: Capture enough normal and loud speech to reveal levels, noise, overlap, and room reflections.
5. Annotate: Enter a test note and verify its timestamp relationship.
6. Stop and close: Ensure the system finalizes the file without error.
7. Replay from storage: Isolate each channel through the intended playback path.
8. Recover: Confirm backup location and the practiced action if the primary stops.

Simply saying “test, one, two” into one microphone while watching a meter misses channel swaps, speaker positions, file-write faults, and remote returns.

What to listen for

Use speech, not only tones. Check consonant clarity, low speech, loud peaks, hum, buzz, radio-frequency interference, clipping, delay, echo, dropouts, fan noise, table impacts, paper, and adjacent-channel bleed. Ask participants to use expected posture and distance. If a witness will face a jury or screen, test that orientation.

Check public playback separately. Playback volume must be adequate without feeding the replay into an active record unexpectedly. Know how to locate a timestamp and return safely to capture.

Capacity and resilience

Verify storage capacity based on the approved format and likely duration, leaving operational margin. Confirm destination and permissions; a large empty drive does not help if software writes to a full system volume. Test backup power indicators and estimate from a documented battery or UPS test, not optimism. Ensure the backup records the necessary sources and is not disabled by the same single failure as the primary when independence is required.

Test network-dependent functions without making core capture unnecessarily depend on an unstable network. Know what continues if internet, local network, or cloud sync fails. A sync icon is not proof that the local master closed correctly.

After a change

Re-test the affected path after replacing a cable, moving a microphone, selecting another interface, updating a driver, reconnecting a remote participant, changing sample configuration, or switching power. Test unaffected critical paths too if the change could alter global routing. Document deviations and tell the appropriate authority before starting if a requirement cannot be met.

Test records and privacy

Use neutral test speech rather than confidential case facts. Label test files clearly, store or dispose of them under policy, and avoid uploading them to unapproved services. A test recording can still reveal room conversation or system details.

Go/no-go judgment

If a critical source remains unusable, do not begin silently. Escalate with precise facts: which path failed, what was tried, which backup is available, and what limitation remains. The authorized official can delay, move, replace equipment, or direct another lawful course. The reporter's role is to provide verified technical information and protect the record, not to declare that an inadequate setup is “probably fine.”

Exam application

Treat a successful test as evidence tied to a configuration. If the witness changes seats, the interface is reconnected, the remote participant switches devices, or the software selects a different input after an update, the earlier test no longer proves the affected path. Re-test the change and enough related functions to detect collateral effects. Record an unresolved limitation before the start so the authorized official can decide whether to delay, relocate, use backup equipment, or proceed under another lawful plan. A green power light never substitutes for intelligible stored playback.

Review checkpoint

A test result belongs to the exact source, route, settings, and stored file that were exercised. Four-channel readiness requires four verified channels, not one good microphone and three assumed paths.