One interview. The right department.

The routing interview classifies your matter, assigns the owning legal seats across 14 divisions, and prepares the structured intake package.

Start intake View the workflow atlas

Intake is stage one of a gated pipeline.

Every matter walks the same eight stages. Nothing reaches filing until research verifies every citation and the firm's own adversary fails to break the position.

1Intakecharter, routing, deadlines
2Strategycase theory or deal thesis
3Structureentities, parties, cap table
4Draftthe actual documents
5AdversarialRED attack, BLUE rebuild
6Filesignature-ready packet
7Docketevery deadline calendared
8Retroclose-out and firm memory

How the routing interview works

Four screens. At the end you get the routed department, the receiving seats, the deadlines to docket, and a package the firm's CLI runs verbatim.

1

Classify the track

Eight tracks. The track selects the review council and the government adversary your work will be tested against.

2

Capture the charter

Parties, jurisdiction, goal, facts, documents on hand. Hard dates are docketed the moment they surface.

3

Refine the routing

Track-specific fields plus refinements: an insurance denial pulls in coverage counsel, an offering pulls in the securities bench.

4

Get the package

Division, seats, docket list, and the runnable intake script. Submit it to the firm or run it yourself.

# the package the interview generates bin/glaw matter new 'Smith v. Jones, nonpayment' bin/glaw-intake set workflow_track litigation bin/glaw-intake set parties 'Smith LLC; Jones Corp' bin/glaw-intake set jurisdiction 'Florida; federal' bin/glaw-intake set goal 'judgment and collection' bin/glaw docket add 2026-09-01 'SOL: breach claim' # conflicts gate, then a named reviewer signs bin/glaw-intake complete --by 'reviewing attorney' bin/glaw stage strategy

Fourteen divisions. No gaps.

Every domain maps to a seat in the firm roster, over 180 specialist seats in total. The interview routes you to the owning division; the atlas shows each division's full intake flow.

Corporate & TransactionalEntity architecture, governance, contracts, IP, employment, real estate Securities, Funds & Capital MarketsFund formation, Reg D, SEC filings Tax & IRSPlanning, controversy, Tax Court Accounting & FinanceBooks of record, close, audit Litigation & Dispute ResolutionTrial, recovery, appeals, coverage Investigations & White-CollarFraud casework, follow the money Intelligence Super-StructureFour bureaus, one fusion command SEC EnforcementMarket abuse, insider, Wells Regulatory, Licensing & ComplianceAML and sanctions, licensing and permits, customs, privacy Private Client & Cross-BorderTrusts, asset protection, immigration Family & Domestic RelationsDivorce, custody, support Public Law & GovernanceConstitutional, legislative, agency Litigation SupportResearch, timelines, forensics Legal Writing & ProductionHouse standard, every deliverable

Each tile opens the workflow atlas: the division's capture list, machine fields, receiving seats, and what gets docketed on day one.

Hard gates

Nothing files on trust alone.

Nine gates stand between intake and a filed document. They are enforced in code: the pipeline refuses to advance until each gate logs its clearance event.

01
Structured intake completeevery required field, a named reviewer, no placeholders
02
Conflicts clearedengagement letter drafted, ethics check logged before any substantive work
03
Citations verifiedevery authority checked by legal research; unverifiable positions do not file
04
Adversarial survivalthe firm's own RED team attacks the position; only survivors advance
05
Red flags resolvedopen flags route back to the owning department until cleared or carried explicitly
06
Final packet verifiedrebuilt against current matter files, hash-recorded
07
Chief approvalthe Council logs the file-readiness decision with score and conditions
08
UPL disclaimeron every external deliverable, without exception
09
Docket completeevery deadline calendared, or no-deadlines recorded with a rationale

Built for the firm's machinery

Every submission is stored and retrievable. The generated package runs verbatim on the GLAW CLI, so a matter opened here is a matter the firm can work immediately.

POST
/api/intakestore a routed submission; returns its intake id
GET
/api/intake/:idretrieve one submission as JSON
GET
/api/intakesadmin listing, bearer-token gated
GET
/atlasthe full intake workflow atlas, every division

Route your matter now.

Four screens, no account, and the package is yours whether you submit it or run it yourself.

Start intake