Legal Services Offshore blog
A matter intake brief that survives partner review
Build an intake brief that gives the supervising attorney the request, the source record, the open conflicts, and the decision still needed without turning preparation into advice.

Start with the decision the partner must make
A matter intake brief is useful only when it makes one decision easier to take. Before the offshore team opens a template, the supervising attorney should name that decision: accept the engagement, ask for more information, route the request to another practice group, or decline it. The brief then carries the facts that change that decision and leaves out background that merely fills space. Many intake packets fail because they summarize a conversation instead of presenting the record.
The reviewer cannot tell which party said what, which document supports the stated scope, or whether a conflict answer was confirmed or simply assumed. A stronger brief separates the request, the source evidence, the open questions, and the recommended next step in four visible blocks. The preparation role should never phrase a conclusion as a legal opinion. Write that the conflict search returned no match in the approved database, not that the firm has no conflict. Write that the client described a possible deadline, not that a filing is due on a particular date. This discipline keeps the brief honest and gives the attorney a clean place to exercise judgment.
Separate new matters from changes to open matters
The queue should know whether a request creates a new matter, reopens a closed matter, or changes an existing record. Mixing those events inflates demand and hides the repair work that a correction requires. A short intake type field, chosen from a closed list, prevents the same request from being counted three different ways. For a new matter, the brief needs the client entity, the requesting contact, the proposed scope, the opposing parties, the key dates supplied by the client, and the source of each fact.
For a change, it also needs the original matter identifier, the field being changed, the reason for the change, and the approver who authorized it. The two paths can share a template, but they should not share an approval rule. When the request is ambiguous, the preparer should ask one focused question and record the answer beside the original request. A message that says the client wants a contract reviewed is not enough to open a matter, because it does not identify the agreement, the counterparty, the governing jurisdiction, or the business objective. The brief can show those gaps without guessing at the missing content.
Attach evidence without copying sensitive material
The brief should point to the authoritative document rather than reproducing it in a shared note. Use a stable document identifier, the version observed, the date the record was read, and the system where it lives. If a sensitive attachment is needed for review, place it in the approved repository and link to it from the intake record. A common failure is the paste-and-summarize habit.
Someone copies an entire email thread into the intake tracker, then a later reader cannot tell which message was the final instruction. The tracker becomes a second, unreliable source of truth. A better pattern keeps the original thread in the mail system and records only the message identifier, the sender, the time, and the specific instruction relied on. When two sources disagree, preserve both observations and mark the conflict for review. Do not silently choose the cleaner value or the more recent message. The attorney needs to see that the engagement letter names one entity while the client contact names another, because that difference may affect who the firm can represent.
Write a conflict section that shows its limits
Conflict preparation is an evidence task, not a clearance. The brief should list the names searched, the databases used, the date of the search, and whether each result was a possible match, a confirmed non-match, or an unresolved question. A blank result and a confirmed negative are different facts and should never share a status code. Names arrive with variants, trade names, affiliates, and misspellings.
Record the name exactly as supplied, then add any normalized search term as a convenience rather than a replacement. If the client cannot explain an affiliate relationship, mark the relationship unknown and route the question to the attorney. The preparer should not infer ownership from a website or a public filing summary. A conflict packet that says only checked is not reviewable. A reviewer should be able to see what was searched, what came back, which result was escalated, and who made the final call. That structure also protects the offshore team when a later question arises about the scope of the original search.
Make the open questions impossible to miss
The most valuable part of the brief is often the short list of what is still unknown. Put that list near the top, not in a footnote. Each question should name the missing fact, the person or system expected to supply it, and the consequence of proceeding without it. A question without an owner will be rediscovered by the next reviewer.
Use plain language rather than internal shorthand. A note that says waiting on KYC tells a new reviewer very little, while a note that says the client has not supplied the beneficial-ownership schedule tells them what to request. The same principle applies to deadline questions, fee arrangements, and signature authority. The brief should be readable by an attorney who has not seen the matter before.
When a question blocks acceptance, the status should be held rather than pending. Held means the firm cannot proceed without a decision or a missing document. Pending often implies that ordinary work continues, which can create the impression that the matter is already open. A precise status prevents accidental client communication and unnecessary file creation.
Review the brief before it reaches the partner
A second reviewer should check the brief against the source record before release. The check is not a reread for grammar; it is a comparison of the request, the evidence, the conflicts, the open questions, and the proposed next step. The reviewer should be able to point to the exact field or document that supports each statement in the brief. Use a short acceptance checklist: the client and matter are identifiable, the scope is stated in the client's words, each key fact has a source, the conflict search is dated, the open questions have owners, and the decision requested is explicit.
If any item fails, return the brief with a reason code rather than a general request to improve it. Reason codes make repeat problems visible across the team. Sampling a few briefs each week is more useful than reviewing every one once and never returning. Choose one ordinary matter, one exception, and one brief that was returned for correction. Compare the reviewer's notes with the final record and ask whether the correction changed the template, the training, or only the individual case.
Close the intake step with a dated handoff
The intake step ends when the attorney receives a complete brief and the next action is clear. Record the handoff time, the recipient, the decision requested, and the evidence attached. If the attorney asks for more information, keep the original brief and add the follow-up rather than overwriting the first version. A closed intake record should show whether the matter was accepted, declined, or held, and who made that decision.
It should also show whether the client was told and through which approved channel. The offshore team can prepare the communication, but the firm should approve any message that changes the client's expectations about cost, timing, or scope. Review the intake queue monthly for patterns rather than individual blame. A recurring missing field may mean the request form is wrong, the client contact does not understand the question, or the reviewer is asking for information too late. Fix the form or the routing rule before coaching the same preparer again.