How to Use Microsoft Copilot for Lawyers

Define the matter and the work product

Do not begin with “summarise this case” or “tell me what to do.” Name the matter, jurisdiction, procedural stage, audience, date boundary and specific work product: a chronology, a clause matrix, a research ledger, an internal outline or questions for a client call. State what is outside scope: no legal conclusion, no filing-ready language, no client communication and no invented authority. Ask Copilot to list its sources and gaps before it writes prose. A bounded task is easier to supervise than an open-ended answer. If the task could affect a deadline, privilege, a filing or settlement, put the human approval point in the prompt and the matter record.

Use the approved workspace and least privilege

Copilot grounds responses in content the user is permitted to access, but permission to retrieve a document is not permission to disclose it to a new audience. Use the firm's approved tenant, account and matter workspace. Follow classification, retention, ethical-wall and external-sharing rules. Do not paste client passwords, private keys, unrelated personal data or a whole mailbox into a chat. Before a pilot, have the security or knowledge-management owner check oversharing, group membership, shared links and audit requirements. Tell Copilot which folder and date range are in scope and ask it to flag material outside that boundary. Keep a record of the prompt, source set, output version and reviewer when the work is consequential.

Build a source ledger before research

Generative systems can produce plausible cases, quotations and propositions that do not exist or do not support the answer. Ask for a ledger with proposition, authority, court or regulator, jurisdiction, date, pinpoint, quoted text, status and verification owner. Give Copilot sources you have opened, or use an approved research system whose results a lawyer can inspect. Tell it to write NOT FOUND rather than complete missing authority. Open every important source yourself in the official reporter, court site, regulator publication or approved platform. Check that it is real, current, in the right jurisdiction and supports the exact proposition. A link is not verification.

Create a defensible chronology

Ask Copilot to extract date, event, source location, actor, document status and confidence. Require it to preserve the difference between an event stated in a document, an allegation, an inference and a missing date. If sources conflict, show both versions and mark the conflict. Compare the table with the originals: check time zones, attachments, redactions, names, speaker attribution and whether a document refers to an earlier event. Ask a second pass to find gaps and duplicates, but do not let it silently rewrite the first. The responsible lawyer should approve the final chronology and retain the sources supporting any event used in advice or a filing.

Compare clauses with a controlled matrix

Provide the governing agreement, comparison version, definitions and business question. Ask for clause location, exact text, change type, operational effect, risk or ambiguity, question for the owner and source. Tell Copilot not to decide whether a clause is acceptable or infer the commercial position. Review every difference in context. Models can miss a defined term, schedule, carve-out or cross-reference, overstate harmless wording or miss a new obligation elsewhere. Use the matrix to accelerate a lawyer's review, not replace it. A final redline or negotiation position needs a human who understands the client's objectives, risk tolerance and authority.

Draft internal work product in layers

Ask for an outline before a memo and an issue table before an email. A useful structure is question presented, known facts, sources, assumptions, competing interpretations, open questions and next step. Require source markers or placeholders for every proposition that needs checking. Keep extraction separate from analysis so the reviewer can see where judgment enters. When revising, ask for plain language, preserved qualifiers, a change log and a comparison against the source. Do not let Copilot invent a client instruction, deadline, authority or certainty level. The final document should reflect the responsible lawyer's considered work.

Protect privilege and confidentiality deliberately

Whether a workflow preserves privilege or satisfies confidentiality duties depends on the facts, jurisdiction, engagement and configuration. Do not make a universal privilege claim from a product description. Follow firm policy and obtain the required approval before using client material. Minimise data, redact identifiers, use matter-specific access and avoid mixing representations in a general workspace. Ask for a privacy checklist naming personal data, privileged material, work product, trade secrets, third-party restrictions and intended audience. Then perform the review yourself. If the prompt creates a new copy of a confidential document, handle it under the same retention and access rules as the source.

Run a citation and quotation check

Before a draft leaves the legal team, ask Copilot to list each case, statute, regulation, quote, page number, date, number and factual assertion. Require source location and VERIFIED, NEEDS CHECK or NOT FOUND. Do not ask it to make the list look complete. Open the source for every material item. Compare quotations character by character where precision matters, check ellipses and brackets, and confirm jurisdiction, court, version and effective date. For filings, apply the court's rules and the firm's checklist. A human sign-off should state what was checked, by whom and what remains uncertain.

Use prompts that expose assumptions

A safe prompt says what Copilot may read, what it must not infer, the output schema and the review gate. Use labels such as SOURCE FACT, ALLEGATION, INFERENCE, QUESTION, DRAFT and UNVERIFIED. Ask it to stop when a source is missing or an instruction conflicts with policy. Do not grant authority to send an email, alter a record, contact a client or file anything simply because the model can prepare the action. For recurring work, save a template with the matter boundary, approved folder, jurisdiction, date range, audience, owner and prohibited actions. Test it on low-risk material and preserve the prompt and output when policy requires.

Supervise and measure the pilot

A legal AI pilot needs an owner, a defined use case, an approval rule and an error channel. Track wrong citations, missed clauses, incorrect dates, confidentiality incidents, unsupported conclusions, review time and rework. Do not measure only minutes saved. If Copilot repeatedly misses schedules, improve document naming or source selection. If users paste too much material, change intake and permissions. If reviewers stop opening authorities, require a source ledger and sign-off. The goal is a traceable legal process, not an impressive demo.

Copy-paste prompt for supervised legal work

Use this starting point: <role>You are a supervised legal-work assistant. You do not give legal advice, choose strategy, decide privilege, contact anyone, file anything or approve a document.</role> <scope>Matter: [ID]. Jurisdiction: [jurisdiction]. Work product: [chronology / comparison / research ledger / internal draft]. Approved sources: [folder, links and date range]. Audience: [internal audience].</scope> <rules>Use only listed sources. Do not invent authorities, quotations, dates, parties, facts or instructions. Label SOURCE FACT, ALLEGATION, INFERENCE, QUESTION, DRAFT or UNVERIFIED. If a source is missing, write NOT FOUND.</rules> <output>First return source inventory and gaps. Then a table with locations. Only then provide the draft. End with every citation, quotation, date and factual claim a lawyer must verify.</output> Give the lawyer the originals, output and checklist. The prompt is not a substitute for professional judgment.

Worked example: turn a document set into a review plan

Suppose a lawyer receives a folder containing a signed agreement, two amendments, a statement of work, six emails and a client note. The first Copilot request should not ask for a risk rating. Ask for a source inventory: filename, date, document type, parties, version indicators, accessible text and obvious gaps. Then ask for a chronology and a clause map separately. The chronology should show when the agreement was signed, when each amendment took effect, what the emails say and where a statement is only an allegation. The clause map should show the service obligation, acceptance language, change control, payment, limitation, termination and dispute provisions with exact locations.

A lawyer can then choose the next human task. If the question is whether a late delivery triggered a termination right, ask Copilot to assemble only the relevant dates, clauses and correspondence. Require a table with source location, quoted language, factual conflict and question for the lawyer. Do not ask it to answer whether termination is available until the lawyer has checked the governing law, notice requirements and the full agreement. If the source set lacks a notice, Copilot should say NOT FOUND. The useful output is a smaller review surface and a visible gap, not a confident conclusion.

Before using the result, compare every date with the original email headers and signed documents. Check whether an amendment changes the definition used in the main clause. Check whether the client note is a statement of fact, a recollection or a request. Keep the approved chronology and the source links together. If the document goes to a client, rewrite it in the responsible lawyer's voice and run the normal privilege, confidentiality, accuracy and scope review. This example shows the boundary: Copilot can organise the evidence and expose the next question; the lawyer owns the legal meaning and decision.

Final legal-work handoff checklist

Before a Copilot-assisted work product is used, ask five questions. What exact sources did the output use, and did the reviewer open the important originals? Which statements are facts, allegations, inferences, recommendations or placeholders? Are the jurisdiction, effective date, version, defined terms and quotations correct? Was confidential material handled in the approved workspace and sent only to the permitted audience? Who has authority to approve the next action?

For a chronology, check dates, time zones, names, attachments, duplicates and unresolved conflicts. For a contract matrix, check cross-references, schedules, definitions, exceptions and the version being negotiated. For research, check each authority in the official or approved source and record the pinpoint. For a client-facing draft, check tone, scope, disclosures, promises, fees and whether the document accidentally states a conclusion more strongly than the evidence supports. Keep the final corrections, source ledger and approval in the normal matter system. A handoff is complete only when another lawyer can understand what the assistant did, what the reviewer verified and what remains open.