Evidence for One Live Workflow

Inspect a fictional invoice correction: the model output, the approved service order, and the evidence that makes the label usable.

OpenTour illustrative sample

TYPE

Fictional invoice extraction

SCOPE

One invoice workflow

TIMELINE

Before repair selection

SOLUTION

Evidence & lineage

01

01

Bounded workflow

03

03

Linked evidence sources

SAMPLE 01 / FICTIONAL RECORDS

The evidence behind one correction

01 / CAPTURED OUTPUT

materials

INV-1042 · line 02

“Site call-out”

Model route v1

02 / APPROVED ORDER

onsite_labor

SO-208 · line 02

Onsite inspection

Available before inference

03 / REVIEWED LABEL

onsite_labor

COR-017 · rubric v3

Reason: service, not parts

Linked to both source records

Same order-line key. Separate source records. One reviewable correction.

OpenTour mark

A correction becomes useful when you can show which record supports it—and what the model could know at the time.

The OpenTour standard

Illustrative delivery package

01 // OVERVIEW

One invoice line. Three linked records.

An operations team uses an open-weight model to extract service categories from contractor invoices. The same ambiguous phrase keeps being labeled as a material charge, sending reviewers back to the approved order.

This fictional example connects the captured output, the order line, and an authorized correction. It illustrates the evidence format; it does not represent a customer deployment or an observed performance result.

THE CHALLENGE

An approved order can support the label. It must also have been available at the decision time before it can be used as model input.

02 // SAMPLE ARTIFACT

Inspect the correction record

The shared order-line key connects the evidence. Availability time, policy version, and reviewer authority determine how each field may be used. Unresolved or conflicting records stay out of the verified training set.

RECORD

EXAMPLE VALUE

WHY IT MATTERS

RECORD

Join key

EXAMPLE VALUE

SO-208 / line 02

WHY IT MATTERS

Matches the invoice to the approved work.

RECORD

Decision time

EXAMPLE VALUE

10:02 UTC

WHY IT MATTERS

Only evidence available by this point can enter the prompt.

RECORD

Order available

EXAMPLE VALUE

09:55 UTC

WHY IT MATTERS

Later records may verify outcomes; they cannot rewrite earlier inputs.

RECORD

Correction

EXAMPLE VALUE

COR-017 / rubric v3

WHY IT MATTERS

Keeps the original output, reviewed label, and reason distinct.

03 // HANDOFF

What leaves this stage

A versioned workflow contract, a permitted evidence manifest, and a reusable correction record. Source cases stay grouped into families so a generated variation cannot leak into the protected evaluation set.

OpenTour checks coverage and recurring burden before choosing a repair. A missing join or an uncertain label produces a hold for that case, not an invented outcome. Customer data and its derivatives stay within the agreed environment.

[READY TO IMPROVE YOUR AI WORKFLOW?]

IMPROVE WHAT YOU’RE

BUILDING

NEXT

Book a focused workflow review to assess recurring errors, your model route, and the records needed to verify a meaningful improvement.

↳ Prefer to send an enquiry?

Tell us about one live workflow, your open-weight model, and where errors create rework. We’ll assess the fit and define a practical starting point.

START WITH [ONE REPEATABLE WORKFLOW]

*Share a workflow overview here. Please do not include customer records or sensitive data.

[READY TO IMPROVE YOUR AI WORKFLOW?]

IMPROVE WHAT YOU’RE

BUILDING

NEXT

Book a focused workflow review to assess recurring errors, your model route, and the records needed to verify a meaningful improvement.

↳ Prefer to send an enquiry?

Tell us about one live workflow, your open-weight model, and where errors create rework. We’ll assess the fit and define a practical starting point.

START WITH [ONE REPEATABLE WORKFLOW]

*Share a workflow overview here. Please do not include customer records or sensitive data.

[READY TO IMPROVE YOUR AI WORKFLOW?]

IMPROVE WHAT YOU’RE

BUILDING

NEXT

Book a focused workflow review to assess recurring errors, your model route, and the records needed to verify a meaningful improvement.

↳ Prefer to send an enquiry?

Tell us about one live workflow, your open-weight model, and where errors create rework. We’ll assess the fit and define a practical starting point.

START WITH [ONE REPEATABLE WORKFLOW]

*Share a workflow overview here. Please do not include customer records or sensitive data.