SOP Development
Every PHA asks for SOPs. Almost none can tell you where they are six months later.
PHA SOP Development
Every public housing authority (PHA) has been told it needs standard operating procedures (SOPs). So it asks for them. Someone writes them. They go into a binder or a SharePoint folder. Six months later, no one can find them. A year later, no one remembers they exist.
The problem is not the writing. It is everything that happens after.
Is This You?
You may need SOP work if:
- Your existing policy documents contain procedure language too vague for anyone to follow
- Staff turnover has left institutional knowledge in the heads of people who already left
- New leadership wants operations documented and standardized
- HUD has cited your agency for lacking documented procedures and you need them written to close the finding
- An RFP or corrective action plan calls for "SOPs" and no one is entirely sure what that means in practice
Start with What You Already Have
Most PHAs already have procedures. They just do not know it.
Model policy documents contain procedure language woven into the policy text: steps for processing applications, conducting inspections, calculating rent. Staff reference these documents regularly, especially program managers. But the procedure sections are thin, written in passive voice, light on examples, and indistinguishable from the policy around them.
The most practical path is to improve those procedures where they already live. That means identifying the procedure content already in your documents and marking it clearly as procedure, distinct from policy. Then strengthening it: specific steps, better examples, cross-references where one process depends on another. A 500-page document may become 700 pages. That is fine. No one reads it cover to cover. It is a reference, and better reference material means fewer errors.
For some agencies, procedures should be separated from policy entirely. The board governs policy. The executive director governs procedure. Updates happen without waiting for a board vote. The tradeoff: standalone procedure documents need their own home and their own maintenance cycle, or they disappear. That conversation deserves to happen before anyone starts writing.
Sometimes procedures need to be built from scratch: new programs, operational areas the models do not cover, or processes specific to your agency's structure and systems.
Getting the Scope Right
RFPs routinely ask for workflow assessments, gap analyses, process maps, and SOPs under a single line item called "SOP development." These are not the same thing.
- Standard operating procedures (SOPs). Step-by-step narrative documentation of how your agency performs a specific function. Written for the person doing the work. This is the core deliverable most PHAs need.
- Workflow assessment. An examination of how work moves through a process: who does what, in what order, where it stalls, where it breaks. This is a form of operational assessment with a narrower scope. It tells you what to fix before you document anything.
- Gap analysis. A comparison of current practice against regulatory requirements or internal policy. Identifies where the agency is exposed. Produces findings, not procedures. Often part of an operational assessment or a policy review.
- Process map. A visual diagram of a workflow: steps, decision points, handoffs, system touchpoints. Helpful for training and identifying inefficiencies. Not a substitute for written procedures, and rarely maintained after delivery because the tools used to create them (Visio, for example) are specialized, expensive, and not sitting on most PHA desktops.
When an RFP asks for all of these under one heading, the scope, timeline, and budget need to reflect that. A well-scoped RFP gets better proposals. A vague one gets creative interpretation, and you end up comparing bids that are not actually for the same work. If you are writing the RFP, this distinction matters. If you are reading this after it is already posted, so are the consultants bidding on it.
Our default format is narrative SOPs: clear, operational, written for the staff member at the desk. Playscript procedures, flowcharts, and other formats are also on the table. The format matters less than whether anyone uses it.
How We Scope
Every contractor bids to the specification. The clearer the spec, the closer the bids reflect what the agency actually needs. What you see in our proposal is what you get. Not every contractor makes that easy to verify.
A mid-size PHA could document hundreds of procedures across every program area. No one will maintain them. When a specification is broad, our approach is to start with the 20 to 25 procedures that matter most: the ones that drive compliance, that new staff need on day one, that break when someone quits. Intake. Eligibility. Recertifications. Interim actions. Inspections. Rent calculations. Move processing. The work that keeps the lights on.
Broader coverage can follow. But starting with everything is how SOP projects fail. Starting with what matters is how they last.
How We Work
The people who process the files, enter the data, and handle the calls know things management does not. SOPs written from a conference room do not match what happens at the desk. That is where the work starts.
A question most engagements skip: how will these documents be maintained after the contractor leaves? Who owns them? Where will they live? Does the team have the tools and formatting skills to keep them current? If those answers are unclear, that gets resolved before anyone starts writing, not after.
What You Get
Narrative SOPs in editable format, organized by program area, written to the scope of your requirements in operational language your staff can follow.
Depending on the engagement, deliverables may also include:
- A procedure inventory. What your agency has, what is missing, and what is buried in policy documents but not usable as written.
- Staff training on new procedures. An SOP no one has been walked through is an SOP no one follows.
- A maintenance framework. Who updates what, when, and how. Not a service contract. A plan your agency can execute internally.
Why ProjectLogic
We are a boutique firm. The person who interviews your staff is the same person who writes your procedures. No handoffs. No junior staff learning on your project.
We work exclusively with PHAs. No one here needs you to explain what an interim reexam is or how portability works. The programs, the regulations, the software your team fights with every day: that is the world we work in.
Most SOP projects produce documents nobody uses. Twenty-five procedures that survive are worth more than 200 that do not.