Areaka: Well, hey friends. Welcome back to another episode of Accreditation Made Easy. I am your host, Areaka Jewell. today I want to talk about one of the most challenging questions accreditation managers face. It's How to prove something that never happened, didn't occur. Now that probably sounds a little strange at first, but if you've been involved in accreditation for any length of time, you know exactly what I'm talking about. There are certain standards tied to events that simply don't happen very often. Things like escapes, searches, maybe delayed evidence submissions. How about when an extra duty employer is revoked? Removal of an unsafe firearm? How about corrective action related to bias policing? Now, depending on your agency, some of these events may occur once during the accreditation cycle, some may occur several times, and some may not occur all. when the assessment time comes around, how do you know? More importantly, how do you prove it? Now, over the years, I've seen agencies do a lot of different things. Some agencies send out emails to the people who are responsible, maybe some supervisors. ⁓ And they ask if any occurrences took place. Others supervisors or unit commanders to draft a memo ⁓ that there were no occurrences during the accreditation period. that approach works. probably one of the more traditional methods, personally. I use a slightly different approach. ⁓ For many of these standards, I have a review workflow attached to either the previous documentation for that standard or just a placeholder document. And when the workflow shows up, whoever is it, whoever it's assigned to, the responsible person, they provide either the updated documentation if the event occurred, or simply respond in the workflow that there were no occurrences. And then from there. Just create a simple note in the file documenting the result. I say something like, there were no strip searches during the accreditation period. What I like about that process is I have the documentation supporting that simple note. So if an assessor wants to verify, I have the workflow responses. I have the supporting documentation. And that's what's important. And if necessary, the assessor can always interview the person responsible. To me, That's a pretty clean process, right? Now, recently I was reminded of another really clever solution, and honestly, it's one I wish more accreditation managers knew about. Now, this idea came from Gary Robinson at the Palm Beach County Sheriff's Office. Now, if you're a large agency like Palm Beach County Sheriff's Office with dozens and dozens of supervisors spread across multiple districts or facilities, Individually tracking everyone down can become a challenge. And that's where PowerDMS surveys can be incredibly useful. Think about it. Instead of sending a bunch of emails waiting for responses, then trying to keep track of who responded, who didn't respond, where all the responses are located, you get the picture. Instead, create a survey. You send it to the appropriate people, and all the responses are compiled in one. Location. It's essentially a one-stop shop for collecting information. And what I really like about this approach is the efficiency. You're not digging through email folders six months later trying to remember who responded. You're not trying to piece together information from multiple sources. you need is already organized for you. Now, am I saying surveys are the only way to handle these standards? No, really. In fact, there are several good approaches. I've also worked in agencies where I was included on the daily supervisor reports, you know, the one that gets sent out at the end of the shift by the supervisor highlighting any significant events that occurred during the shift. And if I saw something that related to a standard, maybe it was a pursuit, an escape, maybe an officer-involved shooting, I would just take note of the case number. Then I would go into the RMS system, locate the report and begin gathering the documentation myself. Now that system worked too, which brings me to what I think is the most important point of this episode. The tool isn't what's important. The system is. I don't particularly care whether you use surveys, I don't particularly care whether you use workflows, don't even care if you use emails, memos, spreadsheets, What I care about is whether you have a process. Because when an assessor asks, how do you know there were no occurrences? You need a better answer than because I don't think there were any. The goal is to have a documented process that gives you the confidence in the answer that you provide. And just as importantly, it gives the assessor confidence in your answer. That's really what accreditation is all about, not assumptions. Not guesses, but verification. so if you have standards that are tied to infrequent events, take a look at your current process and ask yourself, how am I verifying this information? How am I documenting it? And if I had to explain it to an assessor tomorrow, would I feel confident doing so? If the answer is yes, great. If not, This might be a good opportunity to build a more consistent system. Now, as always, will include a companion document in today's show notes. I'll put a link for it. it'll screenshots of a real world DMS survey, thanks, Gary, used for this exact purpose. of course, if you're already signed up for my helpful Tips and resources inside PowerDMS. Be sure to check out the links in the show notes or head over to www.accreditationacademy.net forward slash sign up. Completely free, easy to do. You just your email address in, check which things you're interested in, and that's it. Now, if you found this episode helpful, please consider sharing it with another accreditation manager who could benefit from it as well. And until next time friends, let's keep making accreditation easy, one step at a time.