Platform · Audit Trail

The audit record writes itself.

Six months later, someone asks why. Today the answer lives in emails, screenshots, and memory. In NOVY, every decision, exception, override, and document event is timestamped as it happens — an append-only audit record that builds itself inside the workflow.

01 · Happens

Work happens — the audit record captures it

An approval lands, a fee is overridden, an advisory is acknowledged. Each action writes its event the instant it completes — no one “does documentation” as a second job.

02 · Everything

The exceptions land too

An audit record is only credible if it captures the messy parts — the overridden fee, the manually added form, the upstream version change. Those events appear next to the clean events instead of being omitted.

03 · Who

Every line has a who, a when, a what

Events carry actor, timestamp, and object — a person, a system, or a source — so the audit record answers questions instead of raising them.

04 · Sealed

Append-only means append-only

The audit record grows; earlier events are not rewritten. Later events can supersede earlier ones while preserving the sequence that actually occurred.

05 · Export

Ready when someone asks

When the question comes — from an auditor, an owner, a dispute, or an information request — the audit record exports as it stands: PDF for the reader, CSV for the analyst.

Workflow → audit record
Workflow → record
Written as it happens
Exception approved — J. Moorereason attachedApproved
4:02 PMDecision documentedWritten the instant it completed
Event History
Clean events and exceptions alike
2:51 PMFee value overridden · Returned check fee $25.00K. Gallespi
3:04 PMForm added manually · Bed Bug Addendum v1.4.1K. Gallespi
3:20 PMUpstream version change detected · v1.5Document Library
3:41 PMAdvisory acknowledgment · Language coverage gapK. Gallespi
Event detail
Actor · timestamp · object
2:51 PM
When
Fee overridden · $25.00
What
K. Gallespi
Who
Answers questions instead of raising themReviewer identity captured
Retention
The record grows, never rewrites
Record statusAppend-only
3:41 PMAdvisory acknowledgmentearlier line — stays fixed
4:02 PMDecision documentedappended beneath, nothing rewritten
Form versions pin at send
Exports
PDF · CSV, as it stands
Export recordThe record answers when someone asksPDFCSV
Ready when someone asksExport record
4:15 PMRecord exported · requested by K. GallespiThe export itself is an event
NOVY · Audit TrailWritten as it happens

Who did what, when, and why —
already written down.

What changes

Documentation nobody has to do

When the audit record builds with the workflow, three things stop happening.

Operator

No reconstruction projects

Answering “why” becomes reading, not archaeology across inboxes and screenshots.

Portfolio

One memory

Every property's decisions use the same audit structure — institutional memory is less dependent on staff tenure.

Risk & compliance

An account that holds up

Timestamped, attributed, append-only history supports consistent responses to disputes, audits, and information requests.

Connected system

What this capability inherits, and what it gives

Audit Trail is one step in one governed leasing workflow — each step builds on what came before.

Inherits from upstream
  • Events from every capability — verification, decisions, fees, lease assembly, handoff runs
  • Actor identity from workflow sessions
  • Assembly stamps from lease generation
Gives downstream
  • A reconstructable history per application and lease
  • Exports (PDF · CSV) on demand
  • The evidence layer regulatory tracking and disputes draw on

Ask the audit record a hard question

Bring a “why did this happen” from last quarter — we'll show you what the answer looks like when it's already written. If the right answer isn't NOVY, we'll tell you.