Abstention examples workflow example: one subcontract package, step by step, with the record each step leaves

Short answer

In an ordinary workflow, an abstention example is the record of a person who could have moved a task forward, stopped because something required was missing or outside their authority, wrote down why, and handed the case to someone able to resolve it. The example below follows one fictional subcontract package through seven steps, from intake to signature, and marks which of the records it leaves carry that signal and which are only background.

Visual briefFull-size diagram
A seven-step workflow runs left to right from intake to signature; as each step plays, a record card drops beneath it, and the five cards that carry the abstention signal (arrival state, checklist, hold reason, escalation roles and executed versions) are marked in green.
Illustrative workflow at a fictional 260-person mechanical contractor. Each step leaves a record; five of them carry the signal.

This page is part of abstention examples: five questions for introducers. Its job is one worked example from start to finish. For the missing fields that weaken a history like this, see the evidence gap analysis; for what a company assembles later, see the review packet contents list.

The company, the package and the rule it was checked against (Illustrative)

Everything here is fictional. A 260-person mechanical and HVAC contractor wins ductwork and plant-room installation on a hospital extension. The general contractor sends a subcontract package through its project portal. A contract administrator in the contractor's commercial team checks every incoming subcontract before anyone signs.

The rule comes from the company's own subcontract checklist, last revised in 2024. Two of its 14 lines matter here:

  • Every exhibit referenced in the agreement must be attached, and drawing references must match the revision the estimate was priced on.
  • Any pay-if-paid clause needs approval from in-house counsel. Contract administrators may not accept one.

The first line is an evidence rule. The second is an authority rule. This package breaks both, which makes it a useful example: it shows the two common reasons a careful person stops.

DocumentState on arrivalWhat the checklist requires
Subcontract agreementPresent, version 1Compare with the company template
Scope of work exhibitPresent, cites drawings revision BMust cite revision C, the set the estimate priced
Drawing registerPresent, lists revision CReference only
Schedule of valuesPresentMust match the estimate total
Insurance requirements exhibitPresentWithin company limits
Payment terms, section 7Present, pay-if-paid wordingCounsel approval required

Two lines fail: the scope exhibit points at an older drawing set, and section 7 contains a clause the administrator is not allowed to accept.

Seven steps from intake to signature

Each row is one step, the decision taken in it, the record it leaves behind, and whether that record carries the signal an AI-data review looks for.

StepWhat happenedDecision takenRecord leftCarries the signal?
1. IntakePackage pulled from the portal into the contract tool on day 1Log it and start the checkUpload event listing six files with version labelsYes, it fixes the arrival state
2. ChecklistAdministrator works through all 14 linesMark each line pass or failCompleted checklist with two lines failedYes, it defines what complete meant that day
3. StopRouting for signature is one click awayHold instead of routeStatus set to On hold, reason text naming both gapsYes, this is the abstention
4. EscalationScope question goes to the project manager; section 7 goes to counselSend each gap to the role that can resolve itTwo assignment events with names and rolesYes, it shows the handoff respected authority
5. ResolutionThe general contractor reissues the scope exhibit citing revision C; counsel agrees replacement payment wordingAccept both fixesNew file versions and counsel's approval notePartly, it proves the gaps were real
6. Re-checkAdministrator re-runs the two failed lines; both passRelease the hold and route for signatureStatus change with release reason; signature requestBackground
7. SignatureBoth parties sign on day 11Confirm the executed set matches the reviewed setCompletion record and executed version identifiersYes, it shows that stopping was right

The graphic on this page plays the same seven steps in order and drops each record as its step completes.

The two decisions that make it an abstention example

Step 3, the stop. The administrator had the means to proceed and some pressure to do so: the project manager wanted to mobilize crews the following week. The administrator held the package anyway and wrote two specific reasons, "scope exhibit cites drawings rev B; estimate priced rev C" and "section 7 pay-if-paid, counsel approval required". A hold with a blank or vague reason would look, in the record, exactly like a delay. The named gaps are what turn it into evidence of judgment.

Step 4, the handoff. Stopping is half of it. The other half is sending each gap to someone who can close it. The drawing mismatch went to the project manager, who could get the general contractor to reissue the exhibit. The payment clause went to counsel, because the checklist reserves that call to counsel. Neither gap went to the person pushing for signature.

This is different from asking a clarifying question, which resolves an ambiguity in place; that behavior has its own guide on clarification behavior. Here the administrator did not try to resolve anything. The record shows a refusal to guess and a transfer to the right desk.

Researchers care about this pattern because models are often scored in ways that reward guessing. OpenAI's explainer on why language models hallucinate argues that accuracy-only scoreboards favor a confident guess over admitting uncertainty, even though an error is worse than an abstention. A 2025 survey in Transactions of the ACL reviews abstention research by query, model and human values. Neither source says anything about any company's archive. They explain why a well-judged stop is worth studying at all.

Which records carry the signal, and which are background

Read as a chain, five records do the work:

  1. Arrival state (step 1). Without the original file list and versions, nobody can confirm anything was missing when the hold was placed.
  2. Checklist in force (step 2). It defines "required" in the company's own terms, so a reviewer does not substitute their own rule.
  3. Hold reason (step 3). The named gaps, written at the moment of the stop.
  4. Escalation roles (step 4). Who received each gap and whether policy allowed them to resolve it.
  5. Executed versions (step 7). Proof that what was signed matches what was reviewed after the fixes.

The rest is background. Email threads between the project manager and the general contractor, calendar invites for the counsel call and the release at step 6 all confirm that the case moved, but none of them shows the judgment. A signed PDF on its own carries almost no signal: it shows the end state, not the stop.

Vendors such as Appen market agent data services that include failure-mode taxonomies and verifier and rubric design (Appen's agentic AI page, checked October 18, 2026). That shows the category of material exists. It does not show that any particular contractor's subcontract archive is wanted, and SourceX makes no claim to have bought this kind of record.

The same week's clean package: the control case

The same administrator checked a second subcontract that week, from a different general contractor. All 14 lines passed. It was routed on day 2 and signed on day 4, with no hold and no escalation.

That unremarkable case matters as much as the held one. Restraint is only informative when it is selective: a person, or a model, that holds every package has learned nothing about when to stop. In this fictional company, the commercial team checks roughly 180 subcontracts a year and holds about 30 (Illustrative figures, not a statistic). A history that keeps both kinds, in something like the ratio the business actually sees, is far more useful than a folder of problem files. The finance workflow example pack shows the same principle on approval records, and what is workflow data explains why the ordinary cases count.

Who owns each record, and what a partner can ask

In a company like this one, the commercial or contracts team owns the contract tool and its status history, counsel owns approval notes, project managers hold scope correspondence, and finance often keeps executed copies. Authority to discuss licensing and sign for the company sits with the CEO, with the CFO or general counsel advising. Customer and general contractor agreements may limit reuse of contract terms, so a rights review is expected.

A partner stays at metadata level and asks three things beyond the parent guide's five questions:

  • Which system records the hold status and its reason, and since which year?
  • Roughly how many packages are checked a year, and what share are held?
  • Is the package kept as it first arrived, or replaced by later versions?

The company must have 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Unknown until SourceX reviews it: how many holds carry a usable reason, whether arrival states survived tool upgrades, what redaction counterparty names need, whether there is buyer interest, and therefore any reward. The wider record family is described under contract review workflows.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's contracts team can point to a hold status with a written reason and an escalation route like the one above, register as a partner, confirm the company against who qualifies, and read the program terms before you introduce the decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does the example only work for construction subcontracts?

No. The same chain appears wherever a person checks an incoming package against a rule before passing it on: customer renewals, supplier onboarding, loan files, insurance submissions. The subcontract is simply a case where both an evidence gap and an authority gap are common.

Is the release of the hold at step 6 part of the signal?

Only as background. The release shows the case moved on, but the useful evidence is earlier (what was missing and who was asked) and later (whether the executed documents match what was reviewed).

Should a partner ask to see a held package to confirm the workflow exists?

No. A partner asks which system records holds, since when, roughly how many a year and who owns them. Any look at actual packages happens later, under SourceX's own agreement with the company.

Sources

  1. openai.com/index/why-language-models-hallucinate
  2. aclanthology.org/2025.tacl-1.26
  3. appen.com/agentic-ai
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment