Study guide

6.1 Basic Troubleshooting and Technical Escalation

AAERT Certified Electronic Reporter CER

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Ethical Obligations

1.1 Current Exam Blueprint and Ethical Conduct 1.2 Conflicts of Interest and Appearance of Impropriety 1.3 Gifts, Fees, Accuracy, and Record Duties

2 Chapter 2: Confidentiality and Information Control

2.1 Confidentiality and Non-Disclosure Agreements 2.2 Job-File Security, Equipment Protection, and HIPAA 2.3 Audio Requests, Sealed Material, and Controlled Release

3 Chapter 3: Professional Behavior

3.1 The Impartial Reporter and Professional Client Service 3.2 Courtroom, Non-Courtroom, and Remote Etiquette 3.3 Demeanor, Appearance, Punctuality, Attention, and Disruptions

4 Chapter 4: Digital Audio Hardware

4.1 Digital Audio Systems, Interfaces, and Power 4.2 Microphone Types, Pickup Patterns, Cost, Cables, and Connectors 4.3 Multi-Channel Assignment and Channel Isolation 4.4 Audio Levels and Recording Peripherals

5 Chapter 5: Software, Annotations, Setup, and Testing

5.1 Recording Software, Confidence Monitoring, Playback, Realtime, and ASR 5.2 Speaker Changes, Abbreviations, Timestamps, and Annotation Priorities 5.3 Equipment Setup in Live, Dead, and Variable Rooms 5.4 Testing Installed and Mobile Equipment

6 Chapter 6: Reliability and Reporter Duties

6.1 Basic Troubleshooting and Technical Escalation 6.2 Audio and Computer Maintenance 6.3 Participant Instructions, Record Status, Clarification, and Oaths 6.4 Remote and Hybrid Proceedings

7 Chapter 7: Collaborators, Exhibits, and Transcript Orders

7.1 Working with Interpreters 7.2 Working with Legal Videographers 7.3 Physical and Electronic Exhibits and Chain of Custody 7.4 Transcript Orders, Roughs, Expedites, Originals, Copies, and Estimates

8 Chapter 8: Transcript Production Workflow

8.1 Accurate Transcript Production and Special Record Events 8.2 Pre-Proceeding Meetings, Appearances, Read-Ons, and Stipulations 8.3 Post-Proceeding Spellings, Job Information, Distribution, Archival, and Retention

9 Chapter 9: Federal Rules and Types of Proceedings

9.1 Federal Transcript Orders and Rule 30 Review 9.2 Trials, Hearings, and Court Proceedings 9.3 Depositions, EUOs, Arbitrations, Mediations, Meetings, and Statements 9.4 Order of Proceedings and the Reporter's Role

10 Chapter 10: Case Life Cycle and Participants

10.1 Civil and Criminal Case Life Cycles 10.2 Parties and People in Proceedings 10.3 Witness Types and Testimony 10.4 Reading Legal Documents Relevant to Reporters

11 Chapter 11: Jurisdiction, Case Law, and Trials

11.1 Jurisdiction, Venue, and Civil versus Criminal Proceedings 11.2 Case Law and Citation Elements 11.3 Jury Selection and Bench versus Jury Trials 11.4 Sidebars, Bench Conferences, and In-Camera Proceedings

12 Chapter 12: Legal Terminology

12.1 Core Courtroom Actions and Roles 12.2 Civil Pleadings, Discovery, and Remedies 12.3 Criminal Procedure Terminology 12.4 Evidence, Foundations, Privilege, and Objections

13 Chapter 13: Latin and Medical Terminology

13.1 Common Latin Legal Terms 13.2 Medical Word Building, Positions, Tests, and Treatment Terms 13.3 Body Systems, Pathology, and Diagnostic Language

6.1 Basic Troubleshooting and Technical Escalation

Key Takeaways Explain This Topic AI

Protect current capture before troubleshooting; avoid changes that could destroy the only usable source.

Troubleshoot from symptom and signal path, changing one variable at a time and verifying after each change.

Escalate when the fix exceeds authority, risks the record, requires protected access, or does not restore verified capture promptly.

Technical incident notes should record observed facts, timing, actions, results, and authority without speculation.

Last updated: September 2026

Stabilize before changing

When a warning appears, first determine whether the record is still being captured somewhere. Preserve the working primary or backup, note the time, and use the established interruption protocol if completeness is threatened. Do not restart every device, unplug shared equipment, delete files, or change several settings at once. Broad changes erase diagnostic clues and may stop the only good path.

Describe the symptom , not an assumption: “Channel 3 has no recorded signal after 10:14” is useful; “the microphone is broken” may be wrong. Check whether the issue affects one source, one track, all tracks, monitoring only, playback only, storage, or the remote connection.

Trace the path

For one silent channel:

Confirm the intended speaker and microphone.

Check mute, power, battery, physical connection, and cable strain.

Inspect the interface input and preamp meter.

Confirm software device, input route, arm state, and track mute.

Check file-write status and confidence return.

Substitute one known-good compatible component if authorized.

Record and replay a short test.

If every channel is silent, look for shared points: power, selected device, driver, software state, storage error, or master routing. If only headphones are silent while recorded meters and playback through another authorized output are good, the fault may be the monitor path. Never infer file quality from one indicator.

Common symptoms

  • Symptom Likely areas to inspect
  • Hum or buzz Cable shielding, power relationship, damaged connector, nearby electrical source
  • Clipping Preamp/input level, source distance, overload before software
  • Dropouts Cable, wireless link, USB/network load, driver, storage
  • Echo in hybrid session Duplicate return paths, open speakers and microphones, platform routing
  • Wrong speaker on track Physical patch, software route, label, seating change
  • File stops growing Record state, storage capacity, permissions, application error

These are starting points, not diagnoses. Verify.

Escalation

Escalate to the designated courtroom technician, platform support, agency supervisor, or system administrator when:

  • the record is at risk and a simple approved action did not restore it;
  • the change requires administrator credentials or protected configuration;
  • installed equipment, network, server, or platform infrastructure is involved;
  • a safety, security, suspected tampering, or data-loss incident exists;
  • continuing tests would create greater disruption or uncertainty; or

the assignment protocol requires immediate reporting.

Provide concise information: job and room, time, exact symptom, affected sources, error text, verified working paths, actions already taken, backup status, and how to contact the presiding authority. Avoid hiding an error or flooding support with unsupported theories.

During a live failure

If the primary fails and the backup is confirmed, the authorized process may permit a transition. Announce or document the gap and restart point as directed. A backup that records only a room mix may preserve speech but lose isolation; disclose that limitation. If neither path is verified, promptly notify the presiding official. Participants may repeat or reconstruct only under that authority; the reporter should not silently fill words from memory.

Incident documentation

Record objective facts: warnings, timestamps, files, channels, observed duration, participant instructions, equipment changes, people notified, and verification results. Preserve logs and affected files. Do not edit records to make the incident disappear. A later review needs to distinguish what was captured, what was inferred, and what corrective action was authorized.

Simple versus unsafe troubleshooting

Simple work includes checking connections, selections, power, space, mute and arm states, and replacing a known-good approved cable. Unsafe or unauthorized work includes opening powered hardware, changing court network security, installing unknown drivers, formatting media, or experimenting with the master file. Competence includes knowing that boundary.

Exam application

For practice, classify faults by scope before selecting a fix. One silent microphone suggests its source path; every silent track suggests a shared device, driver, application, or power issue; good recorded files with silent headphones suggest monitoring. Then state the least risky check and the escalation threshold. If a fix needs administrator access or could interrupt the verified backup, stop experimenting. Precise facts—time, channel, error message, current capture, and attempted step—help support act quickly without forcing the reporter to pretend to know the root cause.

Half-split the signal chain

Testing every component in order wastes minutes a live proceeding does not have. Cut the chain in half instead, test the midpoint, and discard the half that proves good. A typical capture chain runs source, microphone, cable, preamp or interface input, driver, software input, armed track, written file, with a parallel monitor return.

Worked example: channel 3 is silent in the recording. Look at the interface's own hardware input meter first, because it sits near the middle of the chain. If that meter moves when the witness speaks, everything from microphone through preamp is functioning and the fault lies in the software route, device selection, arm state, track mute, or file write. If the hardware meter is dead, the fault lies upstream in the microphone, its mute switch, battery, cable, or connector. One observation eliminates roughly half the candidates.

  • Midpoint observation What it eliminates
  • Interface meter moves, track silent Microphone and cable
  • Interface meter dead Software route and file path
  • File size still growing, headphones silent Capture itself; suspect the monitor path
  • Every track silent simultaneously Single-channel causes
  • Competence is an ethical duty

AAERT's Code of Professional Ethics expects members to understand the operation of their own software and hardware and to perform basic troubleshooting. That expectation sets both a floor and a ceiling. The floor: a reporter who cannot swap a cable, reselect an input device, or confirm that a file is still being written is not meeting a professional obligation. The ceiling: basic troubleshooting is not system administration, so credentialed configuration, court network changes, and installed-infrastructure repair belong to the designated technician.

Carry known-good spares

A small spare kit turns many faults into a thirty-second substitution: one tested balanced cable, an adapter set, a spare microphone of a type already in the setup, charged batteries, spare storage, and a fully independent backup recorder. A spare you have never actually recorded with is not known-good — test spares on the same schedule as primary equipment.