CICC compliance: what your file audit actually needs

Nothing focuses the mind like a compliance letter from the College. Most RCICs will never receive one. But every RCIC should build their practice as if next week's mail might contain one — because the cost of unpreparedness is career-ending, and the cost of preparedness is a well-organised practice.

The core question CICC asks in a file audit is deceptively simple: can you reconstruct exactly what advice was given, by whom, to whom, based on what facts, at what point in time? Everything else follows from that.

In practice, a defensible file has: a signed retainer that clearly scopes the engagement; a structured intake showing what the client told you at the start; every material communication logged with timestamps; every document version-controlled with source (client-provided, IRCC-issued, third-party); a decision log for every material judgement call ('recommended CEC over FSW because…'); and a clear paper trail for any changes in scope or advice.

Where most practices fall short is not the retainer or the submission — it's the middle. The two-month period between engagement and submission where advice was given verbally in a call, referenced in a chat message, or captured in someone's private notes. When you need to reconstruct that period later, you can't.

The remedy is not more documentation discipline from the RCIC — that never scales. It's a system that makes structured logging the path of least resistance: calls generate call notes automatically, client messages live in the file (not in personal inboxes), and every material decision has a template that takes 45 seconds to complete.

One additional discipline that pays dividends: every quarter, pick three random closed files and pretend you're the auditor. If the file cannot answer the reconstruction question in fifteen minutes, that's a process problem to fix, not a one-file problem.