Send a Document for Review
Route any document through a formal approval round, assign reviewers, and track every decision in one place, without leaving Completix.
Completix lets you put any document through a structured review and approval process. You add one or more reviewers, submit the document, and each reviewer approves or rejects it directly in the app. Every round is recorded with timestamps and decisions, so you always have a clear audit trail. This works for documents stored in the Documents repository and for documents attached inside components such as RAID, Schedule, and Governance.
Document review is built into the Document Details panel. Open any document, then open Document Details from the toolbar and switch to the Review tab. From here you can add reviewers, submit the document, and watch the approval round progress. A second tab, History, keeps a dated record of every round the document has been through.
Because review is attached to the document itself, you can start a round wherever the document lives. A requirements file in the Documents repository, a mitigation plan linked to a RAID item, or a deliverable attached to a governance gate all use the same Review tab and the same approval flow.
In a document list, the review status of each file is shown at a glance by a small status icon. A yellow clock means the document has an approval round in progress and is still pending a decision. A green check means the document has been approved. Files with no icon have not been submitted for review.
Start an approval round
On the Review tab, click Add reviewer to open the picker. The picker has two tabs:
- People, to search for and select individual users by name or email.
- Groups, to add a predefined group of reviewers in a single step.
Add as many reviewers as the document needs, then submit to start the round. Each reviewer is notified that a document is waiting for their decision. Until you submit, the panel shows that no reviewers are assigned yet.
You choose the reviewers for each round, so the same document can go to different people depending on what is being reviewed. Add a group when the same set of approvers reviews a document type regularly.
How reviewers respond
Once a round is open, each reviewer opens the document and uses the Review tab to record a decision with Approve or Reject. The panel shows the overall progress of the round, such as how many reviewers of the total have completed their decision, and the status of each individual reviewer.
The Comments section in the same panel is for discussion about the document. Comments are kept separate from the approve or reject decision, so a reviewer can ask a question or raise a point without having to reject the document to do it.
Need to run the review again, for example after the document has been revised? Use Reopen to start a fresh round. The previous round stays recorded on the History tab.
Track status and history
While a round is open, the Review tab shows a status banner with who submitted the document and when, along with the live state of each reviewer. The overall result follows the reviewers' decisions, so you can see at any moment whether the document is still pending, approved, or rejected.
The History tab records every approval round the document has been through, with timestamps and the decision each reviewer made. This gives you a full audit trail of how a document reached its current state, without needing a separate tracking tool.
Review in Governance gating
Document review is especially useful in Governance, where a project moves through a series of gates and each stage has deliverables that must be completed before the gate can be passed. A gate deliverable can require document approval, shown by an Approval required badge on the deliverable.
In that case the document attached to the deliverable goes through the same Review tab and the same approval round described above. Once the required reviewers approve it, the deliverable is satisfied and the project can progress through the gate. This ties your document approvals directly to the project's governance, so a stage cannot be passed until the documents that support it have been formally approved.
See the Governance page documentation for the full explanation of how gates, stages, and deliverables work within a project.
