Construction Issue Tracking Guide

What counts as a construction issue?

A construction issue is an unresolved project condition that needs attention beyond routine field documentation. It might be damaged work, an installation conflict, a missing material, an owner concern, a coordination problem or a condition that could become a formal RFI or change.

The key word is unresolved. If the superintendent sees it, addresses it immediately and the work is complete, the daily record may be enough. If another person, decision or return visit is required, the project needs a way to track it.

What should an issue record contain?

Original conditionDescribe what was observed without mixing it with assumptions about the final solution.

Location or scopeIdentify the area, system, trade or work affected so the issue can be understood without another walkthrough.

PhotosUse visual context when it helps explain the condition or later verify the correction.

Current responsibilityShow who has the next action now rather than relying only on a list of people who have touched the issue.

Due date or expected returnAdd a date when timing matters, especially when another trade or inspection depends on the correction.

Resolution historyKeep the responses, decisions and final outcome attached to the original issue.

Issue, punch list item, RFI or change order?

These records can be related, but they are not interchangeable.

IssueAn open project condition that needs investigation, correction, responsibility or follow-through.

Punch listA closeout or completion item used to finish or correct work near the end of a phase or project.

RFIA formal request for clarification when the project needs a design or contract answer.

Change orderA formal path for changed scope, cost or contract value that requires pricing and approval.

An issue can become an RFI or change order when the facts require it. That conversion should preserve the original field context rather than making the project team re-enter the condition from scratch.

Track the path, not just open and closed

“Open” and “closed” are useful endpoints, but they are often not enough to manage an active issue. The useful question is what the team is waiting for now.

Needs field correctionA trade partner or crew has the next move.

Needs PM reviewThe superintendent has surfaced the condition and the office needs to determine the next path.

Waiting on answerThe project needs clarification from design, ownership or another responsible party.

Scheduled returnThe response is known, but the physical correction or verification is still pending.

ResolvedThe required action is complete and the outcome is documented.

A status should explain what the project is waiting on.

If the label does not help the next person understand the required action, it is not doing enough work.

Keep owner-facing issues separate from internal coordination

Some issues require an owner decision or should be visible to the client. Others involve internal subcontractor coordination, pricing preparation or discussion that should remain inside the project team.

The same underlying condition can support both views without exposing every internal note. The client needs the question, decision and current status that involve them. The project team needs the complete coordination history.

Close the issue with an outcome, not just a checkbox

When the item is resolved, the final record should make the outcome understandable: what was corrected, what decision was made, whether another workflow was created and whether any future action remains.

That resolution history is what turns issue tracking from a list of problems into a useful part of the project record.

Track the condition, the responsibility and the resolution — not just the problem.