Change request
State what should change and why, quantify the impact on scope, schedule, cost and quality, and help reviewers approve or reject it.
Prompt
Write a change request: just before launch, the business wants shoppers to be able to stack coupons at checkout on our e-commerce site. Purpose: let reviewers decide whether to approve the change. Requirements: give the request ID and details, compare the requirement before and after, explain the reason and the cost of not changing, tabulate the impact on scope, schedule, effort and cost, quality and risk, offer alternatives with pros and cons, outline the implementation plan if approved, and include an approval and sign-off section. Use concise headings and tables in a professional, crisp tone.
- Source
- Ofox
How to use
- 1
Tap “Make one like this”
Ofox Chat opens with this document’s structure ready to go. Sign in first if you haven’t.
- 2
Make it yours
Edit the highlighted parts of the prompt to swap in your own details.
- 3
Send and create
Send it and Ofox Chat writes the full document for you to download. Keep chatting to revise it.
FAQ
What kind of file do I get?
A complete, downloadable document (Word or PDF) — not just a block of text in the chat.
Do I need to prepare anything?
No — you can send it right away and Ofox Chat writes a first version from the template. Add your background, data or existing documents (paste them in, or upload PDFs, Word files and more) and the result fits your situation much better.
Can I edit the prompt?
Yes. The prompt goes into the Ofox Chat input box — swap in your own topic, add requirements or drop what you don’t need before sending.
Can I copy and use the prompt directly?
Yes. Tap “Copy” on the prompt card to get the plain text — it works in other AI writing tools too.
More like this
More Projects prompts- Project weekly reportProject status on one page: this week's progress, milestones vs. plan, risks and issues, next week's plan and what needs support.Projects
- Project charterExplain why the project matters, what it covers and what it costs, weigh benefits and risks, and help decision-makers approve it.Projects
- Project closure reportMeasure results, schedule and cost against the baseline, capture lessons learned and hand over open items so the sponsor can close the project.Projects
- Acceptance reportCheck each deliverable against the contract and acceptance criteria, log issues and fixes, and give a verdict both sides can sign.Projects
- Project kickoff briefKickoff materials covering goals, scope, milestones and roles, plus agreed meetings, reporting and escalation, so everyone is aligned from day one.Projects
- Statement of work (SOW)Set scope, deliverables, acceptance criteria, timeline and payment milestones so both sides know what gets done, when it's done and when it's paid.Projects
- Project comms planAgree who gets what information, when and how: stakeholder needs, a communication matrix, meeting and reporting cadence, and escalation paths.Projects
- Handover documentHand over system status, work in progress, routine operations, known issues, documents and access as checklists so the new owner can run it alone.Projects
- Bid evaluation reportIssue the evaluation committee's report: document the solicitation and compliance review, total each bidder's scores under the evaluation method, rank them and recommend an award.Projects
- Customer implementation planPlan how software goes live at a customer site: scope, phases, responsibilities on both sides, data migration, training and go-live acceptance, so everyone agrees on who does what.Projects
Have an idea of your own? Start creating
Describe the image you want in one sentence, and Ofox Chat creates it from scratch.