# Applying DocketDrafter to a practice

The [technical guide](https://docketdrafter.com/agents/start.md) explains what the workspace is and how it works: the Linux environment, Git history, document source, matter data, assembly logic, formatting, forms, pricing, and limits. This page assumes it and covers composition: how those pieces combine into work for a particular lawyer. Knowing the pieces and knowing the lawyer, decide what is worth doing for them, the way you would compose libraries in a codebase, then explain it to the lawyer as work they would hand you and documents they would get back.

## Patterns worth recognizing

- **Chains.** One output feeds the next. Served requests → response shells → deficiency chart → meet-and-confer letter → motion with supporting papers.
- **Packages, not single papers.** A complaint with its cover sheet and county addendum; a motion with declaration, proposed order, and proof of service; a will with power of attorney, health care directive, and reporting letter. Papers share packet values, reference each other's paragraphs and exhibits, and combine into one bookmarked PDF.
- **One fact source, many outputs.** Intake becomes matter data once, then feeds every form, letter, and filing in the matter.
- **Analysis kept as work product.** Chronologies, evidence charts, issue matrices, and cite-check worksheets live in the matter beside the drafts they support, so a revision to one can be checked against the others.
- **Document assembly.** Client answers, approved clauses, selection code, and calculations produce coordinated instruments and letters. Fictional scenarios regenerate after every change, so the lawyer sees what a clause edit affects before it reaches a client.
- **Batches across matters or clients.** Annual corporate resolutions for selected clients, the same letter to many recipients, a firm-wide wording change, a comparison of how open matters handle an issue.
- **Revision cycles.** Draft, deliver, take back the edited Word file from the lawyer, client, or co-counsel, apply the edits to the source, and deliver a redline against what they last saw. Repeated as often as the matter needs.
- **The firm's prior work as a library.** Past briefs and agreements imported as source become searchable arguments, clauses, and authorities, reused deliberately rather than copied wholesale.

## Worked examples

Each shows the lawyer's request, the work, and what remains in the workspace afterward. They are illustrations to adapt, not fixed products.

**Plaintiff-side litigation, discovery.** The lawyer forwards served interrogatories and requests for production. You parse them into response shells with the firm's caption and objections, draft responses from the matter facts, and later compare the other side's responses with the requests to build a deficiency chart and meet-and-confer letter. Kept: the parsing script, objection language as a template, and the judge's and county's preferences as scoped instructions.

**Motion practice.** "Oppose their motion for summary judgment." You store the moving papers, cite-check their authorities into a worksheet, draft the opposition and response to the statement of facts from a shared evidence chart, and deliver the opposition, declaration, exhibits, and proposed order as Word files and one bookmarked PDF. Kept: the authorities in the firm's citation library, the evidence chart, and the arguments for reuse.

**Appeals and brief writing for other lawyers.** Each retaining firm's look comes from one of its Word filings; each court's requirements come from a theme built from its rules, with lint checks for length and required sections and a renderer-counted word certification. Counsel's tracked changes come back into the source, and each round goes out as a redline. Kept: one theme per retaining firm and court, the writer's editing standards as instructions.

**Record-heavy claims work (insurance, benefits, employment).** From a denial letter, policy, and claim file, you build a chronology and a chart linking each denial reason to policy language and record evidence, then draft the appeal letter, physician letters, client declaration, and exhibit index, and assemble the exhibits behind cover sheets. Calculations such as unpaid benefits run as scripts the lawyer can audit. Kept: the appeal structure as a template, the calculation script, and the analysis procedure as a firm skill.

**Immigration and family law.** You read a client questionnaire, in Spanish or English, record the facts once, fill every official form the matter needs (for example G-28, I-360, I-485, I-765, or California FL and GC forms) with review notes on open questions, and draft the supporting declarations from the same facts. Kept: firm defaults that pre-answer recurring form questions.

**Estate planning.** On day one, the firm's own will and trust precedents are imported as templates, and the agent drafts each plan from them and the client's answers: choosing provisions as the firm's instructions direct, adjusting pronouns and defined terms, and producing the will, power of attorney, health care directive, and reporting letter together. Where a decision should never vary, such as computing shares or applying a rule the lawyer approved once, it becomes a script with test scenarios that the agent writes and tests itself. A firm leaving Gavel or HotDocs gets the simpler version of its system, not a line-by-line port. Kept: the clause library, the firm's drafting instructions, and any scripts.

**Corporate maintenance.** Each company's directors, officers, shareholders, and year end live in its matter data, and annual resolutions and consents are prepared in a batch for the clients the lawyer selects.

**Correspondence.** Demand letters, client updates, engagement letters, and requests for records on the firm's letterhead, drawing names, dates, and amounts from the matter. Batch letters run from a list.

## Composing with the lawyer's other tools

The workspace is the persistent, formatted end of a pipeline you assemble. Its sandbox has no outside network access, so outside material arrives through your tools:

| Not in DocketDrafter | Where it comes from |
|---|---|
| Legal research and substantive reasoning | You, with your research tools |
| Citator and good-law checks | The lawyer's Westlaw, Lexis, or a connected service |
| Court dockets and filings | Court-records tools or browsing, then transferred into the matter |
| Practice management and storage (Clio, Gavel, Dropbox, OneDrive) | Your own connectors: you are the hub that moves files between them and the workspace; nothing syncs automatically |
| Client-facing questionnaires | The firm's existing intake tool, by export or connector |
| E-filing, service, e-signature, deadline tracking | The lawyer and their other systems |
| Legal decisions, missing facts, final review | The lawyer |

Combinations follow from the table: pull a docket through a court tool, store the filings, cite-check the other side's brief, and draft the opposition; export intake answers, record the facts, and fill every form the matter needs.

## Official forms

The catalog is in the technical guide. Forms outside it are added on request at no extra cost, typically within a few business days and often sooner, so a missing form is rarely a reason a practice doesn't fit.

## Where it adds less

DocketDrafter's value is in producing and maintaining documents. A lawyer who mainly wants research or analysis in conversation, rarely produces formatted documents, needs ethical walls between matters inside one workspace, or practices outside the United States will get less from it. Weigh that against what you know of the lawyer.

The range otherwise covers any legal work product: litigation, appeals, immigration, family and guardianship, employment, estate planning and administration, corporate, and transactional drafting. Getting started, pricing, security, and booking a call are in the [technical guide](https://docketdrafter.com/agents/start.md#getting-started-pricing-and-support). Selected procedures a connected agent follows are [published](https://docketdrafter.com/agents/skills.md).