PATENT PENDING

Entity-Aware Compliance Engine

Select your entity type. Every applicable statute, deadline, and approval requirement activates automatically. This is the core technology that makes TownWorks fundamentally different.

The technology behind automatic compliance

Traditional municipal software treats compliance as an afterthought: a checklist, a reminder, or a report you run after the fact. TownWorks takes a fundamentally different approach. Compliance is not a feature of TownWorks. It is the architecture.

The Entity-Aware Compliance Engine is the core technology that makes this possible. When a municipality tells TownWorks what it is (a township under IC 36-6, a town under IC 36-5, a reorganized town under IC 36-1.5, or a city under IC 36-4), the engine automatically identifies every Indiana Code provision that applies to that entity type and activates the corresponding compliance infrastructure.

This is not a configuration wizard. It is a statutory mapping system that encodes Indiana law as structured data. Each entity type has a defined set of applicable statutes, and each statute has a defined set of requirements that translate into blocking validators, deadline rules, workflow steps, and audit points within the platform.

The result: a township trustee cannot approve a claim that exceeds an appropriation. A board member cannot finalize a meeting without satisfying the 48-hour notice requirement. A records custodian cannot close an APRA request without a documented response. Compliance is not optional. It is built into the software.

How entity detection works

1 Entity Classification

During onboarding, the municipality selects its entity type. TownWorks maps this selection to the corresponding Indiana Code classification (IC 36-6, IC 36-5, IC 36-1.5, or IC 36-4) and loads the complete statutory profile for that entity type.

2 Statutory Provision Loading

The engine loads every applicable Indiana Code provision for the selected entity type. A township activates IC 12-20 (township assistance), IC 5-14-1.5 (Open Door), IC 5-14-3 (APRA), IC 5-11 (SBOA), and more. A town or city activates planning/zoning provisions, code enforcement authority, and additional fiscal statutes.

3 Blocking Validator Activation

For each loaded statute, the engine activates the corresponding blocking validators. These are hard stops in the workflow that prevent actions that would violate the statute. A blocking validator cannot be overridden by staff. It can only be satisfied by meeting the statutory requirement.

4 Deadline and Workflow Configuration

Statutory deadlines (72-hour investigation windows, 48-hour notice requirements, 7-day response timelines) are automatically configured as enforced rules within the workflow engine. Every deadline tracked. Every escalation automated.

Supported entity types

Township

IC 36-6

Full township assistance, finance, meetings, APRA, and cemetery management with SEA 270 readiness.

Town

IC 36-5

Town council governance, planning/zoning, code enforcement, finance, and all universal compliance engines.

Reorganized Town

IC 36-1.5

Combined township and town functions with the full statutory profile of both entity types activated simultaneously.

Class 2 & 3 City

IC 36-4

Full municipal authority with planning commission, BZA, code enforcement, comprehensive finance, and all compliance engines.

Blocking Validators

Compliance you cannot accidentally bypass

Blocking validators are hard stops in the workflow that enforce statutory requirements. They are not warnings, notifications, or suggestions. They are structural barriers that prevent non-compliant actions from completing.

Appropriation Guard

Prevents approval of any claim that would exceed the available appropriation for the fund. Cannot be overridden.

48-Hour Notice Guard

Prevents finalization of any meeting that has not satisfied the Open Door Law notice requirement.

72-Hour Investigation Guard

Prevents closing a township assistance application without documented investigation within the statutory timeline.

APRA Response Guard

Prevents closing a public records request without a documented response within the required timeline.

Budget Adoption Guard

Prevents operation under budget continuation when the budget calendar deadline has passed without adoption.

Findings Requirement Guard

Prevents BZA decisions from being finalized without the required findings of fact for the applicable action type.

Related resources

Technical documentation and compliance architecture guides will be available in our resources section.

See the compliance engine in action

Request a personalized demo to see how TownWorks configures itself for your exact entity type and activates every applicable statute.

Patent Pending: Entity-aware statutory detection, blocking validators, and visual compliance engine

Legal Disclaimer: TownWorks, Inc. is a technology company, not a law firm. The information on this page is for informational purposes only and does not constitute legal advice. Municipalities should consult with qualified legal counsel regarding specific legal questions.