Prepared by Client
Reviewing Evidence
Work through submissions: accept, return with a note, waive, or reopen — and keep client and internal conversation on the request.
When a client submits a request it moves to Submitted and appears in the Awaiting review tile on the PBC workspace. Select the request in the engagement to review it.
Review a submission
The detail panel shows the request's instructions, its configured expectations, every uploaded version, and the full conversation. Click any file to download it through a short-lived secure link.
| Action | Who can do it | Result |
|---|---|---|
| Accept | Admin, manager, reviewer | The request becomes accepted and counts toward the engagement's completion. |
| Return | Admin, manager, reviewer | You are prompted for a note explaining what to change. The request becomes needs changes, the note is shown at the top of the client's request, and the client is emailed. |
| Waive | Admin, manager | Marks the request as not required. It counts as resolved and is excluded from the evidence package. |
| Reopen | Admin, manager | Takes an accepted or waived request back to open so the client can respond again. |
Waive and reopen are available from any state where they make sense: waive on an open or needs changes request, reopen on an accepted or waived one.
Upload on your team's behalf
If a client sends a file outside the portal, use Upload in the detail panel to add it to the request. Firm uploads are versioned exactly like client uploads and are recorded in the audit trail as firm-uploaded. The button appears while the request is open or needs changes.
Comments and internal notes
Every request has one conversation, with two visibilities:
- Client-visible — shown in the portal and emailed to the request's assigned contacts and the engagement's coordinators.
- Internal note — visible only to your firm, highlighted in the panel, and never sent to the client.
Any firm role, including viewer, can comment. Choose the visibility in the dropdown next to the comment box before posting — it defaults to client-visible.
Check completeness
Check completeness runs a rules-based scan across the engagement and lists the requests that need a second look:
| Warning | Meaning |
|---|---|
| Request is overdue | The due date has passed and the request is not accepted or waived. |
| Completed status has no available evidence | The request is submitted or accepted but has no usable file attached. |
| Available evidence does not match the expected format | None of the uploaded files use one of the request's expected extensions. |
| Evidence requires documented redaction review | The request is flagged Redaction required and has evidence, so someone needs to confirm the redaction was checked. |
Click a request number in the results to jump straight to it. The check is a prompt for human review, not a conclusion — it never changes a request's status.
Closing out
Once every request is accepted or waived, click Complete in the engagement header. See Engagements for what completing locks, and Tracking and exports for the tracker and evidence package you hand off afterwards.