Linear builds software for product teams. Its documented practices offer useful design ideas for legal work. The applications below are our proposals, not evidence of legal outcomes or a recommendation to place client information in a particular product. Sources reviewed 10 September 2026.
Bring the question in while choices are open.
Linear describes capturing requests from conversations and connected tools, then reviewing and routing incoming work. Linear: Intake
A legal question may first appear in a discussion about a supplier, a new market or a change to a service. With agreed access, capture the question where the work happens. Keep the original context, identify the business decision and establish when input would still be useful. The person raising it should not have to reconstruct the conversation in a separate briefing.
Review the request before treating it as accepted work. Identify the relevant entity, missing facts, urgency and responsible person. Link related requests without assuming that similar questions have the same facts or answer. A proposed due date needs checking against its source and the applicable circumstances; a routing rule cannot establish a legal deadline.
Connect each task to a decision.
Linear groups issues into projects around an outcome, connects projects to broader initiatives, and provides views of the underlying work. Linear: Concepts
Begin with the organisation’s objective and work back to the questions that need resolving. A supplier negotiation may require an options note, which depends on checking amendments and confirming the cost of switching. Each task should explain which decision it supports and what a useful result must establish.
Maintain the working record so the matter lead, business owner and permitted agent can each see the information they need. A personal action list and a management overview should draw on that record, with appropriate access. Separately rewritten summaries create another place for facts and status to drift.
Make waiting actionable.
Linear distinguishes related work from work that blocks another issue. When a blocker is resolved, its relationship becomes a related link. Linear: Issue relations
“Waiting for information” should identify what is missing, which conclusion depends on it, who can supply it and when to check again. This lets independent work continue and directs attention to the step holding up a consequential decision.
For legal work, finishing the upstream task should prompt a check that the dependency is actually satisfied. Receiving an amendment does not establish that it is complete, operative or applicable. Keep the document, assessment and dated resolution connected. Distinguish a prepared draft, completed review, authorised action and confirmed delivery; each answers a different question.
Delegate the task; keep its owner.
In Linear, an agent receives delegated work while a human remains the primary assignee. Its documentation also says that applying agent guidance depends on the integration. Linear: AI Agents
Give an agent a defined research, comparison or drafting task, the permitted sources and actions, an expected output and a reviewer. Keep the request, result, source references and actual activity available to the people responsible for the work. Instructions, access controls and substantive review perform different jobs.
The person leading the work remains responsible for assessing the result and deciding what follows. A completed agent run does not make advice approved or authorise sending a document. Records of activity help explain what happened; they do not reveal the model’s complete internal reasoning or establish that its conclusion is correct.
Give status a basis and a date.
Linear combines project health with written updates and a history. With update reminders enabled, overdue updates affect how project health is displayed. An agent can prepare an update for a person to refine. Linear: Initiative and Project updates
A useful matter update states what changed, what remains uncertain, who acts next and when the position was last assessed. If that assessment becomes overdue, make the gap visible. Silence should not leave an old reassuring status looking current. Progress in preparing a case and the strength of that case are separate assessments.
For the supplier example, “draft ready; awaiting the complete amendment set; review on Friday” tells the next person more than a percentage complete. Notify the people who need to decide, provide information or intervene, with enough context to act. Record routine activity without demanding attention to every step.
Use recurring checks, and improve them.
Linear’s Loops documentation describes scheduled and event-triggered work, access permissions, run histories and restorable published versions. It also warns that web access can send workspace information to external services. Linear: Loops
A legal workflow can check agreed sources for changes and identify earlier advice that may need review. Specify coverage, frequency, permitted disclosures, the responsible reviewer and what happens when a check fails. Distinguish a completed check with no relevant change from a source that could not be checked. Neither establishes that every relevant development has been found.
Recurring work also creates opportunities to improve the method. If a missed amendment exposes a weakness, correct the present assessment and examine the retrieval, instructions and checks that missed it. Compare the revised method with the earlier version on relevant examples, including examples held back from development. Record the decision to adopt a change and retain a way back. Repetition alone is not recursive self-improvement.
Assess the whole workflow: whether input arrived in time, whether the decision had a sound basis, and how much effort went into preparation, review and correction. A higher task count or a faster first draft can coexist with more work for the client.