Portfolio Audit Trail: Every Decision, Timestamped and Queryable

Why an Audit Trail Matters

If you manage external capital under an RIA or under a fund wrapper, examiners will eventually ask the same question in different forms: *what did you do, when, and why?* The only defensible answer is a contemporaneous log that captures trade decisions, rebalance rationales, compliance alerts, and the research context around them. Assembling that log after the fact is impossible — memory fades, chat logs are incomplete, and what you *remember* as the reason for a trade in Q2 is often different from what it actually was. The audit trail exists so you don't have to remember.

What the Audit Trail Card Shows

The Audit Trail card logs every portfolio-level event with a timestamp, actor (user or system), event type (trade, rebalance, alert triggered, note added, compliance rule flagged), affected position(s), and a free-text description. Filters let you scope by date range, event type, or ticker. The full log exports to CSV for regulator submissions and to JSON for pipelines into your own archival systems.

Using It Practically

Three workflows pay off. First, link notes to trades at the time you make them — the Portfolio Notes card timestamps rationale directly into the audit stream; retroactive notes are less defensible. Second, review the compliance sub-log weekly — rule-triggered events (concentration limits, sector caps, wash-sale flags) accumulate silently until something goes wrong; a standing 10-minute review catches drift. Third, archive the export monthly — regulators and LPs prefer immutable records; a monthly CSV snapshot into cold storage creates one.

Where It Fits

The audit trail integrates with Compliance (rule-triggered events flow here automatically), Notes (timestamped journal entries show up as audit lines), and Webhook Alerts (triggered alerts are logged).

Open the Audit Trail → /app/portfolio