Withdrawal case records · QUICK REFERENCE
Repeated requests for the same document
If the same information appears to be requested repeatedly, create a log of what was requested, when it was sent and what acknowledgement arrived. Avoid repeatedly sending sensitive documents through new channels without checking their authenticity. A compact log can make a support escalation more precise.
A practical checklist
- Record document type without publishing its contents.
- Keep submission acknowledgements.
- Ask what specific item remains outstanding.
Putting it in context
Your log might show an identity document acknowledged on Monday and requested again on Thursday. Ask whether the earlier submission was received or rejected, and why.
Keep in mind
A repeated request alone does not establish the reason for a delay.
References & further reading
The checklist and examples are original editorial guidance. External links provide background within their stated scope; they do not validate an individual operator or case.
- Operator Atlas: research methodologyOur original editorial method
- Gambling Commission: how to complainGreat Britain · complaints guidance
About this edition: how the content is made · corrections & limitations