Many sites. Different assets. A connected record.

Keep site context when the work moves between asset types.

A facilities visit may involve different equipment in different locations. The first job is to make the record identifiable: the customer, the site, the asset reference and the location. Squigg keeps that structure around the inspection and work.

The same approach can be used across the assets your business maintains. Reusable checklists provide a structured way to record findings while allowing the inspection scope to remain specific to the work involved.

The next engineer should not need to reconstruct the last visit.

When someone returns after a reported problem, they need the earlier context: what was inspected, what was found and what happened next. Squigg brings previous inspections, recorded issues, completed follow-ups and associated reports together under the asset reference.

Record reactive work against the asset involved. Keep the customer’s reported problem separate from the engineer’s findings, the work carried out and the outcome. This gives the later history more substance than a completed tick on a separate job sheet.

• Customer sites and mixed assets
• Inspection evidence attached to the work
• Recorded defects and further action
• Completed call-outs and customer-facing reports

Bring existing asset lists into the workflow.

If your starting point is an asset register in Excel, supported .xlsx or UTF-8 .csv data can be mapped and reviewed before assets are added to a site. Check references and locations carefully so later visits are recorded under the intended asset.

Squigg is not presented as an all-purpose facilities enterprise system. Procurement, invoicing, dispatch and planned-maintenance scheduling are outside the capability claims on this page. The focus is connecting inspection and maintenance records across visits.