Configuration Engine
Platform Capability
Configuration Engine
Rules, forms, and workflows live in configuration -- not in code. Regulatory changes become configuration updates, not software projects.
The Operating Problem
Most regulatory technology platforms require a software development project every time a regulation changes. A new license type, a new evidence requirement, a new fee schedule -- each one becomes a ticket in a vendor's backlog, a change order, and a deployment. Agencies lose control of their own processes and become dependent on vendor timelines.
The Principle
"The platform should adapt to the rules -- not the other way around. Regulatory changes should be configuration updates, not software projects."
Three Questions This Answers
How do we add a new license type without a software project?
License types, forms, evidence requirements, fee schedules, and workflows are all configuration. Adding a new license type means creating a new configuration -- not writing new code.
How do we change a fee schedule when the legislature updates it?
Fee schedules are configured in the platform. When the legislature updates a fee, the configuration is updated -- and the new fee applies to all new applications immediately.
Who controls the configuration -- the agency or the vendor?
The agency controls the configuration. RegulatoryWorks provides the configuration tools and the training. The agency's operations staff make configuration changes -- within defined guardrails -- without vendor involvement.
How It Works
Forms are built with a configuration tool
Intake forms, review checklists, and decision forms are built using a configuration tool -- not by writing HTML or code. Fields, conditions, and validation rules are all configurable.
Workflows are defined as branching configurations
Process workflows are defined in a configuration interface -- stages, branches, conditions, and outcomes. Changes take effect immediately for new applications.
Fee schedules are maintained by agency staff
Fee schedules are maintained in the platform by agency staff -- not by the vendor. Changes are effective immediately and logged with attribution.
Configuration changes are versioned and auditable
Every configuration change is logged -- who made it, when, and what changed. Previous configurations are preserved and can be reviewed.
See it with your own process.
Bring a real workflow and we'll walk through it together.