What a Monthly fDoS Walk-Through Actually Does for You

The walkthrough that never gets canceled.

Every organization we work with has a calendar full of important meetings that could be rescheduled if something urgent came up. The monthly fDoS walkthrough is not one of them.

That is the first lesson of the model. When something is on the calendar every month, executed by someone outside the organization, with a written memo that goes to leadership, it does not get postponed into oblivion. It gets done. Month after month. And over a year, that consistency changes the culture of a security program more than any single intervention.

What happens on a visit.

A typical monthly walkthrough, for a church, daycare, senior living facility, or nonprofit in Southwest Florida, follows a structured rhythm.

The opening conversation

Every visit starts with a brief check-in with the primary point of contact. This is not a formal meeting. It is a ten-minute conversation over coffee that covers:

• Anything new since last visit (staff changes, facility changes, events, incidents)
• Status of open items from the prior memo
• Any concerns the point of contact wants us to pay attention to this visit
• Any upcoming events or changes that will affect the next month’s work

The conversation ensures the walkthrough is oriented to the real operational reality of the organization, not a checklist applied in a vacuum.

The physical walkthrough

The physical walkthrough rotates through the facility over time. Not every corner is covered every month. Over a quarter, every part of the facility is seen. Over a year, every corner is seen multiple times, in different conditions (different weather, different staffing, different times of day).

Standard coverage each visit:

• All primary entries, checked for closure, lock function, and use patterns
• A rotating subset of secondary entries (service doors, annex entries)
• Current lighting state, exterior and interior
• Camera positions and live views for a sample of installed cameras
• Access control status (keypad, fob, badge systems as applicable)
• Visitor and check-in areas during an active period
• Any specific zone flagged by the prior visit's memo for re-check

The observational time

A portion of every visit is spent not checking anything in particular, but simply watching the facility operate. Which staff are on shift. How the lobby flows. Where volunteers gather. Which doors are actually used.

Observational time is how drift gets spotted. A policy that says “visitors are escorted” is either visible during observation or it is not. A protocol that says “children are signed out at the designated desk” either happens or it doesn’t. Walking through the space with a checklist finds the checklist items. Watching the space operate finds the things that are not on any checklist.

The staff conversations

Where the schedule allows, every monthly visit includes brief conversations with staff and volunteers who happen to be present. Not formal interviews. Just natural check-ins.

“How’s everything going? Anything new? Anything you want me to know about?”

The questions are simple. The information is often valuable. People who know the advisor will be around monthly develop the habit of saving observations for those visits, and that habit is one of the compounding returns of the model.

The findings memo

Within 48 hours of every visit, a written memo goes to the primary point of contact. The memo is short, rarely more than two pages, structured consistently:

• Summary of what was reviewed
• New findings, if any, with recommended action
• Status of prior open items
• Anything flagged for special attention next visit
• Recommended focus for the next monthly visit

The memo is the artifact that travels through the organization. Leadership can read it quickly. Safety teams can act on it. Over a year, the stack of memos tells the story of the program’s evolution in a way no single audit report can.

What changes between visits.

Organizations shift constantly, even when leadership believes they are stable. The monthly walkthrough is where those shifts become visible.

Common between-visit changes we surface:

• A new volunteer has been given keys without going through the standard vetting process
• A camera has been moved, bumped, or blocked by a new piece of furniture
• A new program has been added to the facility without a security review
• A vendor has been to the facility and was granted access without the usual protocol
• A previously-followed procedure has been informally dropped because the staff member who drove it is no longer present
• A new piece of equipment or signage has changed a sight line

None of these changes are catastrophic in isolation. Over time, unreviewed, they compound into material drift. The walkthrough catches them while they are small.

The Hurricane Ian lesson, specifically applied.

Organizations on fDoS engagements before Hurricane Ian in 2022 had several advantages when the storm hit. Their emergency plans had been reviewed recently. Their vendor contact lists were current. Their staff had rehearsed scenarios, including severe weather, within the year. The monthly cadence meant that when the storm arrived, the preparation was not hypothetical.

We have a piece on the specific ways Hurricane Ian stress-tested Southwest Florida facilities if you want the full picture. The short version: rhythm mattered more than any single preparation.

The verse is an argument for doing what is in front of you with attention and commitment. The monthly walkthrough is that argument turned into a security program. Attention, paid consistently, with the discipline that comes from having it on the calendar every month.

The cost of skipping a month.

The fDoS discipline is monthly. Organizations sometimes ask if they can run it quarterly to save cost. The answer is almost always that quarterly is measurably worse, not proportionally worse.

The reason is that quarterly visits miss the shift windows. Staff changes, volunteer turnover, and facility drift happen on rhythms shorter than a quarter. A quarterly visit catches accumulated drift, often in a volume that is demoralizing. A monthly visit catches drift as it happens, when corrections are small and easy.

Monthly is the minimum cadence at which the rhythm produces the compounding effect that makes the model work.

What the year produces.

At the end of a first year in an fDoS engagement, an organization typically has:

• Twelve monthly memos documenting the specific path of the program
• Four quarterly policy reviews, rotating through the full policy set
• Four quarterly tabletop exercises across a range of scenarios
• One full annual audit with year-over-year comparison
• Measurably fewer open findings than at the start
• Significantly better staff awareness and engagement with security
• Current, tested relationships with vendors and first responders
• A written record that demonstrates, to boards and donors, that the organization takes stewardship seriously

That record is not theoretical. It is visible in the stack of memos on the leader’s desk. It is visible in the staff who bring observations to the monthly visit. It is visible in the tabletop exercise minutes, the vendor contract reviews, the access credential audits that now happen on schedule.

The monthly visit is the compound interest.

If you take one idea from this article, let it be this. A security program is built not by a single audit, no matter how thorough, but by a consistent rhythm that never lets the program drift too far before it is corrected. The monthly walkthrough is the simplest, most reliable mechanism for establishing that rhythm.

If your organization in Fort Myers, Cape Coral, Naples, or Port Charlotte has had a single audit and is wondering what comes next, the monthly walkthrough is often the answer. We would be glad to have the conversation about whether the rhythm fits your organization.