Work order parsing

How to Parse Work Orders from Multiple Agencies into Clean Job Records

A parsing engine that turns each sender's emails and PDFs into structured fields, then writes tidy records to Simpro or Fergus.

Every agency sends maintenance requests its own way: a PDF from one, free text in the email from another, a different layout again from the next. Formpiece is built for exactly that mess. Each sender gets an inbox and a parser, so unstructured input becomes the same structured fields every time.

The result is less data transcription and a cleaner database, because the same rules fill the same fields on every record.

The problem

Unstructured by Design: Why Every Agency's Work Order Is a Different Puzzle

1

Free text with no field names

The order number, address and fault description sit wherever the sender put them, and some agencies write the whole request as a paragraph.

2

PDFs that never line up

One agency's PDF has the order number top right, another's has it in a footer, and a third changes the layout without telling anyone.

3

Copy and paste, then typos

Manual transcription drifts. A mistyped address or a missing order number is easy to make and hard to spot later.

4

A database that fills with variants

The same site entered three ways, or the same job under different descriptions, makes search and reporting unreliable.

5

Re-sent orders become duplicates

An agency chases an order and a second record is created for work that is already booked in.

More agencies means more formats, and every format is another place for a record to go wrong.

How the parsing works

How the Parsing Engine Turns Each Layout into Structured Fields

Set it up once per sender, then every supported work order from that sender is processed the same way. For the full integration blueprint, see how Formpiece writes to Simpro, Fergus and AroFlo, or the Simpro work order import page.

An inbox for each sender

Each agency gets its own Formpiece address with its own defaults. They email it directly, or your office forwards work orders to it.

A parser set up from a sample

A PDF or email parser is set up field by field from a real work order. It reads supported layouts only, so a new sender starts with a sample.

Fields mapped to one platform

Each inbox writes to Simpro or Fergus, chosen when it is created. Simpro records can be jobs or quotes, and Fergus records jobs or enquiries.

Matched before anything is written

Sites are matched to existing records first. With the optional order number check on, a Simpro job that already exists for that customer is found instead of duplicated.

Example workflow

Three Senders, Three Input Shapes, One Record Format

An illustration of how a setup might look, not a result from a customer.

1

Agency A sends a PDF

Its PDF parser reads the order number, address, description and contacts from fixed positions, and the PDF is attached to the record.

2

Agency B writes it in the email

There is no PDF, so an email parser reads the subject and body for each value, then the record is created.

3

Agency C chases an order

The order number matches a record already in Simpro for that customer, so it is found, not duplicated. You choose whether it is left alone or updated.

Each sender has its own inbox and parser. A work order that can't be read is emailed to the people you list, with the order number and the errors.

Database hygiene

What a Cleaner Database Looks Like

Consistent fields

The same rule fills the same field on every record, so work from one agency looks alike in your system.

Less transcription

Values come from the source document, not from someone retyping them.

Fewer double entries

The optional order number check catches a repeat for the same customer, provided the work order carries an order number.

Senders added one at a time

A new agency means a new inbox and parser. The ones already working aren't touched.

What happens next

Once the Record Exists: An Optional Booking Link

This page is about getting clean records in. Once a record exists you can also generate a private booking link for it. The tenant booking guide covers that side, and the complete work order to booking workflow joins the two.

The record already exists

The link is made for the job the work order created.

A private link is generated

It is stored against the record. The Geosearch plan is needed to generate it.

Sent through your own messaging

The message comes from your own process, not from Formpiece. The tenant then picks from the times your booking form offers.

Questions About Parsing Work Orders

Straight answers. About formats, setup and clean records.

Can Formpiece parse work orders from several agencies at once?

Yes. Each agency can have its own inbox with its own address, a parser built for its layout and its own defaults. Work orders in different formats flow into your system side by side, each read by the parser that suits its sender.

Does it read unstructured emails as well as PDFs?

Yes. An email parser reads the subject and body using rules for where each value starts and ends, and a PDF parser reads tagged fields from a sample document. If an email carries a PDF, the email can hand it to a PDF parser.

Will it read any PDF I give it?

No. A parser reads the layouts it has been set up for, from a sample. A sender nobody has set up, or a layout that has since changed, isn't read automatically until the parser is updated.

How does a parser keep my database clean?

By filling the same fields by the same rules every time, matching sites to existing records before writing, and, with the order number check on, finding a Simpro job that already exists for that customer instead of creating another.

Which platforms can the parsed records go to?

Simpro and Fergus. Each inbox and parser writes to one platform, chosen when it is created: Simpro jobs or quotes, or Fergus jobs or enquiries. AroFlo is covered through Formpiece booking and lead forms rather than emailed work order import.

How is a parser set up, and what if the layout changes?

From a sample of the sender's work order, with each field tagged, in your dashboard or by sending Formpiece the sample. If the layout changes, send a new sample or retag the fields. Other senders are unaffected.

What if a work order can't be read?

Whoever you've listed gets an email with the order number and the errors, so someone knows straight away. The inbox keeps the email and whatever was read from it, so the record or the parser can be fixed without asking the agency to send it again.

Show us how your agencies send work orders.

Request a personalised demo and we prepare a sample work order, the resulting record and a private booking link on our own demo account.