Wisanna as an operating system for legal work

The intended deliverable shapes the work plan

Classify the assignment by its intended deliverable before designing the path. For the invoice dispute, the fictional firm might define factual preparation, research into the relevant legal issues, comparison of recovery approaches, drafting, and partner review. The matter lawyer could own preparation and drafting, with the partner responsible for reviewing the recommendation. For the supply agreement, the firm might define clarification of commercial instructions, risk analysis, selection of negotiation positions, revision, and final review. These are illustrative firm choices. They show how the expected result shapes both the work and the responsibility for it.

Choose or adapt the work plan in light of the information already available. In the dispute, the lawyer might accept a proposed preparatory step and use File check to assess whether the material supports a recovery recommendation. In the agreement matter, the lawyer might first clarify the client's commercial objective before examining the proposed wording. The plan does not impose either sequence. This opening decision should produce a clear brief for the next contributor: the intended result, the question to answer, and the uncertainty that could change the approach.

File check and Research clarify the brief

Resolve the missing-input decision against that brief. File check examines a matter against the lawyer's objective, identifies information gaps, and prepares requests grouped by the person who can answer. In the dispute, possible questions concern delivery evidence, partial payments, or the debtor's objections. In the agreement, they concern acceptance criteria, committed volumes, or the client's negotiating latitude. The team decides which answers are needed before continuing and which issues can remain open. Wisanna does not send the requests automatically. The useful output is a set of answerable questions that helps the team decide whether it is ready for the next step.

Conduct distinct research and strategy work when each is needed. Research starts from the lawyer's request. For the dispute, that request might concern the legal significance of an objection to payment; for the agreement, it might concern the effect of a proposed liability provision. Research presents findings with source verification status, including material it could not find or verify in that search. The next contributor can therefore distinguish the support found from the questions requiring further investigation. Research does not guarantee an exhaustive or correct result, and the lawyer must assess whether the findings support the intended use.

From Position to handoff and approval in Draft

Position supports the choice between approaches. In the dispute, the lawyer might compare a demand letter, further negotiation, and preparation for proceedings against the available evidence, risks, and unresolved dependencies. In the agreement, the comparison might concern a preferred provision and a fallback formulation, including the conditions under which the fallback would be acceptable. Position helps organize that comparison; the lawyer chooses, combines, or writes the position to carry forward. Research may precede this work or follow a question it exposes. The plan supports the chosen approach without turning a provisional comparison into a final legal decision.

Make the colleague handoff explicit. On Practice, handing a step to a colleague creates an Inbox item. Wisanna does not automatically assign work by matter value or complexity. In the fictional firm, the matter lawyer could hand the recovery comparison to a partner and a particular contractual issue to a specialist colleague. A useful handoff identifies the decision requested, the unresolved issues, and the contribution needed. The matter holds documents, confirmed or corrected facts, decisions, sources, and related work for later use. Lawyers control what its memory retains, so the next contributor can work from the matter's recorded context.

Prepare and approve the deliverable in Draft. The two paths now produce different editable documents: a demand letter and a revised supply agreement. Draft keeps versions, change review, saved risk analysis, and planned amendments. Colleagues can review a draft, and approval is tied to a specific version. The team should check that the document delivered corresponds to the version approved. The lawyer remains responsible for the final work. Across the matter, Wisanna offers Chat, Draft, File check, Research, and Position as distinct kinds of work, with availability depending on the customer's plan.

Matter visibility and the firm's baseline

The practice leader can then examine where each matter stands and where work is waiting. Wisanna can show matters by work-plan stage and surface review and handover items. Delivery commitments are set and managed by the legal team; plans do not enforce deadlines, service levels, or automatic approvals. Evaluate each recurring matter type against its own baseline. Record opening-to-first-reviewable-deliverable time, waiting by step, and the time to the approved version. Compare similar disputes with similar disputes and similar agreement assignments with each other, accounting for complexity, staffing, and the completeness of incoming material.

A repeatable path may reduce avoidable preparation and handoff delay, but the adopting firm must measure that effect. Check rework, source quality, legal completeness, and whether approval matches the delivered version alongside elapsed time. The lesson of these two requests is that the same specialist work can serve different purposes within plans the firm designs. A focused Wisanna demonstration can test that proposition: bring a fictional or appropriately sanitized recurring matter type, define its steps and owners, and inspect what each contributor needs to receive before the team can deliver its intended result.