Document that something worked in one release and broke in the next
Draft before-and-after regression material covering scope and missing comparison tests.
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: aligns the releases and drafts, you check
Claude builds the release comparison table, then drafts the regression material in the same chat. You check both stages.
You
Collect the case files
Claude
Align the releases
You
Check the worksheet
Claude
Draft the scope
You
Check and decide
Have ready: customer cases, release evidence, approved rules
Use:You
The customer cases, the supplied release comparison evidence, and the approved rules, scope and as-of dates.
Check
Check nothing needed for the task was removed and source IDs are unchanged. Never paste credentials or full payment details.
Align steps and outcomes by release
Use:Claude
Upload the files to one Claude chat; ask it to align comparable steps and outcomes by release in one table, returned as chat text.
Details
What to paste into the tool
Task: Evidence worksheet as a table in the chat reply with row IDs, source references, original values, status and unresolved gaps. Attached are the supplied files. Build a worksheet: one row per item, stable row ID, source file and location, exact quote or original value, applicable rule or version, confirmed or reported status, unresolved gap. Align comparable steps and outcomes by release in separate columns. Give every difference its version evidence. Do not state a cause; correlation is not cause. Use only the supplied files. Keep every source ID, quote or original value, rule or version reference and as-of date exactly as supplied. List anything missing, contradictory or unchecked as unresolved; do not fill gaps by inference. Do not repeat passwords, authentication codes, session tokens or payment details, and keep customer details to the minimum needed. If sources or a qualified reviewer are missing, label the output incomplete. Do not send, publish, assign, execute or commit anything. Return the worksheet as a table in the chat reply; do not create or return a file and do not run code.
Check the worksheet and correct it
Use:You
Check every worksheet row against the originals and correct it.
Check
Check claims, values, chronology and rule applicability against the originals for this case: Workflow worked before an update and now fails. Do not fill missing or contradictory facts by inference.
Draft the regression scope and missing tests
Use:Claude
In the same chat, ask for the regression scope and missing comparison tests from the corrected worksheet.
Details
What to paste into the tool
Task: Draft before-and-after regression packet; Explicit unresolved questions and a proposed next human decision, not an executed action. Using only the corrected worksheet, draft the before-and-after regression packet. Scope the regression, list missing comparison tests, give version evidence for each difference and do not assert a cause. State unresolved questions and a proposed next human decision; do not execute or commit anything. Use only the supplied files. Keep every source ID, quote or original value, rule or version reference and as-of date exactly as supplied. List anything missing, contradictory or unchecked as unresolved; do not fill gaps by inference. Do not repeat passwords, authentication codes, session tokens or payment details, and keep customer details to the minimum needed. If sources or a qualified reviewer are missing, label the output incomplete. Do not send, publish, assign, execute or commit anything. Return the draft as chat text; do not create or return a file and do not run code.
Check the draft and decide next steps
Use:You
Check the draft against the originals and decide what, if anything, happens next.
Check
Check each difference has version evidence; correlation is not asserted as cause. Confirm the evidence and draft; completion is preparation, not downstream execution. Check the draft text stays inside the worksheet rows. Nothing is sent, filed, assigned or committed by this path; any later action is approved separately.
ChatGPT: builds the table and drafts, you check it
ChatGPT builds the table, then drafts the regression material from your checked table and outline. You check each stage.
You
Collect the case files
ChatGPT
Build table and draft
You
Check and decide
Have ready: customer cases, release evidence, approved rules
Use:You
The customer cases, the supplied release comparison evidence, and the approved rules, scope and as-of dates.
Check
Never paste credentials or full payment details.
Build the table and draft the material
Use:ChatGPT
Ask ChatGPT to build the evidence worksheet from the case material, then draft the regression material from the checked table and an outline you supply.
Details
What to paste into the tool
Task: Draft evidence worksheet aligning comparable steps and outcomes by release. Use only the supplied material. Give each row a row ID, the source location and the original value, exactly as supplied. Do not fill gaps by inference; record missing or contradictory facts as unresolved rows. Keep every source ID, quote, original value, rule or version reference and as-of date exactly as supplied. Do not repeat passwords, authentication codes, session tokens or payment details, and keep customer details to the minimum needed. Do not send, publish, assign, execute or commit anything.
Task: Draft before-and-after regression packet; Unresolved questions and a proposed next human decision. Attached are a checked evidence table and an outline for the before-and-after regression packet. Apply the outline to the table. Show each before-and-after difference with its version evidence and list missing comparison tests. Do not assert a cause. Cite the row ID for every statement and list unresolved questions. Use only the supplied files. Keep every source ID, quote or original value, rule or version reference and as-of date exactly as supplied. List anything missing, contradictory or unchecked as unresolved; do not fill gaps by inference. Do not repeat passwords, authentication codes, session tokens or payment details, and keep customer details to the minimum needed. If sources or a qualified reviewer are missing, label the output incomplete. Do not send, publish, assign, execute or commit anything.
Check the table and draft against the originals
Use:You
Check the table and the draft row by row against the originals; decide what, if anything, happens next.
Check
Check each statement cites a row ID that supports it; delete extra statements.
Gemini Notebook: quotes the passages, you write the rest
Gemini Notebook only locates quoted passages with citations. You build the worksheet and write the regression material yourself.
You
Load the sources
Gemini Notebook
Quote the passages
You
Build the worksheet
You
Draft the scope
You
Check and decide
Have ready: customer cases, release evidence, approved rules
Use:You
The customer cases, release comparison evidence and approved rules. Load only the sources for one release at a time into a notebook.
Check
Check your organisation allows the files to be uploaded to this tool. Check nothing needed was removed; source IDs unchanged; no password, code, token or payment detail remains.
Quote the passage for each item
Use:Gemini Notebook
Ask one targeted question per item and read the cited passages.
Details
What to paste into the tool
Task: Answers with citations to quoted source passages. For each step and outcome in this release, quote the passage that supports the answer and name its source. If the sources do not answer it, say so. Do not explain causes or motives, and do not add anything not in the sources. Do not infer causes beyond the sources. If sources or a qualified reviewer are missing, label the output incomplete. Do not send, publish, assign, execute or commit anything.
Build the worksheet from the checked quotes
Use:You
Copy the checked quotes and source references into your own worksheet; mark each confirmed or reported.
Check
Check claims, values, chronology and rule applicability against the originals for this case: Workflow worked before an update and now fails. Do not fill missing or contradictory facts by inference.
Draft the regression scope yourself
Use:You
Draft the regression scope and missing comparison tests yourself, with no AI drafting step.
Check
Check each statement cites a worksheet row.
Check the draft and decide next steps
Use:You
Check the draft against the worksheet and the originals; decide what, if anything, happens next.
Check
Check the evidence and draft; confirm completion is preparation, not downstream execution.
Compare the three approaches
Option A: Claude: aligns the releases and drafts, you check
Best when: One assistant takes the files through both stages
What it does: Claude builds the table and drafts; you check
Strong at: Worksheet and draft stay in one chat as text
Limit: Non-PDF files give extracted text only, not images
Free plan: Yes, limited (5-hour and weekly caps)
Option B: ChatGPT: builds the table and drafts, you check it
Best when: The tool builds the table and draft; you check
What it does: ChatGPT builds and drafts; you check each row
Strong at: The tool sees the checked table, not raw originals
Limit: Every row needs checking against the originals
Reviewer checks every row and statement against the supplied originals.
No password, code, token or payment detail is entered or reproduced.
Missing or contradictory facts stay marked as unresolved.
Nothing is sent, filed, assigned or committed; any later action needs separate approval.
Each difference carries version evidence and correlation is not asserted as cause.
Suggestions and preparation only. Do not send, publish, change records or accounts, assign work, execute code, initiate a purchase, or commit a remedy or deadline. A human separately approves any downstream action.
Check the result against your original inputs. Approve it before sharing or acting.
What still needs checking
Whether the release comparison evidence supplied is complete for the workflow in question
Which customer cases the engineer treats as in scope