How do you track and resolve site issues so nothing gets lost?
Capture in fifteen seconds, assign a named owner and a date, review the log by AGE rather than by status, and escalate on a published trigger rather than on somebody’s willingness to have an awkward conversation.
Capture has to be almost free
A photo, a location, one line. Every second of friction filters out a real issue — and the ones filtered out are precisely the ones nobody thought were important enough to justify two minutes of typing, which is not at all the same thing as unimportant.
An issues log that is tedious to fill in does not record the issues on the project. It records the issues somebody had time for.
Ownership and ageing are the whole discipline
A named person, never a company — “the MEP subcontractor” cannot be asked why an item is sixty days old, cannot be escalated to, and cannot explain itself. And a date.
Then review the log by age, weekly, oldest first. Status is what people report; age is what is true. An item open for sixty days is telling you its owner cannot resolve it and has not said so — regardless of what the status field claims. And escalate by published rule, because the reason an item ages is very often that escalating it would be socially expensive.
And keep the thread when it escalates
This is the subtle failure. An issue that becomes an RFI gets marked resolved — and the RFI is now tracked in a different system, by a different person. Two systems, one problem, and a gap exactly at the handover.
Keep the issue open until the instrument it became is ANSWERED, not until it is raised. Otherwise the log will tell you the issue was resolved, when what actually happened is that it was forwarded.
References
- module: /modules/issues/ — capture, ownership, ageing and rule-based escalation
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
Related questions
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting