Document scanning enquiries1300 338 365

Work orders that file against the right job

An example of a work-order scanning workflow: paper is scanned, read and indexed, then filed into SharePoint against the job and property. The fields and output are agreed on your own sample.

Example workflow

From a stack of job sheets to a searchable record

Job paperwork can contain work-order numbers, property addresses, dates and supporting pages. The useful result is a complete document attached to the correct job, with those references available as fields.

This is an illustrative workflow, not a published customer case study. The file names shown are sample data; no customer identity or performance figures are claimed.

Documents: SharePoint All documents ▾
NameTypeDate
Invoice 10482: Coates HireInvoice14 Mar 19
Work Order 59697: 14 Marine PdeWork order18 Mar 19
Contract: Brady ConstructionsContract2 Apr 19
Example output: documents named from their contents, with fields you can filter. Your own documents and fields are agreed with you.

What the pipeline does

  1. Scan and keep the orderCapture the paperwork and its supporting pages, keeping document relationships intact.
  2. Read the referencesIdentify the document type, work-order number, property and date using the fields agreed with you.
  3. Flag uncertaintyUnclear references go for review rather than being treated as a confident match.
  4. File into SharePointDeliver the document with its metadata, so the team can filter by job, property or date.

Agree the result before the archive

Your document types

Use your own sample paperwork, including the awkward pages and handwritten references.

Your fields

Decide which references matter and how exceptions should be reviewed.

Your destination

Confirm the library, permissions and integration before a full run.

Try it on one box

Drop one off or let us collect it. We scan and index it free, so you see exactly what comes back before committing to anything. Collection is quoted separately.