Current-state workflow discovery helps a municipality understand how work actually happens before it selects, procures, or configures a new ERP system. For Canadian municipalities, this matters because finance, tax, utilities, payroll, assets, records, reporting, approvals, and compliance workflows often depend on spreadsheets, legacy systems, manual handoffs, municipal add-ons, and staff knowledge that may not appear in a standard requirements list. A structured ERP advisory phase helps make these dependencies visible.
Before procurement begins, municipalities should know what must be preserved, improved, replaced, retired, or redesigned.
What is current-state workflow discovery?
Current-state workflow discovery is the process of documenting how municipal work is done today.
It looks beyond system names and module lists. It examines the actual steps, people, data, approvals, reports, controls, timing, and exceptions involved in daily and year-end operations.
For a municipality, current-state discovery may cover:
- Finance and fund accounting
- Budgeting and reporting
- Property tax
- Utility billing
- Payroll and HR handoffs
- Asset management
- Work orders
- Procurement
- Document control and records
- Citizen service workflows
- Compliance and audit evidence
- Integrations and data movement
- Manual spreadsheets and workarounds
The goal is not to defend the current state. The goal is to understand it clearly enough to make better procurement and modernization decisions.
Why discovery should happen before procurement
Many municipalities begin ERP procurement by asking vendors what their systems can do. That is useful, but it is not enough.
Before evaluating vendors, the municipality should understand its own operating reality.
Current-state discovery helps answer:
- Which workflows are critical?
- Which reports must continue?
- Which integrations are required?
- Which data must be migrated?
- Which controls must be preserved?
- Which manual processes create risk?
- Which departments are affected?
- Which timing constraints matter?
- Which requirements are real needs versus old habits?
- Which pain points should be solved first?
Without this understanding, procurement can become a generic feature comparison instead of a focused evaluation of municipal fit.
Why requirements lists are not enough
A requirements spreadsheet can be useful, but it often misses the way work actually happens.
For example, a requirement may say:
“System must support utility billing.”
But current-state discovery may reveal:
- Meter reads arrive from a separate source
- Exceptions are handled manually
- Billing adjustments require supervisor review
- Notices are generated from templates
- Payment files reconcile through finance
- Resident inquiries depend on account notes
- Year-end balances feed reporting schedules
- Some data is tracked in spreadsheets outside the billing system
The requirement is technically true, but incomplete. Discovery turns broad requirements into implementation-ready understanding.
How discovery reduces implementation risk
ERP implementation risk often comes from hidden dependencies.
A municipality may not realize that a report, spreadsheet, approval path, or data extract is critical until it disappears, changes, or fails during testing.
Discovery reduces risk by identifying:
- Undocumented reports
- Spreadsheet dependencies
- Manual reconciliations
- Informal approvals
- Legacy data sources
- Municipal add-ons
- Integration points
- Department-specific workarounds
- Security and role assumptions
- Audit evidence locations
- Cutover constraints
This gives the project team a clearer view of what must be addressed before implementation accelerates.
How discovery improves vendor evaluation
A municipality with strong current-state discovery can ask better questions during procurement.
Instead of asking only whether a vendor supports a function, the municipality can ask:
- How would this workflow be configured?
- Which steps are standard?
- Which steps require customization?
- How would this report be produced?
- How would this data migrate?
- How would this integration work?
- How would this approval path be controlled?
- How would audit evidence be retained?
- How would the first close or first billing cycle be supported?
This helps the municipality evaluate fit, not just presentation quality.
How discovery supports PSAB and audit readiness
For municipal finance leaders, current-state discovery is especially important for PSAB reporting and audit readiness.
Discovery should identify:
- Fund accounting structures
- Chart-of-accounts dependencies
- Deferred revenue schedules
- Grant tracking
- Reserve continuity
- Tangible capital asset records
- Year-end working papers
- Audit evidence files
- Manual adjustments
- Reporting packages
- Historical data access
- Finance-to-payroll handoffs
- Finance-to-tax and utility handoffs
If these items are not understood before procurement, the future system may be selected without a clear view of PSAB reporting and audit requirements.
How discovery supports Dynamics GP migration
For municipalities planning a Dynamics GP migration, discovery is essential.
A Dynamics GP environment may include:
- Management Reporter outputs
- Excel reporting packages
- Custom exports
- Municipal add-ons
- Payroll handoffs
- Property tax and utility billing interfaces
- Banking files
- Historical transactions
- Manual reconciliations
- Legacy approval paths
- Staff-owned workarounds
Discovery helps identify what must be migrated, rebuilt, redesigned, retired, or retained for historical access.
It also helps prevent the municipality from recreating old complexity inside a new system.
How discovery supports RICE planning
Current-state discovery is the foundation for a RICE inventory.
RICE stands for Reports, Interfaces, Conversions, and Extensions or Enhancements.
Discovery helps identify:
- Reports that must continue
- Interfaces that must be rebuilt or replaced
- Data conversions that need planning
- Enhancements that may be required
- Legacy items that can be retired
- Testing scenarios that must be included
Without discovery, the RICE inventory may be incomplete, which can create late-stage implementation risk.
What should be included in discovery?
A practical discovery process should capture:
- Process flows: How work moves from request to completion, including approvals, exceptions, and handoffs.
- Systems and tools: Which applications, spreadsheets, reports, shared drives, and templates are used.
- Data inputs and outputs: What data enters the process, where it comes from, where it goes, and who validates it.
- Reports and evidence: Which reports, schedules, extracts, and documents support operations, leadership, audit, and compliance.
- Roles and ownership: Who performs, reviews, approves, maintains, and supports each step.
- Pain points: Where work is delayed, duplicated, manual, unclear, or dependent on one person.
- Controls and compliance: Which approvals, audit trails, access rules, and evidence requirements must be preserved.
- Timing constraints: Which cycles cannot be disrupted, such as month-end, year-end, tax billing, utility billing, payroll, audit, and budget season.
- Future-state opportunities: Which steps can be simplified, standardized, automated, or retired.
Who should participate in discovery?
Current-state discovery should include more than IT and finance leadership.
Depending on scope, participants may include:
- CFO or finance director
- Controller or accounting lead
- Tax administrator
- Utility billing lead
- Payroll or HR lead
- Public works or asset lead
- Records or document control owner
- IT lead
- Procurement lead
- Department supervisors
- Staff who run daily processes
- Staff who handle exceptions
- Staff who prepare reports or audit evidence
The people who know the real process are often not the same people who approve the project.
When should discovery happen?
Discovery should happen before procurement or at the very beginning of procurement planning.
The best timing is:
- Before RFP drafting: So the municipality can write better requirements.
- Before demonstrations: So demos can be scenario-based instead of generic.
- Before vendor scoring: So evaluation criteria reflect real municipal workflows.
- Before implementation planning: So scope, RICE, data migration, testing, and cutover planning are realistic.
If discovery happens only after vendor selection, the municipality may have already made decisions based on incomplete information.
What this means for your municipality
Current-state workflow discovery is not extra paperwork. It is risk control.
For Canadian municipalities, it helps convert informal knowledge, spreadsheets, reports, handoffs, and legacy dependencies into a shared view of what must be addressed before ERP decisions are made.
A stronger discovery process leads to better procurement, clearer scope, safer migration, more realistic timelines, and better first-year stabilization. A dedicated Workflow Review can help jumpstart this process.
Frequently asked questions
What is current-state workflow discovery?
Current-state workflow discovery is the process of documenting how municipal work is done today, including steps, systems, data, reports, approvals, exceptions, handoffs, controls, and timing dependencies.
Why should discovery happen before ERP procurement?
Discovery should happen before procurement so the municipality understands its actual workflows, dependencies, risks, and requirements before evaluating vendors or writing an RFP.
How does discovery reduce ERP project risk?
Discovery reduces risk by identifying hidden reports, spreadsheets, integrations, data issues, manual workarounds, controls, and timing constraints before they become implementation problems.
Who should participate in discovery?
Participants should include leaders and operational staff from finance, tax, utilities, payroll, HR, IT, public works, records, procurement, and any department affected by the future system.
How does discovery help Dynamics GP migration?
Discovery helps identify Dynamics GP reports, integrations, data, municipal add-ons, Management Reporter outputs, spreadsheets, and manual processes that must be migrated, redesigned, retired, or retained.
How does discovery support PSAB readiness?
Discovery supports PSAB readiness by identifying fund accounting structures, year-end schedules, audit evidence, deferred revenue, grants, reserves, tangible capital asset records, and reporting dependencies.
Is discovery only useful for large ERP projects?
No. Discovery is useful for small, finance-first, phased, or advisory projects because it helps the municipality clarify scope, risk, and readiness before committing to a path.