QAD Customization Change Request Template
Small changes to a customized ERP are where regressions begin. This form makes every QAD customization request state its reason, affected objects, tests, rollback and approvals before it reaches production.
Fill in
QAD Customization Change Request Template
Change Request CR-2026-0147
Title: Add customer PO number to pick list report Requested by: Warehouse supervisor Date raised: 2026-10-20 Type: Report change Priority: Normal
Business reason
Pickers cannot match shipments to customer orders without the customer PO number, causing mispicks.
Objects affected
Custom pick list report program and its output template.
Impact assessment
| Question | Answer |
|---|---|
| Which users or departments are affected? | |
| Does it change data or only display it? | |
| Does it touch interfaces or scheduled jobs? | |
| Does it affect period close or reporting? | |
| Is there a standard alternative? | |
| Effect on upgrade or migration plans? |
Test plan
Run report for three orders in the test domain, compare to expected output, check performance with a full day of orders.
Rollback plan
Restore the previous program version from source control and clear cached output.
Implementation
| Step | Environment | Date | Done by |
|---|---|---|---|
| Build and unit test | Development | ||
| User acceptance test | Test | ||
| Release | Production | ||
| Post-release check | Production |
Approvals
This form is a generic change control starting point. Align it with your own change management policy and, for regulated environments, your quality system requirements.
Automate your change documentation
Optional: we can discuss generating impact notes from your custom code and usage logs.
Optional. The tool and every export work without this. No spam.
How to use the form
The requester fills the business reason and desired result. The QAD administrator or developer completes the affected objects, impact questions and test plan. Approvals are collected before the change is moved to the test environment and again before production. Export the finished form as PDF and file it with the change record so audit questions have an answer later.
The impact questions that matter
Most incidents come from changes someone thought were cosmetic. Always ask whether the change writes data or only reads it, whether any interface, scheduled job or downstream report depends on the object, and whether period close or financial reporting uses it. Also ask whether the same need can be met with standard functionality, because every custom object adds to future upgrade and migration effort.
- Read-only changes still need performance testing.
- Interface changes need partner notification.
- Check month end and year end dependencies.
Test and rollback evidence
A test plan that says 'tested OK' is not evidence. Record the cases, the data used and the result. For rollback, state precisely how to return to the prior state: the source version to restore, any data corrections and who runs them. Emergency changes should use the same form completed after the fact, within an agreed time.
Common mistakes
Verbal requests, undocumented fixes directly in production and approvals by email threads nobody can find are the usual failures. Another is not recording the object version, which makes rollback guesswork. Keep the form short enough that people actually complete it.
Frequently Asked Questions
Is this specific to QAD?
The structure is generic change control, with field names suited to QAD customizations such as programs, reports and interfaces. You can reuse it for any ERP by editing the labels.
Do emergency changes need approval?
They still need authority, but it can be given verbally by a named approver. Complete the form afterwards and review the change at the next change meeting.
Should every report change use this form?
Use a lighter path for trivial cosmetic edits if your policy allows, but anything affecting data, finance, compliance or interfaces should have a full request.
Where do I store completed forms?
Store them with the change record in your ticketing or document system, linked to the source version. Auditors typically ask for the reason, approval, test evidence and release date.
Netray can help document your existing custom QAD programs with on-prem AI so the objects affected section is faster and more complete.
Related Tools
QAD EE Custom Code Inventory Worksheet
Editable inventory of QAD customizations with type, use, complexity and retire or rebuild decision, totalling rebuild effort.
ERP Migration & SelectionQAD Mock Conversion Load Log Worksheet
Editable log of data objects per mock conversion cycle with extracted, loaded and rejected counts and an automatic load percentage.
ERP Migration & SelectionIFS Cloud Implementation Statement of Work Template
Document template for an IFS Cloud implementation statement of work covering scope, deliverables, assumptions, roles, change control and acceptance.
MES & Shop FloorPlex Go-Live Readiness Sign-Off Template
Go or no-go document for a Plex site rollout covering data, training, integrations, shop floor hardware, support and rollback, with sign-off lines.