Issue Register

What is an Issue Register?

An issue register is a document that records current problems affecting a project. It contains entries for active issues requiring immediate resolution by designated parties.

Each entry in the issue register includes the problem description, severity level, and responsible owner. The document tracks status from identification through closure, creating a complete record of obstacles. Issue registers differ from risk registers, which document potential future events rather than existing problems.

The issue register exists as a spreadsheet, database, or project management system component. It captures defects, coordination conflicts, material deficiencies, and quality failures discovered during execution.

Issues Register Template Key Components

Issues register template contains standardized fields that track and monitor problems from identification through resolution. These components capture problem details, assign responsibilities, and document corrective measures taken throughout the project life cycle.

Key fields that comprehensive issue tracking templates include are:

• Issue ID: Unique reference number following PMI standards for tracking across project documentation and progress meetings.
• Date Identified: When the problem was first discovered during site inspections, quality audits, or coordination reviews.
• Description: Detailed problem summary including location, affected specification sections, impacted trades, and contract clause references.
• Category: Classification such as design conflict, material deficiency, MEP coordination failure, workmanship defect, or non-conformance issue.
• Priority Level: Severity ranking as critical, high, medium, or low based on schedule delays and cost impacts.
• Assigned Owner: Specific contractor, subcontractor, or responsible party accountable for investigation and corrective action implementation.
• Target Resolution Date: Deadline aligned with milestones, submittal approvals, inspection schedules, or substantial completion requirements.
• Status: Progress indicator showing open, assigned, in progress, pending review, on hold, or closed per CMAA guidelines.
• Resolution Notes: Documentation of corrective actions, rework completed, materials replaced, and verification methods including photos or test results.
• Related Documents: Links to supporting RFIs, submittal logs, change orders, punch list items, inspection reports, or safety documentation.

💡 Pro Tip: Add a "Days Open" auto-calculation column to instantly flag overdue items. This drives faster resolution by making chronic delays visible to everyone during weekly coordination meetings.

How to Use This Issue Register Template

Set the four thresholds on Setup first, then record one row per issue. Target dates, priority, status and escalation are all calculated from those thresholds, so nothing in the register is typed by hand except the facts.

A worked example runs through every sheet, and the banner clears once you type your own project name on Setup.

1. Complete Setup with the project, the one named person maintaining the register, and today's date, which every age and overdue flag is measured against
2. Set the cost and the number of days delay the project manager may settle alone, since that single pair of numbers is the entire escalation rule
3. Set how many days each priority has to be resolved, then enter your contract notice period and the warning window
4. Record two dates on every issue: the date it arose or was first known, and the date it reached the register
5. Write what has happened, where, and what it is holding up, rather than a heading like "ground conditions"
6. Set severity and urgency separately, then leave priority, target date and status alone because all three derive themselves
7. Answer the notice question on every row, and put the detail on Notices & Early Warnings wherever one is in play
8. Add each update as a new line on Updates Log, then close the issue against a reference and the name of whoever accepted it

Never delete a row. Mark it Void instead, because a gap in the reference numbering destroys the register's value as a contemporaneous record.

Why Use an Issues Register for Project Management?

Issues registers prevent coordination failures that delay substantial completion and jeopardize final payment release. Project management teams use them to create clear accountability for problem resolution and provide documentation supporting change order requests during disputes.

Key benefits project teams gain from risk and issue registers include:

• Payment protection: Resolving documented issues before closeout prevents owners from withholding retention or delaying final payment.
• Clear accountability: Every problem has one designated owner, eliminating confusion about who investigates and implements corrective actions.
• Faster escalation: Priority rankings immediately identify which coordination failures threaten critical path activities or milestone deadlines.
• Dispute documentation: Complete audit trails showing notification dates, response times, and resolution steps support change order justifications and delay claims.
• Quality pattern recognition: Historical data reveals recurring defects in workmanship, materials, or trade coordination enabling corrective measures.
• Improved trade coordination: Transparent tracking shows subcontractors how their issues create downstream impacts on MEP installations or finishes work.
• Reduced finger-pointing: Written records eliminate disputes about who received notifications, when responses were due, and what commitments were made.
• Schedule protection: Early identification and resolution of problems prevents minor coordination conflicts from escalating into project-wide delays.

For example, a commercial GC tracked MEP coordination conflicts in a centralized issue register instead of email threads. When disputes arose about who was notified and when, the timestamped register provided irrefutable evidence that supported their change order request - something scattered emails never could have proven to the owner's satisfaction.

Who Should Use an Issue Register for Construction?

Construction issue register serve professionals responsible for project delivery, quality control, and coordination. Multiple roles across owner organizations, contractors, consultants, and specialty trades rely on these tracking systems.

Key users of project management issue register include:

✅ Project Managers: Construction professionals overseeing multiple trades, schedules, and budgets.

✅ General Contractors: Prime contractors holding head contracts with project owners.

✅ Construction Managers: Site-based professionals managing daily construction operations.

✅ Client-Side PMs: Owner representatives overseeing contractor performance and project outcomes.

✅ Contract Administrators: Professionals managing contractual documentation, compliance, and formal processes.

✅ Subcontractors: Specialty trade contractors performing specific scope elements.

✅ Site Supervisors: Field-based personnel overseeing trade crews and daily work execution.

✅ Cost Estimators: Cost professionals managing budgets, change orders, and financial reporting.

✅ Project Coordinators: Administrative staff supporting documentation and stakeholder communication.

✅ Quality Managers: Professionals responsible for quality assurance and control programs.

When to Use a Construction Project Management Issue Register

The most ideal time to deploy an issue register is at project mobilization, maintaining it actively through substantial completion and warranty periods. Teams update the register immediately whenever problems surface during any construction phase or review cycle.

Specific occasions when project teams actively use issue registers include:

• At project kickoff: When construction activities begin and site mobilization occurs.
• During weekly progress meetings: Every scheduled coordination session with general contractors, subcontractors, and consultants.
• Following quality inspections: When formal audits, material testing, or workmanship reviews identify defects or non-conformance issues.
• When processing submittals and RFIs: During shop drawing reviews, material approvals, or design clarification responses.
• After design changes: When change orders, value engineering proposals, or owner modifications are approved.
• At substantial completion: During pre-final inspections and milestone certification walkthroughs per AIA contract requirements.
• Throughout warranty periods: After project handover during defect correction and warranty coverage timeframes.
• Before dispute documentation: When preparing change order requests or delay justification packages.

💡 Pro Tip: Start your issue register during design development, not at construction start. Early capture of constructability concerns, specification conflicts, or OSHA compliance gaps prevents costlier field corrections during execution phases.

👉 Generate your customized issue register with Mastt AI and maintain full project visibility from mobilization through closeout.

Related Articles and Templates

• Issue Log
• What is a RAID Report?
• What is a Risk Register?
• Project Risk Register
• Construction Risk Matrix
• 5x5 Risk Matrix Template
• Construction Risk Management Guide