Skip to main content
When a client submits a request item, it’s ready for your review. You have two decisions.

​
Accept

Accepting a submitted item is terminal: the accepted document(s) are promoted to evidence on the permanent engagement record, stamped with your identity and the acceptance timestamp. The item’s status becomes accepted and it drops off the outstanding list.

​
Request a revision

If a submission isn’t right, request a revision with a structured reason. The item moves to needs revision, the reason is stored, surfaced at the top of the item in the client portal, and included in the revision email and later reminders. The client re-submits, and you review again.
A review decision applies to the item’s current submission, not to individual files independently. Superseded and rejected files are retained as “previous attempts” — never deleted — so the record of what you relied on stays intact.

​
The audit trail

Every transition — requested, submitted, accepted, revision requested — is recorded in an immutable activity log with actor and timestamp. The engagement’s record tells its own story, so you’re never reconstructing the trail after the fact.

​
What clients can and can’t do

Only a Firm User can accept an item; a client can never self-accept. Comments never change status — a conversation on an item doesn’t move it forward on its own.