How to use the Change Request Generator.
A change request should explain the baseline, requested difference and effect. Approval should cover the impact, not merely acknowledge the new idea.
Make the workflow fit your task.
Describe the approved baseline and requested difference, then assess scope, effort, dependencies and delivery impact. Present the decision needed and keep the proposed change separate from work already authorized.
- What you provide
- Requested change and baseline project plan.
- What you get
- Impact summary, alternatives and approval questions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Approved site scope has three pages. Client requests a fourth FAQ page. Content, effort and delivery impact have not yet been estimated. Draft a change record.
Completed example
Baseline: three agreed pages. Requested change: add one FAQ page. New inputs needed: approved questions and answers, design requirements and acceptance criteria. Impact to assess: content preparation, implementation, review effort and delivery date. Decision required: approve the added scope and its estimated commercial and schedule effects before work begins. Status: proposed; no approval or estimate is implied.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does acknowledging a request mean approving the change?
No. Record the impact and obtain the decision required by the project's process before treating the new work as committed.
Why is the change request hard to approve or reject?
Specify the added deliverable and its consequences. A request framed only as an idea does not reveal the trade-off.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑