Stop 1 of 8 · Read once
The hard line
What never enters a chat in a police department, and the division Project that holds everything that may.
Twenty years in, and half the job is paper
Lieutenant Reyes commands a patrol division. Four teams on rotating shifts, a policy manual that has to track state law, a training calendar, a budget request, a federal grant due in March and a council meeting every month. None of that is police work. All of it is Reyes's work, and this course is about that half of the job and only that half.
The line
No case details. No evidence. No criminal justice information. No personnel records. Not in a chat, not in a Project, not in an upload, not paraphrased, not photographed, not one paragraph of a report pasted in to see whether the writing can be tightened.
That is the boundary every stop after this one stays inside. Reyes is not writing reports here. Reyes is writing the policy that says how reports are written, the bulletin that trains people to write them, the schedule that decides who is on shift, and the presentation that explains a quarter to council.
| Goes into a chat | Stays in the records system |
|---|---|
| Policy text, statutes, model policies, curricula | Reports, narratives, evidence, CAD and case numbers |
| Shift patterns, post counts, hours and overtime by code | Officer names, badge numbers, anything identifying |
| Budget categories, grant criteria, agendas, published statistics | Personnel files, complaints, internal affairs, medical records |
Two things sit under that table. Criminal justice information is governed by rules that have nothing to do with how private a chat window feels, and whether any outside system may touch it is answered by the chief and legal counsel before anyone types. And legal sufficiency is never Claude's call and never Reyes's. Claude drafts and marks what turns on law. Counsel decides.
The division Project
One Project holds the administrative side of the division: policy sections, the state model policy, the training calendar, budget categories, the writing standard. No personnel data, nothing from the records system. Because of that, Reyes works in it at speed without re-deciding the question every time.
You help a patrol division lieutenant with administrative work only: policy drafting, training material, scheduling analysis, budget and grant writing, community messaging and command presentations. Rules that never change: 1. Never ask me for case details, report content, evidence, criminal justice information, or anything from a personnel or internal affairs file. If my message contains any of it, stop and tell me to take it out before you answer. 2. Refer to people by role or code, such as Officer A or Team 3. Never use a name or a badge number, even if I use one. 3. You do not decide legal sufficiency. When a draft turns on a statute, a court decision or liability, mark the line and say it goes to legal counsel. 4. Write so a new officer and a council member both follow it. Short sentences, active voice, no jargon that is not in our manual. 5. Use our manual's numbering and formatting for policy drafts. When you do not know what our manual says, ask instead of inventing. 6. End every draft with the facts you assumed, so I can check them.
Write me a one page checklist for a police administrative office to run over any document before it goes into a chat. List the categories that must come out, the fields that carry an identifier by accident such as headers, footers, file names, tracked changes and document properties, and what to put in place of each one. Give it to me as a printable list, not prose.
Here are the administrative tasks I do in a month: [paste your list]. Sort them into three groups: work you can draft from material carrying no case, personnel or criminal justice content; work you can help with only after I remove something, with the thing named; and work that should not come near you at all.