1. Overview
This circular establishes expectations for how licence holders, applicants, suppliers, and related
parties should respond to supervisory communications, reporting requests, clarification notices,
operational queries, and information requests.
The objective is to ensure structured communication, timely cooperation, and consistent handling of
operational information relevant to oversight and verification activities.
2. Core Principle
A delayed, fragmented, contradictory, or evasive response creates operational concern even before
the underlying issue is reviewed.
3. Response Expectations
| Area |
Expectation |
| Clarity |
Responses should directly address the request raised. |
| Consistency |
Information should align with previously submitted materials. |
| Timeliness |
Requests should be handled within the stated timeframe. |
| Ownership |
Responsible personnel should be identifiable. |
| Evidence Support |
Claims should be supported by documentation where relevant. |
4. Information Request Handling
Where information is requested, entities should:
- provide complete and organised responses
- avoid duplicate or contradictory submissions
- clearly identify updated documents
- maintain version control across responses
- identify whether responses replace earlier submissions
Large document dumps without structure are not considered good responses merely because the file
size is impressive.
5. Clarification Requests
Clarification requests are intended to resolve gaps, inconsistencies, missing controls, or unclear
operational explanations.
- responses should map directly to the clarification points raised
- updated documents should be clearly labelled
- partial responses should identify outstanding items
- entities should avoid introducing unnecessary unrelated material
6. Reporting Expectations
Entities may be requested to provide operational reporting, governance information, incident
summaries, complaints data, control updates, or related materials.
Where reporting is requested:
- information should be internally reviewed before submission
- data sources should be reasonably identifiable
- material inaccuracies should be corrected promptly
- significant operational changes should not be concealed
7. Communication Standards
- communications should remain professional and structured
- responses should avoid ambiguity or unnecessary escalation language
- entities should maintain internal records of supervisory communications
- third-party representatives should coordinate responses consistently
8. Common Failures
- submitting multiple conflicting versions of documents
- responding without addressing the actual request
- providing screenshots instead of structured evidence
- failing to identify document ownership or approval status
- introducing new contradictions during clarification cycles
10. Contact
For operational communication or clarification regarding this circular:
11. Effective Date
This circular takes effect immediately upon publication.
