Enterprise Permitting and Licensing: what to get right before go-live

Treat EPL as a service change across departments

In this guide, EPL refers to Tyler Technologies' Enterprise Permitting & Licensing. Tyler describes its Civic Access portal as supporting online permit and license applications, payments, and inspection requests. Its business management offering addresses business licensing functions. Confirm the modules, version, deployment, and capabilities included in your agency's agreement.

A permitting or licensing project touches applicants, counter staff, reviewers, inspectors, finance, GIS, and records management. A working application screen is only one acceptance condition. Staff need to complete a case, applicants need to understand what happens next, and the agency needs reliable records and financial results.

Sources: Tyler Technologies — Enterprise Permitting & Licensing Civic Access; Tyler Technologies — Enterprise Business Management

Approve the workflow before configuring it

Choose the permit and license types in scope. For each, map intake, completeness review, departmental reviews, corrections, fee assessment, payment, issuance, inspections, and closure or renewal as applicable. Identify prerequisites and the people authorized to make decisions.

Pay particular attention to cases returned for corrections, reassigned during an absence, reopened after issuance, or withdrawn. Define how parallel reviews interact and which status the applicant should see. Distinguish adopted policy from informal workarounds before either is embedded in configuration.

Have the agency approve those rules and keep a change record. A configuration decision that changes a review obligation or an applicant's payment needs the appropriate business approval.

Build a fee inventory that finance can verify

For every fee in scope, record its authorized basis, effective date, calculation inputs, rounding rule, exemptions, penalties, and refund treatment where applicable. Distinguish a fee assessed from an amount paid and identify the financial coding needed for each.

Business licensing may involve renewals, ownership or location changes, classifications, and overdue charges. Use examples from the agency's adopted rules. Verify how the proposed EPL configuration handles those cases; do not assume a standard setup matches the ordinance.

Create expected results before testing and have finance and the licensing or permitting owner approve them. Include a fee change crossing an effective date, a correction after assessment, and a refund or cancellation if allowed.

Reconcile case data and retain the history staff need

Inventory active applications, issued permits, license records, inspections, contacts, parcel and address identifiers, attachments, payments, and relationships between them. Define authoritative sources for addresses and parcels and resolve conflicting identifiers with GIS and department owners.

Choose what moves into EPL and what remains in a controlled archive. Preserve identifiers that let staff connect an active case to its legacy history. Specify how retained records will be searched and produced, subject to the agency's retention schedule and legal holds.

Test attachments, dates, balances, inspection histories, and case relationships on representative records. A matching record count will not show that a plan set is attached to the correct permit or that a license renewal retained the right business history.

Test the public portal and inspection journey

Ask an applicant to complete the process using approved test records: find the right application, provide information, submit documents, pay when required, respond to a correction, and see the current status. Verify instructions, notices, accessibility, and assistance for applicants who need another service channel.

Then follow the same case through the staff workflow. Check who receives it, what triggers the next review, what blocks issuance, and what appears to the applicant. For inspections, demonstrate scheduling, assignment, results, reinspection, and the record of completion in the contracted tools.

Review public and staff access separately. Decide which contacts, documents, comments, and financial details may be visible. Validate actual role permissions with the records and privacy owners.

Verify every handoff to another system

List connections to GIS, cashiering or payment services, the ERP ledger, document management, identity services, and reporting tools. Record what data moves, its timing, who monitors it, and the method for resolving rejected or duplicated transactions.

Ask the implementation team to demonstrate the proposed handoffs using the agency's configuration. Shared vendor branding does not establish that a connection is licensed, configured, or included in scope. Confirm responsibilities and costs in writing.

EPL fee-rule validation worksheet

Record the approved source version and effective date with the policy owner before translating a rule into configuration. Keep the fee assessed, amount paid, and amount refunded distinct. Do not use AI-generated monetary values as the expected result.

From worksheet to acceptance

Trace each approved source to a documented rule, the proposed configuration, an independently calculated expected case, the observed test result, and the agency’s approval. Resolve ambiguity with the policy owner before configuration or acceptance.

Make the go-live decision by complete service journey

Approve launch when department owners can demonstrate the agreed permit and license scenarios, fee results reconcile, migrated records are usable, access is appropriate, and staff know how to handle exceptions. Name support contacts and a process for managing urgent configuration problems.

For an agency already using EPL, apply the same review to a troublesome workflow before proposing a full replacement. The findings may point to configuration, data cleanup, training, or a missing integration.

• Approve process maps and fee test cases with the agency owners.
• Reconcile active cases, financial balances, and retained history.
• Test applicant, reviewer, inspector, and finance tasks end to end.
• Document a contingency plan for accepting applications and tracking decisions during an outage.