# ERP rescue assessment worksheet

Prepared by erpence | https://erpence.com/failed-erp-implementation-rescue-uae/

Use one record for each critical issue. This blank planning template is not a completed audit or a customer case study.

## 1. Protect the operation

- Platform and affected process:
- Business transactions or reporting at risk:
- Immediate containment or temporary control:
- Business decision owner:
- Systems, environments and backups the customer controls:
- Access or ownership gaps to resolve:

## 2. Record the finding

- Issue reference:
- Expected behaviour:
- Observed behaviour and date:
- Evidence references (logs, records, screenshots, reconciliations):
- Business consequence:
- Root cause: confirmed / hypothesis / not yet investigated:
- Business owner:
- Technical owner:

## 3. Compare recovery options

| Option | Work retained | Work required | Dependencies | Risks | Effort estimate |
|---|---|---|---|---|---|
| Stabilise existing design | | | | | |
| Simplify or reduce scope | | | | | |
| Rebuild the affected part | | | | | |

Record the evidence for the chosen route and the person authorised to approve it.

## 4. Define acceptance before repair

- Test scenario, including retry or exception:
- Test inputs:
- Expected records, quantities, balances and outputs:
- Actual result and evidence reference:
- Outstanding differences and owner:
- User acceptance decision:
- Business sign-off and date:

## 5. Prepare the recovery release

- Scope included and deferred:
- Data and integration prerequisites:
- Backup and rollback approach:
- Cutover tasks and owners:
- User communication and training:
- Support contacts and escalation route:
- Monitoring and first operating review:

Do not include passwords or access tokens in this worksheet. Reference securely controlled access records instead.