Skip to content

What Actually Happens After Go-Live (And Why That’s Where Most Problems Start)

SEP Technology Consulting
SEP Technology Consulting

Implementing a new permitting, licensing, or regulatory management system is a significant undertaking. Months or even years of planning, configuration, data migration, testing, and training lead up to one important milestone: go-live. But while implementation marks the beginning of a new system, it doesn't mean the work of maintaining an effective technology environment is complete. For government agencies, some of the most persistent challenges emerge in the months and years that follow, when operational needs change, processes evolve, and the system doesn't always keep pace.

Understanding what happens after go-live, and planning for it, can make the difference between a platform that continues delivering value and one that gradually becomes harder to manage.

Key Takeaways 

Go-live is the beginning of a system's operational lifecycle, not the end of its implementation journey. Maintaining long-term effectiveness requires ongoing attention to workflows, integrations, data quality, user needs, and system performance.

The most important considerations include:

  • Go-live confirms that a system is ready to begin production operations, but it doesn't guarantee that every workflow has been optimized for long-term use.
  • Operational changes, regulatory updates, staffing transitions, and new service requirements can gradually create gaps between system configuration and actual business processes.
  • Manual workarounds often emerge when systems cannot easily accommodate changing requirements, creating inefficiencies that may go unnoticed.
  • Technical support and system optimization serve different purposes. Resolving incidents keeps a system running, while optimization helps it remain effective.
  • Regular system reviews, clear ownership, documented processes, and prioritized enhancements can help agencies address issues before they become more expensive or disruptive.
  • Existing platforms, including Accela Civic Platform, may be capable of supporting new requirements through targeted configuration, automation, and integration improvements rather than full replacement.

Who This Guide Is For

This guide is intended for government organizations responsible for implementing, maintaining, or improving permitting, licensing, inspection, and regulatory technology systems.

It is particularly relevant to departments and teams managing Accela environments, coordinating technology across multiple agencies or business units, or evaluating how to improve an existing system without undertaking another major implementation.

The principles also apply to organizations using other enterprise platforms where operational processes, regulatory requirements, and technology configurations must remain aligned over time.

What Actually Happens Immediately After a System Goes Live?

The first several months after go-live are typically a period of operational adjustment, when real-world use begins revealing issues that may not have been apparent during implementation.

Even well-planned implementations cannot anticipate every situation that will arise once a system is used across departments, locations, and user groups.

During implementation, teams generally focus on defined requirements, approved workflows, data migration, testing, and readiness for production. Once the system is live, those processes encounter the full complexity of daily operations.

For example, a permitting system may successfully process standard applications during testing, but production use may reveal exceptions involving unusual property configurations, overlapping jurisdictions, complex fee calculations, or applications that require multiple departments to coordinate approvals.

Similarly, an Environmental Health system may function as designed for routine inspections but require additional configuration when inspection frequencies change, new license categories are introduced, or reporting requirements evolve.

Common post-go-live activities include:

  • Resolving production issues identified by staff and external users
  • Refining workflows that operate differently than anticipated
  • Adjusting user permissions and department-specific access
  • Correcting data migration or record mapping issues
  • Updating forms, notifications, and reporting configurations
  • Improving integrations with financial, geographic, or document management systems
  • Providing additional training as employees encounter less common scenarios
  • Evaluating enhancement requests that were deferred during implementation

These activities are not necessarily signs of a failed implementation. They are part of transitioning from a defined project environment to a continuously operating system.

The challenge arises when organizations treat this adjustment period as temporary and fail to establish a sustainable process for managing the system afterward.

Why Do Government Technology Systems Begin to Drift After Implementation?

System drift occurs when a technology platform's configuration gradually becomes misaligned with the processes, policies, and operational requirements it is supposed to support.

Unlike a major system failure, drift often develops slowly. Individual changes may appear minor, but their cumulative effect can make everyday operations increasingly complicated.

Several factors contribute to this misalignment.

How Do Changing Regulations Affect System Configuration?

Regulatory changes can make previously effective workflows outdated when system rules, forms, calculations, or approval processes are not updated accordingly.

Government agencies routinely respond to changes in local ordinances, state requirements, fee schedules, licensing standards, and reporting obligations.

A new requirement may affect multiple parts of a technology environment. For example, updating a permit fee may require changes to calculation logic, application forms, payment processing, reports, and public-facing information.

If those components are not updated consistently, staff may need to perform manual corrections or maintain separate records to ensure compliance.

Over time, these exceptions can become part of normal operations, even though the underlying system was originally intended to automate them.

How Do Departmental Changes Create Workflow Gaps?

Departmental changes create workflow gaps when organizational responsibilities evolve without corresponding updates to system routing, permissions, or automation.

Government departments rarely operate exactly the same way year after year. Responsibilities shift, new positions are created, review procedures change, and services expand.

For example, a planning department may introduce an additional review step for certain development applications. If the Accela workflow is not updated, employees may coordinate the new review through email or spreadsheets while the official system continues following the previous process.

The work still gets completed, but the system no longer provides a complete picture of the process.

These gaps can affect workload visibility, reporting accuracy, turnaround times, and coordination between departments.

Why Do Small Workarounds Become Long-Term Problems?

Workarounds become long-term problems when temporary manual solutions are repeatedly used instead of addressing the system limitations that created them.

A workaround may be reasonable when an immediate operational need arises. However, repeated use can create dependencies that are difficult to eliminate.

Common examples include:

  • Tracking application statuses in spreadsheets because system dashboards do not provide the necessary visibility
  • Manually calculating fees that could be handled through configurable business rules
  • Sending approval notifications outside the system because automated messages are outdated
  • Reentering information between platforms when integrations are incomplete
  • Maintaining separate inspection schedules because assignment logic no longer reflects staffing or geographic requirements
  • Relying on a specific employee to interpret undocumented system behavior

Each workaround adds another layer to the operating process.

Eventually, departments may become accustomed to these extra steps, making it harder to distinguish between required business processes and inefficiencies created by system limitations.

What Are the Most Common Accela Challenges After Go-Live?

Common post-go-live Accela challenges involve workflow configuration, automation, integrations, reporting, user access, and the ongoing maintenance of business rules.

Because Accela environments can support multiple departments and regulatory programs, a change in one area may affect several connected processes.

The following areas frequently warrant review.

Why Do Accela Workflows Become More Complicated Over Time?

Accela workflows can become more complicated when new approval steps, exceptions, and department-specific requirements are added without reviewing the overall process.

An agency may begin with a relatively straightforward application workflow. Over time, additional review requirements, conditional routing, special permit categories, and approval exceptions may be introduced.

If each change is handled independently, the resulting workflow can become difficult to understand and maintain.

Periodic workflow reviews help identify redundant steps, outdated statuses, unnecessary handoffs, and opportunities to automate routine decisions.

What Causes Fee Calculation and Renewal Problems?

Fee and renewal problems often arise when regulatory changes, new classifications, or evolving business rules are not consistently reflected in system configuration.

Accela environments may need to accommodate complex fee structures involving application types, inspection results, geographic conditions, project characteristics, or multiple departments.

Without a consistent approach to maintaining those calculations, staff may encounter unexpected fees, manual adjustments, or inconsistent processing.

Renewal workflows can present similar challenges when eligibility rules, notifications, deadlines, and payment requirements change.

Configurable fee logic and automated renewal processes can help reduce repetitive work while making future updates easier to manage.

Why Do Integrations Require Ongoing Maintenance?

Integrations require ongoing maintenance because the systems, data structures, security requirements, and business processes they connect can change independently.

Accela may exchange information with GIS, ERP, payment processing, document management, and other enterprise systems.

A change to one connected application can affect data synchronization, transaction processing, or record accuracy elsewhere.

For example, an updated financial process may require changes to how fee payments or refunds are transferred between Accela and an ERP system.

Ongoing integration monitoring, documentation, and testing help agencies identify issues before they affect critical operations.

Why Does Reporting Become Less Reliable?

Reporting becomes less reliable when system data, workflow definitions, and reporting requirements evolve without corresponding updates to dashboards and report logic.

A report built during implementation may accurately reflect the original process but become less useful after departments introduce new statuses, record types, or performance measures.

If staff cannot obtain the information they need, they may begin exporting data and maintaining separate spreadsheets.

Regular reporting reviews can help ensure that dashboards and operational reports continue reflecting current processes and support informed decisions.

How Can Agencies Recognize When Their Systems Need Optimization?

A system may need optimization when employees consistently rely on manual processes, encounter recurring issues, or struggle to obtain accurate information from the platform.

Not every problem requires a major enhancement project. However, recurring patterns often indicate that the system no longer fully supports operational needs.

Warning signs include:

  • Staff regularly maintain spreadsheets or external tracking tools alongside Accela.
  • Routine approvals or inspections require unnecessary manual coordination.
  • Fee calculations or renewals frequently require staff intervention.
  • Reports do not accurately reflect current workloads or performance.
  • Different departments use inconsistent processes for similar activities.
  • Users report recurring issues that are repeatedly resolved without addressing the underlying cause.
  • System changes take longer than expected because existing configurations are poorly documented.
  • New regulations or service requirements are difficult to accommodate.
  • Integration failures create duplicate entry or reconciliation work.
  • Staff avoid certain system functions because they are confusing or unreliable.

These indicators do not automatically mean the platform needs replacement.

In many cases, they suggest that the organization would benefit from reviewing how the existing system is configured and identifying opportunities for targeted improvements.

What Is the Difference Between System Maintenance and Optimization?

System maintenance focuses on keeping technology operational, while system optimization focuses on improving how effectively that technology supports business processes.

Both are necessary, but they address different needs.

Maintenance typically includes resolving incidents, monitoring integrations, applying updates, managing access, and addressing technical issues that affect availability or reliability.

Optimization takes a broader view. It examines whether the system continues supporting current requirements and identifies opportunities to reduce manual work, improve usability, or introduce new capabilities.

For example, correcting a broken inspection notification is a maintenance activity. Redesigning the notification process to automatically communicate inspection results, next steps, and required follow-up actions is an optimization activity.

Similarly, repairing an integration that has stopped transferring data restores functionality. Reviewing the integration to eliminate duplicate entry or improve data validation may create additional operational value.

A sustainable post-go-live strategy should account for both activities rather than treating all support requests as isolated technical incidents.

How Should Agencies Plan for Ongoing System Optimization?

Effective optimization planning requires a repeatable process for identifying needs, evaluating priorities, implementing improvements, and measuring whether those changes are delivering value.

Without a structured approach, enhancement requests may accumulate until departments are forced to address them through urgent projects or manual workarounds.

A practical optimization program can be organized into five steps.

1. How Can Agencies Establish a Baseline of Current System Performance?

Agencies can establish a baseline by documenting existing workflows, recurring issues, manual processes, and performance measures before making changes.

This assessment should consider both technical performance and operational effectiveness.

Useful questions include:

  • Which processes generate the most support requests?
  • Where are employees performing work outside the system?
  • Which integrations experience recurring errors?
  • What information is difficult to obtain through current reporting?
  • Which workflows have changed significantly since implementation?
  • Are there upcoming regulatory or departmental changes that will affect configuration?

The goal is to identify where system behavior and operational needs are no longer aligned.

2. How Should Enhancement Requests Be Prioritized?

Enhancement requests should be prioritized based on operational impact, regulatory importance, implementation effort, and dependencies rather than the order in which they are submitted.

Not every request requires immediate action, and some improvements may deliver substantially more value than others.

A useful prioritization framework considers:

  • Regulatory or compliance requirements
  • Frequency and severity of the problem
  • Number of employees, departments, or external users affected
  • Amount of manual effort involved
  • Risk to data accuracy or financial processing
  • Dependencies on other systems or planned projects
  • Estimated implementation and maintenance effort

This approach helps distinguish high-value operational improvements from lower-priority preferences.

3. Why Is Cross-Department Collaboration Important?

Cross-department collaboration is important because changes to shared technology platforms can affect multiple business units, even when a request originates from one department.

An adjustment to a permitting workflow may influence inspections, fee calculations, reporting, or public-facing services.

Including representatives from affected departments helps identify dependencies and prevent unintended consequences.

Clear governance also establishes who can request changes, who evaluates their impact, and who approves implementation.

4. How Can Agencies Reduce Risk When Making Changes?

Agencies can reduce change-related risk through documented requirements, controlled testing, stakeholder validation, and planned deployment procedures.

Accela enhancements may involve workflow configuration, scripts, integrations, and business rules that interact with other system components.

Testing should therefore consider more than whether an individual change functions as expected.

A structured approach may include:

  • Documenting the intended operational outcome
  • Reviewing dependencies with existing workflows and integrations
  • Testing standard and exception scenarios
  • Validating fee calculations and financial processes
  • Confirming user permissions and access restrictions
  • Performing regression testing on affected functionality
  • Obtaining feedback from relevant department users
  • Documenting changes and establishing rollback procedures when appropriate

Automated testing can also help validate repeatable processes and reduce the effort required to assess future updates.

5. How Should Agencies Measure Optimization Results?

Optimization results should be measured against the operational problem the enhancement was intended to solve.

Completing a technical change does not automatically mean the underlying business issue has been resolved.

Depending on the project, useful measures may include:

  • Reduction in manual processing steps
  • Changes in application or permit turnaround times
  • Number of recurring support incidents
  • Frequency of integration errors
  • Accuracy of fee calculations or reporting
  • Staff time required for recurring administrative tasks
  • Adoption of online services
  • User feedback and satisfaction

Establishing a baseline before implementing improvements makes it easier to determine whether the changes are producing meaningful results.

When Should Post-Go-Live Optimization Begin?

Post-go-live optimization planning should begin before implementation is complete, with clear ownership, support processes, and enhancement priorities established before the system enters production.

Waiting until problems accumulate can make optimization more difficult because workarounds and undocumented changes may already be embedded in daily operations.

A practical lifecycle approach includes several stages.

What Should Happen During the First 30 to 90 Days?

The first 30 to 90 days should focus on stabilization, issue resolution, user feedback, and identifying gaps between tested workflows and actual operations.

During this period, agencies can document recurring questions, identify unexpected process exceptions, and distinguish immediate fixes from enhancements that require additional planning.

A defined transition from the implementation team to ongoing support is especially important to preserve technical knowledge and clarify responsibility.

What Should Happen During the First Year?

The first year should include structured reviews of workflows, reporting, integrations, and enhancement requests as the system becomes established in daily operations.

Once initial production issues are resolved, teams can evaluate whether processes are delivering the efficiencies anticipated during implementation.

This is also an opportunity to address deferred requirements and refine capabilities based on actual user experience.

What Should Happen in Subsequent Years?

Long-term system management should include regular operational reviews, proactive maintenance, and a prioritized roadmap for enhancements.

As regulatory requirements, staffing, and technology dependencies change, the roadmap should be updated accordingly.

Rather than relying exclusively on large, infrequent modernization projects, agencies can pursue incremental improvements that keep the platform aligned with evolving needs.

Does an Agency Need to Replace Its Accela System to Address These Problems?

An agency does not necessarily need to replace its Accela system to resolve post-implementation challenges, because many issues can be addressed through targeted configuration, workflow automation, integrations, and ongoing optimization.

When a system becomes difficult to use, replacement may seem like the most straightforward solution. However, the underlying problem may be a mismatch between current processes and existing configuration rather than a fundamental limitation of the platform.

Before pursuing a major replacement, it is worth evaluating whether the current environment can be improved through:

  • Workflow redesign and automation
  • Business rule and script updates
  • Improved fee and renewal configuration
  • Integration enhancements
  • Reporting and dashboard improvements
  • User interface and portal enhancements
  • Data quality improvements
  • Targeted training and documentation
  • More consistent application support

This evaluation should also identify limitations that cannot be reasonably resolved within the existing environment.

In some situations, substantial modernization or replacement may be appropriate, particularly when the platform cannot meet essential requirements or ongoing maintenance has become unsustainable.

The objective is not to avoid replacement at all costs. It is to make an informed decision based on operational needs, technical constraints, long-term costs, and the capabilities already available.

What Role Do Managed Application Services Play After Go-Live?

Managed Application Services provide ongoing technical expertise and structured support to help agencies maintain, troubleshoot, enhance, and optimize their application environments after implementation.

For organizations managing complex Accela systems, internal resources may be limited or focused on broader technology responsibilities.

A managed services arrangement can supplement internal capabilities with specialized knowledge of platform configuration, scripting, integrations, testing, and operational processes.

Depending on the engagement, services may include:

  • Incident resolution and troubleshooting
  • Workflow and business rule enhancements
  • System configuration and administration support
  • Integration maintenance and improvements
  • Upgrade planning and testing
  • Reporting and data-related enhancements
  • Technical documentation and knowledge transfer
  • Proactive recommendations for system optimization

The value of ongoing support extends beyond responding when something breaks.

With consistent technical oversight and a clear understanding of the agency's operations, support teams can identify recurring issues, recommend improvements, and help prevent small configuration gaps from becoming larger operational problems.

An effective arrangement should also establish clear responsibilities, communication procedures, prioritization criteria, and expectations for knowledge sharing.

The goal is to create a sustainable operating model that supports the agency's long-term technology investment.

How Can Agencies Prevent the Same Problems From Reappearing?

Agencies can reduce recurring post-go-live problems by maintaining clear system ownership, documenting changes, regularly reviewing workflows, and treating optimization as an ongoing responsibility.

Technology environments are not static, and even well-designed systems require adjustments as organizational needs evolve.

Several practices can help maintain alignment:

  • Establish governance for configuration changes and enhancement requests.
  • Maintain current documentation for workflows, scripts, integrations, and business rules.
  • Review recurring support issues for underlying causes rather than repeatedly applying temporary fixes.
  • Schedule periodic discussions with departments about changing operational requirements.
  • Maintain a prioritized enhancement roadmap.
  • Test changes before deployment and validate their effect on connected processes.
  • Provide ongoing training as functionality and staffing change.
  • Track operational performance to identify emerging inefficiencies.
  • Ensure that technical knowledge is shared rather than concentrated with one employee or vendor.

These practices help agencies move from reactive troubleshooting toward more deliberate system management.

They also make future modernization initiatives easier by preserving institutional knowledge and reducing the accumulation of undocumented processes.

Why Should Long-Term System Success Be Measured Beyond Go-Live?

Long-term system success should be measured by how well technology continues supporting agency operations, not simply whether the implementation was completed on time or within budget.

Go-live is an important milestone, but it represents only one point in the system's lifecycle.

A platform may meet its original implementation requirements and still become less effective over time if workflows, integrations, and configurations are not maintained.

Conversely, an agency that continuously evaluates and improves its system may be able to extend the value of its original investment while adapting to new requirements.

The most meaningful measures of success are operational: whether staff can complete work efficiently, whether information is reliable, whether processes are consistent, and whether the public can access services effectively.

Achieving those outcomes requires ongoing collaboration between operational departments, technology teams, and specialized support resources.

How Can SEPTech Help Agencies Get More Value From Accela After Go-Live?

SEP Technology Consulting helps government agencies maintain and improve their Accela environments through specialized application support, workflow optimization, integrations, automation, and system enhancements.

SEPTech's experience spans complex permitting, licensing, Environmental Health, and regulatory technology environments, including systems that support multiple departments and external stakeholders.

Our approach begins with understanding how an agency operates, where its current environment may be creating unnecessary work, and what improvements can realistically be achieved within the existing platform.

That may involve automating manual processes, refining complex business rules, improving system connectivity, enhancing reporting, or providing ongoing Managed Application Services.

Rather than viewing implementation as the finish line, SEPTech focuses on helping agencies maintain systems that continue evolving with their operational and regulatory requirements.

If your Accela environment has become more difficult to manage, relies on manual workarounds, or no longer reflects how your departments operate, a targeted assessment can help identify practical next steps.

Contact SEPTech to discuss your current Accela environment and opportunities for ongoing optimization.

Share this post