top of page

630-413-9511

The Data Behind The Compliance Engine

  • Writer: BRYCER
    BRYCER
  • Jun 25
  • 6 min read

BRYCER LEADERSHIP SERIES

A Conversation with Josh Holsclaw, Head of Data Operations

 

 

Josh Holsclaw is the Head of Data Operations at BRYCER - and one of the longest-tenured members of the team. He makes sure that every piece of data that either comes in or out of The Compliance Engine is correct - reports, notices, the AHJ information itself, premises, contacts, deficiencies. He joined when there were five people in a two-office suite, answered support calls forwarded to his cell phone at 2 a.m., and helped build the data infrastructure that now supports thousands of Authorities Having Jurisdiction (AHJs) across the United States. Today, he leads the teams responsible for making sure every piece of data that moves through The Compliance Engine is accurate, complete, and actionable.


Data Operations at BRYCER is not a back-office function. It is the layer that determines whether the information an AHJ sees in The Compliance Engine is something they can act on. Inaccurate data does not just slow down a department - it creates gaps in a community's compliance picture. The conversation below covers what that work looks like day to day, how his teams support fire departments behind the scenes, and where The Compliance Engine is headed as BRYCER scales into 2026 and beyond.

 

On the Work at BRYCER

Most people who interact with The Compliance Engine see the reports, the dashboards, the notices. What they do not see is the data quality management work that makes all of it reliable. That is Josh's domain.


What is unique about working at BRYCER?


Josh Holsclaw: Every day there are different events going on. The amount of opportunity and growth potential is insane.

That range - no two days the same - reflects the nature of compliance data itself. Every new AHJ brings a different data structure, different building records, different edge cases.


What is something most people do not realize about fire and life safety compliance until they are working in the industry?


Josh Holsclaw: Most people do not realize how many deficiencies just go unchecked. You could look up restaurants near you and not realize how many open deficiencies they have. On the elevator side, half of elevators have issues you may never notice when you enter a building. You would never know if a fire alarm is not working. If there is a fire, you might never know.


That visibility gap is exactly what The Compliance Engine is built to close. Fire inspection reporting software exists to collect that data - but fire compliance software and fire department inspection software have to do more than store records. They have to surface the right information so deficiencies get resolved before they become safety failures.


Can you share a moment when your work felt especially meaningful?


Josh Holsclaw: Being able to shape what The Compliance Engine has become - being part of the development side for the call center, for multiple notices, inventory, premise users... none of that was there when I started. Being able to work on it and create what it would actually provide and be helpful to people, that is what stands out to me.


Each new feature was not planned from day one. It was built because a fire department needed it and BRYCER's team was close enough to the work to see it.

 


"Being able to work on [The Compliance Engine] - that is what stands out to me."



On the AHJs that partner with BRYCER

Every AHJ that comes onto The Compliance Engine brings its own data structure, its own building records, and its own history. Josh's teams are the reason that complexity becomes a clean, reliable foundation for fire safety compliance software - from day one.


What does a typical day look like for your teams?


Josh Holsclaw: The AHJ Configuration team sets up each department - gathering information, adding what systems they want to track, pricing documents, and so on. Once the department is created, the Data Quality team cleans the data and loads the buildings into the database. From there, they handle held for review and pending premises - reviewing contractor-created buildings for AHJs and either accepting them or sending them back.


Configuration gets the department built correctly. Data Quality makes sure the records inside it are accurate and complete. Both have to work before a fire department can start using The Compliance Engine with confidence.


How do your departments help AHJs with their day-to-day operations, and how do you make sure TCE runs smoothly while setting the tone for precision every day?


Josh Holsclaw: The AHJ Configuration team handles all tickets, answers questions, and provides technical support for each department. Every AHJ has its own special use cases - we keep detailed notes and CRM records to make sure nothing gets missed. On the data side, we monitor core systems daily and can identify issues quickly when something shifts. For quality control, every data load goes through multiple review steps - one person cleans it, another peer reviews it, it gets loaded, then a final check before approval. There is a lot of accountability built into that process.


The data quality assessment process Josh's teams run for each new jurisdiction - combined with the operational rigor that keeps inspection compliance software outputs dependable - is what makes that complexity manageable at scale. Professionalism in data operations is not a value statement - it is a process.

 

 

On What's Next at BRYCER

BRYCER is expanding rapidly into 2026 - new features, new markets, and new AHJs coming onto the platform. Josh is thinking carefully about what that means for Data Operations.


What is your vision for The Compliance Engine moving forward - and are there markets you are especially focused on?


Josh Holsclaw: A major city on the East Coast. It is one of the last major ones - Los Angeles, Chicago, and this market are the top three. Getting all of them would be significant. Large markets take time because the process is thorough, but that is also what makes landing them meaningful.


The path to markets like this requires persistent relationship-building, patience with institutional processes, and a platform that can handle the complexity those jurisdictions bring.


As BRYCER releases new features in 2026, how do you make sure data quality keeps pace with expansion?


Josh Holsclaw: Some of the AI developments affect my teams - particularly around Report Review and held for review processes. Most of it is going to help make things faster and allow us to support more AHJs. The quality standard does not change. What changes is our capacity to maintain it at a greater scale.


Quality stays constant, capacity grows - that is the right framing for what AI can do inside fire compliance software. It is not replacing the judgment of Josh's team. It is handling more volume so that judgment can be applied where it matters most.


What are you most proud of from your team, and what do you think can still be improved?


Josh Holsclaw: The best thing is the quality the team provides - making sure every building actually falls under the right jurisdiction. We help better a department's database because of the knowledge we have built over time. For improvement, there is real potential for AI with held for review and Report Review. That is where we can get meaningfully faster without sacrificing accuracy.


The Data Quality team's institutional knowledge is one of BRYCER's most durable advantages. As AI assists with the more structured parts of that work, human expertise gets applied to the problems that require it most.

 

 

Closing Reflection

Josh's perspective reflects something that does not always get talked about in compliance technology: data quality management is as important as the platform itself. The Compliance Engine works for fire departments because Josh's teams make sure the information inside it is accurate, complete, and ready to act on. That standard - built over 15 years, across thousands of jurisdictions - is what makes BRYCER's growth possible without compromising the quality that AHJs depend on.

 

To learn more about The Compliance Engine, visit thecomplianceengine.com.

 

About The Compliance Engine

The Compliance Engine is BRYCER's industry-leading compliance management platform that streamlines inspection reporting and regulatory enforcement for fire, life safety, and mechanical systems. By connecting service providers, property owners, and Authorities Having Jurisdiction through one centralized platform, TCE improves reporting accuracy, accountability, and operational efficiency.

 

Media Contact

Paige Robson

Head of Marketing

2300 Cabot Drive, Suite 250, Lisle, Illinois 60532





Comments


BRYCER_flame_white_transparent (2).png

info@mybrycer.com

630-413-9511

 

Warrenville, IL Office
4355 Weaver Parkway, Suite 230
Warrenville, Illinois 60555

Lisle, IL Office

2300 Cabot Drive, Suite 250

Lisle, Illinois 60532

  • LinkedIn
  • Instagram
  • Facebook
BRYCER_logo_transparent.png

Our mission is to deliver proactive services and technology to ensure jurisdictional compliance with inspection, testing, and maintenance laws. Our solutions are developed to be economical, efficient, flexible, and scalable to meet the needs of code officials, inspection companies, and consumers worldwide. We strive to create a safer environment for all.

Vision: Make Your Community Safe

Values: Integrity, Professionalism, Innovation, Teamwork

bottom of page