Start with the municipal process, not the product demo
A municipal ERP evaluation should begin with the work the institution needs to control: budgeting, procurement, supplier administration, contracts, assets, human resources and reporting. A broad feature list can hide gaps in the hand-offs between these functions.
Document one end-to-end scenario, such as a procurement request moving from initiation to approval, supplier engagement, contract delivery and reporting. Ask each vendor to show where the record is created, who may approve it and how exceptions are handled.
Test governance and audit evidence
Ask how roles are separated, how approval limits are applied and how changes are recorded. The evaluation should cover who changed a record, when it changed, what evidence is retained and how an authorised reviewer can reconstruct the decision.
Treat dashboards as views of underlying records, not proof of control. Agree definitions for each management measure and trace a sample back to its source.
Plan for integration and migration
List the systems that must remain in place and identify which system is authoritative for each data set. Confirm available interfaces, data formats, migration responsibilities, reconciliation rules and ownership of errors.
Do not assume that an API connection means the integration is complete. Test failed messages, duplicates, retries, access restrictions and reconciliation.
Use a scored, evidence-led evaluation
Score functional fit, governance, interoperability, migration, usability, support and total cost separately. Require demonstrations against the same scenarios and record whether each capability is available, configurable, dependent on integration or still planned.
For a South African public institution, align the procurement and implementation process with the institution's own legal, policy and oversight requirements. Obtain appropriate professional advice for compliance questions.
The strongest municipal ERP evaluation is a controlled comparison of real workflows, evidence, integration dependencies and accountable delivery—not a competition between feature lists.