Skip to main content
All articles

Software & ERP

After ERP Go-live: What Managers Should Review in the First 90 Days

A launch date does not show whether staff can complete their work. Review real tasks, exceptions and workarounds with the people doing the work, then assign each problem to the right owner.

Peter Bamuhigire 10 min read
A project manager checks task status and delivery records on a planning screen
Review unfinished tasks with their owners and separate a training gap from a configuration issue.

An ERP can be live while work is still happening in notebooks, spreadsheets and messages. That may be a deliberate short-term control, or it may show that a role cannot finish a task in the new process. A login count will not tell you which.

Managers need a short, regular conversation with the people processing the work. Review what they completed, where a task stopped, what they recorded outside the ERP and what decision they could not make from the reports. The 30/60/90-day rhythm below is a planning tool. It is not a standard adoption timetable or a promise that every rollout should be complete in three months.

Agree what successful work looks like by role

Before go-live, list the critical tasks each role must complete: raise a request, approve it, receive a delivery, reconcile a supplier document or produce a management report. Define the evidence that demonstrates each task is complete, such as a transaction reference, approval history or reconciled report.

Ask the staff who will perform the work to review the list. A task written by a project team may omit a handover, an exception or an approval that matters in daily operations. If the starting expectations are unclear, the post-launch review will become a debate about impressions rather than work.

A professional reviews a dashboard at her desk

Illustrative photograph. Give the person reviewing the work a clear task and the records needed to complete it.

Use 30, 60 and 90 days as review points

At each checkpoint, inspect a small sample of real work with the staff involved. Use authorised records and follow your data-handling rules. A manager’s review sheet can include:

Review itemWhat to record
Role and taskWho does the work and the intended result
Completion evidenceRecord reference, approval or report reviewed
ExceptionWhat stopped or differed from the expected path
Age and ownerWhen the issue began and who is responsible for the next action
WorkaroundAny spreadsheet, paper record or message used outside the ERP
Cause and actionKnowledge, policy, configuration, defect or unresolved; next step and due date

Use the three checkpoints for different decisions. At day 30, identify tasks people cannot finish and assign an owner to each blocker. At day 60, repeat the same task sample and check whether the fixes removed the workaround or merely moved it elsewhere. At day 90, review what remains open, confirm any continuing control, and hand ongoing support to its named owner. Shift the dates if the organisation’s rollout or transaction cycle calls for it; these are prompts, not an audit standard.

Colleagues review charts and reports together

Illustrative photograph. Review the work with the people responsible for completing it.

Diagnose before scheduling more training

When someone cannot complete a task, ask them to show where the process stops. Then classify the cause:

  • Knowledge gap: the user has the right access and the process is clear, but needs guidance or practice.
  • Policy gap: the organisation has not decided who may act or what should happen in the exception.
  • Configuration issue: the agreed rule exists, but the system’s roles, workflow or report does not reflect it.
  • Software defect: the configured system does not behave as specified, and the issue can be reproduced.
  • Dependency or support issue: an integration, data record or support route prevents completion.

Training may address a knowledge gap. It cannot fix an approval rule that nobody has defined or a defect that stops a valid transaction. Give every issue an owner, evidence, priority and next action. Record any temporary workaround, its control and the date it should be reviewed.

Ask why each spreadsheet remains

List parallel spreadsheets and paper logs that people still rely on. For each, write what job it performs, who owns it, what information it duplicates, how often it is reconciled and what risk would follow if it were withdrawn today.

Some parallel records are intentional during a controlled transition. Others may reveal that a report is missing, a task cannot be completed, or teams do not trust the source record. Do not delete a working control until the process owner has confirmed that the underlying need is met and the change is approved.

A professional examines records on a desktop computer

Illustrative photograph. Use a real task to identify the support the team needs.

Review reports with the person who makes the decision

Choose the reports managers actually use to release work, manage stock, review commitments or plan cash. Ask the report owner to trace one figure to its underlying transaction and explain its date, status and source. If the number cannot be explained, write down what is missing before commissioning a new dashboard.

Country-specific accounting, payroll, tax, currency and reporting rules need confirmation for the operating country. A review routine can travel across markets; statutory settings and local integrations cannot be assumed from a regional label.

Make the next review a decision point

At each checkpoint, decide which issues are closed, which remain open, what temporary controls stay in place and who accepts the remaining risk. Escalate recurring blocked work and unresolved control failures through the organisation’s project governance. Change the plan when the evidence calls for it; the calendar is there to prompt a decision, not to force one.

Chwezi’s Kraal Code implementation service brings together testing, training, adoption, support and continued improvement. Agree support routes, response times and review responsibilities for your project. Explore Kraal Code and bring your team’s first-month priorities to the planning discussion.

Before launch, use a complete ERP purchase scenario with an exception to define what users and reviewers will accept. For earlier preparation, see Is Your Organisation Ready for an ERP Implementation?.

Sources and scope

  • Chwezi Core Systems, Kraal Code ERP implementation.
  • Microsoft Learn, Monitor and service the health of your Dynamics 365 solution. Product-specific operational guidance; it does not set the review calendar or support terms for Kraal Code.
  • The 30/60/90-day checkpoints and review sheet are proposed management tools, not a validated benchmark or guaranteed adoption duration. Adapt them to the rollout, risk and support model your organisation agrees.

Common questions

What should managers review after an ERP goes live?
Review whether people can complete the critical tasks assigned to their roles, which exceptions remain unresolved, what work is still being recorded elsewhere, and whether decision reports can be traced to their underlying records. Assign an owner and next action to each finding.
Does logging in mean a user has adopted the ERP?
No. A login only shows that an account accessed the system. Adoption is better reviewed through agreed work completed, usable records, appropriate exception handling and reports that the intended decision-makers can use.
What if staff still use spreadsheets after go-live?
Ask what job the spreadsheet performs and who owns it. It may be a temporary controlled reconciliation or an unplanned duplicate record caused by missing access, unclear policy, a configuration gap or a defect. Document the reason before withdrawing it.
Does every ERP need a 90-day adoption period?
No fixed period suits every organisation. Treat 30, 60 and 90 days as review points that can be adapted to the rollout scope, transaction volume and agreed support arrangements. Define what evidence will trigger a decision at each point.

A practical next step

Agree the review routine before go-live

Ask your implementation team to define critical role-based tasks, support routes, evidence and review owners in the project scope. Make sure the plan reflects your operating model and the support terms you have agreed.

Discuss Kraal Code implementation