What Is a CRS in Project Management?
A CRS is the register that stops a review like this ending in verbal agreements nobody can evidence later. Photo: Gustavo Fring via Pexels.
In project management for design and construction, CRS stands for Comment Resolution Sheet — the register used to track and formally close review comments on project deliverables. A CRS sheet is the document itself: one row per comment, carrying the comment, the response, the owner, and the status, until every row is closed and the deliverable can be approved.
It is the control that turns a pile of review comments into a managed, closable list.
CRS Means Several Things — Check Which One You Have
"CRS" is an overloaded abbreviation, and project managers hit more collisions than most because the letters are reused across unrelated domains.
| Where you saw it | What CRS most likely means |
|---|---|
| Design review, document control, transmittals, EDMS | Comment Resolution Sheet |
| Change control logs, PMO templates | Change Request Sheet — a different register; see below |
| Civil / survey / GIS data, map projections | Coordinate Reference System |
| Structural or reinforcement callouts (e.g. "T16 @ 200 CRS") | Centres — bar spacing |
| Mechanical drawings, material specs, bar stock | Cold Rolled Steel |
| Canadian immigration scoring | Comprehensive Ranking System |
| Tax and banking compliance | Common Reporting Standard |
The rest of this article covers the first one. For the discipline-specific readings, see CRS meaning in construction and CRS full form in engineering.
What a CRS Sheet Actually Contains
A CRS sheet is deliberately narrow — narrow enough to read across one screen. The columns that earn their place:
| Column | Why it exists |
|---|---|
| Comment ID | A permanent handle. Never renumber between revisions, or the audit trail breaks. |
| Document number and revision | Ties the comment to exactly what was reviewed, not to "the drawing". |
| Discipline | Lets each squad filter to its own comments without a meeting. |
| Reviewer | Who raised it — and therefore who is allowed to close it. |
| Comment | The issue, stated so someone who was not in the review can act on it. |
| Response | What the author did, or why they disagree. "Noted" is not a response. |
| Response code | A/B/C/D or Accepted / Rejected / Superseded — see document review codes. |
| Status | Open / Responded / Agreed / Closed / Rejected. |
| Dates raised and closed | The two dates that make cycle time measurable. |
Anything beyond this tends to be reporting dressed up as a column, and it is usually the first thing that stops being filled in.
One Comment, End to End
The lifecycle is the part AI summaries usually skip, and it is where most CRS processes actually fail:
- Raised. Reviewer logs comment C-047 against Drawing E-2201 Rev B: cable tray clashes with the duct run at grid F/4. Status Open.
- Responded. The designer reroutes the tray, issues Rev C, and writes the response against C-047. Status Responded — not closed. The author does not get to close their own comment.
- Verified. The reviewer checks Rev C, agrees the clash is gone, and closes C-047. Status Closed, with the closing date.
- Carried over. Any comment still open at Rev C is copied into the Rev C CRS with its original ID intact, so its age is visible.
Step 2 is the one that gets skipped under schedule pressure, and skipping it is what produces a deliverable marked "approved" with unresolved comments buried inside it.
Where the CRS Fits in Document Control
Document control governs how deliverables are issued, reviewed, and approved. The CRS is the review layer of that process: when a drawing or specification is issued for review, every comment becomes a tracked entry, the author responds, and the document is only approved once all comments are closed. Without it, "reviewed" is an opinion; with it, approval is evidenced. For the full lifecycle, see What Is a Comment Resolution Sheet?
Who Owns the CRS on a Project
Ownership usually sits with the document controller or a designated review lead, who consolidates reviewer input into a single sheet and manages closure. Reviewers raise comments; authors respond; the lead ensures each comment is verified and closed. The one rule that protects the record: the author responding is not the same as the comment being resolved — only the reviewer closes.
CRS vs the Other Project Registers
Project managers run several logs that look similar and are not interchangeable. Mixing them is a common cause of comments going missing.
| Register | What it tracks | Closes when |
|---|---|---|
| CRS | Comments on a deliverable under review | The reviewer accepts the response |
| RFI log | Questions to the client or designer | An answer is issued |
| NCR | Work already built that does not conform | The non-conformance is corrected or accepted |
| Punch / snag list | Defects found at handover | The defect is fixed and re-inspected |
| Submittal log | Status of documents issued for approval | The submittal is approved |
The CRS is the only one of these that operates before approval, on the document rather than the work. That is why it is the cheapest register to act on and the most expensive to ignore.
Why the CRS Matters to Schedule and Scope
- Schedule: open comments that are never closed resurface at commissioning or close-out, when they are far more expensive to fix. A visible CRS keeps them from hiding.
- Scope and claims: the CRS is the written record of who raised what and how it was resolved. If a dispute arises years later, it is often the deciding evidence.
- Quality: it guarantees that every comment — a potential design error, safety issue, or contractual gap — is addressed before approval.
Running the CRS Without the Admin
Managed in a spreadsheet, the CRS depends entirely on discipline: stable IDs, honest statuses, and reviewer-only closure. As reviewer and revision counts grow, that discipline gets expensive. If you want to start from a working sheet, take the free CRS template for Excel or look at worked examples by discipline.
Contrat.io enforces the same rules automatically — role-based closure, permanent comment IDs, automatic carry-over between revisions, and a defensible audit trail. Try it free for 30 days, no credit card required.
Frequently Asked Questions
What does CRS stand for in project management?
In AEC and EPC project management, CRS stands for Comment Resolution Sheet — the register used to track review comments on deliverables and close them before a document is approved.
What is a CRS sheet?
A CRS sheet is the document that holds the comment resolution register: one row per review comment, with the comment, the author's response, a response code, an owner, and a status, tracked until every row is closed.
What is the difference between a CRS and a change request sheet?
A comment resolution sheet tracks review comments on a deliverable before it is approved. A change request sheet tracks proposed changes to agreed scope, cost, or schedule after approval. They run at different points in the project and should never share a log.
Who is responsible for the comment resolution sheet?
Typically the document controller or review lead, who consolidates reviewer comments and manages closure. Reviewers raise comments and authors respond, but only the reviewer closes a comment.
How does a CRS affect project schedule?
It keeps review comments visible until they are resolved, preventing "minor" open comments from resurfacing at commissioning or close-out where they cause costly rework and delay.
Is a CRS a contractual deliverable?
On many EPC projects, yes — the completed CRS is required as proof that every client and third-party comment was formally addressed before a document was approved for construction.
How is a CRS different from an RFI log?
A CRS tracks comments raised against a deliverable during review. An RFI log tracks questions raised to the client or designer when information is missing. A comment is closed by the reviewer who raised it; an RFI is closed by an answer.