Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
Claude builds the scenario spreadsheet and drafts the clearance options in one chat. You correct between the stages.
You: Prepare input pack
Claude: Build scenario table
You: Correct row by row
Claude: Draft clearance options
You: Check and decide
Use: You
Have ready: backlog counts and age bands, throughput ranges, intake forecast, capacity scenarios, planning horizon and work calendar. Mark unstated throughput as not stated.
Check nothing outside the supplied inputs is added.
Use: Claude
Ask Claude to build the stock, intake and throughput scenario table by capacity scenario, horizon and calendar, with time-to-clear or explicit not-stated entries.
What to paste into the tool
Task: Dynamic starting-stock/intake/throughput scenario table by offered capacity scenario, horizon and work calendar with time-to-clear calculations or explicit not stated entries. Use only the attached input pack. Build the scenario table by offered capacity scenario, horizon and work calendar. Where throughput is not stated, write not stated and do not estimate a value. Show time-to-clear calculations where the inputs support them.
Use: You
Check the table row by row against the original inputs and correct it in place.
Compare identifiers, definitions, dates and ambiguous claims against the original inputs.
Use: Claude
Ask Claude to draft the clearance options from the corrected table, leaving unresolved throughput unresolved and listing unresolved fields with references.
What to paste into the tool
Task: Draft backlog clearance options retaining queue evolution, capacity assumptions, intake, horizon, work calendar and unresolved throughput; Explicit unresolved fields and source references. Use only the corrected scenario table and the supplied inputs. Keep queue evolution, capacity assumptions, intake, horizon and work calendar visible, leave unresolved throughput unresolved, and list unresolved fields with their source references.
Use: You
Check the draft against the requirements; confirm any next action separately. No staffing or clearance-time promise is made.
Service lead checks observed rates, work calendar and capacity scenarios; unstated throughput stays unstated; no staffing or clearance-time promise.
You build the scenario table with your own formulas. Gemini only drafts the options from that checked table.
You: Build table yourself
Gemini: Draft clearance options
You: Check against table
Use: You
Build one row per capacity scenario in your own spreadsheet: stock, intake, throughput or not stated, horizon, calendar, time to clear. Write the formulas yourself.
Compare identifiers, definitions, dates and ambiguous claims against the original inputs.
Use: Gemini
Ask Gemini to draft the clearance options from the checked table, leaving unresolved throughput unresolved.
What to paste into the tool
Task: Draft backlog clearance options retaining queue evolution, capacity assumptions, intake, horizon, work calendar and unresolved throughput; Explicit unresolved fields and source references. Use only the pasted checked table and the supplied inputs. Keep queue evolution, capacity assumptions, intake, horizon and work calendar visible, leave unresolved throughput unresolved, and list unresolved fields with their source references.
Use: You
Compare the draft with the hand-built table line by line and fix any drift; confirm any next action separately.
Service lead checks observed rates, work calendar and capacity scenarios; unstated throughput stays unstated; no staffing or clearance-time promise.
ChatGPT computes the scenario table with readable Python. After your check, Notion AI drafts the options in a separate workspace.
You: Select supplied inputs
ChatGPT: Compute with code
You: Check, carry over
Notion AI: Draft the options
You: Check and decide
Use: You
Have ready: backlog counts and age bands, throughput ranges, intake forecast, capacity scenarios, planning horizon and work calendar. Mark unstated throughput as not stated.
Check nothing outside the supplied inputs is added.
Use: ChatGPT
Ask ChatGPT to build the scenario table with Python it shows you: by capacity scenario, horizon and calendar, not stated where throughput is unstated.
What to paste into the tool
Task: Dynamic starting-stock/intake/throughput scenario table by offered capacity scenario, horizon and work calendar with time-to-clear calculations or explicit not stated entries. Use only the attached input pack. Build the scenario table by offered capacity scenario, horizon and work calendar, and show the Python used. Where throughput is not stated, write not stated and do not estimate a value.
Use: You
Check the table against the originals and correct it before it leaves ChatGPT; carry over the checked table with the supplied inputs.
Compare identifiers, definitions, dates and ambiguous claims against the original inputs.
Use: Notion AI
Ask Notion AI to draft the options from the checked table, keeping unresolved throughput unresolved.
What to paste into the tool
Task: Draft backlog clearance options retaining queue evolution, capacity assumptions, intake, horizon, work calendar and unresolved throughput; Explicit unresolved fields and source references. Use only the pasted checked table and the supplied inputs. Keep queue evolution, capacity assumptions, intake, horizon and work calendar visible, leave unresolved throughput unresolved, and list unresolved fields with their source references.
Use: You
Check the draft against the requirements; confirm any next action separately. No staffing or clearance-time promise is made.
Service lead checks observed rates, work calendar and capacity scenarios; unstated throughput stays unstated; no staffing or clearance-time promise.
Best when: You want a downloadable scenario sheet and drafted options
What it does: Claude builds and drafts; you check twice
Strong at: The sheet comes back with working formulas
Limit: A first-stage error can carry into the draft; check carefully
Free plan: Yes
Best when: You want to control every formula, tool only writes
What it does: You build the table; Gemini drafts from it
Strong at: Every value and formula is placed by you
Limit: First stage is hand work; slower on large inputs
Free plan: Yes
Best when: You want readable calculation code, drafting in a workspace
What it does: ChatGPT computes, you check, Notion AI drafts
Strong at: The Python can be audited and re-run before reliance
Limit: Two tools mean a manual copy between workspaces
Free plan: ChatGPT: Yes, limited (uploads and analysis capped); Notion AI: Paid plan needed
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Deciding between ChatGPT and Claude for this? See the comparison.
Named human compares every identifier, date, number and uncertain claim with the original inputs before the draft moves on.
Missing facts stay not stated; nothing is sent, published, assigned or authorised.
Cut down operational and personnel data pasted into any tool.
Check the result against your original inputs. Approve it before sharing or acting.