If there's one compliance requirement that trips up migration agents more than any other, it's file notes. They're required by the Code of Conduct, they're the first thing OMARA auditors examine, and they're the area where most agents have the biggest gaps.
The good news? Getting file notes right isn't complicated — it just requires consistency and the right system.
What the Code of Conduct requires
The Code of Conduct requires migration agents to maintain adequate records of their dealings with and on behalf of clients. This includes a contemporaneous record of:
- All advice given to the client
- Instructions received from the client
- Actions taken on behalf of the client
- All communications (phone calls, meetings, emails)
- Key decisions and their rationale
The key word is contemporaneous — meaning made at the time of the event or as soon as practicable afterwards. Backdated file notes created weeks or months later are obvious to auditors and problematic.
What auditors actually look for
1. Timestamps
Every file note should have an accurate date and time. Auditors look for notes that are timestamped close to the event they describe. A cluster of file notes all created on the same date (especially just before an audit) is a red flag.
2. Substance, not summaries
A file note that says "Spoke with client about visa options" is almost useless. A good file note says: "Phone call with client (15 mins). Discussed eligibility for Subclass 190 vs 491. Client's points score is 65 without state nomination. Advised that 190 adds 5 points, 491 adds 15 points. Client confirmed preference for 190 pathway due to desire to live in Melbourne. Advised I will check Victorian nomination requirements and follow up within 48 hours."
3. Advice trail
Auditors want to see a clear chain of: advice given → instructions received → action taken. If you advised a client to gather specific documents, there should be a note recording that advice. When they send the documents, there should be a note recording receipt. When you lodge the application, there should be a note recording lodgement.
4. Consistency with outcomes
If a visa was refused because of insufficient relationship evidence, auditors will check whether your file notes show you advised the client about evidence requirements. If there's no record of that advice, it raises questions about the quality of service provided.
5. Immutability
File notes should not be editable after creation. Auditors are suspicious of notes in Word documents or emails that could have been modified after the fact. Purpose-built case management systems with immutable, timestamped notes provide the strongest audit trail.
Practical file note format
A good file note includes:
- Date and time
- Type of interaction (phone call, email, meeting, action taken)
- Duration (for calls and meetings)
- Summary of discussion — what was discussed, what advice was given, what instructions were received
- Action items — what you committed to doing and by when
- Author — who created the note
Common mistakes
- Relying on emails as file notes — emails document communication but not the advice behind the communication. A separate file note should record the reasoning behind any advice given by email.
- Batch-creating notes — writing a week's worth of file notes on Friday afternoon. By then, details are forgotten and timestamps don't match events.
- Generic notes — "Reviewed application" or "Discussed next steps" don't demonstrate the quality of your advice.
- No notes for internal actions — if you spent 2 hours researching a policy change that affects a client's case, note it. It demonstrates the work you're doing on their behalf.
The system matters
The best file notes come from agents who have a system that makes note-taking effortless. If creating a file note requires opening a Word document, formatting it, saving it in the right folder, and hoping you remember to do it — you won't do it consistently.
LodgeHQ makes file notes a natural part of the workflow. Every note is timestamped, immutable, and attached to the relevant matter. You can create a note in seconds from any device, and the audit trail is always complete. It's the difference between compliance being a burden and compliance being a byproduct of good workflow.