Recent content by johnreynolds

We have customers who track alarm permits. They keep a separate list of "unregistered alarms", and when an incident happens, they add them to this list and send letters requiring the business or homeowner to register their alarm. It's pretty common to see a structure very similar to what @Eric...

Well, in terms of working with the cashiering system, what we've found the priority is tracking the right distribution codes when payments come in (like, being able to separate building permit fees from plan review fees, etc). Usually that satisfies most finance departments. This can usually be...

I run civicreview.com but it really depends on what the priorities are. Each software has different angles. Some are more GIS-centric, other are tied in closely with accounting systems (like Tyler), others prioritize customer experience, etc. I'll be happy to share what I know about the...

My two cents: Lock down the plan review cycle and make sure it's going through a single touch-point. For example, designate somebody (a permit tech) to serve as the gatekeeper for all new submission and feedback. It may feel faster to have, say, the engineer immediately send redlines back even...

I'm the founder of a permitting software company and have helped a lot of municipalities transition (even a lot moving away from Caselle). Here's what we've learned works best: Take the opportunity to re-assess what you REALLY need to be asking for in your application forms. I've found a lot of...