DWG PN-101 / LEGAL FRONT DOOR

One front door for every legal request.

Stop triaging your inbox by hand. Pantheon gives stakeholders a single entry point, classifies every request to the right team, holds the sensitive or unclear ones for a person, and dockets an SLA on it all, automatically.

Become a design partner See how it works
PANTHEON · LEGAL FRONT DOOR DWG NO. PN-101 SCALE: NONE REV 03
01 Request arrives

From the intake form, a shared mailbox or Teams.

trigger: form · outlook · teams
02 AI classify & route

To the right team, with a priority and a confidence score.

classified: confidence 0.93
03 Gate: held for review

Sensitive or unclear? The run waits for a person.

Hold point gate_key: sensitivity
04 Register & offer

SLA docketed, offered to the owner. Requester acknowledged.

sla=business-hours · offer: 4h

NOTE: SENSITIVE OR UNCLEAR REQUESTS DO NOT PASS THE GATE UNREVIEWED.

REGISTERED
SLA DOCKETED
ProjectPANTHEON · LEGAL FRONT DOOR
Drawn byLAWYER
Checked byCOMPLIANCE
Approved byGENERAL COUNSEL
Date2026-07-11
Rev03
Sheet1 OF 7
SHEET 02 / THE PROBLEM

Requests arrive everywhere. Accountability lives nowhere.

When intake is manual, senior lawyers become a routing layer and nothing is measured.

PANEL A / EXISTING CONDITION

Today, without Pantheon

  • Requests scattered across email, chat and hallway asks
  • No log, no SLA, no throughput data
  • Senior lawyers triage by hand
  • Stakeholders chase for status
PANEL B / PROPOSED WORKS

With the Legal Front Door

  • One intake link and mailbox
  • Every request logged to a register with an SLA
  • Auto-triaged by matter type
  • Owners assigned, stakeholders kept informed
SHEET 03 / METHOD OF WORKS

What runs the moment a request lands.

Four steps, every time.

1

Request arrives

From the intake form, a shared mailbox or a message in Teams. However your stakeholders reach you today, the front door captures it.

2

AI classifies and routes

Each request is classified to the right team, with a priority and a confidence score attached.

3

Sensitive or unclear? Held

Low-confidence or sensitive requests stop and wait for a person before anyone else is notified.

Hold point
4

Registered and offered

Logged to the register with an SLA, offered to the owner with capacity, and the requester is acknowledged.

DETAIL A / SENSITIVITY GATE

Nothing sensitive routes itself.

Sensitive or unclear requests stop and wait for a person. The gate is a hold point in the run, not a note in a policy:

  • Low-confidence classifications are held for human review
  • Sensitive matters are flagged before anyone else is notified
  • Confidential reports such as whistleblowing are redacted and access-restricted

That is the core intake flow, not everything: teams typically run a continuous inbox monitor, an oversight sweep and a daily leadership report alongside it, and every step is configurable.

Run #4471 · Legal Front Door gate: sensitivity
14:02:07trigger request received (Outlook)
14:02:09classify commercial · priority high · confidence 0.93
14:02:11gate flagged sensitive, held for human review
14:26:40human approved for routing, by email reply
14:26:42register SLA docketed · offered to owner · requester acknowledged
DWG NO. PN-101SLA=BUSINESS-HOURS
WORKS WHERE YOUR TEAM ALREADY WORKS
Outlook Microsoft Teams Slack SharePoint Word Jira DocuSign Ironclad CourtListener
SHEET 04 / OUTCOME SCHEDULE

Intake that measures itself.

entry point for every request

of requests logged with an SLA

requests lost in an inbox

to stand up, not months

SHEET 06 / RFI REGISTER

What your team will want to know.

RFI-01What channels can requests come from?
A shared mailbox (Outlook or Gmail), an intake link or form, and messages in Teams or Slack. However your stakeholders reach you today, the front door captures it.
RFI-02What happens to sensitive or unclear requests?
They stop and wait for a person. Low-confidence classifications are held for review, sensitive matters are flagged, and confidential reports such as whistleblowing are redacted and access-restricted before anyone else is notified.
RFI-03Can we customise the triage rules?
Yes. Matter types, routing, SLAs and the register fields are all configured to how your team actually works.
RFI-04What do stakeholders see?
A clear acknowledgement, a reference, and status updates, without anyone on your side chasing or forwarding.
SHEET 07 / ISSUE FOR APPROVAL

Give every request a front door.

Join a small cohort of legal teams shaping Pantheon before general availability.

Become a design partner

ONE ENTRY POINT · EVERY REQUEST LOGGED · SENSITIVE ONES HELD FOR A PERSON