Skip to content
forebot.
Sign inBook a demo

When the problem comes and goes.

Reach for this when the complaint is not happening during your visit, or it stops and returns.

A clean check made while the problem is absent says little, so parts get swapped on a guess.

Run it on a job in ForeBotAll checklists

Step by step

7

  1. Sort the kind of problem

    Lone code, safety lockout, unexplained stop, or occupant complaint? The answer decides whether a reset is even an option.

    Write down · Note

  2. Copy stored records first

    A qualified tech reads and copies fault history with the unit's address before any reset or power cycle.

    Write down · Reading

  3. Start a timeline

    Have occupants log date, time, place, severity, and duration. Add weather and nearby activity. Staff log equipment cycles and maintenance.

    Write down · Note

  4. Plan for the next event

    Place a logger or book a visit around the pattern. Decide who checks what when it happens next.

    Write down · Task

  5. Time your checks to the problem

    Count a clean result only if it was taken while the problem was happening, at the suspected spot.

    Write down · Reading

  6. Reset only where it fits

    A qualified tech may reset a lone code and watch it. Leave lockouts and repeats alone until someone finds why.

    Write down · Decision

  7. Log what came back

    Record whether the code returned under the same conditions. Hand the captured event to the next check, not straight to a part.

    Write down · Note
Done when

A finished run leaves copied records, a dated timeline, and checks tied to whether the problem was present.

General guidance for a qualified person, not a finding about any home. The person on site decides.