# ERP Hypercare Issue Log Worksheet > Source: https://netray.co/tools/erp-hypercare-issue-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A hypercare issue log with severity, owner, hours open, SLA and a breach flag calculated per row. ## Category erp-migration ## Audience - Project manager - Support lead - ERP administrator ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Issue ID **Key:** id **Type:** text #### Date logged **Key:** logged **Type:** date #### Module **Key:** module **Type:** select **Options:** - Finance - Purchasing - Inventory - Production - Sales - Quality - Interfaces - Security - Reports #### Description **Key:** desc **Type:** text #### Severity **Key:** sev **Type:** select **Options:** - 1 Critical - 2 High - 3 Medium - 4 Low #### Owner **Key:** owner **Type:** text #### Status **Key:** status **Type:** select **Options:** - New - In progress - Workaround - Resolved - Closed #### Hours open **Key:** open_hrs **Type:** number **Unit:** hrs #### SLA target **Key:** sla_hrs **Type:** number **Unit:** hrs #### SLA breached (1 = yes) **Key:** breach **Type:** number **Expr:** if(gt(open_hrs, sla_hrs), 1, 0) **Format:** integer **Rows:** **Id:** HC-001 **Logged:** 2027-06-01 **Module:** Inventory **Desc:** Receipts for lot-controlled item will not post, lot number rejected **Sev:** 1 Critical **Owner:** IT lead **Status:** In progress **Open hrs:** 6 **Sla hrs:** 4 **Id:** HC-002 **Logged:** 2027-06-01 **Module:** Sales **Desc:** Invoice shows wrong tax rate for one ship-to **Sev:** 2 High **Owner:** Finance lead **Status:** Workaround **Open hrs:** 20 **Sla hrs:** 24 **Id:** HC-003 **Logged:** 2027-06-02 **Module:** Interfaces **Desc:** EDI 856 not sent to one customer **Sev:** 2 High **Owner:** Integration dev **Status:** Resolved **Open hrs:** 30 **Sla hrs:** 24 **Id:** HC-004 **Logged:** 2027-06-02 **Module:** Reports **Desc:** Open orders report missing promise date column **Sev:** 3 Medium **Owner:** Report dev **Status:** New **Open hrs:** 10 **Sla hrs:** 72 **Id:** HC-005 **Logged:** 2027-06-03 **Module:** Security **Desc:** Planner cannot approve requisitions, missing role **Sev:** 3 Medium **Owner:** Security admin **Status:** In progress **Open hrs:** 5 **Sla hrs:** 48 **Totals:** #### SLA breaches **Key:** breach **Agg:** sum **Format:** integer #### Average hours open **Key:** open_hrs **Agg:** avg **Format:** hours #### Issues logged **Key:** open_hrs **Agg:** count **Format:** integer **Summary:** #### SLA breach rate **Key:** breach_rate **Expr:** sum_breach / count * 100 **Format:** percent **Primary:** true #### Average hours open **Key:** avg_open **Expr:** avg_open_hrs **Format:** hours **Notes:** Update Hours open daily for unresolved issues and set the SLA target by severity, for example 4 hours for critical and 24 hours for high. Track the issue count by day: a falling trend of new issues, not zero issues, is a typical hypercare exit signal. ## Content **Intro:** In the weeks after go-live, issues arrive faster than the project team can remember them. A single log with severity, owner and SLA gives everyone one list to work from and tells the steering committee when stabilisation is real. **Sections:** #### How to use the log **Body:** Log every issue the moment it is raised, whether it came from a phone call, a message or a ticket. Give each issue a module, a severity and a single owner. Update the hours open for unresolved items each day, and set the SLA target by severity. The breach column flags any row where hours open exceed the target. Run a short daily stand-up on critical and high issues and a weekly review of trends. Export to Excel for the steering committee. #### Severity and SLA definitions **Body:** Agree severity definitions before go-live. A common scheme: severity 1 stops a core business process such as shipping or receiving with no workaround, severity 2 has a major impact with a workaround, severity 3 affects a smaller group or a report, and severity 4 is cosmetic. Targets scale accordingly, such as 4 hours for severity 1 down to a few days for low severity. Keep definitions short so that users and support agree on classification without debate. **Bullets:** - Severity 1: core process stopped, no workaround - Severity 2: significant impact, workaround exists - Severity 3: limited users or reports - Severity 4: cosmetic or enhancement request #### Reading trends and exiting hypercare **Body:** Look at new issues per day, the open backlog by severity and the breach rate. A healthy pattern shows new issues peaking in the first week then falling, severity 1 and 2 reaching zero open, and the first month-end close completing without critical problems. Write the exit criteria before go-live, for example no open severity 1 or 2 issues for ten working days, completed first period close, and support handed to the operations team. Separate genuine defects from training gaps and enhancement requests. #### Common mistakes **Body:** Mistakes include logging issues in several places, no clear owner per issue, and classifying everything as critical, which hides what is urgent. Another is letting hypercare run without an end date, so the project team never returns to other work. Make sure every closed issue records its root cause, as patterns show where training or configuration needs reinforcing. **Cta:** If many hypercare issues are repeated how-to questions or report requests, we can discuss a private assistant that answers from your procedures and queries ERP data in read-only mode to cut ticket volume. **Faq:** #### How long does ERP hypercare last? **Answer:** Four to eight weeks is common, usually long enough to cover the first month-end close. Complex or multi-site rollouts may need longer. Define exit criteria in advance rather than choosing a fixed duration only. #### What is hypercare in an ERP project? **Answer:** Hypercare is the intensive support period after go-live, when the project team, partner and key users resolve issues quickly and help users adapt. It ends when the system is stable and support moves to normal operations. #### What SLAs should we use in hypercare? **Answer:** A typical scheme is a response within an hour and a workaround or fix within four hours for severity 1, with one working day for severity 2, and a few days for severity 3. Set them with the business and make sure support staff can meet them. #### Should the project team or the support team own issues? **Answer:** During hypercare the project team and partner own most issues alongside the new support team, which learns by shadowing. By the exit date, ownership and the log move fully to the support organisation. ## Search terms erp hypercare issue log, hypercare issue log template, post go live issue tracker erp, erp hypercare support plan, hypercare log excel, go live issue log template, erp stabilisation tracker, erp hypercare exit criteria --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json