Log the ending too.

Two logs, not one. The problem — and how it ended. Most people log the problem and never log the ending.

Say it the day you see it.

Who's on it, what's happening, where it is — talk it in and hit DONE.

“Water intrusion at the northeast stairwell — plumber called, temporary containment in place.”

SiteLog AI capturing the water intrusion problem log

Mark it URGENT.

Four buttons come up when you're done talking. URGENT is the one you'll search for later.

SiteLog AI type picker with URGENT chosen for the problem log

When it's fixed, say that too.

Two days later, same spot, thirty seconds. Mark this one RECORD.

“Plumber replaced the weeping fitting at the northeast stairwell riser. Second pressure test held at 100 psi for thirty minutes — leak resolved, drywall hold released.”

SiteLog AI capturing the repair log two days later

Say what proved it.

Not “it's fixed.” Say the test and the number:

“Second pressure test held at 100 psi for thirty minutes.”

A test and a number end an argument. “It's fixed” starts one.

Say what it released.

Then say what the next trade is clear to do:

“Leak resolved, drywall hold released.”

Now the record shows when the wall was cleared to close — and who cleared it.

Both come back together.

Two years later, ask the Vault about the water leak in the stairwell. The problem and the ending, both dated.

SiteLog AI Vault returning both the problem log and the repair log, dated

The three ways it goes wrong.

YOU LOGGED THE LEAK, NOT THE REPAIR

A year later the record shows a problem with no ending. That reads like it was never handled.

YOU WROTE “FIXED” AND NOTHING ELSE

No test, no number, no date on the proof. It's your word against theirs.

YOU NEVER SAID WHAT IT RELEASED

The next trade waits, or closes the wall early. Both cost you.

The problem and the ending. Both dated.

A record that stops at the problem reads like it was never handled.

The day you don’t log is the day they ask about.

Running a crew? Teams — 30 days free →