ProductsCRS BuilderNew
Client comments in. A finished CRS out.
When a client returns a marked-up document, someone usually retypes every comment into a Comment Resolution Sheet. CRS Builder reads the return, makes one numbered row per comment with its picture, and exports into the client’s own form with the header untouched.
| No. | Ref. | Comment | Marked area | Response | Status |
|---|---|---|---|---|---|
| 1 | p. 1 · N2 | Confirm N2 orientation against the P&ID. | — | Open | |
| 2 | p. 1 · note 4 | Hydrotest pressure to be revised; update the note. | — | Open | |
| 3 | p. 2 · det. B | Add the lifting lug detail. | — | Open | |
| 4 | p. 2 · N2 | Confirm N2 orientation. Repeat of 1 | — | Repeat |
The retyping, done for you.
With its section, page and a picture of the marked area.
Upload their blank sheet once; every export fills it in.
Each clouded note on a drawing becomes its own row.
Edit, merge or split rows. Repeats are flagged.
From the client’s return to their own form.
Upload the return
The marked-up document or drawing, as the client sent it.
Rows are made
One numbered row per comment, with its section, page and picture. Repeats flagged.
An engineer edits
Merge, split or correct rows, write the responses, sign off.
Export
Into the client’s own form, header untouched. Nothing retyped.
What document controllers ask first.
What does it read?
The marked-up documents a client sends back. On drawings, each clouded note becomes its own row, with a picture of the marked area.
We have to answer in the client’s template.
That is the point. Upload their blank sheet once; every export fills it in, with their header untouched.
What if the client repeats a comment?
Repeats are flagged, so the same point is not answered twice in two different ways.
Who checks the rows?
An engineer. Rows can be edited, merged or split before anything is exported, and the engineer signs off.
What happens to the documents?
Records sit in your own database, files are deleted when the run ends, and an administrator approves every account.