Skip to content

Subcontract change order intake

For Construction project accountants

Prepare project, change reference, scope, amount and stated time impact from a change order with fields you can edit. Approval external.

25 free credits/month · No card needed

See the workflow and review checks

Inspect a document example.

Synthetic documents · Expected output
Standard documentPDF
subcontract change order intakeFictional sample · For demonstration
project name
Example Community Workshop - synthetic
subcontractor name
Example Subcontractor - synthetic
change number
DEMO-CHANGE-0042
issue date
2026-09-30
scope text
Scope explicitly stated in this synthetic source.
change amount
1250
stated time impact
Example stated time impact - synthetic
{
  "project_name": "Example Community Workshop - synthetic",
  "subcontractor_name": "Example Subcontractor - synthetic",
  "change_number": "DEMO-CHANGE-0042",
  "issue_date": "2026-09-30",
  "scope_text": "Scope explicitly stated in this synthetic source.",
  "change_amount": 1250,
  "stated_time_impact": "Example stated time impact - synthetic"
}

A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.

When this work lands on your desk

A change order arrives for construction project accountants. The next step needs project, change reference, scope, amount and stated time impact, recorded under the correct document reference before the information enters your project document review register.

A change order is labeled proposed and includes both added and deducted work. Preserve status and signed amounts before approval. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.

Start with the documents you already collect

  • Change order PDFs
  • Scanned or photographed change order pages

PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.

  1. Define the fields

    Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.

  2. Extract at intake

    Send the document and saved schema slug to POST /api/v1/extract, or collect the file through a branded upload site.

  3. Hand off reviewed data

    After checking project name, subcontractor name, change number, your application maps the reviewed record into your project document review register. Keep the original document reference with the result. Approval external. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.

A schema shaped around the next step.

Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.

Download editable starter schema

Choose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.

FieldTypeWhat to capture
project_namestringProject name exactly as printed in this change order. Preserve identifiers and qualifiers; do not look up or infer missing information.
subcontractor_namestringSubcontractor name exactly as printed in this change order. Preserve identifiers and qualifiers; do not look up or infer missing information.
change_numberstringChange number exactly as printed in this change order. Preserve identifiers and qualifiers; do not look up or infer missing information.
issue_datedateIssue date explicitly printed in this change order. Keep it distinct from other dates; leave it empty if no calendar date is stated.
scope_textstringScope text exactly as printed in this change order. Preserve identifiers and qualifiers; do not look up or infer missing information.
change_amountcurrencyChange amount explicitly labeled in this change order. Preserve its sign and stated currency; do not calculate a missing amount.
stated_time_impactstringStated time impact exactly as printed in this change order. Preserve identifiers and qualifiers; do not look up or infer missing information.

Give exceptions a clear path to review.

Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.

A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.

Read the response contract

Run a synthetic response through a review gate

Checks for this process

  • A change order is labeled proposed and includes both added and deducted work. Preserve status and signed amounts before approval.
  • Check issue date against their own printed labels; leave an unstated date empty instead of deriving it.
  • Check change amount for signs, decimal placement and stated currency before any downstream calculation or posting.

Prove the fit on a representative batch.

Test change order examples from the layouts your team actually receives. Include the exception described here: A change order is labeled proposed and includes both added and deducted work. Preserve status and signed amounts before approval. Compare the extracted project name, subcontractor name, change number and any line rows with a reviewer's checked reference before enabling downstream actions.

Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.

The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.

Expand when the next process is ready

Add recurring extraction capacity when change order intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.

For a tailored implementation

Discuss document volume, page lengths and schema setup for construction project accountants. Bring difficult change order samples and the review requirements your implementation must preserve.

Talk through document mix and volume

Start small. Add capacity as intake grows.

All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.

Free

$0/month

  • 25 credits/month
  • 2 schemas
  • 1 branded upload site
Test this workflow

Starter

$99/month

  • 500 credits/month
  • 10 schemas
  • 5 branded upload sites
Explore Starter

Growth

$499/month

  • 3,000 credits/month
  • 50 schemas
  • 25 branded upload sites
Explore Growth

Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details

Questions about subcontract change order intake

Which fields can I capture from a change order?

The starter schema contains project name, subcontractor name, change number, issue date, scope text, change amount, stated time impact. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.

What needs review in subcontract change order intake?

A change order is labeled proposed and includes both added and deducted work. Preserve status and signed amounts before approval. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.

How does this data reach your project document review register?

Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. Approval external.

How do I test this workflow on my own documents?

Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.