What Are Atlas Lists?
Atlas Lists are curated collections of firm-specific content scoped to practice areas, matter types, or teams. An M&A team's indemnification precedents. A litigation group's privilege playbook. A contracts team's approved clause library. A real estate practice's closing-checklist templates.
Unlike generic template libraries, Lists are authored by your team, live in your firm's curated knowledge graph, and stay current as your practice evolves. They're queryable from Atlas Chat, wired into Atlas Agents so they appear in every review, and shared across your firm so every deal, case, and contract benefits from your institutional knowledge.
The Problem They Solve
Most firms have decades of decision-making embedded in closed deals, concluded cases, and approved contracts. That knowledge is fragmented across iManage, SharePoint, email archives, and the heads of senior partners. When a junior M&A associate starts a new deal, she doesn't know which indemnification caps the firm typically accepts, which survival periods work for your underwriters, or which representations and warranties your GC insists on.
When she turns to AI for a first draft, she gets a generic SPA with generic caps. She then has to manually walk it back to firm standard. Every deal, every time.
Atlas Lists solve this by surfacing institutional decisions inside AI workflows. Your firm's playbook becomes part of the AI's base knowledge, so the first draft is already aligned to your standards. The agent that reviews the other side's markup knows your precedents and flags deviations before they reach a human. The agent that drafts an indemnification schedule pulls from your actual caps, not from a legal template site.
How Lists Ride on Singularity
Atlas Singularity (v6) is a per-tenant curated knowledge graph that ingests your firm's data from iManage, SharePoint, OneDrive, NetDocuments, and email. Atlas Agents continuously refine that graph, classifying documents, linking related work, and extracting firm-specific patterns as new content lands. That curation is what makes the graph sharp and firm-specific.
Atlas Lists are authored inside that graph. When you create a precedent set or a clause library, you're not building it from scratch, you're curating it from your existing work. When an Atlas Agent runs a review or drafts a document, it reads from the Lists you've defined, pulling context from the curated knowledge graph, and grounds every decision in your firm's prior output.
What Just Shipped
This week we shipped the prompt library modal redesign with clearer visibility controls and segmented filters. The authoring experience now matches the rest of Atlas: card rows, toggles for private / team / firm visibility, and filters so you can organize Lists by practice area, matter type, or custom tag. When you save a List, it's immediately available to all Atlas Agents in your firm.
We also wired live-refetch into the prompt library so Lists you just authored appear immediately without a page reload, and aligned the assistant-picker interface so the same mental model (select a template, configure it, run) carries through chat, agent creation, and Workspace task setup.
Concrete Workflows
M&A teams: Create a 'Standard M&A Reps & Warranties' List pulling from your last 10 deals. When an agent reviews an incoming SPA, it flags reps and warranties that deviate from your standard. When an agent drafts your response, it starts from your template.
Litigation teams: Author a 'Privilege Log Template' as a List, with your firm's definitions of attorney-client privilege, work product, and common waiver risks. Every privilege review agent gets configured with that template, so your whole practice enforces consistent standards across 20 parallel cases.
Contracts teams: Curate Lists for each contract type (NDA, MSA, SOW, Service Agreement). Each List includes your firm's red-line positions, approved clause variants, and negotiation notes. When a contracts agent drafts an NDA, it pulls from your Library, not from Termly or a public template.
Access Control and Sharing
Lists inherit the same access model as the rest of Atlas. You can author a private List for your own use, share it with your practice group, or publish it firm-wide. Every access decision is logged in the audit trail. When you update a List, agents that use it see the new version immediately on their next run.
Where Lists Live
- Authoring: Inside the prompt library modal in Atlas Chat. Name your List, paste in precedent text or outline a playbook, tag it by practice area and matter type, set visibility, and publish.
- Discovery: Searchable from within Atlas Chat and the assistant picker when you're creating or configuring an agent.
- Execution: Every Atlas Agent in your firm is pre-configured to read from your Lists. When a review agent runs, it knows your Lists. When a drafting agent produces an SPA or indemnity schedule, it pulls from your precedents.
- Updating: You can update or retire a List anytime. Agents that are in flight will complete against the version they started with; agents created after the update will use the new version.
Next Steps
Atlas Lists are available now in Singularity (v6). If you're already using Atlas Workspaces for document review and drafting, you can author your first List in the prompt library today.
Visit https://atlas-ai.io to request a demo and see Lists in action across a real M&A workflow.
See it in your environment.
AtlasAI deploys inside your Azure tenant. Private by architecture, not policy.
Request a demo →