Skip to content
Arrange a meeting

Product reference

AI workspace: Chambers: how it works

Ask, inspect and retain counsel’s decision with its rationale. Follow that context into later answers and drafting, and review covered work whose known recorded basis has changed.

On this page

Return to ai workspace: chambers

Availability

Available
Supported work
Ask the next matter question with sources and drafts beside the conversation, then retain counsel’s chosen approach for later work.
Start with
A retained decision carries counsel’s rationale and recorded basis into later answers and bounded drafting context. Discussing an option is separate from recording counsel’s chosen approach. A superseding decision preserves the earlier entry.
Key limit
Chambers proposes workflows; it does not start them. A reply is not an action, and BRON checks any reply that claims one against what actually ran.

Some capabilities have their own availability or configuration requirements, shown below.

Before you start

  • A retained decision carries counsel’s rationale and recorded basis into later answers and bounded drafting context. Discussing an option is separate from recording counsel’s chosen approach. A superseding decision preserves the earlier entry.
  • The matter’s recorded sources, reviewed requirements, drafts and retained decisions give the next question context. Asking what to prepare on the notice dispute can open the testimony or held draft, with unresolved receipt and reading questions visible.
  • A seat at the firm with access to the matter. Someone screened by an ethical wall does not see it.
  • Chambers answers from what the matter holds: its record and citations, the task list, deadlines, discovery, trust, the client thread and the decisions recorded on it. It also draws on the firm's workflow library.
  • Preparing an obvious next step as a draft for review is off by default.

How it works

Ask the next question with the matter’s record and counsel’s recorded decisions in context. Inspect the sources or draft beside the conversation, retain the chosen approach and why, then review the proposed work where it belongs. Known reliance can return covered work for review when its basis changes; proposed actions still require their own approval.

Given the notice record and any recorded decisions, what should we prepare next?

Decisions and the work that relies on them

  • Record the chosen approach and why

    Counsel can retain a decision, its rationale and recorded basis in matter context. Discussing an option is different from recording the chosen approach. Later answers and drafting read the retained context; superseding a decision keeps the earlier entry. Counsel still checks whether the generated text follows it.

  • Return known reliance for review

    Tracked source versions and digests can identify affected pending approvals, client drafts and research memos. Accepted fact corrections separately flag dependent drafts. Coverage and failed reads stay visible; BRON does not claim to find every reliance or rewrite finished work.

From matter question to working surface

  • Ask a question that moves the matter

    Ask what the notice record and counsel’s recorded choices mean for the next deliverable. Research and reviewed claim elements supply the legal frame; source-linked facts and chronology supply the factual basis. Compare the two accounts, identify original evidence that could answer receipt and reading, and keep those questions open until supported.

  • Review the next work where it belongs

    Open the notice draft with both accounts beside it, or ask for a workflow proposal to prepare the evidence request. Review the proposed deliverable, its source work and who must review it before starting. The draft, plan and exact outside act retain their own review; a conversational explanation does not establish that research, collection or service ran.

Answers that open the work

  • Open the work beside the conversation

    A date question opens the calendar beside the conversation; a draft question opens the draft. Valuation, discovery and billing open there too. Close the last view to return to the matter's brief.

  • A citation opens at the pincite

    A memo of linked authorities opens in a two-pane reader. Click a citation and the case or record it cites opens beside it, at the pincite.

  • One person edits the draft at a time

    The draft beside the conversation has one author at a time. Take it over and you hold the pen. Hand it back and BRON saves a draft with tracked changes. Handing it back does not send or sign anything.

What Chambers will not do on its own

  • Sending, signing, trust and phase changes need approval

    Available

    Sending, signing, moving trust money and changing a matter's phase always stop for a person's approval, whatever the firm's automation settings. Each approval covers one action, on one matter, with the exact details you saw.

  • Conversation and panels share the approval checks

    Available

    An action taken from a panel goes through the same checks as one asked for in the conversation: the person's role, the conflicts block, a single-use approval and the audit record.

  • The model never sees the approval

    BRON issues each approval for one action and sends it to your screen, not to the AI model. Your click on Approve is what carries it back.

  • Review each item in a batch

    A batch review lists each item with its summary and an unticked box. Nothing runs until you tick and confirm, and only what you ticked is approved, each with its own single-use approval.

  • A person starts the proposed workflow

    Chambers can propose a plan for an assignment. A person starts the run on the workflow screen, and the conversation records that it started.

  • A reply that claims an action is checked

    If a reply says it sent, calendared or filed something, BRON checks the claim against the actions that actually ran that turn. An action waiting for approval does not count. The check warns. It does not block.

What the matter remembers

  • Decisions carry into later answers

    Decisions your team records on a matter, with the reasons, carry into later drafts and answers on that matter. BRON carries the most recent ones.

  • How the firm decided similar changes before

    When you review a proposed change, BRON can show how the firm decided similar ones before.

When Chambers cannot read something

  • A quiet brief needs both checks

    The brief says nothing is pressing only after the deadline check and the contradiction check both succeed. A check that failed shows as unavailable, not as an empty list.

  • Each review call says who made it

    A responsiveness or coding call shows whether an attorney made it, a model proposed it, or its source is unknown. A call with no recorded source shows as unknown, never reviewed.

  • Re-scan when the board may be behind

    The checks behind the board run on a schedule and when documents arrive, so the board can show a result from before your last change. Re-scan runs a new pass for the matter, and a scan that failed says so.

Finding your way

  • One shortcut for asking and going

    One keyboard shortcut opens a box for a question, a matter search or a place to go. A second opens the brief for what you are looking at.

  • A standing brief for each matter

    Each matter keeps one written summary and a ranked agenda drawn from its task list. If the written summary cannot be produced, a plainer version shows and says which one you are reading.

What it reads from

  • The matter record and its citations
  • The matter's task list
  • Deadlines, discovery, trust and the client thread
  • The firm's workflow library
  • Decisions recorded on the matter

Who can do what

  • Counsel records or supersedes the approach and reviews affected work. Advanced strategy-decision paths retain their snapshot, exact-confirmation and provisioned-record prerequisites.
  • Counsel checks the cited accounts, keeps receipt and reading open, and chooses whether to revise the analysis or propose an evidence assignment. Review the proposed deliverable, source work and review responsibility in its existing surface; a structured workflow proposal still needs a person to start it.
  • Required reviewers of a proposed record change come from the attorneys of record for the claims it touches. Every recorded owner is required; ownership that could not be read is reported separately from no owner recorded. Chambers does not choose a substitute reviewer.
  • Sending, signing, moving trust money and changing a matter's phase always stop for approval, whatever the firm's automation settings.
  • Nothing happens until a person with access to the matter approves that exact action. Phase changes, deadlines and client document sharing need a licensed attorney.
  • Calendaring a deadline needs a licensed attorney. Chambers does not prepare that approval for anyone who cannot give it.
  • Each approval covers one action, on one matter, with the exact details you saw. It works once, and the model never sees it.
  • An action taken from a panel goes through the same checks as the conversation: role, conflicts, approval and audit record.
  • Chambers proposes a workflow. Starting it is a separate step for a person.
  • The draft beside the conversation has one author at a time. Handing it back saves a draft with tracked changes and does nothing else.
  • In a batch approval, each item starts unticked, and only what you tick is approved.

What it produces

  • The matter screen each answer opens
  • The approvals queue
  • Workflow proposals
  • Drafting and the citation check
  • The audit trail

Limits

  • What Chambers drafts, proposes or summarizes is attorney work product for your review. BRON is software, not a law firm, and nothing it produces is legal advice.
  • A reply in the conversation is not an action. An action shows in the audit trail once it has run.
  • A board that failed to refresh keeps the rows it last checked and marks that section unavailable, so what is on screen may be older than this minute.
  • Chambers does not stage next steps as drafts on its own. That option is off by default.
  • Case memory carries the most recent decisions recorded on the matter, not every one.

What BRON will not do

  • Let a list of steps in a reply pass as a plan.

    Only a plan proposed on the workflow screen can be approved and started. A reply that lists steps and owners without one is caught by a check on the answer.

  • Take an approval from the model.

    Text inside a document the model reads could try to approve something. An approval counts only when BRON issued it to a person's screen and their click brought it back.

  • Prepare a deadline approval for someone who cannot calendar one.

    Calendaring a litigation deadline takes a licensed attorney, and BRON checks before it prepares the approval. A paralegal with access to the matter never gets a prompt for an act they cannot take.

  • Put your client's question in the address bar.

    A question in a web address can end up in server logs and browser history. Chambers passes it separately, in a one-time handoff that expires after sixty seconds, and only the matter's ID appears in the address.

  • Invent a date to make the greeting urgent.

    Where no dated deadline exists, the greeting leaves out the time. A deadline runs from a real trigger an attorney confirms, and a date counted from today is worse than none.

  • Show a board count that disagrees with its list.

    The count and the rows come from one read, so the number is the number of rows you see.

When something goes wrong

  • Tracked source-version and digest reliance can identify affected pending approvals, client drafts and research memos; accepted fact corrections have a separate dependent-draft path. Unread inputs and incomplete coverage remain explicit.
  • Remembering an approach does not guarantee an answer follows it, discover every dependency, rewrite a filing or change client settlement authority.
  • A reply describing a task is not proof the task ran. Research, collection, drafting and external acts retain their own recorded states.
  • A failed deadline check shows as unavailable, never as an empty list.
  • The brief says nothing is pressing only after both of its checks have succeeded.
  • A board that failed to refresh keeps the rows it last checked and marks that section unavailable, so what is on screen may be older than this minute.
  • A scan that failed says so.
  • If the written summary of a matter cannot be produced, a plainer version shows and says which one you are reading.
  • A section nobody could read is shown as a gap, not as empty.
  • If a reply says it sent, calendared or filed something, BRON checks the claim against the actions that ran that turn. The check warns. It does not block.