Tracks all design reviews — concept, schematic, detailed, GFC — with reviewer comments, resolution, sign-off. Critical record for design coordination + dispute resolution.
Review #34 (Drawing STR-FDN-04 Rev 3). Reviewer: PMC Structural Lead, 12-May-2026. Comments: (1) Lap length inadequate at col-beam junction — Resolved (revised to 50d). (2) Cover specification incorrect for severe exposure — Resolved (75 mm). Status: Closed. GFC issued 15-May-2026.
Every project goes through multiple design iterations — concept → preliminary → detailed → GFC (Good for Construction). Each iteration produces drawings + specifications that the PMC, structural / MEP consultants, contractor, and client review. The Design Review Register is the single document tracking every review cycle: what was reviewed, who reviewed, what comments were raised, how they were resolved, when the design got approval.
Without this register: the project enters a 'who-said-what' chaos when a discrepancy emerges months later. Was the structural drawing approved by the client? When? Was the MEP consultant's comment closed? Is there a sign-off from the architect for the final version? The register answers all of this with documented evidence.
Per-design-package: 1. Distribute the design package to all reviewers (PMC, structural, MEP, architect, contractor) 2. Set review deadline (typically 5-10 working days) 3. Reviewer comments logged in register — observation, criticality (major / minor / info), suggested resolution 4. Designer response — accept / reject / partial; redline drawing 5. Revised package issued for next review round 6. Final sign-off — GFC release with all comments closed
Per-iteration entry: - Document reference + revision number - Date issued / reviewer / closed - Comments raised vs comments closed (count + status) - Approval signatures
Who maintains: PMC document controller or design coordinator. Who uses: every reviewer + designer in the design cycle.
1. Untracked design changes — designer modifies drawings post-review without documented review cycle → contractor builds to wrong revision. Register's revision tracking + approval signatures prevents this.
2. Open review comments at construction start — projects sometimes start construction before all review comments are closed → mid-construction drawing changes → cost overrun + delay claims.
3. No designer accountability — register documents designer's response to every comment; designer can't claim 'comment never raised' later.
4. Lost review history — when a contractor disputes a design clarification 18 months in, the register's archived entries are the contractor's defence.
5. Inadequate consultant coordination — structural + MEP + architectural reviews not synchronized → conflicts found only in construction. Register's multi-reviewer entries force concurrent review.
6. GFC release without all approvals — register's sign-off discipline ensures every reviewer has approved before GFC is released.
Companion PMC formats: - Drawing Transmittal (PMC-DES-FRM-001) — formal document transmission record - Clash Detection Report (PMC-DES-RPT-001) — 3D coordination issues found during review - GFC Submission Tracker (PMC-DES-LOG-002) — final GFC issue log - BIM Coordination Log (PMC-DES-LOG-001) — BIM-based design review for major projects
Process: design review is typically governed by the PMC contract + the architect-engineer agreement. ISO 9001:2015 Clause 8.3 (design and development) provides the framework. Major Indian PMC firms (Jacobs, AECOM, Egis, Tandon, Architect-Hafeez Contractor) all run similar registers.