Extract data from statements of work

A statement of work is the contract that turns a service engagement into something you can hold a vendor to. It names the buyer and the supplier, describes the project, and then commits both sides to a schedule: the deliverables, the milestones, the acceptance criteria, and the payment tied to each. Three readers depend on it: a project manager runs the engagement against it, a procurement lead checks the total against the budget, and a finance team releases payment only when a milestone's acceptance criteria are met. Whether the SOW sits under a master service agreement or stands alone, its schedule of deliverables and payments is the part everyone returns to. The detail that governs money and time lives in tables, not prose. One SOW can list eight deliverables, each with a due date and its own acceptance criteria, mapped to four milestones that trigger staged payments totaling $320,000. Payment terms reference Net 30 from milestone acceptance, and the assumptions-and-exclusions section decides what counts as out of scope when the client asks for more. Governing clauses sit alongside the schedule, so a change-of-control clause, an IP-assignment clause, and a liability cap travel with it, and the difference between a completion date and an acceptance date can shift a payment by weeks. Talonic reads the SOW and returns the parties, the project scope, the schedules of deliverables, milestones, and payments, and the governing clauses as structured records. Deliverables come back with due dates and acceptance criteria, milestones with their target dates and payment triggers, and the payment schedule with amounts in a single currency. Point it at a data-migration SOW between Riverstone Health as buyer and Foldertree Consulting LLC as supplier, running 2026-07-06 to 2026-12-18 at a total of $320,000 in USD across four milestones, and it loads into a project and billing system with its acceptance criteria intact, so a project manager releases payment against met criteria rather than a retyped schedule.

What gets extracted from statements of work

How extraction works for statements of work

Statements of work reach a team as signed PDFs, appendices to a larger agreement, or scans, and the schedules that carry the commitments are laid out as tables that shift from vendor to vendor. Talonic classifies the document and maps it to the contract schema in the Field Registry, which keeps the deliverables, milestones, and payment schedule as separate linked tables rather than flattening them. Each deliverable retains its due date and acceptance criteria, each milestone its target date and payment trigger, and each payment its amount, currency, due date, and the condition that releases it. The total contract amount is typed as a number and reconciled against the payment lines, and the assumptions-and-exclusions and liability clauses are captured as their own fields. Every value returns with a confidence score and a pixel-region pointer conforming to DIN SPEC 91491, so a project manager or a finance approver can verify a milestone payment against the source document before releasing funds.

Sample extraction

A fixed-fee data-migration statement of work

{
  "document_number": "SOW-2026-0706",
  "document_date": "2026-07-06",
  "effective_date": "2026-07-06",
  "buyer": {
    "name": "Riverstone Health",
    "contact_person": "Dana Whitfield"
  },
  "supplier": {
    "name": "Foldertree Consulting LLC",
    "contact_person": "Omar Haddad"
  },
  "project_title": "EHR data migration",
  "project_description": "Migrate and validate patient records from a legacy EHR to the new platform",
  "start_date": "2026-07-06",
  "end_date": "2026-12-18",
  "total_amount": 320000,
  "currency": "USD",
  "payment_terms": "Net 30 from milestone acceptance",
  "governing_law": "State of Massachusetts",
  "deliverables": [
    {
      "deliverable_id": "D1",
      "deliverable_name": "Data mapping specification",
      "due_date": "2026-08-14",
      "acceptance_criteria": "Signed off by buyer data lead",
      "status": "planned"
    },
    {
      "deliverable_id": "D2",
      "deliverable_name": "Migrated records, validated",
      "due_date": "2026-11-20",
      "acceptance_criteria": "99.5% record match on reconciliation",
      "status": "planned"
    }
  ],
  "milestones": [
    {
      "milestone_id": "M1",
      "milestone_name": "Discovery complete",
      "target_date": "2026-08-14",
      "payment_trigger": "20% on acceptance"
    },
    {
      "milestone_id": "M2",
      "milestone_name": "Phase 2 cutover",
      "target_date": "2026-10-01",
      "payment_trigger": "40% on acceptance"
    }
  ],
  "payment_schedule": [
    {
      "payment_id": "P1",
      "payment_amount": 64000,
      "currency": "USD",
      "due_date": "2026-09-13",
      "trigger_condition": "M1 acceptance",
      "invoice_terms": "Net 30"
    },
    {
      "payment_id": "P2",
      "payment_amount": 128000,
      "currency": "USD",
      "due_date": "2026-10-31",
      "trigger_condition": "M2 acceptance",
      "invoice_terms": "Net 30"
    },
    {
      "payment_id": "P3",
      "payment_amount": 128000,
      "currency": "USD",
      "due_date": "2026-12-31",
      "trigger_condition": "Final acceptance",
      "invoice_terms": "Net 30"
    }
  ]
}

Frequently asked