Product / Audit Log

Audit log for AI-built financial models

Bridge Town treats model changes as reviewable project history. The audit-log surface helps finance teams inspect model edits, run activity, output changes, and collaboration events without relying on after-the-fact notes.

Start Free Bring your own agent. Bridge Town does not run an LLM on your behalf.

What the audit log gives your team

Bridge Town is the versioned product layer beneath your AI agent: model storage, collaboration, run outputs, and review history that agents and finance teams can both understand.

Bridge Town product interface showing model files and reviewable project activity.
Bridge Town product interface showing model files and reviewable project activity.

A reviewable trail of model changes, runs, and collaboration activity.

Commit-linked context for why assumptions or model logic changed.

Project history that supports finance review and operational handoff.

Clear separation between your agent actions and the Bridge Town storage and review layer.

Audit workflow

  1. 1

    Review the project history before adopting a model change.

  2. 2

    Inspect the files, assumptions, and outputs associated with a run.

  3. 3

    Compare revisions when a forecast or scenario changes materially.

  4. 4

    Use the accepted project version as the reference point for future review.

Where teams use this page of the product

Model change reviewRun historyFinance handoffAssumption governance

Product details

Is this a compliance certification claim?

No. This page describes product auditability features. Formal certifications and assurance work are separate offline processes.

What does the audit log track?

It focuses on model and project activity: changes, runs, outputs, and collaboration context that help a team review how a financial model evolved.

Connect your agent to Bridge Town

Start with a versioned workspace, then let your own MCP-compatible agent build, inspect, and revise the finance model with you.

Start Free