Create intermediate Works with: Any AI

Change Request Evaluation

Table output Has example

Decide whether to accept a change.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Evaluate a change request. The request: [CHANGE_REQUEST]. Requester and rationale: [REQUESTER_AND_RATIONALE]. Current plan, budget, and schedule: [CURRENT_PLAN].

Produce an impact assessment: scope affected; effort estimate (low, likely, high) with arithmetic; cost; schedule impact on the critical path; quality and testing; risks introduced; dependencies; benefits; and alternatives (do later, smaller version, trade for removing other scope).

Create a decision table: Option | Cost | Schedule | Benefit | Risk | Recommendation. Draft the change request form fields, a decision record (approved, rejected, deferred, who decided, date), and a reply to the requester (100 words) that is clear and respectful. Add a rule for emergency changes and a log to track the cumulative effect of changes (baseline vs current). Use only my data; label estimates.

Return a clear recommendation of accept, reject, defer, or accept with changes, with the one reason that decides it. Estimate the effect on the critical path in days, and show the arithmetic for cost as hours times rate plus any purchase.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Request: add a customer portal export (CSV) before launch.
Impact: scope +1 feature; effort 28 to 40 hours (likely 34) at 70 an hour = 2,380; schedule: critical path +3 days; testing +6 hours; risk: data privacy review; benefit: avoids manual exports for 15 customers.
Options: A accept now (+3 days, 2,380); B defer to release 2 (no impact); C smaller version (summary only, 12 hours, 840, +1 day).
Recommendation: C, then full export in release 2.
Decision record: C approved by sponsor, 18 June.
Reply to requester (about 90 words): "Thanks for the request. A full export adds three days; a summary export fits with one day. We will deliver the summary now and the full export in release 2."
Emergency rule: sponsor can approve within 24 hours.

• change-request