Summarise a sudden jump in incoming tickets, with checked counts

A draft spike brief with reconciled counts and examples with customer details removed.

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: normalises the patterns and drafts the brief

Claude normalises the issue patterns, then drafts the spike brief separating pattern from root cause. You check both.

  1. You

    Assemble sources

  2. Claude

    Normalise patterns

  3. You

    Check the rows

  4. Claude

    Draft the brief

  5. You

    Confirm and label

  1. Assemble the originals into one source set

    Use: You

    Assemble the current and comparison exports, their category definitions and the approved rules, scope and as-of dates into one source set with stable IDs.

    Check

    Never paste credentials or full payment details. Confirm nothing outside the supplied case evidence and approved rules is included.

  2. Normalise the patterns into a worksheet

    Use: Claude

    Upload the source set to one Claude chat and extract the normalised issue patterns across the windows.

    Details

    What to paste into the tool

    Using only the uploaded files, build a worksheet. For each row give a source ID, the quoted span or original value, the rule or version reference, whether it is confirmed or only reported, and any gap. Do not fill gaps by inference.

  3. Check the worksheet and write corrections

    Use: You

    Check the worksheet row by row against the originals and write corrections.

    Check

    Compare extracted claims, values, chronology and rule applicability against the supplied originals. Do not resolve missing or contradictory facts by inference.

  4. Draft the spike brief

    Use: Claude

    In the same chat, give the corrected worksheet and ask for the volume-change brief separating pattern from root cause.

    Details

    What to paste into the tool

    Using only the corrected worksheet and the rules in the uploaded files, produce the draft. Mark anything not supported as not stated in the files and list the open questions and the proposed next human decision. Do not state an executed action, remedy or deadline.

  5. Check the brief and label gaps

    Use: You

    Preparation only: do not send, publish, change records or accounts, assign work or commit a remedy or deadline.

    Check

    Check counts reconcile and shared cause remains a hypothesis. Label the draft incomplete if a source or reviewer is missing. Check recipient scope and required authority; do not treat the draft as approval.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

Never paste credentials or full payment details.

Every claim is compared with the supplied originals and approved rules by the queue manager.

No send, publish, record or account change, assignment, code execution on the case, purchase, remedy or deadline; you approve any later action.

Customer details cut down; no passwords, codes, tokens or payment credentials in any upload or prompt.

Missing source or reviewer: return a labelled incomplete draft.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • 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.

Share this page