Objective. Students will enter a complete incident report into a simulated digital records management system, attach a supplemental document, and demonstrate correct data fields, version history, and access-control awareness without instructor prompting.
This lesson, its worked examples and its practice questions has not yet been verified by a licensed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Paper reports have been the backbone of corrections record-keeping for generations, but most modern facilities now use a Records Management System (RMS) — software that stores, organizes, and controls access to incident reports, use-of-force records, grievances, and other official documents. Entering data accurately into an RMS is not a clerical task; it is a legal act. A digital record can be subpoenaed, audited by a state oversight body, reviewed during an ACA accreditation visit, or presented in court. Errors you make at the keyboard carry the same consequences as errors on paper — and sometimes worse, because digital systems log exactly when you typed, what you changed, and whether you submitted the record on time.
Every RMS platform is different, but the core structure is similar across systems. When you log in, you authenticate with a unique username and password tied to your officer ID. That credential is the digital equivalent of your signature — never share it. Once inside, you will find a form with required and optional fields. Required fields are usually marked with an asterisk or highlighted in red; the system will not allow submission until every required field is filled.
Common required fields in a use-of-force entry include:
Many incidents require supplemental documents: a diagram of the scene, medical observations, witness statements, or your handwritten field notes. Attach files through the system's upload function and confirm the attachment is visible and correctly labeled before submitting. An attachment icon that shows a broken file or zero bytes means the upload failed. Name your file clearly — for example, Smith_J_UseOfForce_04262025_FieldNotes.pdf — so a supervisor or investigator can identify it without opening every attachment in the folder.
Scan paper documents at a resolution that makes handwritten text legible. A blurry or sideways scan is effectively useless in a legal review.
One of the most important features of an RMS is the version history — a log that records every time a record was opened, edited, or saved, along with the timestamp and the user ID of the person who made the change. This audit trail exists to protect everyone: the inmate, the officer, and the facility. If a record is altered after submission, the system captures it. Supervisors and investigators can see the original version and every subsequent change.
Best practice: get your entry right before you submit. If you discover a factual error after submission, notify your supervisor immediately and correct through the system's official amendment process — never delete and re-enter without authorization, and never attempt to alter a submitted record without proper documentation of why the change was made.
Not every staff member can see every record. RMS platforms use role-based access control: your login grants you access only to the records and functions your job role requires. Incident reports may be visible to officers, supervisors, investigators, and administrators — but not to inmates, the general public, or staff in unrelated units. Be aware of who can see what you enter. Do not include information in a digital record that should not be there, such as an informant's identity in a general incident report that many staff can read.
Log out of the system every time you leave a workstation, even briefly. An unattended logged-in session is a security and confidentiality violation. This is the digital equivalent of leaving a paper file open on a public counter.
Five errors appear repeatedly in digital corrections records, and each carries real operational or legal risk:
1. Wrong inmate ID format — creates a misfiled record; the incident may never be associated with the correct inmate during a disciplinary hearing.
2. Date or time in wrong format — can invalidate a record during a legal challenge if it appears the timeline was altered.
3. Narrative left partially blank — gaps in the narrative suggest the officer did not complete the report, undermining credibility in grievance hearings or litigation.
4. Attachment missing — supporting evidence is lost; the case may proceed without key documentation.
5. Submission status not updated — the record exists only as a draft; supervisors cannot review or approve it, and reporting deadlines may be missed, violating policy and possibly state law.
Digital documentation does not involve the same physical hazards as other corrections tasks, but two professional-safety points are critical. First, protect your login credentials as you would your keys — a compromised password can allow unauthorized record changes that are traced back to you. Second, accuracy protects you personally: a well-documented, properly submitted digital record is your best defense against a false allegation. Take the same care with every field that you would take drafting the paper report.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.