Waste haul disposal ticket capture
For Construction waste record coordinators
Prepare project, material, hauler, weight and destination from a disposal ticket with fields you can edit. Environmental certification external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- project name
- Example Community Workshop - synthetic
- ticket reference
- DEMO-TICKET-0042
- haul date
- 2026-09-30
- hauler name
- Example Hauler - synthetic
- material description
- Example material description - synthetic
- weight
- 1200
- weight unit
- lb
- destination name
- Example Destination - synthetic
{
"project_name": "Example Community Workshop - synthetic",
"ticket_reference": "DEMO-TICKET-0042",
"haul_date": "2026-09-30",
"hauler_name": "Example Hauler - synthetic",
"material_description": "Example material description - synthetic",
"weight": 1200,
"weight_unit": "lb",
"destination_name": "Example Destination - 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 disposal ticket arrives for construction waste record coordinators. The next step needs project, material, hauler, weight and destination, recorded under the correct document reference before the information enters your project document review register.
A disposal ticket uses tons while a load sheet uses pounds. Capture the ticket unit and stated destination without certifying disposal compliance. 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
- Disposal ticket PDFs
- Scanned or photographed disposal ticket pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking project name, ticket reference, haul date, your application maps the reviewed record into your project document review register. Keep the original document reference with the result. Environmental certification 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 schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
project_name | string | Project name exactly as printed in this disposal ticket. Preserve identifiers and qualifiers; do not look up or infer missing information. |
ticket_reference | string | Ticket reference exactly as printed in this disposal ticket. Preserve identifiers and qualifiers; do not look up or infer missing information. |
haul_date | date | Haul date explicitly printed in this disposal ticket. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
hauler_name | string | Hauler name exactly as printed in this disposal ticket. Preserve identifiers and qualifiers; do not look up or infer missing information. |
material_description | string | Material description exactly as printed in this disposal ticket. Preserve identifiers and qualifiers; do not look up or infer missing information. |
weight | number | Weight as reported in this disposal ticket. Preserve the labeled measure and its unit; do not estimate it. |
weight_unit | string | Unit printed beside the weight, kept separate from the numerical weight. |
destination_name | string | Destination name exactly as printed in this disposal ticket. 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 contractChecks for this process
- A disposal ticket uses tons while a load sheet uses pounds. Capture the ticket unit and stated destination without certifying disposal compliance.
- Check haul date against their own printed labels; leave an unstated date empty instead of deriving it.
- Resolve missing project name, ticket reference, haul date against the source before using the record.
Prove the fit on a representative batch.
Test disposal ticket examples from the layouts your team actually receives. Include the exception described here: A disposal ticket uses tons while a load sheet uses pounds. Capture the ticket unit and stated destination without certifying disposal compliance. Compare the extracted project name, ticket reference, haul date 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 disposal ticket 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 waste record coordinators. Bring difficult disposal ticket samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart 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.
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 waste haul disposal ticket capture
Which fields can I capture from a disposal ticket?
The starter schema contains project name, ticket reference, haul date, hauler name, material description, weight, weight unit, destination name. 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 waste haul disposal ticket capture?
A disposal ticket uses tons while a load sheet uses pounds. Capture the ticket unit and stated destination without certifying disposal compliance. 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. Environmental certification 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.