How the Peoria Police Department runs policy review, accreditation and command reporting on a portal built in Zite.

Peoria PD tracked its policy revisions in Microsoft Teams. Policies lived in folders. Assignments got passed around in messages. There was no single place to see who owed what.
A policy could sit in a review phase for weeks because the reviewer never realized it was theirs. Nobody could say where a policy was stuck, or for how long. Finding a current policy meant digging through nested folders, so people stopped wanting to.
“People just hated trying to find policies. If you’ve worked in Teams, you know how it is, this folder, then that folder. It was a mess. So people were getting upset about it.”
Jeana Johnson was handed the problem and told to find a policy management system. She started getting quotes.
“I was getting quoted about 15 to 20,000 to have a basic policy management system. And it wouldn’t even be customizable to our workflows!”
Instead of buying, Jeana built. A peer had mentioned building their own site on Zite, so she started experimenting. She got far enough, fast enough, that the department told her to keep going.
“Once we saw the initial results, our agency was like: yes, absolutely, let’s do this.”
Peoria PD now runs two portals off a shared database. The Policy Management Portal is live and in daily use across the department. An Accreditation Management Portal is close behind, solving the same visibility problem for accreditation proofs, where people used to drop files in a folder with no record of who owned what. A training portal is under consideration.
The dashboard shows what is assigned to you and what is late. Staff filter by title, due date, phase, status or assigned user, or switch to “assigned to me.” Overdue work sorts to the top. Each policy card shows its phase, its due date and how far the review has actually gotten, such as six of eight reviewers done, 75 percent through the phase.
Jeana kept adding the things a real review process needs:
When you build your own software, users notice every time it changes.
“I go and do something, and then the users are like, why is this suddenly different? And then they freak out, and then it’s a headache.”
So she built a What's New page. Zite drafts release notes from recent changes on demand. Jeana reviews them, edits what she wants and publishes. The note pops up for users the next time they log in, and they acknowledge it. Next to it sits a bug and feature request form that feeds an internal tracker, so suggestions from the department get logged the same way hers do.

Notifications got the most attention, because a system that emails the wrong people is one staff will tune out. Every notification type carries one of four designations: Required, Optional, Off by Default or Disabled. Send timing is set per type, either on the event, a set number of days before or after the due date, or on a repeat.
Admins keep their own preferences separate from the department defaults, since the assistant chief does not need the same inbox as the policy manager. Users can also set personal reminders. A commander who has delegated a policy can subscribe to a recurring nudge to check that it is still moving.
Overdue alerts only go to people who still owe something.
“If somebody already did it, I don’t want them getting an email telling them it’s overdue, because then they think they have to do something. I only want it to go to the people who actually need to take action.”
New users get a welcome email when their account is created, with a link to a training video. That matters when a brand new system is going out to a whole department.


Three kinds of reporting come out of the portal, and each one replaced something manual or something that did not exist.
“I sat down with my commander and we literally went through it with pen and paper. We want this, we don’t want this, change this. Then I went in and made those tweaks, piece by piece.”
The $15,000 to $20,000 the department did not spend is the easy headline. It is not the first thing Jeana mentions.
“It’s kind of a twofold benefit. Cost was a big benefit. But realistically, once we actually got into the system and started building it, it was the fact that we have control of it.”
Off-the-shelf software would not have had phase locking that matched Peoria's workflow, or fail-to-review logging, or a strategic plan dashboard shaped by a commander over an afternoon with a notepad. And it would not have changed when the department needed it to.
“Honestly, the customization has been the biggest thing. I say I want it to do this, and we can make it happen.”
See how agencies run policy, accreditation and training on Zite, with SSO, permissions and audit logs.
Talk to our team