Handle a client revision request
Who does this: FS Preparer · FS Reviewer · Senior Accountant · Platform Admin When: The client opened the portal and chose Request revision instead of Approve. Result: The comment is addressed upstream (mapping / disclosure / notes / regenerate / re-export); a fresh portal link is dispatched.
The engagement does not advance or regress on a revision request — it stays at NOTES_COMPLETE. The audit trail captures the comment; addressing it is up to the staff.
Before you start
- [ ] An
fs.client.revision_requestedevent in the engagement's activity log. - [ ] You hold the permission(s) appropriate to the upstream step you need to revisit (mapping / disclosure / notes / export).
Steps
- Open the engagement detail page; find the revision-request entry in the activity log. Read the client's comment in full.
- Identify the upstream step:
- Mapping issue? → Override a mapping. Regenerate statements + notes after.
- Disclosure response wrong? → Complete the disclosure interrogation. Regenerate notes after.
- Notes wording? → Generate notes (regenerate). If the client wants verbatim policy language changed, that's a constitution issue — qualified-accountant sign-off PR.
- Statement figure? → Almost always a mapping issue. Fix at mapping; regenerate.
- Re-export the DOCX.
- Re-dispatch the portal link.
How to know it worked
- The client receives a fresh portal email and (eventually) approves.
- The activity log threads
fs.client.revision_requested→ upstream-step events → freshfs.client.review_requested→fs.client.approved.