Records to explore
Initial requests, task or job records, correspondence, attachments, status changes, approvals, exception notes, handovers and close-out records. A case may span an inbox, spreadsheet, operational system and document folder.
A brief can focus on one record type or a connected set across several systems. The following families show the kinds of material that could be investigated, the relationships that may matter and the AI tasks an evaluation could test.
Link an enquiry, its correspondence, job records and close-out notes to reconstruct what happened, identify an outstanding action or explain an exception.
Initial requests, task or job records, correspondence, attachments, status changes, approvals, exception notes, handovers and close-out records. A case may span an inbox, spreadsheet, operational system and document folder.
Case identifiers, timestamps, document versions, the order of events and links between the request, action and result. A useful history may include failed attempts and unresolved issues as well as completed work.
Reconstruct a timeline; identify the next action supported by the current case; summarise a handover; explain a delay; compare a requested outcome with the recorded result.
How complete the history is, whether timestamps are reliable, which links are explicit and which have been inferred, and whether later information must be withheld when testing an earlier decision.
Connect emails, CRM notes and support threads to the relevant quote, order or issue, so an answer can recover the customer’s requirements and the commitments still open.
Email threads and attachments, internal messages, CRM notes, lead and opportunity histories, customer enquiries, support tickets, service notes and recorded follow-up actions.
Link a conversation to the relevant customer case, quotation, order, project or issue. Preserve thread order, attachment references and changes in status where the source allows it.
Retrieve an answer with evidence; extract a customer's requirements; identify outstanding commitments; classify an issue; summarise a long case; draft a response grounded in the authorised records.
Personal information, confidential negotiations, third-party correspondence and whether the business has authority for the intended use. A mailbox export does not establish permission to license everything inside it.
A customer request might start in a Salesforce case, be discussed in Slack and lead to a Jira issue, fix and follow-up. The useful bundle preserves the links between those records, the order of the discussion and any later correction. A proposed task could ask a model to identify the unresolved commitment and draft an evidence-backed reply. Case closure alone would not prove that the underlying problem was fixed.
The source check would establish whether comments, attachments and historical states survive export. These product names illustrate possible source systems; they do not imply a partnership, integration or access to a company’s records.
Connect specifications, quote revisions, supplier prices and accepted orders to explain a commercial change or identify which scope and price were agreed.
Enquiries, specifications, estimates, quotation versions, line-item prices, supplier price lists, proposals, scope changes, customer questions, accepted orders and relevant contract documents.
Match revisions to the original request, identify changed quantities or specifications, and connect the accepted offer to the order and subsequent fulfilment or project record.
Compare quotations; extract inclusions and exclusions; explain a price change; flag inconsistent quantities; identify the accepted revision; produce an evidence-backed scope summary.
Whether quoted and accepted prices are distinguishable, how discounts and tax are represented, whether supplier information can be shared and whether the acceptance record is present.
Link orders, invoices, credits and delivery or completion records to reconcile a charge and distinguish what was billed, adjusted or recorded as paid.
Purchase orders, sales and supplier invoices, credit notes, delivery or completion records, remittance information where appropriate, reconciliation notes and correspondence about disputed or adjusted charges.
Connect the ordered item or service to receipt or completion, invoicing, corrections and any recorded payment status. Keep quoted, invoiced, credited and paid amounts distinct.
Match documents; extract line items; reconcile totals; explain a credit; identify a missing reference; flag a discrepancy for review without inventing its cause.
Sensitive financial details, bank information and identifiers; consistent currencies and tax treatment; and whether the records actually establish payment or only an amount billed.
Connect purchase orders, stock movements, dispatch records and proof of delivery to trace a shortage, partial shipment, substitution or unresolved return.
Purchase requests, supplier quotations, purchase orders, stock records, goods-received notes, allocation and picking records, dispatch notes, manifests, proof of delivery, shortages, substitutions and returns.
Product or part identifiers, order lines, locations, batches where recorded, quantities and event dates. Link an exception to the original requirement and the actions taken to resolve it.
Reconcile ordered and received quantities; trace a shortage; compare promised and recorded delivery dates; identify an unresolved return; answer a stock or order-status question from the available evidence.
Inconsistent item codes, partial deliveries, stock snapshots versus transaction histories, missing events and commercially sensitive supplier or customer information.
Link product variants and catalogue versions to orders, shipments and support cases to answer specification questions or investigate a fulfilment or return issue.
Product descriptions, specifications, variants, catalogue revisions, stock and order exports, fulfilment events, return reasons, support tickets, FAQs and authorised product documentation.
Join product and variant identifiers to orders, shipment records, returns and support cases. Keep the product information that applied at the time of the transaction where it can be established.
For a Shopify-based business, connect the order and line items to the product variant and policy version that applied at purchase, then to fulfilment, support, returns and refunds. An orders CSV alone does not establish the complete case: order events, comments, attachments and helpdesk conversations need separate checks.
Answer specification questions; compare variants; extract product attributes; assess whether a support response uses the right product evidence; explain a return or fulfilment exception.
Rights to manufacturer content and product images, personal customer data, changing catalogue information and whether outcomes such as refund or replacement are explicitly recorded.
Connect drawing revisions, CAD files, CNC programmes, job cards and inspection records to check which requirement applied and how the recorded work relates to it.
Engineering drawings, CAD files or exports, revision histories, specifications, bills of materials, CNC programmes, setup sheets, tooling notes, job cards, inspection reports and non-conformance records.
Link the part and drawing revision to the quotation, production job, programme or setup and inspection outcome. The relationship between files can be as important as the files themselves.
Retrieve the applicable revision; compare requirements; identify a mismatch between a drawing and job instruction; connect an inspection finding to its source specification; summarise a technical change.
Customer and third-party intellectual property, file interpretability, units and revision control, and the availability of appropriate domain review. Historical programmes or instructions are not automatically safe or correct for execution.
Join production runs, machine and maintenance logs, quality checks and rework records to reconstruct a stoppage or investigate a recorded output or quality issue.
Production schedules, work orders, batch records, machine logs or sensor exports where recorded, downtime entries, material usage, scrap or rework records, quality checks, fault reports, diagnostic notes, parts selection, service reports and corrective-action notes.
Relate events to the machine, job, product, batch and time period where identifiers exist. Link a reported problem to the inspection, repair or follow-up outcome rather than treating each log entry in isolation.
Classify downtime; reconstruct a maintenance case; find repeat recorded issues; explain an output discrepancy; retrieve a relevant procedure; summarise the evidence behind a quality investigation.
Log resolution, timestamp alignment, missing operating context, consistency of fault labels and whether a reported cause was verified or merely suspected. Predictive uses would need a separate assessment of coverage and labels.
Connect SOPs, contract terms, checklists and decision logs to the relevant task and date, so a model can retrieve the applicable instruction and identify unresolved obligations.
SOPs, work instructions, checklists, handover notes, meeting records, project decision logs, agreed specifications and contracts or amendments that the source is authorised to share.
Associate the applicable document version with the task or decision. Link a change in instructions to its stated reason and any evidence of implementation.
Retrieve the relevant procedure; compare versions; extract obligations or deadlines for human review; identify an unresolved action; test whether an answer distinguishes a stated rule from a practice observed in the records.
Confidentiality, ownership and third-party rights; whether a procedure was current at the relevant time; and the distinction between a recorded contractual term, an interpretation and legal advice.
Connect briefs, working files, creative revisions, approvals and campaign records to understand what was requested, what changed and what was eventually released.
Design or campaign briefs, authorised working files and assets, copy and artwork versions, feedback, approval records, channel plans, advertising histories and associated performance reports.
Link a brief and its requirements to the relevant asset version, review comments, approval and publication or campaign record. Keep reported outcomes separate from any explanation of what caused them.
Compare the final work with the brief; trace the reason for a revision; identify the approved asset; summarise outstanding feedback; retrieve evidence for a campaign review.
Rights to creative assets, stock material, brands, likenesses and third-party content; client confidentiality; and whether performance records can be reliably linked to the work being assessed.