All templates

Carta Automated Cap Table Anomaly Detection

Every night, WebRun opens Carta, runs a set of data-integrity checks across all active grants and stakeholder records, flags anomalies such as missing vesting schedules, duplicate entries, or ownership math errors, posts an exception report to your legal Slack channel, and logs each flag to a Google Sheet for your equity team to resolve.

Runs on WebRun · Strict Lockdown policy
Every night at 11:00 PM WebRunorchestrates each step
1 Carta audit grants and stakeholder records for anomalies
2 Slack post exception report to legal channel
3 Google Sheets log each flag with status for resolution tracking
In short

How can I automatically detect and flag cap table anomalies in Carta?

Every night, WebRun audits your Carta cap table for data anomalies including missing vesting schedules, unsigned grants, duplicate stakeholders, and ownership math errors. It posts a categorised exception report to your legal Slack channel and logs every flag in a Google Sheet with resolution status. Your equity team works through the list and marks items closed. No Carta record is changed without human action.

  • Cap table anomalies are caught nightly before they affect compliance or fundraising
  • Legal team gets a categorised Slack exception report every morning
  • Resolved flags are cleared from the Google Sheet tracker automatically on the next run

Built for equity managers · legal teams · startup CFOs · cap table administrators

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.carta.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Carta - audit grants and stakeholder records for anomalies
    carta.com
    WebRun in Carta: audit grants and stakeholder records for anomalies
    WebRun opens Carta to audit grants and stakeholder records for anomalies.
    • Open Carta and review all active equity grants and stakeholder records
    • Check for grants missing a vesting schedule, a board consent record, or an accepted signature
    • Verify that total ownership percentages sum correctly within each share class
    • Flag duplicate stakeholder names or email addresses as potential merge candidates

    Done when All data anomalies in the current Carta cap table are identified and categorised.

  3. 2
    Slack - post exception report to legal channel
    slack.com
    WebRun in Slack: post exception report to legal channel
    WebRun opens Slack to post exception report to legal channel.
    • Post a nightly exception report to the legal Slack channel grouped by anomaly type
    • List each flag with the affected record, anomaly description, and suggested resolution
    • Tag the equity manager for any critical flags such as ownership math errors

    Done when The legal team has a current exception report in Slack with every active flag and its resolution hint.

  4. 3
    Google Sheets - log each flag with status for resolution tracking
    google.com
    WebRun in Google Sheets: log each flag with status for resolution tracking
    WebRun opens Google Sheets to log each flag with status for resolution tracking.
    • Append each new flag as a row in the anomaly-tracking Google Sheet
    • Columns: date detected, record type, affected entity, anomaly description, and resolution status
    • Mark previously flagged items that have been resolved as closed, so the sheet shows only open items

    Done when The Google Sheet shows all open anomalies with detection date and status, and resolved items are marked closed.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.carta.com
ScheduleRuns automatically on this cadence
Every night at 11:00 PM
DeliveryHow each run's result reaches you
Exception report · Slack
OutputWhat each run produces - A nightly Slack exception report of cap table anomalies plus a Google Sheet tracker with open and resolved flags.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it edit or correct Carta records to fix the anomalies it finds?

No. WebRun only reads Carta and reports what it finds. All corrections are made by your equity team in Carta after reviewing the exception report. WebRun does not modify any cap table record.

What anomalies does it check for?

WebRun checks for missing vesting schedules, grants without board consent records, unsigned agreements over 14 days old, duplicate stakeholder entries, and ownership percentages that do not sum correctly within a share class. You can add custom checks during setup.

How do I mark an anomaly as resolved so it stops appearing?

Update the resolution status column in the Google Sheet to 'resolved'. WebRun reads the sheet each night and excludes resolved items from the Slack report, so only genuinely open flags appear.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.