AI Prompt for Business Analysts: As-Is To-Be Gap Analysis

Prompt

Act as a senior business analyst who runs process improvement workshops and turns messy as-is notes into a gap analysis that sponsors can approve and delivery teams can build from.

Inputs:
- Process name, trigger, end point, and the business goal behind the change: [ProcessScope]
- Current steps as described by the people who do them, including workarounds and spreadsheets: [AsIsNotes]
- Pain points, complaints, and any measured numbers (cycle time, error counts, volumes) with their source: [PainPointsAndMetrics]
- What good looks like according to the sponsor: [ToBeVision]
- Systems, roles, and teams involved: [SystemsAndRoles]
- Fixed limits such as budget, deadline, regulation, or systems we cannot replace: [Constraints]
- Output format: [Format]

Generate:
1. A scope statement for the process: trigger, end point, in scope, out of scope.
2. An as-is step table from AsIsNotes: step number, actor, action, system or tool, handoff, and a workaround flag. Quote the note a step came from when it is ambiguous.
3. A pain point to root cause map: each pain point, the step where it starts, and the likely cause type (process, people, technology, data, or policy). Label each cause as stated by stakeholders or as your hypothesis.
4. A to-be step table from ToBeVision and Constraints, with removed steps listed separately and new steps marked NEW.
5. A gap analysis table: as-is, to-be, gap, gap type, and the change needed to close it.
6. Numbered requirements derived from the gaps: business requirements (BR), functional requirements (FR) written as "The system shall...", and non-functional requirements (NFR), each traced to a gap row.
7. Two or three user stories with Given, When, Then acceptance criteria for the highest value functional requirements.
8. A RACI for the to-be process from SystemsAndRoles.
9. Measures of success: use only metrics from PainPointsAndMetrics as baselines; where none exists, write BASELINE NEEDED and say how to collect it.
10. Risks, assumptions, and open questions for the next workshop, each with an owner role.

Constraints:
- Do not invent volumes, durations, costs, or savings.
- Keep requirements testable and free of product names unless the input names the system.
- No em dashes.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

AI Prompt for Business Analysts: As-Is To-Be Gap Analysis - Result

Examples

Example Input

ProcessScope: Vendor invoice approval at a regional food distributor. Starts when an invoice arrives in the AP inbox, ends when it is approved for payment. Goal: stop paying late and losing early payment discounts.
AsIsNotes: AP clerk downloads PDF invoices from the shared inbox and keys them into the ERP. Clerk emails the PDF to the buyer who placed the order. Buyer checks it against the PO and receiving slip from the warehouse, which is a paper copy scanned weekly. Buyer replies "ok" by email. Clerk tracks status in a spreadsheet called Invoice Log. Invoices over $10,000 also need the controller, who approves in a batch on Fridays.
PainPointsAndMetrics: Controller says about 30 invoices a month miss early payment terms (her count from the Invoice Log for August). Buyers say invoice emails get buried. Warehouse scans arrive up to a week late.
ToBeVision: Invoices route automatically to the right approver, matched to PO and receipt, with status visible to everyone.
SystemsAndRoles: ERP (keeps POs and vendor master), shared Outlook inbox, Invoice Log spreadsheet. Roles: AP clerk, buyers, warehouse receiving lead, controller.
Constraints: Must keep the current ERP. Approval limits stay as they are. Go live before year end close.
Format: sections 1 to 10, tables where useful

Example Output

1. SCOPE
Trigger: invoice lands in the AP inbox. End: invoice approved for payment. In: capture, matching, routing, approval, status. Out: payment runs, vendor onboarding.

2. AS-IS STEPS
| # | Actor | Action | Tool | Handoff | Workaround |
| 1 | AP clerk | Download PDF, key into ERP | Inbox, ERP | | |
| 2 | AP clerk | Email PDF to buyer | Outlook | to buyer | Yes |
| 3 | Buyer | Match to PO and receiving slip | ERP, scans | | Yes ("paper copy scanned weekly") |
| 4 | Buyer | Reply "ok" | Outlook | to clerk | Yes |
| 5 | AP clerk | Update status | Invoice Log | | Yes |
| 6 | Controller | Approve over $10,000 on Fridays | | to clerk | |

3. ROOT CAUSES
- Missed early payment terms (step 6, steps 2 to 4): policy (weekly batch) and process (email routing). Hypothesis.
- Buried emails (step 2): process, stated by buyers.
- Late receipts (step 3): data, receipts not in ERP until scanned. Stated.

4. TO-BE STEPS
1 Capture invoice into ERP. 2 NEW: system matches invoice to PO and electronic receipt. 3 NEW: route exceptions to buyer, amounts over $10,000 to controller. 4 Approve in queue with due date shown. 5 NEW: shared status view.
Removed: email to buyer, "ok" reply, manual Invoice Log.

5. GAP TABLE
| As-is | To-be | Gap | Type | Change |
| Receipts scanned weekly | Receipt recorded at dock | No timely receipt data | Data | Warehouse records receipts in ERP same day |
| Email routing | Rule based queue | No routing rules | Technology | Configure approval workflow |
| Friday batch | Approve by discount date | Batch policy | Policy | Controller reviews queue daily or delegates within limits |
| Spreadsheet status | Shared status view | No single status | Process | Retire Invoice Log |

6. REQUIREMENTS
BR-1 Approve eligible invoices before early payment terms expire. (Gaps 1 to 3)
FR-1 The system shall match invoices to PO and receipt and flag mismatches. (Gap 1)
FR-2 The system shall route invoices over $10,000 to the controller. (Gap 2)
FR-3 The system shall show discount due date on each queued invoice. (Gap 3)
NFR-1 Status shall be visible to AP, buyers, and the controller. (Gap 4)

7. USER STORIES
As a controller, I want invoices over $10,000 queued with their discount date so I approve them on time.
Given an invoice over $10,000 is matched, When it enters the queue, Then the controller sees it with its discount due date.

8. RACI
Capture: R AP clerk, A controller. Receipt entry: R receiving lead. Exceptions: R buyer, C AP clerk. Approval over $10,000: R/A controller.

9. MEASURES
Missed early payment invoices: baseline about 30 a month (controller, August Invoice Log). Cycle time: BASELINE NEEDED; sample 50 invoices from the log, inbox date to approval date.

10. RISKS AND QUESTIONS
- Risk: warehouse may not enter receipts same day. Owner: receiving lead.
- Assumption: the ERP can host an approval workflow. Owner: ERP admin, confirm.
- Question: may the controller delegate approvals during close? Owner: controller.