Why a promotion event is different from a sync
Most advisor software moves data between systems continuously and silently: a note syncs to the CRM, a summary posts to the client file, a draft lands in the sent folder. Those movements are convenient and they are invisible, which means the firm cannot say when a given item became a record or who decided it should. A promotion event replaces the silent movement with an explicit one. Nothing enters the system of record until a person promotes it, and the promotion leaves a receipt. For a compliance officer, the receipt is the evidence that supervision happened before the record existed rather than after. For a small firm, the practical effect is that the client file contains what the advisor decided it should, not everything a system produced.
What a promotion event is not
A promotion event is not an export, which copies data out without a record of approval. It is not an integration or a write-back, which moves data on a schedule or a trigger rather than on a decision. It is not an audit log entry, which records that something happened; the promotion event is the thing that happens, and the log entry describes it. The distinguishing feature is that the promotion is gated by approval and produces a receipt from the destination.
Where a promotion event touches regulation
Rule 204-2(g) (17 CFR 275.204-2(g)) permits an SEC-registered adviser to keep required records electronically if the adviser can arrange and index them for retrieval, produce legible copies promptly, and safeguard them from loss or alteration. A promotion event with a receipt is one way to show when a record was created, from what, and by whom, which supports all three. Rule 204-2(e)(1) sets the retention period at five years from the end of the fiscal year of the last entry; the promotion event's timestamp is the entry. Which items are required records remains the firm's determination; the promotion event records the decision either way. Regulatory descriptions are U.S. federal and current as of September 2026.
How the term is used on this site
Promotion is the sixth stage of the sequence on the Governed Intelligence Principles page: "Approved work enters firm systems deliberately. An approved artifact should enter an established workflow with its destination, version, approval, and receipt recorded." The Regulation First design register lists the firm's designated repository and records workflow as the authority; the promotion event is how approved work reaches it.
Related terms
Articles that use this term
- Your AI Approved Nothing. You Did. Where Is That Written Down?
- Which AI-Generated Work Product Is a Required Record Under Rule 204-2?
- The Firm Remembers What It Can Reconstruct
- The Engineer Signs the Drawings. Who Signs the Advice?
Questions
How is a promotion event different from a sync or an integration?
A sync moves data on a schedule or a trigger, silently. A promotion event moves work only on a recorded decision by an accountable person and produces a receipt from the destination. The difference is that the firm can say when an item became a record and who decided it should.
Is a promotion event an audit log entry?
An audit log entry records that something happened. The promotion event is the thing that happens: the gated movement of approved work into the system of record. The log describes it.
Does a promotion event decide what counts as a required record?
No. Which items are required records under Rule 204-2 remains the firm's determination. The promotion event records the decision either way, with its time and approver.