Prepare the batch

  1. Open Processing → Processing jobs. Select the supported upload or authorised source selection and give the job a meaningful title.
  2. Choose the published profile/stages, classification strategy, OCR options, review rules and any required QC or output settings. Verify budget and size/page limits.
  3. Review the selected source membership and settings before starting. The job records its pipeline configuration so later profile edits do not silently change it.
  4. Monitor queued/running work, review-needed results and exceptions. Open a job and use Review next document or a specific document action for the next unresolved task.

Read the job view

The job separates document counts, review work, exceptions and queued/running items. Job insights groups Performance, Usage & billing, Stage evidence and Settings & QC. Use the document filters and pagination to work through the list without assuming the displayed page is the whole job.

Not reported means unavailable evidence, not a passing result. Whole-job totals and displayed-document stage counts can have different populations. Always read their coverage labels.

Local product example · sample dataClick to enlarge ↗
Read processing outcomes before opening a job

The first sample batch has finished with exceptions and still needs review. The second has completed processing. Open job takes you to its documents; expand Processing time and estimates for timing information.

Interpret timing

Average document time measures recorded worker execution over its stated coverage. Total worker time includes available attempts and retries. Queue elapsed time includes waiting and is not interchangeable with worker execution.

ETA needs recent throughput observations and is not an SLA or guaranteed hourly capacity. Modelled savings need an explicit human baseline; they are not measured operator labour.

Recover safely

Inspect the reported exception and current source/profile binding before retrying. An uncertain provider call or completed delivery should retain its durable identity to avoid duplicate effects. Use the supported retry/recovery action rather than starting indistinguishable duplicate jobs.

Machine work can finish while review, indexing, QC or delivery is still outstanding. Follow the remaining stage-specific next action.

Work by exception before release

  1. Check membership against the intended source set.
  2. Use queued/running, review-needed and exception counts to choose the next task.
  3. Page through the filtered document list; the current page is not the whole job.
  4. Resolve review and fixed QC requirements, then inspect output readiness independently of machine completion.