You get a call six months after practical completion. The superintendent wants to know why a particular instruction wasn’t issued until Week 14. Or worse — legal wants your file notes. This is the moment you find out whether your documentation actually captured what happened, or just what was formally recorded in the contract system.
flowchart TD
A["Instruction or Issue Arises"] --> B{"Document in
Contract System?"}
B -->|Yes| C["Formal Record Created"]
B -->|No| D["Create Personal Issues
Register Entry"]
C --> E["Add Context Notes
to Register"]
D --> E
E --> F{"Issue Resolved
or Closed?"}
F -->|No| G["Track Status in
Register"]
F -->|Yes| H["Maintain Complete
File Record"]
G --> H
That’s exactly why every CA should be running a personal contract administrator issues register alongside whatever system the project uses for formal correspondence.
Why the Contract System Alone Isn’t Enough for CA Documentation Best Practice
At the 9am site meeting on any active construction project, a dozen issues will surface that never make it into a formal RFI or instruction that day. A subcontractor flags a clash between structural steel and the mechanical duct run. The site manager mentions the concrete supplier is struggling to meet slump requirements. Someone raises a question about whether the waterproofing spec matches what was tendered.
These are real issues with real consequences — but they exist in a grey zone. They’re not yet RFIs. They haven’t triggered a formal instruction. They won’t appear in the contract management system until someone logs them, if they ever do.
This is where CA documentation best practice diverges from what most CAs actually do. The formal record tells you what was decided. Your personal issues register tells you what was identified, when, by whom, what you did about it, and what you were waiting on. Those are two completely different stories.
When a dispute arises — and on complex projects, it’s when not if — your personal register is what lets you reconstruct the sequence of events with confidence. It’s your working memory of the project, not just the official version.
understanding your obligations as superintendent
How to Structure Your Construction Issues Log So It’s Actually Useful Later
# Personal Issues Register System - Construction Contract Administration # Smart tracking and escalation for daily contract issues and resolutions from ContractAdminCore import IssueRegisterEngine from SOPADeadlineTracker import RisksAndConstraints from RFIClassifier import PriorityMatrix from DailyReportWriter import IssueDocumentation from EscalationAlert import CriticalPathMonitor import WeatherDelayAnalyzer # Initializing Issues Register for Project: Riverside Retail Complex ✓ Database connected - 847 active issues loaded ! 12 outstanding RFIs awaiting consultant response (Day 5+ overdue) ✓ Priority matrix updated - 3 critical path risks flagged ! Safety hold notice on Subcontractor XYZ - documentation pending ✓ Daily register exported to stakeholder portal ✗ Concrete delivery delay detected - 4 dependent tasks now at risk
When you’re walking the site at 2pm on a Tuesday and you spot that the expansion joint detail hasn’t been installed to the specification, you need a fast way to capture that — with enough context to be useful in three months.
A good construction issues log doesn’t need to be complicated. What it needs is consistency. Here’s the register structure I’d recommend:
ISSUES REGISTER — ENTRY FORMAT
================================
Issue ID: [PROJECT CODE]-ISS-[SEQ e.g. 047]
Date Raised: [DD/MM/YYYY]
Raised By: [Name, Role, Company]
Location: [Area / Level / Grid Reference / Chainage]
Issue Summary: [1-2 sentence plain-English description]
Contract Ref: [Clause / Drawing / Spec Section e.g. Spec B42 Cl.4.3.2]
Linked RFI/RFQ: [RFI-012 / RFQ-004 / NIL]
Risk Flag: [Cost / Time / Quality / Safety / Latent]
Action Required:[Who needs to do what by when]
Status: [Open / Pending Response / Instructed / Closed]
Date Closed: [DD/MM/YYYY]
Notes: [Any follow-up, verbal advice given, escalation]
The key fields most CAs skip are Contract Ref and Risk Flag. Without those two, your log is just a to-do list. With them, it becomes a defensible audit trail.
| Field | Why It Matters | Common Mistake |
|---|---|---|
| Contract Ref | Links issue to specific obligations | Left blank — hard to defend later |
| Risk Flag | Identifies which issues carry cost/time exposure | Treated as optional |
| Linked RFI/RFQ | Shows formal follow-through | Issues resolved verbally and never linked |
| Date Closed | Confirms resolution was documented | Issues left “open” indefinitely |
| Notes | Captures verbal advice and informal decisions | Absent — verbal comms unrecorded |
Building Your Register with AI: A Step-by-Step Process for Principal Representatives
After Friday’s progress meeting, you’ve got two pages of handwritten notes, a marked-up drawing, and three voice memos from the site walk. Turning that into structured register entries used to take an hour. With AI, it takes ten minutes.
Here’s exactly how to do it using ChatGPT (free tier available; Plus subscription from $20/month — best suited for CAs who want flexible, conversational prompting) or Claude by Anthropic (free tier available; Pro from $20/month — best suited for longer document analysis and more precise instruction-following):
Step 1: Export your raw notes — Copy your site meeting minutes, voice memo transcription, or even your bullet-point scrawl into a plain text document. Don’t clean it up. The AI doesn’t need perfect prose.
Step 2: Open your AI tool and set the context — Paste a one-line context setter before your notes so the AI understands what it’s working with.
Step 3: Run the structuring prompt — Use the prompt below to convert your notes into register entries.
Step 4: Review for contract references — The AI won’t know your specific spec sections. Scan each entry and add clause references manually. This takes two minutes and is non-negotiable.
Step 5: Paste into your register — Whether you’re using Excel, Notion, or a purpose-built tool like Procore (from $375/month per project — best for large projects with full contract admin modules) or Aconex (enterprise pricing — best for principal representatives on major infrastructure), paste the structured entries directly in.
Step 6: Flag anything with cost or time risk — Before you close the tool, add your risk flags. AI won’t assess contract risk for you. That judgement stays with you.
Try this prompt:
You are assisting a contract administrator on a commercial construction project. Below are raw notes from today’s site meeting and site walk. Convert each distinct issue into a structured register entry using these fields: Issue Summary, Location, Risk Flag (choose from: Cost / Time / Quality / Safety / Latent), Action Required, Action Owner, and Status (Open / Pending / Instructed). Do not invent information — if a field is unclear from the notes, write “Confirm with CA”. Here are the notes:
[PASTE YOUR RAW NOTES HERE — include trade names, locations, drawing numbers, and any verbal comments made]
Using Your Register as a Principal Representative Register During Disputes and EOT Claims
During the assessment of an extension of time claim — often six to twelve months after the events in question — the contractor’s QS will present a detailed delay narrative. They’ve been building it from day one. If you haven’t been maintaining a contemporaneous record as principal representative, you’re reconstructing your position from formal correspondence alone.
A well-maintained principal representative register changes that dynamic entirely. When the contractor claims that Variation 14 caused a two-week delay to the structural frame because of late instruction, your register should show:
- When the issue was first identified (site meeting, Week 6)
- What information was requested from the contractor to allow the instruction to be formed
- When that information was received
- When the instruction issued
- Any contractor-caused delays in providing information
This is the chronological evidence base that formal RFI logs alone don’t give you. how to assess EOT claims as superintendent
The standard for a contemporaneous record isn’t perfection — it’s consistency. Courts and adjudicators give significant weight to records that were clearly maintained as events occurred, not assembled after a claim lands on your desk.
One practical approach: block 15 minutes at 4:30pm every site day to update your register. Not at the end of the week. Daily. Issues that aren’t logged within 24 hours of being identified lose their contemporaneous credibility.
Frequently Asked Questions
Frequently Asked Questions
What should a contract administrator issues register include?
At minimum: a unique issue ID, the date raised, who raised it, the location or relevant drawing, a plain-English summary, the contract clause or spec reference, the linked RFI or instruction number, a risk flag, the action required with an owner, and a status. The fields most CAs skip — contract reference and risk flag — are the ones that matter most when a dispute arises.
Is a personal issues register legally admissible?
Yes. Contemporaneous records — documents created at the time events occurred — are given significant weight in adjudication, arbitration, and litigation. A consistently maintained issues register, even a simple spreadsheet, can be more persuasive than formal correspondence if it demonstrates a clear, real-time record of what was identified and when. Consult your legal team on specific matters.
How is a personal issues register different from the project RFI log?
The RFI log records formal requests for information and their responses. Your personal issues register captures everything that isn’t yet an RFI — verbal discussions, observations, potential problems flagged in site meetings, and issues that were resolved without ever generating formal correspondence. It’s the layer of documentation that sits between what happened and what was formally recorded.
Can I use AI to maintain my construction issues log?
Yes, and it significantly reduces the admin burden. Tools like ChatGPT and Claude can convert raw meeting notes into structured register entries in minutes. The important caveat: AI won’t apply contract-specific knowledge automatically. You still need to add clause references, risk flags, and any professional judgement. Use AI to remove the friction, not to replace your expertise.
Start Running Your Register Before the Next Site Meeting
The three things worth taking from this article:
One — Your formal contract system records decisions. Your personal register records the journey to those decisions. You need both.
Two — Consistency beats completeness. A register updated daily with imperfect entries is worth more than a perfect register assembled from memory two months later.
Three — AI cuts the admin time to almost nothing. There’s no excuse for not having a structured issues log when you can convert a page of meeting notes into formatted register entries in under ten minutes.
If you’re setting this up for the first time, start with the register format in this article, run it in Excel or Notion, and use the AI prompt above after every site meeting for the next two weeks. By the end of a fortnight, you’ll have a register that actually reflects the project — not just the paper trail.
download a CA site documentation checklist
For more practical guidance on construction contract administration, subscribe to the ConstructionHQ newsletter — plain-English advice for CAs and principal’s representatives, delivered fortnightly.