Construction Issue Log Template
Download a construction issue log template to track project risks, design questions, delays, quality concerns, responsible parties, due dates, impacts, and resolution status.
Track Construction Issues From Identification Through Resolution
A construction issue log gives project teams one organized record for problems, constraints, risks, and unresolved decisions that may affect field work. It helps contractors document each issue, assign responsibility, set deadlines, monitor cost and schedule exposure, and preserve the final resolution.
This Construction Issue Log Template is designed for subcontractors, specialty contractors, general contractors, project managers, superintendents, foremen, project engineers, quality-control teams, safety personnel, estimators, purchasing staff, and construction administrators.
What Is a Construction Issue Log?
A construction issue log is a structured register of conditions or decisions requiring attention during planning, procurement, construction, commissioning, closeout, or warranty work. Issues may involve design conflicts, missing information, delayed materials, access restrictions, safety concerns, failed inspections, quality deficiencies, labor shortages, equipment problems, owner decisions, or coordination between trades.
Each issue should identify what happened, where it occurred, who owns the next action, when resolution is required, what project activities may be affected, and how the issue was ultimately closed.
When to Use This Template
- Tracking unresolved field coordination problems
- Recording design conflicts or missing information
- Monitoring procurement and delivery risks
- Documenting schedule constraints and delayed activities
- Assigning responsibility for safety or quality concerns
- Following failed inspections or incomplete corrective work
- Tracking owner, architect, engineer, or general contractor decisions
- Monitoring access, permit, shutdown, utility, or predecessor issues
- Preparing weekly progress and coordination meetings
- Maintaining a project history through closeout
Who Should Use This Template?
This template is suitable for subcontractors, specialty contractors, general contractors, construction managers, project managers, project engineers, superintendents, foremen, schedulers, quality-control personnel, safety teams, procurement staff, owners’ representatives, and contract administrators.
It can be adapted for electrical, plumbing, HVAC, fire protection, concrete, structural steel, framing, drywall, roofing, glazing, painting, flooring, civil, excavation, landscaping, controls, commissioning, service, and maintenance work.
What a Construction Issue Log Should Include
| Issue Log Section | Purpose |
|---|---|
| Issue Identification | Assigns a unique issue number, title, category, date identified, and current status. |
| Location and Scope | Identifies the building, floor, room, area, system, trade, and affected work. |
| Issue Description | Explains the condition, missing decision, conflict, or project constraint. |
| Responsibility | Assigns one accountable company and individual to coordinate resolution. |
| Priority and Risk | Records urgency, probability, severity, and potential impact. |
| Cost and Schedule Impact | Tracks affected activities, labor, equipment, procurement, milestones, and cost exposure. |
| Corrective Action | Records the proposed solution, required follow-up, target date, and mitigation plan. |
| References | Links the issue to RFIs, drawings, specifications, submittals, change orders, photos, inspections, and reports. |
| Resolution and Closure | Documents the final decision, completion evidence, verification, and closure date. |
How to Use the Template
- Assign a unique issue number and concise title.
- Record the date identified, project area, trade, work activity, and issue category.
- Describe the issue in factual language and explain why it requires action.
- Identify affected drawings, specifications, schedule activities, cost codes, or project records.
- Assign one responsible company and one accountable person.
- Set the priority, target resolution date, and escalation date if needed.
- Record potential cost, schedule, safety, quality, procurement, and operational impacts.
- Document the proposed corrective action or mitigation plan.
- Update the status, follow-up notes, and supporting references until the issue is resolved.
- Close the issue only after the designated reviewer verifies the resolution.
An electrical subcontractor identifies that the planned transformer route is blocked by permanent ductwork installed by another trade. The issue log records the Level 1 electrical room location, affected drawing, responsible coordination lead, required decision date, schedule activity, possible crane impact, and a proposed alternate route. The issue remains open until the revised route is approved and the installation sequence is updated.
Best Practices for Construction Issue Logs
- Use one unique number for every issue.
- Write issue titles that identify the subject and location.
- Assign one accountable owner instead of a general group.
- Include realistic target dates tied to project activities.
- Separate open issues from formal RFIs, changes, and notices while linking the records.
- Record both potential and confirmed impacts.
- Update aging and status during regular project meetings.
- Carry unresolved issues forward until verified complete.
- Preserve reassignment, due-date, and status history.
- Close issues with a documented resolution and evidence.
Common Construction Issue Log Mistakes
- Using vague titles without locations
- Assigning an issue to “the team” instead of one owner
- Leaving target dates blank
- Failing to record affected schedule activities
- Mixing formal notices and informal coordination without clear references
- Closing an issue before the corrective action is verified
- Deleting reopened or reassigned issue history
- Failing to escalate overdue high-impact issues
- Creating duplicate issues in separate meeting logs
- Not linking the final resolution to revised documents or field direction
Frequently Asked Questions
What types of items belong in a construction issue log?
Common entries include design conflicts, access restrictions, delayed materials, inspection failures, quality concerns, safety issues, utility conflicts, schedule constraints, missing decisions, and coordination problems.
How is an issue log different from an RFI log?
An issue log tracks any project problem requiring resolution. An RFI log specifically tracks formal requests for clarification. An issue may lead to an RFI, but not every issue requires one.
How is an issue log different from a risk register?
A risk register usually tracks uncertain future events. An issue log generally tracks a condition that has already occurred or currently requires action. Some teams use one workbook for both but classify them separately.
Who should own an issue?
Assign the person responsible for coordinating the next action or resolution. That person may not have caused the issue, but should have authority or responsibility to move it forward.
Should every issue include cost and schedule impact?
Record whether an impact is anticipated, confirmed, unknown, or not applicable. Even when the impact is not yet quantified, identifying the exposure helps the team prioritize follow-up.
When should an issue be escalated?
Escalate when the issue is overdue, affects a critical activity, creates safety or quality exposure, requires executive or design-team authority, or cannot be resolved by the assigned owner.
When is an issue considered closed?
Close the issue after the required action is completed, the result is verified, affected documents are updated, and no further follow-up remains.
Can a closed issue be reopened?
Yes. Reopen it when the correction is incomplete, the condition returns, the resolution creates a new conflict, or the approving party rejects the result. Preserve the original closure history.
Keep Project Issues Visible, Assigned, and Moving Toward Resolution
A structured construction issue log helps project teams identify problems early, assign responsibility, monitor deadlines, and preserve a reliable record of decisions and corrective actions.
Consistent issue tracking also supports scheduling, procurement, quality control, safety, change management, and closeout. SimplySub can help subcontractors organize job information, documents, RFIs, change orders, photos, purchase orders, and related project records within one workflow.