The next visit starts with the whole history.

A customer’s site is more than a folder of reports.

Reports tell you what happened on a visit. An asset history helps you find that visit in relation to the equipment you are looking at now. Squigg brings the recorded inspections, issues and follow-up work together around the asset.

The same reference can connect a routine inspection and a later call-out. Engineers can review the record before adding another visit, rather than comparing filenames or asking the office to find an old attachment.

• Previous completed visits
• Recorded issues and their context
• Follow-up outcomes
• Reports behind completed work

See the defect and the work that followed it.

In the fictional AHU-023 record, an inspection on 12 September records a worn drive belt. A follow-up on 18 September records replacement and an operation check, with a Fixed outcome. Both visits remain visible: the original finding is not erased by the later repair.

This continuity matters when more than one engineer attends the same site. The engineer who returns can understand the finding, the subsequent work and the recorded outcome as one asset story.

Keep outcomes precise.

A historical failure does not always mean the issue is still outstanding. A recorded Fixed outcome resolves the issue; a No fault found outcome leaves the reported fault unconfirmed. The history keeps those distinctions instead of reducing every visit to a generic completed badge.

This is a record of work and recorded issues. It is not a predictive-maintenance system or a guarantee of an asset’s current condition. Use the history alongside the checks and professional judgement needed for the next visit.