Client Portal
QA Workflow
Route reports through a QA review cycle before delivering them to clients — assign reviewers, track approvals, and gate publication on the portal.
The QA workflow ensures every report meets your quality standards before it reaches the client. Reports move through defined statuses, and reviewers can flag issues or request changes before final delivery.
Report Statuses
Every report follows a three-stage lifecycle:
| Status | Description |
|---|---|
| Draft | The report is being written. Findings, narrative sections, and evidence are still being added or edited. |
| Review | The report is ready for internal review. A reviewer examines the content for accuracy, completeness, and quality. |
| Final | The report has been approved and is ready for client delivery. |
Review Process
- The consultant completes the report and sets the status to Review
- A reviewer is assigned to examine the report
- The reviewer checks findings, narrative content, evidence, and formatting
- If changes are needed, the reviewer flags specific issues and the status returns to Draft
- Once all issues are resolved, the reviewer approves the report and sets it to Final
- The finalized report is exported and shared through the portal
Only users with the appropriate permissions (typically Admin or Consultant roles) can change report statuses and approve reports.
Best Practices
- Establish review criteria -- define what reviewers should check (e.g., severity accuracy, evidence quality, remediation clarity)
- Use the Draft-Review-Final cycle consistently -- avoid sharing reports that have not been through review
- Assign dedicated reviewers -- separate the person writing the report from the person reviewing it
Treat Final as locked by convention — if further changes are needed after finalization, move the report back to Draft so reviewers know it needs another pass.