Proactive Client Disclosure & Informed Consent
This criterion assesses the organization's commitment to proactive, clear, and comprehensive communication with clients, ensuring they are fully informed and empowered to make sound decisions. It evaluates the extent to which the organization goes beyond minimum legal requirements to provide easily understandable information about services, fees, risks, and potential conflicts of interest. The aim is to ensure clients have genuine informed consent (Rida), enabling them to participate in financial/professional relationships based on trust, transparency, and a clear understanding of their rights and obligations. This encompasses the entire client lifecycle, from initial engagement to ongoing service delivery, with a particular focus on vulnerable clients or complex services. The organization should actively seek to bridge any information asymmetry and empower clients through education and open dialogue, fostering a relationship built on mutual respect and fairness. Communications must avoid concealing the truth (Qur'an 2:42), embody truthfulness (Sidq), and prevent harm (La darar wa la dirar) by pausing transactions if comprehension is lacking.
- Does the organization have a defined RACI for disclosure accuracy and a process for Board/Partner review of comprehension MI?
- Is there a standardized 'Key Facts Summary' template that includes a mandatory 'Known Limitations/Defects' box?
- How does the organization test client comprehension? Is there a version-controlled question bank and a defined pass threshold?
- Describe the Conflicts of Interest policy: does it define a mitigation hierarchy (Avoid -> Mitigate -> Disclose) and when to decline engagements?
- How are vulnerable clients identified (triage tool) and what specific communication adjustments are mandated for them?
- What controls (versioning, watermarking, approval workflows) ensure only current, approved client materials are used?
- How does the organization define 'material changes' and ensure re-confirmation of consent when they occur?
- Are there defined SLAs for providing accessible formats (e.g., large print, interpreters) and is digital content WCAG 2.2 AA compliant?
- How are complaints regarding clarity or misunderstanding used to drive specific updates to disclosure documents (closed-loop process)?
- For Shariah-compliant services, are screening criteria, purification policies, and SSB approvals explicitly disclosed?
- Does the organization provide statutory pre-contract information and cancellation rights compliant with the Consumer Contracts Regulations 2013?
- How is staff competence in disclosure and teach-back assessed (e.g., roleplay vs. just attendance)?
- RACI matrix for client disclosure and consent governance.
- Samples of 'Key Facts Summary' documents with the 'Known Limitations' box populated.
- Comprehension testing framework: Question bank, pass/fail logs, and remediation records.
- Conflicts of Interest Policy and register, showing mitigation hierarchy and examples of declined engagements.
- Vulnerability Triage Tool/Guidance and anonymized case logs showing tailored communication plans.
- Document Control Policy and screenshot of repository showing version history/watermarking.
- Change Notices and records of re-confirmed consent for material changes.
- Accessibility logs (requests vs. SLA delivery) and WCAG 2.2 AA audit reports.
- Board/Partner MI packs showing comprehension scores, readability metrics, and complaint trends.
- Training records showing roleplay/competence assessment results.
- Shariah disclosure documents (where applicable) with SSB sign-off.
- Privacy notices (layered) and consent records for data processing.
| Level | Rating | Description |
|---|---|---|
| 5 | 5/5 | Exemplary. Closed-loop improvement driven by deep analysis of comprehension data; independent audits confirm clarity; 'Known Limitations' box standard; teach-back used in 100% of high-risk cases; accessibility SLAs consistently met. |
| 4 | 4/5 | Strong. Systematic measurement of comprehension with defined targets; vulnerability triage active; conflict mitigation hierarchy enforced; digital channels WCAG compliant; material changes trigger re-consent reliably. |
| 3 | 3/5 | Adequate. Standardized templates (Key Facts Summary) in use; conflicts disclosed; initial comprehension checks for high-risk services; meets minimum regulatory requirements (CCR, GDPR, Sector rules). |
| 2 | 2/5 | Weak. Disclosure processes exist but lack tailoring; templates used but may be outdated (poor version control); vulnerability handling is ad-hoc; conflicts register exists but engagement-level disclosure is inconsistent. |
| 1 | 1/5 | Deficient. Ad-hoc disclosure; jargon-heavy; no comprehension testing; no conflicts management; potential for misleading clients or concealing defects. |
Related Criteria
Discussion (1)
📋 **Version updated: 1.0.0 → 2.9.7** **Changes:** Full import from mizan-297.json
Sign in to post a comment.