AgentPresent Blog
The Printed Carrier Page Beside the iPad
When a client points to a printed carrier illustration during a meeting, the producer needs to preserve more than the general subject of the conversation. A useful record identifies **the exact document and printed page**, states what the client asked or decided, and assigns the next action. That co
The Printed Carrier Page Beside the iPad
When a client points to a printed carrier illustration during a meeting, the producer needs to preserve more than the general subject of the conversation. A useful record identifies the exact document and printed page, states what the client asked or decided, and assigns the next action. That context helps a later follow-up address the same rider or illustration the client was viewing, rather than a similarly named provision in another version.
The iPad may contain related information the producer navigates during the conversation. The object being documented, however, is the printed carrier page beside it. This is not a night-before figure check, a PDF-export task, or a second-screen workflow. It is a meeting-note practice for connecting a physical page to a client discussion.
The distinction matters because a later reader has to find the same document the client was looking at. FINRA Rule 4511 requires members to make and preserve the books and records required by FINRA rules and Exchange Act rules, and to keep FINRA books and records in a format that complies with SEA Rule 17a-4. That duty belongs to FINRA members. It does not create a page-reference log for every insurance producer. It does show why a retained record should identify the document that was actually discussed. [1]
How Page-Level Context Is Preserved
Identify the document before recording the question
A printed page number is useful only when it is tied to the document that contains it. “Page 12” alone may describe several carrier illustrations, a rider document, or a later revision. At the point of discussion, the producer can record:
- Carrier and product name.
- Illustration or rider title, as printed.
- Version or issue date, if visible.
- Printed page number, including “page X of Y” when shown.
- A distinguishing heading or section name when the page number is ambiguous.
- The client’s specific question or choice.
- The follow-up owner and target date.
The note should distinguish facts visible on the page from information the producer inferred. If the sheet has no date or version identifier, the producer can record that the identifier was not visible and flag the document for confirmation. A missing identifier should not be filled in from memory.
Page numbering deserves similar care. A printed page might say “12 of 24,” while a cover sheet or attachment uses a different numbering sequence. Recording the printed label and a section heading gives the follow-up owner a way to locate the same passage without assuming how the document was assembled.
Capture the client’s words and the meeting outcome
The page reference establishes location; the meeting note establishes meaning. “Discussed rider” does not show whether the client asked about eligibility, cost, a limitation, or an alternative. A more useful entry separates three elements:
- Question: What did the client want clarified?
- Outcome: Was an answer provided, was a choice made, or did the issue remain open?
- Action: Who will verify or explain the point, and by when?
For example, an illustrative note might read:
Carrier A, Product B, illustration dated March 4, printed page 12 of 24, “Optional Rider” section. Client asked whether the rider applies after a specified event. No determination made in meeting. Producer to verify the applicable rider language and respond by March 12.
This example describes a documentation pattern, not the terms of an actual policy. It avoids implying that the rider applies, that the client selected it, or that an unresolved question was answered.
Connect the note to the retained record
The producer can enter the note in the firm’s approved client-record system and link it, where appropriate, to the retained illustration or other source document. The printed sheet should not be the only means of reconstructing the discussion: it can be misplaced, replaced, or separated from the rest of the client file.
SEC Rule 204-2 requires a registered investment adviser to make and keep true, accurate, and current books and records of its advisory business. The rule covers defined categories, including certain written communications, and it allows electronic storage only when its conditions are met. Those duties apply to registered advisers, not automatically to every insurance-only producer. They still illustrate why a meeting note and the source page should stay findable together. [3]
Comparing Documentation Methods
Memory, general notes, and page-specific notes
Relying on memory is the least durable method. After multiple meetings, a producer may remember that a client asked about a rider but not which illustration or printed provision prompted the question. The risk is especially apparent when a revised illustration contains similar material in a different location.
A general meeting note is better because it establishes that a subject was discussed. Still, an entry such as “client asked about rider benefits” leaves the later reader to infer both the document and the question.
A page-specific note adds a small amount of structure at the moment when the information is available. It is not a substitute for the underlying policy, application, signed illustration, or the firm’s required records. It is an index to the discussion: a way to find the relevant source and understand what remains to be done.
FINRA Rule 2111 requires a member or associated person to have a reasonable basis to believe a recommended transaction or investment strategy involving a security is suitable, based on information obtained through reasonable diligence about the customer’s investment profile. A page reference can help a later reviewer see which document was in front of the client. It does not itself prove suitability, and the rule applies to FINRA members rather than to every insurance sale. [2]
A producer-side research example
AgentPresent, an industry participant concerned with producer-side workflows, is one possible context for examining this documentation problem. The use case does not depend on a claim about a particular product feature: the practical question is whether the producer can retain the printed document’s identity and the client’s question alongside the meeting record. The cited regulatory and industry materials support the importance of identifiable documents and organized notes, not an endorsement of any vendor. [1][2][3]
A full transcript versus a focused entry
A transcript can preserve extensive dialogue, but it may still fail to identify the physical page the client pointed to. A focused entry makes that reference explicit and is easier for a follow-up owner to scan. Conversely, a short note should not be treated as a complete account of a complex recommendation.
The appropriate level of detail depends on the firm’s policies and the significance of the discussion. A concise page-level entry can coexist with more comprehensive suitability notes, communications, and retained documents. It should also follow the firm’s privacy, access, retention, and supervisory procedures rather than encouraging unnecessary collection of sensitive client information.
Follow-Up and Long-Term Record Integrity
Verify the source before answering
A later follow-up should begin with the recorded carrier, product, title, version, and page—not with a search for any rider bearing a similar name. The owner can then:
- Locate the retained document matching the note.
- Confirm the printed page and relevant heading.
- Check whether a revised illustration or other applicable document changed the context.
- Verify the answer against the appropriate current source.
- Record the response and any remaining action in the client file.
If the document cannot be matched confidently, the follow-up should say that verification is needed rather than presenting an answer as though it came from the page the client saw. If a revision exists, the record should distinguish the page discussed in the meeting from the document used to answer the later question.
This distinction is important because a follow-up can otherwise answer from a different version than the page the client saw. Rule 4511 is about preserving required books and records, not about naming every printed page. The operational recommendation is narrower: keep enough identifiers to avoid mixing versions. [1]
Preserve context as records move between people and formats
The long-term value of a page-level note is continuity. A producer may hand the matter to an associate, a service team may respond later, or a reviewer may need to understand why a communication was sent. Without a document identifier and a precise question, each handoff creates another opportunity to substitute a different rider, page, or version.
As firms combine paper discussions with electronic client files, the central challenge is not eliminating paper. It is maintaining a reliable relationship between the physical page, the recorded conversation, and the source used in a subsequent answer. A short, specific note—made while the page is in view—provides that relationship without turning an operational recommendation into a supposed regulatory mandate.