Skip ahead to the main page
Partner Huddle
Pages

Client decisions to confirm before acting: 4 to record

Partner Huddle Editorial Team · Published · 13 min read

Confirm four client decisions in writing before staff act: the objectives, settlement, which steps staff may take alone, and standing permissions. Every firm has a version of the same moment. A client calls about a deadline, the matter manager is out, and a staff member asks whether they can just send the filing, sign the letter, or accept the other side's offer. The answer depends less on the staff member's skill than on decisions the client has already made, or has never made at all.

Operations leads and partners are the people who decide how much room staff get. Get that wrong in one direction and every small step waits for a phone call, which slows the matter and frustrates the client. Get it wrong in the other direction and staff act on permissions nobody actually gave, which is where disputes start. This post covers four client decisions worth confirming in writing before the firm acts on them, and a few habits that keep those decisions current.

The stakes are practical. A firm that acts too cautiously loses speed and billable momentum, and clients notice when a simple question waits all afternoon for an answer. A firm that acts too freely can end up doing something the client never agreed to, and then has to explain the gap. Neither problem is solved by better staff alone. Both are solved by clearer decisions made up front, written where the next person will find them.

The rules quoted here come from state versions of the professional conduct rules for lawyers. Your firm's obligations depend on the jurisdiction where it practices and on its own engagement terms, so treat these as the starting point for a conversation with counsel, not as a substitute for one.

Key takeaways

  • Write each matter's objective in the client's own words, and date it.
  • Confirm in writing who receives settlement offers and what staff may say in reply.
  • Sort routine steps into three groups: no approval needed, a note to the client, or the client's decision first.
  • Record each standing authorization with its scope and date, and check for a material change before relying on it.

Decision 1: What the client wants the matter to achieve

Start with the objectives. The Minnesota rule puts the basic point plainly: "Subject to paragraphs (c) and (d), a lawyer shall abide by a client's decisions concerning the objectives of representation and as required by Rule 1.4, shall consult with the client as to the means by which they are to be pursued."

Two ideas sit inside that sentence. The client decides the objectives. The lawyer consults the client about the means. A staff member who knows the objective can often make routine choices about how to reach it. A staff member who does not know the objective is guessing.

In practice, the confirmation should be short and specific. "Resolve the dispute" is too vague to act on. "Resolve the dispute for an amount we can both live with, without a trial, and within a budget the client has approved" gives staff something to measure a choice against. Write the objective in the matter file in the client's own words where possible, and date it. When the client changes its mind, that change should be recorded too.

Operations leads can help by building an objective field into intake forms. For a related checklist, see the Accounting Client Intake Checklist for a Clear Handoff. Partners should review it at the first substantive meeting. Neither step requires legal training; both require asking the client directly what success looks like and writing down the answer.

Objectives also move. A matter that begins as a request for advice can turn into litigation, and a dispute that was about money can become a dispute about a principle the client cares about more than the money. When that happens, the old objective no longer tells staff what to do. Pause, ask the client again, and update the file before the next routine step goes out.

Decision 2: Whether the client alone decides on settlement

Settlement is the decision most likely to be treated as routine and most likely to cause trouble when it is not. The Minnesota rule is direct: "A lawyer shall abide by a client's decision whether to settle a matter."

That sentence leaves no room for staff to read a settlement offer as a process step. A demand letter arrives, the opposing side proposes a figure, and an associate who thinks the figure is fair may be tempted to reply in a way that signals acceptance.

Confirm, in writing, who may receive settlement offers, who must take them to the client, and what the client wants to hear first. Some clients want every offer, however small. Others want offers above a threshold only. Either is fine. What matters is that staff know which one applies before the offer arrives.

Partners should also decide what staff may say in response. Acknowledging an offer is usually different from negotiating. Saying "we will take this to our client" is a different act from naming a counter-offer. Writing those distinctions into the matter plan avoids a common situation where a sensible email commits the client to something it never approved.

Settlement talk often starts by phone, which is where the risk is highest. A caller on the other side may ask, "Would your client take a figure like that?" A staff member who answers from memory, even with a hedge, has in effect given an answer. The safer habit is a short script the team agrees on in advance: thank the caller, say the offer will go to the client, and note the time and the terms in the file. Partners can approve that script once and reuse it across matters.

Illustrative example: a settlement call

A caller from the other side offers a figure while the matter manager is out. The staff member does not answer from memory. They thank the caller, say the offer will go to the client, and note the time and terms in the file. The partner sends the client a summary and asks for a reply within 30 days. Until the client answers, nobody on the team signals acceptance or names a counter-offer.

Decision 3: Which steps staff may take on their own

The third decision is about the means. Most of the work on a matter is means: which documents to pull, which motions to draft, which witness to call, which vendor to hire. The rules expect lawyers to consult clients about these choices, but they also recognize that not every step needs a fresh conversation. The Pennsylvania rule states the balance this way: "With respect to the means by which the client's objectives are to be pursued, the lawyer shall consult with the client as required by Rule 1.4(a)(2) and may take such action as is impliedly authorized to carry out the representation."

"Impliedly authorized" is the phrase to focus on. It covers steps that obviously follow from the objective and that the client would expect without being asked. Ordering a copy of a public record for a pending filing usually fits. Agreeing to a change in the scope of the engagement, or spending a large sum of client money on a new expert, usually does not. The line is not always clear, which is why it helps to write down what your firm treats as routine.

Consider a simple case. A client has asked for a complaint to be filed by a set date. Requesting the court's current forms, booking a process server, and sending the client a draft are usually steps the client would expect. Hiring a second firm to handle a related claim, or agreeing to drop one of the client's claims to speed things up, is not. The first group can proceed with a note in the file. The second group waits for the client.

A practical way to do this is a short list of categories, reviewed with the responsible partner: steps that are routine and need no approval; steps that need a note to the client; and steps that need the client's decision first. Keep the list short enough that staff will actually use it. A long list will be ignored; a short one will be applied.

Operations leads are well placed to own this list. They see the recurring tasks across matters, so they can spot where staff keep stopping to ask the same question and where the answer is always yes.

When a routine step turns out to carry more weight than expected, stop and ask. A document request that reveals privileged material, a vendor quote that is far above what the client discussed, or a witness who wants to change the story can each move a routine step into the decision category. Staff should know that the category can change midstream, and they should feel free to pause rather than push ahead.

Decision 4: Standing permission given in advance

The fourth decision is the one that most often outlives its usefulness. Some clients, particularly those with recurring matters, will say at the start of a relationship that staff may take certain steps without checking back. The Pennsylvania rule recognizes this: "(3) At the outset of a representation, the client may authorize the lawyer to take specific action on the client's behalf without further consultation."

The same rule then sets a condition on when that permission can be relied on: "Absent a material change in circumstances and subject to Rule 1.4, a lawyer may rely on such an advance authorization."

Read that second sentence carefully. The permission depends on nothing material having changed, and it stays subject to the duty to communicate under Rule 1.4. A standing authorization given at an early stage may not cover the same action after the facts shift. A new adverse party, a change in the client's business, or a new deadline could each be a change that matters.

So when you record an advance authorization, record its scope in specific terms, record the date it was given, and record the circumstances the client was describing when it was given. Then build a simple habit: before relying on an old authorization, the responsible person confirms nothing material has changed. This is where operations leads add value, because they often hold the file history and can spot a change that a busy partner missed.

Also note what an advance authorization does not do. It does not let staff take a step the client never mentioned. Staff who read a general instruction ("handle the routine stuff") as permission for a major decision are stretching it. The narrower the written scope, the easier it is to rely on it safely.

Advance authorizations also need an end date of sorts, even if nobody writes one down. Review them when the client's matter reaches a new stage, when the team changes, or when the client's instructions are revisited. A quick periodic look at standing permissions across active clients is a sensible habit for firms that rely on them heavily.

Keep clients informed even when they delegate

Delegation changes who takes a step. Under the North Dakota rule, it does not remove the duty to keep the client advised: "Even when a client delegates authority to the lawyer, the client should be kept advised of the status of the matter." Check your own jurisdiction's version.

For a firm, this means that delegated authority still needs a reporting rhythm. The client should know what was done under its authorization, what is pending, and what decisions are coming up. The form can be simple: a short status note at agreed intervals, plus a prompt message when something unusual happens. The point is that the client is never surprised by an action taken in its name.

Build this into the workflow rather than leaving it to memory. A standing note in the matter file can list the client's delegations, the date each was confirmed, and the update cadence agreed with the client. Operations teams can run a periodic check that each open matter with delegated authority has had a recent status update. Partners can spot-check the file before major events.

A useful status note is short and concrete. It says what the firm did under the client's authorization, what it plans to do next, and what it needs from the client. It avoids jargon. If the client asked for updates on a specific schedule, the note should arrive on that schedule even when nothing has happened, because the silence itself tells the client something.

Running the confirmation conversation

Most of these decisions can be confirmed in a single conversation, held before the first substantive step on the matter. Who leads it matters less than who attends. The client should hear the questions from someone who can answer follow-ups, and the responsible partner should be present for anything touching settlement or scope.

Send a written summary afterward. Restate each decision in plain terms, list anything the client asked you to check, and ask the client to reply to confirm. Silence is not confirmation, and a firm should not treat it as one. If the client does not reply, follow up through the same channel and note the follow-up in the file.

Common mistakes to avoid

The first mistake is treating a general engagement letter as a full set of instructions. Boilerplate that says the firm may handle matters as it sees fit does not tell staff how to handle a settlement call. Specific decisions need specific language, even if that makes the letter longer.

The second is reading silence as consent. A client that does not object to a plan has not necessarily approved it, and a client that is simply busy may not have read the email at all.

The third is letting an old authorization carry a new matter. A permission given for one dispute does not automatically cover the next one, even with the same client and the same team. Check the scope and the circumstances each time.

The fourth is assuming the file is current. Matter notes written at intake are often the last thing anyone updates. Make the decision record a living part of the file, reviewed at each major event, rather than a form signed once and forgotten.

A short checklist for your next intake

Before staff act on a matter, confirm the following, and write the answers into the file:

  1. What the client wants the matter to achieve, in the client's own words, with a date.
  2. Whether the client wants to decide every settlement offer, and what staff may say in reply.
  3. Which categories of step staff may take on their own, which need a note to the client, and which need a decision first.
  4. Any standing authorizations, their exact scope, the date given, and the circumstances they assume, along with a reporting rhythm for the client while delegated authority is in use.

Revisit the file when something material changes. A new party, a new deadline, a shift in the client's goals, or a dispute over a step all count. Treat each as a reason to confirm again rather than assuming the earlier answers still hold.

Closing thought

Client decisions are easy to assume and hard to reconstruct later. A firm that writes them down at the start, and checks them when circumstances change, will spend less time on phone calls and far less time on disputes about who approved what. Your firm's counsel can tell you how they apply in your jurisdiction and under your engagement terms.

If you take one thing from this post, let it be the habit of asking the client again when the facts move. Today, check the next matter that opens against the checklist above before any staff member acts on it.

Related guides: Bank reconciliation: 8 checks before client sign-off · Check 5 mileage-log details before a client's return · Apply the 22% flat rate before a client bonus payroll.

Frequently asked questions

Which client decisions should a firm confirm first?

Confirm the four decisions covered here: the matter's objectives, whether the client decides settlement, which steps staff may take on their own, and any standing authorizations.

Can a general engagement letter settle these decisions?

No. A general line about handling matters does not tell staff how to handle a settlement call. For intake terms, see Engagement letter: 6 terms to settle at intake.

Sources