Policy and SOP Writing

Policies that match what people do, and procedures people can follow.

Already have an IT provider? Here's how we work together.

A school district office

The binder nobody opened

The challenge. A district has a thick information security binder from a template. A new teacher asks whether she may use a free classroom app that wants students’ names, and nobody can say which page answers that. The technology director spends a week finding out.

The insight. A policy that does not match practice is ignored, and a procedure that takes a week to find is no procedure. Useful policies are short, say who decides, and come with a one-page procedure for the question people actually ask.

The decision. The district replaced the binder with a small set of short policies and a one-page procedure for the ten situations that come up most.

The action. We interviewed the technology director, a principal and a teacher, and wrote policies from what they described: who approves a new app, what student data may leave the district, how an incident is reported. We added a request form and a decision record. The board approved the policies and the staff were walked through the procedures in a short session.

The result. The teacher’s question now has a two-day answer and a record. The district can show its policies to a parent, an auditor or a board member, and each has a yearly review date.

What Security Medic does

Policy sets

Security, privacy, acceptable use, access, backup, incident response, vendor management and AI use, written in plain language.

Standard operating procedures

One-page procedures for the situations people face: onboarding, leaving, a lost device, a new vendor, a suspicious email.

Approval and ownership

Each document has an owner, an approver and a review date, so leadership can show it was adopted.

Policies mapped to rules

A table showing which rule or contract each policy helps meet, for auditors, insurers and customers.

Where this sits in the cycle

Every client goes through the same six steps, from a town office to a family at home. The Security Medic method

  1. 1. Govern
  2. 2. Design
  3. 3. Assess
  4. 4. Review
  5. 5. Conform
  6. 6. Improve
  • Govern. Policies are how leadership’s decisions are written down.
  • Design. Procedures turn the design into steps people can follow.
  • Assess. We check whether practice matches the document.
  • Conform. Staff and the IT provider follow the procedures; we check the records.
  • Improve. A yearly review updates each document and retires what is unused.

The standards we draw on

The Govern function of the NIST Cybersecurity Framework 2.0, NIST SP 800-53 policy and procedure controls, the NIST Privacy Framework and AI Risk Management Framework, and the rules that require written policies, such as HIPAA, NYDFS Part 500, the FTC Safeguards Rule and New York Education Law § 2-d.

Audit preparation →Training and coaching →Quality control →

Getting ahead of it

Rules about AI and privacy are arriving in many places at once. A policy set with one short AI-use policy now is easier to extend than one written after the first complaint.

Start with a free 30-minute call

Tell us which policies you have and which questions keep coming up. We will talk through where to start.

Book a free 30-minute call