11.2 Creating, Keeping & Retrieving Records Correctly

11.2 Creating, Keeping & Retrieving Records Correctly

Quick Answer: Record-keeping skill has four legs: (1) create accurate records contemporaneously; (2) keep them securely under firm procedures for the full FAIS/GCOC/FIC retention periods; (3) retrieve them promptly when the Authority, compliance officer, key individual, or client lawfully requires access; and (4) never destroy, fabricate or backdate during the retention window. A missing record of advice, a botched client copy request, or an unprepared inspection are exam and real-world failure modes.

From statutory map to operating skill

Section 11.1 answered what must be kept and for how long. This section answers Task 5’s second qualifying criterion: can you create, keep and retrieve records correctly as a representative inside an FSP’s systems?

Regulators do not grade your memory. They grade the file. Ombud determinations often turn on whether the provider can show what was disclosed, what needs were recorded, which products were compared, and what the client decided. Compliance monitoring under section 17 samples the same files. Your personal credibility and the FSP’s licence standing both depend on operational discipline.

Skill 1 — Create accurate records contemporaneously

Why timing matters

A record written while the facts are fresh is evidence. A “reconstruction” written after a complaint is advocacy — and if it invents details, it becomes an honesty and integrity problem.

Contemporaneous practice means:

• Completing the record of advice (or equivalent advice documentation) as part of the advice process, not “when I have a quiet Friday”;
• Logging client instructions when received (including telephone instructions) with date, time, substance and any risk warnings given;
• Capturing disclosures made (or confirming that standard disclosure packs were delivered and explained);
• Opening a complaint record the same day a complaint is recognised, even if investigation continues later;
• Filing FICA identification and verification artefacts when onboarding, not after the product is already in force and forgotten.

What “accurate” means

Accuracy is not volume. A ten-page template full of unchecked boxes is worse than a shorter file that truthfully shows:

Scenario A — Missing record of advice

Facts: Six months after placing a retirement annuity, the client complains that the product was unsuitable. The representative insists the advice was perfect. The file contains an application form and a commission schedule, but no record of advice, no needs analysis, and no note of products considered.

Analysis:

• Under the GCOC advice rules, a record of advice must document the basis of the advice (information used, products considered, reasons for the recommendation).
• Under GCOC section 3(2), systems must record and retrieve material documentation relating to the financial service.
• Without that record, the FSP cannot demonstrate suitability review, complaint handling becomes defensive, and the representative’s recollection is weak evidence.
• Correct conduct at the time would have been: complete the record of advice before or when finalising the recommendation and store it in the firm system immediately.

Exam trap: “The signed application is enough.” An application proves a transaction was concluded; it does not prove advice quality or the basis of the recommendation.

Scenario B — Verbal advice never written down

Facts: On a Teams call, a representative recommends switching a unit trust. The client agrees verbally. The switch is processed. No call note, no record of advice, no confirmation of risks discussed.

Analysis: Verbal channels are still financial services communications contemplated by the Codes. Section 3(2) expressly contemplates recording verbal and written communications. Digital convenience is not a record-keeping exemption.

Skill 2 — Store securely (and lawfully)

Security is a compliance control, not only an IT preference

“Safe from destruction” and confidentiality duties (GCOC section 3 themes) require more than a cardboard box under a desk:

Electronic records

Electronic storage is expressly contemplated. The practical test taught for RE5:

• Can authorised persons access the record within operational deadlines?
• Can the record be readily reduced to written or printed form for the Authority, Ombud, client or court process?
• Is the electronic system included in business continuity and cybersecurity arrangements proportional to the firm’s risk?

Photos of handwritten notes on a personal phone that only the representative can unlock are a fragile system — not a robust firm procedure.

Retention vs storage location

Do not confuse “we use a cloud CRM” with “we meet five-year retention.” You still need:

• Retention rules that prevent auto-deletion before the FAIS/GCOC/FIC clocks expire;
• Exportability if the vendor relationship ends;
• Mapping of which repository holds advice files, complaints, section 18 logs, register evidence, and FICA packs.

Skill 3 — Retrieve on lawful request

Who may require retrieval

Representatives must cooperate with retrieval requests from, among others:

GCOC section 3(2) themes teach that providers must ensure records are available for inspection within the prescribed time when the Authority requests (commonly taught: within seven days). Firm procedures may set tighter internal SLAs so that the CO can meet external deadlines.

Scenario C — Client requests a copy of the record of advice

Facts: A client emails: “Please send me the record of the advice you gave me last year about my endowment.” The representative is annoyed and replies that records are “internal only.”

Analysis:

• Question-bank logic and Code practice treat the record of advice as something the client is entitled to receive as a summary of the basis of advice — not as a secret firm weapon.
• Refusing without a lawful basis undermines transparency, damages complaint posture, and can escalate into a formal complaint.
• Correct path: follow firm procedure, retrieve the stored record, provide the client with the record of advice content (and any other documents the firm’s policy and law require), and log the request and response.

Exam trap: “Records exist only so the FSP can defend itself; clients never see them.” Defence and client transparency are both legitimate purposes — and poor files achieve neither.

Scenario D — Inspection readiness

Facts: The CO announces that next week the Authority (or an intensive internal audit) will sample twenty advice files, ten complaint files, the representative register extract, and a sample of FICA onboarding packs. Several representatives plan to “update files over the weekend.”

Analysis:

• Inspection readiness means files are complete before the notice, because they were built correctly at the time of service.
• Weekend backdating of needs analyses or fabricating product comparisons is an integrity failure — often worse than an honest gap with a remediation plan.
• Ready firms can retrieve within hours: register current; section 18 categories populated; client files indexed; FICA packs attached; complaint statuses visible.

Practical readiness checklist for a representative’s book of business:

1. Every advice case has a record of advice (or documented reason if pure intermediary service with no advice).
2. Disclosures and product documents are stored with the file.
3. Instructions and material calls are noted or recorded per firm policy.
4. Complaints touching your clients appear in the firm complaints system, not only in your inbox.
5. Your appointment and supervision status on the register matches reality.
6. FICA artefacts for your onboarded clients are complete in the approved system.
7. You can find any file without relying on a personal laptop that is offline.

Skill 4 — No destruction (or alteration) during the retention period

What you must not do

When a genuine error is found (wrong product code typed, incomplete disclosure pack), the lawful path is usually supplement with a dated correction note or remediation, not rewrite history to pretend perfection.

Scenario E — “Delete it; the five years feel long enough”

Facts: A branch manager tells staff to purge all files older than three years to save cloud costs. Some products terminated only two years ago; some FICA relationships ended last year.

Analysis: A casual three-year purge is not aligned with the commonly taught five-year FAIS/GCOC floors, nor with FIC retention triggers. Representatives who participate in unlawful destruction expose themselves. Escalate to compliance/KI; do not execute a purge instruction that contradicts statutory retention.

Putting the four skills into a single workflow

Use this end-to-end loop for every material client interaction:

Interact → Capture facts contemporaneously → File into firm system
    → Secure storage + retention clock → Retrieve on request
    → Remediate gaps honestly → Never destroy early

How Task 5 links to other RE5 tasks

Exam focus — choose the option that preserves the trail

When RE5 offers four responses to a record scenario, prefer the option that:

1. Creates a contemporaneous, truthful record;
2. Uses firm systems rather than private side-channels;
3. Retrieves and shares lawfully with client/Authority/CO;
4. Refuses destruction or fabrication;
5. Escalates retention or access conflicts to compliance/KI rather than improvising.

Reject options that treat records as optional admin, claim verbal advice needs no trail, deny clients any copy of advice records as a blanket rule, or invent post-complaint paperwork as if it were original.

If you can create cleanly, store securely, retrieve quickly and never destroy early, you have operationalised Task 5 — and you have protected the client, the FSP licence and your own fit-and-proper standing at the same time.