A Comment Resolution Sheet (CRS) — sometimes called a comment review sheet, comment response sheet, or comment log — is the standard document AEC and EPC teams use to track review comments on technical deliverables. Every comment raised by a Reviewer is logged as a row, the Author responds, and the comment moves through statuses until it is formally closed. The CRS becomes the audit trail that proves every review comment was addressed before a document was approved.
If you need a working CRS structure today, this page gives you a complete template you can copy into Excel or Google Sheets, the recommended status codes, and the ground rules that keep a manual CRS from collapsing under its own weight.
Copy this structure directly into Excel or Google Sheets. Each row is one comment on one document revision.
| Column | What Goes In It | Example |
|---|---|---|
| Comment ID | Unique, permanent identifier. Never reuse or renumber. | C-042 |
| Document Number | The deliverable the comment applies to | DWG-ME-1204 |
| Revision | Revision of the document reviewed | Rev B |
| Section / Sheet Ref | Precise location of the issue | §4.2 / Sheet 3, Detail A |
| Comment | The reviewer's comment, stated as a verifiable requirement | Pipe support spacing exceeds allowable span per spec 200-PIP-001 |
| Category | Technical / Editorial / Clarification | Technical |
| Criticality | High / Medium / Low | High |
| Raised By | Reviewer name and discipline | J. Weber (Piping) |
| Date Raised | Date the comment was logged | 2026-07-03 |
| Author Response | The author's written response | Support spacing revised to 3.0 m; see Rev C |
| Response Code | Accepted / Accepted with Comment / Rejected / Clarification Needed | Accepted |
| Status | Open / Answered / In Discussion / Closed | Closed |
| Closed By / Date | Who verified closure, and when | J. Weber, 2026-07-15 |
Keep the status list short. Ambiguous statuses are the number one reason manual comment logs stop being trustworthy.
| Status | Meaning | Who Moves It Forward |
|---|---|---|
| Open | Comment raised, no response yet | Author |
| Answered | Author has responded, awaiting reviewer verification | Reviewer |
| In Discussion | Response disputed; needs a decision | Lead / Consolidator |
| Closed | Reviewer confirmed the resolution in the revised document | Nobody — closed is final |
1. One comment per row. Compound comments ("fix the spacing and also update the title block") can be half-resolved, and half-resolved comments are the seeds of claims. Split them.
2. Only the reviewer closes a comment. The author answering is not the same as the comment being resolved. If authors can close their own comments, your audit trail proves nothing. We cover why this matters in Role-Based Permissions in AEC Collaboration.
3. The Comment ID is sacred. IDs never change between revisions. When Rev C is issued, comment C-042 must still be C-042, or cross-revision traceability dies.
4. Write comments as verifiable requirements. "Section 4 is unclear" cannot be closed objectively. "Section 4 does not state the design pressure; add it per datasheet DS-1104" can.
5. One sheet, one owner. A designated consolidator merges reviewer input. The moment two people edit parallel copies, you have two conflicting records — see 7 Mistakes You're Making with Manual CRS Workflows.
An Excel CRS works for a handful of documents and a small review team. It reliably breaks when:
None of these are formatting problems, so no template fixes them. They are workflow problems.
Contrat.io is a dedicated CRS platform for AEC and EPC teams: every comment is a tracked item with a permanent ID, statuses change only through role-based permissions, revisions carry open comments forward automatically, and the full history of every comment is recorded as a defensible audit trail. You can try it free for 30 days — no credit card required — and import your existing review process in an afternoon.
Until then, this template and these rules will keep your manual CRS honest. For a deeper look at standardizing the process itself, read CRS Workflow Automation 101.