5.2 Speaker Changes, Abbreviations, Timestamps, and Annotation Priorities

Purpose of annotations

An annotation or log note is a time-linked entry that helps locate and understand a digital recording. Useful notes identify speakers, on/off-record transitions, witnesses, oaths, exhibits, objections and rulings when required, spellings, technical incidents, and other significant events. They help a transcriber navigate but do not repair missing or unintelligible audio.

The U.S. Courts guidance describes systems that tie log notes to the digital voice record and emphasizes that detailed notes plus constant attention affect transcript quality. The reporter must balance note entry with active monitoring; typing a perfect narrative while a track fails is poor prioritization.

Speaker changes

Create or select a consistent participant identifier as soon as identity is confirmed. Record the formal name and role in case information, then use approved short labels in live notes. A speaker-change note should mark the point at which the new person begins, not several sentences later. During rapid exchange, capture enough changes to reconstruct turns and add verified detail during an authorized pause if the system permits.

Do not guess. If an unseen remote voice speaks or several people overlap, request identification or clarification under protocol. Mark uncertainty transparently rather than assigning speech to the most likely person. When participants change seats or microphones, update the relationship between speaker, location, and channel.

Proper and improper abbreviations

An abbreviation is proper when it is standardized or defined, distinct from other labels, and understandable to the intended user. Examples might include approved role labels such as JDG, WIT, or INT, but local systems may prescribe different forms. A personal shorthand that another person cannot decode is improper for shared job information.

Avoid abbreviations that:

• collide, such as using P for plaintiff, prosecutor, and petitioner;
• resemble a different participant's initials;
• contain a legal conclusion rather than an observed event;
• change meaning across jobs without a legend; or
• sacrifice an essential spelling or exhibit number.

Maintain an approved legend when needed. Write out a term if compression creates ambiguity.

Timestamps

A timestamp links a note to a position in the recording. Systems may display elapsed time, file time, clock time, or media offsets. Know which basis is used and keep it consistent through pauses, file segments, and backup transitions. Synchronize system clocks according to policy before the job; do not change the clock casually during a live recording.

For a technical interruption, note the last verified capture, problem, action, and resumption point. If the backup uses a different clock or segment numbering, document the relationship. A timestamp is only useful when the referenced media and time basis are preserved.

Annotation priority

When events move quickly, use this practical hierarchy:

1. Record status and speaker identity — on/off record, new witness, unidentified voice.
2. Events essential to proceedings — oath, exhibit mark, sidebar, playback, recess, confidential segment.
3. Transcript-critical detail — names, spellings, numbers, citations, specialized terms.
4. Technical events — channel change, equipment fault, backup start, recovered capture.
5. Helpful navigation — topic changes or routine procedural markers.
6. Nonessential description — detail that does not aid an authorized record user.

The exact ordering may change under local procedures, but essential capture always outranks decorative detail.

Quality review

After the proceeding, compare notes with the job information and recording. Resolve spellings using authorized sources, flag unresolved uncertainty, verify exhibit sequences, and preserve the edit history required by the system. Do not rewrite logs to conceal a problem or insert an event that did not occur. An amended annotation can clarify; it must remain traceable when policy requires an audit trail.

Exam questions may offer a verbose note as the “most complete” answer. Prefer the note that is timely, accurate, unambiguous, and useful without distracting the reporter from audio.

Exam application

During rapid objections, the reporter can either write a paragraph summarizing the argument or mark speaker changes, objection, ruling, and timestamp. The second set is more useful and less likely to compromise monitoring. A later authorized review can add a verified spelling, but it cannot recover audio lost while the reporter composed prose. Practice converting events into concise, defined labels and maintaining a legend that a different transcriber could understand without asking what personal shorthand meant.

Essential versus nonessential, with examples

The blueprint asks candidates to identify essential and nonessential annotations separately, so learn them as two lists rather than one spectrum.

The dividing line is whether an authorized later user — a transcriber, a clerk, an appellate reader — needs the note to locate, interpret, or protect the audio. A note that records the reporter's impression fails that test and can itself become a discoverable statement of opinion, which the Code's prohibition on personal opinions makes a poor habit.

One federal content rule sharpens the same instinct: private communications and off-the-record conversations that are inadvertently recorded must not be included in a federal transcript. If such material is captured, note the boundary and the fact of the inadvertent capture, then escalate; do not annotate its substance.

Reconcile the time basis

Timestamp errors usually come from mixing bases. Suppose the primary recorder logs elapsed time from a 9:02 a.m. start and the backup writes wall-clock file times. An annotation reading 00:47:15 — Ex. 4 marked maps to 9:49:15 a.m. on the backup only if the start time is preserved and neither device drifted. Record the start wall-clock time, the elapsed-time origin, and the segment boundary for every file at the outset, and re-record them after any restart. Without that anchor, an accurate elapsed timestamp points nowhere on the surviving media.