01
Field Map
One row per field: its type, whether each export path returns it, whether it is history or a snapshot of right now, which pull to take it from, and what specifically breaks if it comes from the CSV. Build it before touching the data, because it is the one artefact that stays true after the data changes.
02
Ticket Register
The deliverable. One row per ticket, carrying the multi-select, multi-line text and custom date fields recovered from the JSON export. Durations arrive in native minutes instead of rounded hours, timestamps carry both clocks, and each snapshot field sits next to its value when the work was done.
03
CSV to JSON Reconciliation
An arithmetic bridge from what the file returned to the population the question was about, one line per named reason, balancing to zero. Nothing downstream is quotable until it balances. It also records the clock and pull moment for each path, since two pulls an hour apart are two datasets.
04
Restated Figures
The sheet anyone who read the original report needs. Per published number: the corrected value, the documented export behaviour that moved it, and whether the row sets agree. Ranked by consequence rather than by size of move, so the figure that changed a decision comes first.
05
Export Procedure
The three pulls, in order, with what each one is for and what to record about it. Widen the range by a month either side, take the cursor form of the incremental endpoint rather than the time-based one, and side-load the metric records in the same pass.
06
Field Completeness Note
Which fields each path omits and what a report loses per omission, including the four separate reasons a Tags column is not the multi-select field behind it. Pairs with the naming convention pack when the fix is the tag namespace rather than the report, and with the support ticket categorization template when the recovered field turns out to hold categories nobody can apply.
07
Measurement Definitions
Every reported figure with the timestamp that selects its rows, the clock it is computed on, the unit it comes from, and whether its field is history or a snapshot. The metric definitions pack does the same job across the whole business, and the SLA reporting template applies the same discipline to a breach rate specifically.
08
Reconciliation Findings
The worked example end to end: nine reported figures, what each one actually was, and the documented behaviour behind each move. Written so it reads as an explanation rather than an accusation against whoever built the original report.
Support Ticket Export Template