The Five Questions US City and County Technology Leaders Should Ask a Technology Consultant Before Funding a Custom Permitting Platform

This article is part of our series on Custom Municipal Permitting and Code Enforcement Platform Development for US Cities and Counties: Building a Plan Review, Inspection, and Citizen Portal System

Introduction: Five Questions Before the Council Vote

Municipal technology projects can fail publicly. A permitting system that goes wrong gets noticed by contractors across the jurisdiction. Problems may reach local news or surface during council meetings.

That visibility makes early planning critical before funding begins. A capable municipal technology consultant can help shape custom software development decisions before scope, cost, and responsibilities are fixed. 

The failure patterns are often recognizable. Parcel authority was never settled, causing records to diverge over time. Accessibility was postponed, only for a compliance deadline to arrive anyway. Procurement rules made the intended engagement structure impossible midway through the project.

A strong web application development plan should also define ownership, maintenance, integrations, accessibility, and long-term operational responsibilities.

Nobody planned who would maintain the platform after the original champion moved on. The current review cycle was never properly measured. Without that baseline, nobody could clearly explain what the project would save.

Each issue represents a question with a knowable answer before any funding decision. This article presents five questions for any consultant or development partner. It explains what a strong answer sounds like and what a weak answer reveals.

Question One: Have You Settled Where Our Parcel and Address Authority Lives?

This comes first because getting it wrong produces a data problem that compounds silently for years. The authoritative parcel and address record almost always lives with the jurisdiction’s geographic information system team or the assessor. An address assignment process that the permitting department does not control governs it. The permitting platform should consume that record rather than create its own.

Ask a prospective partner where the authoritative data lives and what it publishes. Ask how the platform will consume it. Then ask the harder follow-up: what happens when a parcel splits or an address changes?

A permit issued years ago against a parcel that no longer exists in that form still has to be findable. It must trace back to the land it relates to. The answer tells you whether the partner has built for the local government before.

A good answer proposes meeting the GIS team early and designing a history that follows the land. A weak answer treats addresses as a text field. It might describe GIS as a map display rather than a data authority.

Question Two: What Is Our Accessibility Deadline, and Does Your Design Meet the Standard?

This question is most likely to separate partners who work in the public sector from those who do not. A federal rule now sets a technical standard for state and local government web content and mobile applications. 

In April 2026, the Department of Justice extended the compliance dates by one year. Larger entities now have until April 2027, while smaller entities have until April 2028. A permitting portal falls squarely within the rule regardless of the extension. 

Ask directly what your jurisdiction’s compliance date is and what standard applies. Ask how the partner’s design and testing process meets it. Then ask what evidence they will provide, including a current accessibility conformance report and named testers.

A good answer comes from a partner who already knew the rule. They can state the applicable date for a jurisdiction of your size. They treat accessibility as a build standard with named testing, not a late review. They also note that building it now costs far less than remediating toward a deadline.

A weak answer offers accessibility as a later phase, calls it a best practice, or hands it to a plugin. Confirm the specific dates and thresholds with your own attorney. They should not come from a vendor either.

Question Three: Can We Actually Procure This the Way You Are Proposing?

A private organization decides to build and start. A public agency has a procurement process that determines what is even possible. The mismatch between how software is best built and how the government buys it is a real constraint.

Ask a prospective partner how their proposed engagement fits your procurement rules. Iterative development with evolving scope is difficult to specify inside a fixed solicitation. A partner who has worked in this sector will have views on structuring it well.

That might mean phased awards, task orders, or a cooperative purchasing arrangement your jurisdiction already uses. Ask specifically about cooperative agreements, since many jurisdictions can purchase through contracts that other governments have already competitively procured.  That path shortens the calendar substantially, and it gets overlooked often.

Ask also what happens if the solicitation produces a different scope than discovery recommended. A good answer comes from a partner who asks about your procurement rules first. A weak answer presents a commercial engagement model with no reference to how you buy.

Question Four: Who Maintains This Across Administrations?

This question exists because public agencies face a discontinuity that commercial organizations mostly do not. Leadership changes during an electoral cycle. A project championed by one administration can lose its sponsor before it finishes.

A custom platform is a permanent obligation. It needs maintenance, security patching, accessibility retesting, and regulatory updates. Custom mobile app development for the inspector-facing side adds device and OS update obligations of its own. That holds for as long as the jurisdiction uses it, likely a decade or more for a permitting system.

Ask who maintains the platform in year four. Is it an internal team, a retained arrangement with the partner, or simply unresolved? What does that cost annually, and does it sit in the operating budget?

Then ask about the exit. If the jurisdiction parts ways with the partner, do the code, documentation, and data transfer cleanly? A good answer raises maintenance and continuity before being asked, proposed as a budgeted arrangement. A weak answer states a build cost with maintenance mentioned only as a percentage.

Question Five: What Does Our Current Review Cycle Actually Cost?

Most jurisdictions cannot answer this question. That is why most permitting business cases rest on staff frustration rather than on numbers. The measurable pieces exist and are worth gathering before any scoping conversation begins.

How many correction cycles does a typical building permit go through, and how long is each? What proportion of applications are returned incomplete at intake? How many status calls does the department field, and what does answering them cost in staff time? How long passes between an inspection request and the inspection itself?

Those numbers make the case in a form a council understands. They also point out what the project should fix first, which is frequently not what the department assumed. Review cycle time connects to community outcomes too, since it shapes how long housing and small business projects take.

Ask a prospective partner how they would establish that baseline before scoping anything. A good answer proposes measuring the current state from existing system data and direct observation. A weak answer arrives with a feature list and no baseline at all.

What a Good Partner Sounds Like, and the Red Flags to Watch

A capable partner does specific things before quoting anything. They meet the GIS team, sit at the permit counter for a morning, and ride along on inspections. They ask to see the last twelve months of cycle time data. They also ask about your procurement rules and your accessibility conformance date.

Several signals should raise concern. A fixed price offered before any discovery work is one. Parcel data treated as a map display rather than a governed record is another. Accessibility offered as a phase two, silence on procurement, and unaddressed maintenance all belong on this list too.

A few signals should end the conversation entirely. Any proposal to automate code enforcement through to citation, abatement, or lien without human review belongs here. So does AI-driven violation detection or enforcement targeting. A suggestion that records can be deleted outside the retention schedule also belongs here.

The strongest positive signal is simple. A partner who asks which departments sit in the review path before discussing features is usually the right one.

Turning Five Questions Into a Defensible Decision

Technology leaders who put these five questions to a partner before funding anything end up in one of two places. They commission a project that a council can support. Or they establish that an existing platform through a cooperative agreement serves the jurisdiction better. Both outcomes hold up under public scrutiny, the standard that matters most in this sector.

If you are weighing a custom permitting platform against the systems you run today, a structured assessment changes the conversation. Parcel authority, accessibility position, procurement path, and a measured cycle time baseline turn a council decision into an evidence-based one. NewAgeSysIT works with city and county teams to run that assessment and scope a permitting platform built on evidence. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.