Form CRS Delivery and Acknowledgment Tracking Log
Track Form CRS delivery, acknowledgments, exceptions, and audit trail in one log. Use it to document when each retail investor received the relationship summary and what follow-up is still open.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Registered Investment Advisers · Broker Dealers · Wealth Management Firms · Financial Advisory Compliance
Overview
This template tracks delivery of the Form CRS relationship summary to retail investors and captures the evidence needed to show that delivery happened. It is built for firms that need a clean record of delivery date, time, method, status, recipient reference, acknowledgment, and follow-up in one place.
Use it when you need to document routine delivery at onboarding, re-delivery after a change, or any case where compliance wants proof that the relationship summary reached the client. The structure supports both direct delivery and exception handling, so you can record a missing acknowledgment, assign a follow-up action, and keep the issue visible until it is resolved.
Do not use this log as a substitute for the actual Form CRS, client consent records, or your document retention system. It is also not the right tool for non-retail communications or for collecting unnecessary PII. Keep recipient identifiers limited to what you need for traceability, and use conditional logic or progressive disclosure if your workflow only needs follow-up fields when delivery is incomplete. The result is a record that is easier to review, easier to audit, and less likely to fail because the evidence is scattered across email, CRM notes, and spreadsheets.
Standards & compliance context
- This template supports recordkeeping for Form CRS delivery by preserving the date, method, acknowledgment status, and supporting evidence in an audit-ready format.
- Limit recipient data to the minimum necessary for compliance tracking to align with GDPR data minimization and reduce unnecessary PII exposure.
- If the log is used in a public-facing or client-submitted workflow, ensure the fields meet WCAG 2.1 AA accessibility expectations and that labels and validation are clear.
- Use retention_notes to align the record with your firm’s document retention policy and to show how long the delivery evidence must be kept.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Delivery Record Details
This section captures the core facts of the delivery event so you can prove when, how, and to whom the Form CRS was sent.
-
Delivery Date
Date the Form CRS relationship summary was delivered to the retail investor.
-
Delivery Time
Optional time of delivery if your recordkeeping process requires it.
-
Delivery Method
How the Form CRS was delivered to the investor.
-
Delivery Status
Indicate whether delivery was completed on time or requires follow-up.
-
Investor Type
Confirm the recipient is a retail investor for this record.
Recipient and Account Reference
This section links the delivery record to the right client without storing more identity data than the workflow actually needs.
-
Client Reference ID
Internal client or household reference used for recordkeeping.
-
Account Number Last 4 Digits
Optional masked account reference if needed for audit trail. Do not enter full account numbers.
-
Recipient Name
Optional name only if your compliance process requires it. Collect only what you need.
-
Primary Contact Channel
Channel used to send or confirm delivery, if applicable.
Evidence of Delivery
This section preserves the proof behind the record, which is what makes the log useful during review or audit.
-
Evidence Type
Select all evidence types that support the delivery record.
-
Acknowledgment Received?
Indicate whether the investor acknowledged receipt of the Form CRS.
-
Acknowledgment Date
Date acknowledgment was received, if applicable.
-
Supporting Evidence Attachment
Upload supporting documentation such as a delivery receipt, email confirmation, or acknowledgment record.
Exceptions and Follow-Up
This section keeps incomplete or disputed deliveries from disappearing by assigning a clear next step and due date.
-
Exception Reason
Select the reason delivery was not completed on time or requires remediation.
-
Follow-Up Required?
Indicate whether corrective action or re-delivery is needed.
-
Follow-Up Action
Describe the corrective action taken or planned, such as re-sending the Form CRS or updating contact details.
-
Follow-Up Due Date
Date by which the follow-up action should be completed.
Compliance Review and Audit Trail
This section shows who entered the record, who reviewed it, and how it should be retained for future reference.
-
Submitted By
Name or identifier of the employee entering the record.
-
Reviewed By
Compliance reviewer or supervisor, if review is required.
-
Review Date
Date the record was reviewed for completeness and compliance.
-
Retention / Audit Notes
Add any notes needed for retention, audit trail, or exception documentation. Avoid unnecessary PII.
How to use this template
- 1. Set up the log with the required delivery, recipient reference, evidence, exception, and review fields, and mark optional fields clearly so users only enter what is needed.
- 2. Enter the delivery event as soon as the Form CRS is sent or handed off, using the correct delivery method, status, and retail investor type for that record.
- 3. Add only the minimum recipient identifiers needed for traceability, such as a client reference ID and masked account number, and avoid collecting unnecessary PII.
- 4. Attach or reference the delivery evidence, then record whether acknowledgment was received and use conditional follow-up fields only when the delivery is incomplete or disputed.
- 5. Route the completed record to a reviewer, capture the review date, and note retention instructions so the log can be filed with the rest of the compliance record.
Best practices
- Use a date picker for delivery_date and follow_up_due_date so users do not free-type dates in inconsistent formats.
- Keep account_number_last4 masked and avoid storing full account numbers or other unnecessary PII in the log.
- Make follow-up fields appear only when delivery_status or acknowledgment_received indicates an exception, so the form stays short for routine cases.
- Require an evidence attachment or evidence reference for each delivery record so the log can stand up during review.
- Separate submitted_by from reviewed_by to preserve an audit trail and make approvals easy to trace.
- Use standardized delivery_method and delivery_status values so reporting does not break across teams.
- Write the follow_up_action as a specific next step, not a vague note like 'handle later' or 'check back'.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Form CRS Delivery and Acknowledgment Tracking Log used for?
This template records when the Form CRS relationship summary was delivered to a retail investor, how it was delivered, and whether acknowledgment was received. It also captures evidence, exceptions, and follow-up so the firm can show a clear audit trail. Use it as the source record for delivery tracking rather than relying on email threads or memory.
Who should complete this log?
It is typically completed by the advisor, operations team, or compliance staff responsible for client communications. The reviewer field lets a supervisor or compliance reviewer confirm the record before retention. If your workflow is decentralized, assign one owner for data entry and one reviewer for quality control.
How often should this template be used?
Use it whenever Form CRS is delivered, re-delivered, or acknowledged, including at onboarding and when a new delivery event occurs. It is also useful during periodic compliance reviews to confirm that delivery evidence is complete. If your firm updates the relationship summary or changes delivery methods, log those events separately.
Does this log replace the actual Form CRS or client consent records?
No. This template tracks delivery and acknowledgment evidence, but it does not replace the Form CRS document itself or any required disclosures stored elsewhere. Keep the underlying relationship summary, the delivery artifact, and any related client communications in your document system. The log should point to, not substitute for, the supporting record.
What should count as evidence of delivery?
Use evidence that matches your delivery method, such as an email sent record, portal notification, mail log, or signed acknowledgment. The template includes a field for evidence type and an attachment field so you can store or reference the proof. Avoid vague notes like 'sent' without a supporting artifact.
What if the recipient did not acknowledge receipt?
Record the acknowledgment status as not received, document the exception reason, and set a follow-up action with a due date. That keeps the issue visible instead of burying it in a comment field. If your process allows re-delivery or alternate contact methods, note the exact next step in the follow-up section.
Can this template be customized for different delivery channels?
Yes. You can add or remove delivery methods, adjust the evidence field to match your systems, and tailor the recipient reference fields to your client record structure. Keep the core fields intact so the log still shows who received the disclosure, when it was sent, how it was sent, and what proof exists.
How does this help during a compliance review or audit?
It creates a consistent record of delivery, acknowledgment, exceptions, and reviewer sign-off in one place. That makes it easier to answer questions about timing, method, and missing evidence without reconstructing the history from multiple systems. The retention notes field also helps you align the log with your recordkeeping policy.
What is the biggest mistake firms make with this kind of log?
The most common mistake is treating the log as a checklist instead of a record with evidence. Missing delivery dates, unclear recipient references, and no follow-up on exceptions make the log hard to defend. Another common issue is collecting more PII than needed when a masked client reference would be enough.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
Learn how AI-driven workflows close compliance gaps in hiring, field inspections, and compensation — before they become audit findings.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
Ready to use this template?
Get started with MangoApps and use Form CRS Delivery and Acknowledgment Tracking Log with your team — pricing built for small business.
