Home / Blog / Role design

Build a partner billing delegation agreement that names decision rights

A written delegation agreement that defines preparation, review, approval, escalation triggers, and the evidence standard for a billing support role.

Legal Billing Assistant Editorial Team · Published · 9 min read

Editorial illustration representing Build a partner billing delegation agreement that names decision rights
Table of contents

Start with the decisions the partner owns

A delegation agreement works best when it starts with the decisions that stay with the partner. Fee adjustments, client commitments, confidentiality calls, and legal strategy belong to the attorney, not to an assistant. Write those decisions down before describing the tasks that can move. The agreement should make the boundary obvious to both people on a busy day.

Distinguish a decision from a preparation task. Preparing a write-off packet is not the same as approving the write-off, and drafting a client note is not the same as sending it. Use plain verbs such as prepare, check, recommend, approve, and send. The verb list becomes the shared vocabulary for the role.

Define preparation, review, and approval

Describe what the assistant prepares, what the partner reviews, and what the partner approves. For each output, name the source records, the required fields, and the point at which the work is ready for review. A prebill packet, for example, may be prepared with a reconciliation and an exception list, then reviewed by the partner before release. The sequence should be written, not assumed.

Set a service expectation for each step so the partner knows when to expect the review. A short turnaround for a routine prebill and a longer window for a complex matter are both reasonable if they are stated. Record what happens when the partner is unavailable. A delegation agreement without a backup path will stall at the first trip.

Write the escalation triggers

List the conditions that require the assistant to stop and escalate rather than decide. Common triggers include a missing client authorization, a fee change above a set amount, a conflict between the engagement letter and the client's instruction, and any request to communicate a legal position. Keep the list short enough to remember and specific enough to apply. Review the triggers after the first month and add any situation that actually required a judgment the assistant could not make.

For each trigger, name the person to contact and the information to include. The assistant should be able to escalate with the source, the question, and the deadline in one message. A vague escalation creates another round of questions. Review the triggers after the first month and add the situations that actually occurred.

Set the evidence standard for each task

The agreement should say what a complete record looks like for each delegated task. A time entry needs a narrative that identifies the task, the document, and the result. A cost needs a receipt, a matter reference, and an approval. A rejection needs the portal code, the line, and the correction. The standard should be checkable by someone who did not do the work.

Keep the standards in a short appendix rather than scattering them through the agreement. Link each standard to the template or system field that supports it. If a standard cannot be met because the system lacks a field, fix the template or record the exception. An evidence standard that the tool cannot capture will be ignored.

Agree the communication boundary

Decide which messages the assistant may send, which must be drafted for the partner, and which must come from the partner. Client fee negotiations, legal advice, and sensitive relationship issues usually stay with the attorney. Routine status updates and document requests may be delegated with a clear template. Write the boundary by audience and topic, not just by channel.

Give the assistant approved language for the common messages so the tone stays consistent. Include a rule for copying the partner on any message that touches a disputed amount or a deadline. Review a sample of sent messages in the first month. The communication boundary protects the client relationship and the firm's professional obligations.

Name the backup and the review cadence

A delegation agreement needs a named backup for both the assistant and the partner. The backup should have the access, the context, and the authority to keep the queue moving. Test the backup once during a planned absence. An untested backup is a name on a document, not a control.

Set a short weekly check-in and a longer monthly review. The weekly check-in covers the open queue, the exceptions, and the next deadlines. The monthly review looks at the evidence sample, the rework, and any change to the client's requirements. Keep the notes brief and store them where both people can find them.

Test the agreement on one live matter

Choose a matter with a clear scope and a partner who will give honest feedback. Run the agreement for one billing cycle and record where the role had to ask for a decision that was not covered. Note the tasks that took longer than expected and the reviews that were skipped. The test should produce a short list of changes, not a pass or fail grade.

Revise the agreement with the partner and the assistant together. Add the missing triggers, remove the steps that added no value, and clarify the evidence standard that caused the most questions. Keep the old version so the change is visible. A tested agreement is more credible than a template that was never used.

Revise it when the role or client changes

Review the agreement when the assistant changes, when the partner changes, or when a client adopts new billing guidelines. A new client requirement can move a task from routine preparation into a decision that needs approval. Update the evidence standard and the escalation list at the same time. A stale agreement is a source of quiet errors.

Keep the current version in the shared workspace and remove old copies from personal folders. Note the effective date and the person who approved the change. Give the assistant a chance to raise the parts that no longer work in practice. The agreement should evolve with the work, not sit in a drawer after the first review.

Common questions answered

Who owns the delegated decisions? The partner keeps fee, client, confidentiality, and legal decisions, while the assistant prepares evidence, checks completeness, and escalates anything outside the written rule. The partner keeps fee, client, confidentiality, and legal decisions. The assistant prepares evidence, checks completeness, and escalates outside the written rule.

What makes a delegation agreement usable? It names the preparation, review, and approval steps, the escalation triggers, the evidence standard, and the backup in plain language. Name the preparation, review, and approval steps in plain language. Include the escalation triggers, the evidence standard, and the backup.

How often should it be reviewed? Review it weekly during the first month, then monthly and whenever the role, the partner, or the client's billing requirements change. Review weekly during the first month, then monthly. Repeat the review whenever the role, partner, or client requirements change.

Authoritative sources

These public references inform the operating questions in this article. They do not replace legal, ethics, privacy, financial, or client-specific advice.

  1. American Bar Association Model Rules of Professional Conduct

Put the guidance to work

Choose one recurring billing workflow, identify its authoritative source records, and name the owner who reviews exceptions. We can help turn that boundary into a focused support role.

Discuss your workflow