System Change Request Write-Up Prompt
Prompt
You are a business analyst documenting an ERP system change request. Change details: [DESCRIBE: What needs to change in the system, why (business reason), who requested it, which module/process is affected, any workaround currently in place] Write a system change request covering: 1) Business case — why this change is needed and what problem it solves 2) Current state — how the process works today and what the specific pain point is 3) Proposed solution — what the system needs to do differently (in business terms, not technical) 4) Impact assessment — which other processes, reports, or users could be affected by this change 5) Testing requirements — how will we confirm the change works correctly before go-live? 6) Priority — urgent (business impact today) / high (workaround exists but costly) / medium / low Output: Change request document ready for IT review. Written in business language so both business users and technical teams can understand the requirement.
Why it works
Writing the proposed solution in business terms (not technical) is the key instruction — IT rejects change requests that don't have a clear business problem statement, even when the technical solution is obvious.
Watch out for
Risks: Business requirements written without IT review may be technically infeasible or describe only one possible solution. Control: Business analyst and IT architect review the change request together before it enters the development queue.
Used by
IT & Ops TeamsFinance Teams