India Audit Lens
Use the Client Overview relationship workspace
Open a client and use Overview to govern the relationship from Prospect through Profile KYC, Acceptance, service mandates, appointment, continuance, exit, and Former client. The single workspace composes the existing…
By India Audit Lens product team · Updated 2026-08-28
Before you begin
Open the existing client record and confirm its legal identity and current relationship status. Complete the Client Profile facts and KYC sections required for the intended decision. Identify the intended services and the actual relationship event; do not create a case merely to change a display status. Confirm a Manager-or-above preparer and the eligible Partner approver are available. Keep Engagement creation, execution, letters, checklists, and closure in the separate Engagement module.
Understand the four stages
Profile & KYC shows the reusable Client Profile, registrations, people, sources and KYC conclusions. Acceptance embeds the existing authoritative acceptance/continuance assessment and Partner decision. Service Mandates records one or more services proposed or authorised for the client. A service may be added later without recreating the client or repeating KYC. Relationship records the applicable appointment, continuance, rotation or exit process, requirements, evidence, decisions and history for the selected mandate.
On desktop the stage rail and active working pane scroll independently. On tablet and mobile the same stages use one natural page flow. There is no second onboarding stepper and no need to leave Overview for ordinary relationship setup.
Relationship statuses include Prospect, Onboarding, Under acceptance, Accepted, Active, On hold, Exiting, Former client, and Rejected. They are changed through governed actions, not by editing a display badge.
What the lifecycle release delivered
The release deliberately does not add a second KYC page, a second calendar, mobile verification, or any Engagement lifecycle change.
Roles
A Manager or above can prepare cases, requirements, evidence, mandates, conditions, and draft lifecycle documents. A Partner or other eligible approver makes acceptance, appointment, activation, and exit decisions where the gate requires it. Other users and read-only support grants can review but cannot prepare or approve.
Create a service mandate
Open Clients, select the client, open Overview, and choose Service Mandates. Click the add action and select an active service from the Firm service catalogue. Enter the proposed scope and fee context. For an applicable statutory-audit takeover or change, enter the current auditor and reason for change in the Relationship appointment context. Those questions are not shown for unrelated GST, tax, advisory or other mandates. Save the mandate and review its starting status, normally Proposed or Under evaluation.
Assurance mandates may require predecessor communication, independence, appointment eligibility, appointment evidence, and statutory filing evidence. A mandate cannot be moved into force merely because a client record exists.
Create the applicable lifecycle case
Choose the case type that reflects the real event:
Historic imported records may display Withdrawal or Service exit. Those values are retained for migration and history only; they are not offered when creating a new lifecycle case.
In Relationship, choose the service mandate and click the applicable relationship action. Select the actual event and appointment branch. A generic Onboarding case is not offered. Enter the effective period, reason, and scenario facts. Save the case. The product creates the applicable requirement set in legal and professional sequence.
Complete requirements and evidence
Open each requirement and read its applicability and blocker message. Add the evidence record, document, source reference, completion date, reviewer note, or not-applicable basis requested. Use Satisfied only when the requirement is complete and supported. Use Waived or Not applicable only when the control permits it and a clear basis is recorded. Core KYC, acceptance, predecessor, appointment, rotation, and exit controls can be non-waivable. Resolve blockers and structured conditions before the next controlled gate.
Requirement statuses are Pending, In progress, Satisfied, Waived, and Not applicable. Evidence remains attached to the case history.
Move the case through controlled states
The available action depends on the case and evidence. The normal path is:
Submit: Draft or Information pending to Under review. Approve or Approve with conditions: partner decision after reviewing blockers, conditions, rationale, and evidence. Record appointment: stores the approved appointment term and authority. Activate: moves an eligible mandate into force and the relationship to Active. Start exit: moves the case and relationship to Exiting. Close: completes the case only when the effective date and all exit controls permit it.
The product also supports Reject, Withdraw, and Reopen with preserved history. Enter the reasoned basis whenever prompted.
Understand the Engagement boundary
Client Lifecycle does not create, edit, activate, close, or migrate an Engagement. After the relationship and service mandate gates are complete, use the existing Audit / Engagements area to create and execute work. Acceptance templates, Engagement Letter templates, checklists, workpapers, audit files, and engagement status continue to follow their existing workflows.
Expected result
The relationship status, mandate status, applicable case, evidence, partner decision, conditions, appointment or exit record, and calendar obligations form one traceable client-level history.