Importing inspection PDFs from other systems.

Section 01How to do it

1. 01

   Decide whether you need the import at all

   The better route is to invite the inspector into your account. Their records are then yours from the start, and you remove their access when the contract ends. Import is for contractors who will not move.

2. 02

   Upload the PDF

   One report at a time. It is read for the property, the doors, the components, the pass/fail results and the notes.

3. 03

   Check it before you add it

   This is the step people skip and regret. Check it matched the right property. Check the door numbers against your register. Check that a component read as failed really failed.

4. 04

   Add it to your records

   Once added, the doors carry the imported history and behave like any other record. Repairs, quotes, reports and exports all work from them.

5. 05

   Send anything odd to support

   Layouts vary widely between suppliers. If a report reads badly, send it to us. That is how the import gets better for the next one.

Section 02What the app actually does here

• Uploads are limited to 20MB per PDF
• The text in the PDF is read first. Scanned pages are read as a fallback, up to six pages — this part is still in testing
• A confidence score is shown, never above 90% — it never claims certainty
• It reads the property, address, inspection date, inspector, contact and who asked for the inspection
• Imported components follow the same limit as captured ones: up to three failure reasons
• If no doors are found, you are told to add them by hand
• A layout it does not recognise can be sent to support to be set up
• This is for finished inspection reports. A client’s door schedule, loaded before your own visit, has its own import

Section 03What goes wrong

Every one of these has cost somebody real time. They are cheap to avoid and expensive to unwind.

Section 04Questions

Section 05Related