Show how much of a metric's change comes from the new definition versus a real change

A draft definition bridge showing how much of the change comes from the rule and how much from the sample.

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 →

ChatGPT: applies both definitions and drafts the bridge

ChatGPT applies both definitions to your sample and drafts the bridge. You recompute rows by hand and check every number.

  1. You

    Prepare the sample and rules

  2. ChatGPT

    Draft worksheet and bridge

  3. You

    Recompute and check

  1. Have ready: the metric rules and ticket sample

    Use: You

    Take credentials and payment details out of the sample; keep ticket IDs; list both metric definitions, the cohort boundary and clock rules with their dates.

    Check

    Check nothing needed for the calculation was removed, the same sample serves both definitions, and no personal or payment detail remains.

  2. Draft the worksheet, then the bridge

    Use: ChatGPT

    Paste the sample, both definitions, cohort boundary and clock rules into one ChatGPT chat; ask for the worksheet, then the bridge from the checked worksheet.

    Details

    What to paste into the tool

    Apply the two supplied metric definitions below to the same ticket sample. For each row keep a stable row ID, the ticket ID and the original values exactly as supplied. Record both counts, the denominators and any excluded rows, showing the calculation so it can be checked. List rows with missing data as still to confirm; do not resolve missing facts by inference. Do not say performance improved or declined because of a rule change and do not infer staff performance or protected traits. Use only the supplied material. Do not send, publish, assign, execute or commit anything. Pasted below as text is a checked worksheet applying two supplied metric definitions to the same ticket sample. Do not calculate and do not write or run any code, including Python; work from the supplied figures only. If you start to run code, stop and say so. Draft a bridge that separates the effect of the definition change from the difference in the sample. Keep every ticket ID, row reference and original value exactly as supplied, state denominators, missing items and remaining differences, and do not say performance improved or declined because of a rule change. Use only the supplied files. 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. Use only the supplied metric definitions, cohort boundaries and clock rules; state denominators and missing data; do not infer staff performance or protected traits.

  3. Recompute rows and check the bridge

    Use: You

    Recompute a sample of rows by hand under each definition, correct in the same chat, then check the bridge against the sample and rules.

    Check

    Check denominators and missing items are stated, every number appears in the checked worksheet, and no code ran. Do not resolve missing facts by inference. Nothing is sent, published or changed; any later action is approved separately.

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.

Both calculations use the same cohort.

Denominators and not stated data are stated.

No performance improvement or staff or protected-trait inference is drawn from a rule change.

Nothing is sent, published or changed; any later action needs separate approval.

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
  • Rows with data missing for either definition
  • Whether clock rules were supplied for every timestamp used
  • Whether a second reviewer is available for path C

Share this page