Task statement 5.5 · Context management and reliability

Design human review workflows and confidence calibration

The pipeline extracts 10,000 documents a week, and reviewers check its output. The dashboard says 97% of extractions are correct, and the proposal is to stop reviewing the ones the model is confident about.

Scenario switchThis section uses the guide's structured-extraction scenario: a pipeline that extracts fields from invoices, contracts and support emails. The support agent's case facts are extracted from customer messages the same way, so the same checks apply to it.
Why it's tested

The tempting move is to trust the two numbers the pipeline already reports. The overall 97% is a mean dominated by the largest document type, so a small type that fails badly disappears into it. The confidence score looks like a probability, but until it is compared with labelled answers nobody knows how often a 0.9 is right. Cutting review on either number removes the check on the extractions that are wrong.

Start hereThree terms this section leans on

segment
Extractions measured on their own: one document type, or one field within it, such as requested_amount in support emails.
labelled validation set
Documents with a human-recorded correct value for every field.
calibration
Setting a field's review threshold from that set, so each confidence score maps to an observed accuracy.

KnowledgeWhat an overall accuracy figure hides

Accuracy here is the share of labelled documents whose extracted fields all match the human answer. Measured over everything, it is a mean weighted by volume, so each document type counts in proportion to its size. Here 7,000 invoices at 99.0% and 2,000 contracts at 97.5% outvote 1,000 support emails at 85.0%, giving 97.3%. At 85%, about one support email in seven is extracted wrongly, and those emails carry the refund amounts customers ask for. So accuracy is validated by document type and field segment, and must be consistent across all segments, before any high-confidence extraction is automated.

  1. Measure accuracy by document type, then by field within any failing type.
  2. Have the model output a confidence score for each field.
  3. Calibrate each field's threshold on a labelled validation set.
  4. Route low-confidence fields, and ambiguous or contradictory documents, to human review.
  5. Automate only passing segments, and keep stratified random sampling of them.

Interactive · the same 10,000 extracted documents, measured three ways

Horizontal accuracy bars against a dashed 95% automation line: one overall bar, or one bar per document type, or one bar per field within support emails ACCURACY · % OF LABELLED DOCUMENTS WITH EVERY FIELD CORRECT ACCURACY · % OF LABELLED EXTRACTIONS OF THIS FIELD CORRECT 0% 100% Invoices All documents order_number 7,000 documents 10,000 documents support emails 99.0% 97.3% 99.5% Contracts issue_type 2,000 documents support emails 97.5% 97.0% Support emails requested_amount 1,000 documents support emails 85.0% 88.0% automation bar: 95% ↑ CAN HUMAN REVIEW BE REDUCED? Only for invoices and contracts. Support emails fail the bar, so their review stays. It looks like yes, for everything. This is the proposal, and it has not been segmented. Target the fix: automate the two passing fields, and route low-confidence requested_amount to reviewers.

Choose how accuracy is measured, and see whether review can safely be reduced.

One number, 97.3%, clears the bar. Nothing here says which document types it is made of.

Split by document type, about one support email in seven is extracted wrongly. The 7,000 invoices outvoted them in the overall figure.

Within support emails, one field fails. Reviewer time can go to requested_amount instead of to every support email.

Illustrative figures. 97.3% is the volume-weighted mean (6,930 + 1,950 + 850 correct of 10,000). A support email is correct only when all three fields are. Blue bars clear the 95% bar; red bars do not.

SkillCalibrating field-level confidence, then routing

The field view shows that requested_amount causes most support-email errors, so review can target that field instead of every support email. Choosing which extractions of it to trust needs a field-level confidence score, and the raw score is only the model's own estimate. Calibration turns it into a measurement: run the extractor over 500 labelled support emails, group the extractions by score, and count how often each group was right.

score band    extractions   actually correct
0.95 – 1.00       280            97%
0.85 – 0.95       140            86%
below 0.85         80            61%

Scores between 0.85 and 0.95 are right only 86% of the time, below the 95% bar, so the threshold goes at 0.95. A requested_amount scored under it goes to a reviewer. So does a document whose source is ambiguous or contradictory, such as an email naming both $40 and $65 as the refund, because any single value the model picks is a guess. Reviewer capacity is limited, so when the queue outgrows it, contradictory sources and the lowest-confidence fields go first, because that is where errors are likeliest.

SkillSampling what nobody reviews any more

Automating a segment does not end measurement, because a confident extraction can still be wrong and no reviewer sees it. Stratified random sampling keeps measuring its error rate: it splits the high-confidence extractions into segments, document type by field, and draws at random within each one. Each segment usually gets a fixed number of reviews (disproportionate allocation), because a sample proportional to volume gives small segments the same handful a simple random sample does. Of 210 weekly reviews, that handful is about 147 invoices, 42 contracts and 21 support emails, against a fixed 70 of each.

The fixed allocation is what detects novel error patterns. In week 12 a large retailer starts forwarding support emails with an older order thread quoted underneath, and the extractor takes the old order number with confidence 0.97. About 100 of the week's 1,000 support emails are affected, and confidence routing never sees them. The two samples see that week differently:

Simple random sample

210 reviews drawn from all 10,000

About 21 support emails, 2 with a wrong order_number. That looks like noise, and the overall figure falls about one point, still above 95%.

Stratified random sample

70 reviews within each document type

70 support emails, about 7 with a wrong order_number, in a segment that usually shows none. The new pattern is found in its first week.

Not the same as self-reported confidence. Section 5.2 rejects the model's self-reported confidence as a trigger for escalating a conversation. Here a score routes review only after calibration against labelled answers turns it into a measured accuracy. An uncalibrated score is as unreliable here as there.

Before any extraction skips review, ask: has accuracy been measured for this document type and this field, on a labelled validation set, at the confidence threshold you plan to use? Yes → automate above that threshold, and keep stratified random sampling running. No → keep human review, and measure first.
Takeaway
  • 97% overall can contain a document type at 85%, because the large types outvote the small one.
  • A confidence score routes nothing until a labelled validation set has shown what each score band is actually worth.
  • Confidently wrong extractions never reach the review queue by themselves, so sample a fixed number from every segment.

check yourself

0 / 3 answered

Calibrated thresholds now send about 650 invoice extractions a day to human review, but reviewers can clear 400. Among the 650 are 120 invoices whose stated total disagrees with the sum of their line items. The team's stated goal is to catch as many extraction errors as possible per review hour.Which way of ordering the review queue best meets that goal?

Select one.

Contracts are 3% of the 20,000 documents extracted each week. High-confidence contract fields stopped being reviewed after passing segment checks, and reviewers have 300 checks a week for sampling. The team must learn within a week if a new contract template causes errors the model is confident about.Which sampling design best achieves this within the 300 checks?

Select one.

Before any payment_terms extraction from supplier invoices skips review, it must show 97% observed accuracy. The model outputs a confidence score per field. On 600 labelled invoices, the payment_terms extractions it scored between 0.90 and 1.00 were correct 93% of the time.Which TWO changes best set up review routing for payment_terms?

Select two.

sources

  1. Claude Platform Docs, "Define success criteria and build evaluations": evals that "mirror your real-world task distribution" including edge cases and rare inputs, test sets with human-labelled answers, and LLM-based grading that you "test to ensure reliability first then scale". Checked 2026-10-01.
  2. Anthropic's documentation does not describe stratified sampling or confidence calibration. Both are standard statistical and evaluation practice; the fixed-per-segment (disproportionate) allocation is the course's clarification of the guide's "stratified random sampling". The 97% example, document type and field segments, field-level confidence, labelled validation sets and the routing rule: Claude Certified Architect — Foundations Exam Guide v1.0, Domain 5.5 and Exercise 3. All figures are illustrative.