Workshop-to-Deliverable Chain: Turn One Workshop's Notes into a Gap List, FDD, and Test Script

What This Builds

A single Claude Project holds your engagement's document templates and turns one workshop's raw notes into four drafts in sequence: a gap list entry, a functional design document, a UAT test script, and a training job aid. A discovery day that used to leave you with a page of shorthand and a week of catch-up writing instead ends with four documents ready for your own edit pass.

Prerequisites

• You have used a Claude Project before, or are willing to create one following Claude's own setup steps.
• You have your client's document templates on hand: the gap list format, the functional design document (FDD) template, and the test script format the project already uses.
• You have a Pro subscription, since a Project needs enough context room to hold your templates plus a full workshop's notes.
• Total ongoing cost: $20/month per month for Pro. No other subscription is required for this build.

The Concept

A Claude Project works like a filing cabinet that also drafts for you. Load it once with your templates, and it stops needing to be reminded of the format every time you ask for a document. Feed it a workshop's raw notes and ask for the next document in the chain: gap list first, then the design document for whatever gets approved, then the test script, then the training aid. Each step reads what came before it, so a gap you defined in step one shows up correctly in the test script you ask for in step three.

Build It Step by Step

Part 1: Create the Project and Load Templates

1. In Claude, start a new Project and name it for the client and module, for example "Meridian Retail, Order-to-Cash."
2. Open the Project's knowledge section and upload blank versions of your client's gap list template, FDD template, test script template, and training job aid template. Strip any real client data from these files before uploading. A blank template with placeholder headers is all the Project needs.
3. If your firm has a house style for these documents (a preferred tone, a required disclaimer, a numbering convention), add a short style note as a separate uploaded file.

Part 2: Write the Chain Instructions

Open the Project's custom instructions field and paste something close to this, adjusted for your client's actual template headings:

You are helping an ERP implementation consultant turn workshop notes into a sequence of deliverables for one module at a time. Work in this order and stop after each step for review before continuing:

1. Gap List Entry: Given raw workshop notes, sort each requirement into Fit, Gap, or Needs Follow-Up against the named ERP platform's standard functionality. Use the uploaded gap list template's columns exactly.
2. Functional Design Document: For each item marked Gap and approved by me, draft a full FDD using the uploaded FDD template's section headings. Mark anything needing a screenshot or exact field name as [NEEDS CONFIRMATION].
3. Test Script: For each approved FDD, draft a UAT test script in the uploaded test script format, with numbered steps, expected results, and a pass or fail column.
4. Training Job Aid: For each configured process the test script confirms, draft a one-page job aid for the end-user role who will use it.

Never invent a specific field name, button label, or menu path you were not given. Use [NEEDS CONFIRMATION] instead of guessing.

Save the instructions and send a short test message asking for a sample gap list entry from a made-up requirement. Confirm the Project follows your template's column order before you trust it with a real workshop.

Part 3: Run a Real Workshop Through the Chain

1. After a workshop, type up or paste your notes with the client's company name and real stakeholder names removed. Use generic role titles (Warehouse Manager, AR Clerk) and the platform name instead. This Project keeps everything you feed it for as long as it exists, not just for one session, so treat the sanitizing step as mandatory for every workshop, not only the first one.
2. Ask for step 1, the gap list. Read the output and correct anything wrong. Then tell the Project which items are approved.
3. Ask for step 2 for each approved gap, review before moving on, and fill in anything marked [NEEDS CONFIRMATION] yourself.
4. Repeat for steps 3 and 4, reviewing each draft before it becomes the input for the next one. Nothing in this chain reaches the client until you or your engagement manager has read and corrected every stage. The Project drafts. You and your engagement manager decide what is accurate enough to send.
5. Before the test script goes to whoever runs UAT, walk through its first scenario yourself in the actual sandbox and confirm the expected result matches what the platform really does. Claude drafts from your notes, not from testing the live system, so a script can read as complete and still be wrong about what the system actually does.

Real Example: NetSuite Order-to-Cash Returns Gap

Setup: A Project named "Meridian Retail, Order-to-Cash" holds NetSuite-specific gap list, FDD, test script, and job aid templates.

Input: Workshop notes: "Client wants a restocking fee auto-applied on returns older than 30 days. Standard NetSuite return authorization has no built-in aging rule for fees."

Output: The Project drafts a gap entry (Gap: standard RMA has no aging-based fee logic), an FDD proposing a saved search plus a workflow action to apply the fee, a test script with steps to create a return at day 15 and day 45 and confirm the fee only applies to the second, and a one-page job aid for the AR clerk who processes returns.

Time saved: Work that would normally spread across a week of evening writing sessions comes out as four reviewable drafts in one afternoon, leaving editing time instead of blank-page time.

What to Do When It Breaks

• The Project drifts from your template's format after several workshops → Re-upload the template file and remind it in your next message to use the exact column order from the uploaded gap list template.
• Drafts sound generic instead of tied to the actual target module → The Project only knows what you told it. Check any Fit or Gap call against the platform's own documentation or its native AI assistant (SAP Joule, NetSuite's help center) before treating it as final.
• Notes from two different modules start blending together in one Project's answers → Split into a second Project. One module per Project keeps the chain's memory clean.

Variations

• Simpler version: Run the same four prompts as separate one-off chats instead of a Project. You lose the persistent template memory and have to re-paste the format each time, but it still works for a single workshop.
• Extended version: Add a fifth step to the chain that drafts a RAID log entry for any gap flagged as high-risk, so the risk register gets seeded from the same notes.

What to Do Next

• This week: Set up one Project for your current highest-priority module and run one real workshop's notes through the full chain.
• This month: Create a second Project for another module and compare how much editing each draft still needs.
• Advanced: Feed the approved test scripts into a test management tool import instead of copying them by hand.

Advanced guide for ERP Implementation Consultant professionals. These techniques use more sophisticated AI features that may require paid subscriptions.