Why verbal instructions create billing risk
A partner often gives billing direction in a hallway, on a call, or in a short message that assumes context the assistant does not have. The instruction may be clear in the moment and ambiguous an hour later, especially when it involves a write-down, a rate change, or a narrative standard. Without a written record, the assistant must guess or interrupt the partner again. Both outcomes cost time and create avoidable errors.
The risk is not that partners are careless. The risk is that informal instructions are optimized for speed and not for auditability. A later reviewer cannot tell whether the instruction applied to one line, one matter, or the whole client. A short confirmation note closes that gap without turning every conversation into a formal memo.
Capture the instruction while the context is fresh
Write the note immediately after the conversation, using the partner's words where possible and a plain summary where not. Record the date, time, channel, and participants so the source is traceable. Include the matter, the timekeepers, and the specific lines or period affected. A note written a week later is a reconstruction, not a record.
Ask one clarifying question if the scope is unclear, rather than filling the gap with an assumption. For example, confirm whether a reduced rate applies to all work in the matter or only to a defined phase. The answer should be captured in the same note. A brief pause at the point of instruction prevents a much longer correction at prebill.
State the action in operational language
Translate the instruction into the fields the billing system actually uses: rate, hours, narrative, write-down amount, approval path, or client communication. Avoid recording only the partner's conclusion, such as make this reasonable, because that phrase does not tell a reviewer what to change. Write the specific action and the evidence that supports it. A reviewer should be able to read the field and know exactly what to change.
If the instruction requires a judgment, name the person who owns that judgment and the basis they used. A note that says the partner approved a courtesy reduction is weaker than one that records the amount, the reason, and the client context. The operational version lets another reviewer apply the same logic consistently. Record the basis beside the decision so the reasoning survives a staff change.
Separate the decision from the execution
Record what was decided, who decided it, and what still needs to happen before the invoice changes. The partner may approve a write-down while the billing assistant still needs to update the time entry, notify the client, and adjust the prebill. Keeping decision and execution separate prevents a note from looking complete when the work is only half done. The execution list should name the next owner and the date the step is due.
Assign the execution steps to named owners with dates. If the partner's instruction depends on a client guideline or an engagement letter, note the source that was checked. If the source was not checked, mark it as an open item rather than implying approval. A clear execution list turns a conversation into a workflow.
Confirm the note back to the partner
Send a short confirmation that states the action in one or two sentences and invites a correction. Keep it easy to answer, such as a reply with confirmed or a specific change. Do not bury the request in a long recap that the partner will skim. The goal is a fast, durable agreement on the record.
If the partner does not respond, treat the note as pending rather than approved for any action that changes a client invoice. Set a follow-up date and escalate through the agreed path if the matter is time-sensitive. Silence is not authorization for a billing adjustment. The confirmation rule should be written into the role brief so everyone applies it the same way.
Link the note to the matter and the invoice
Store the confirmation in the matter record or the billing file, not in a personal inbox. Link it to the relevant time entries and the prebill packet so a reviewer can find the source without searching. Use a consistent naming convention that includes the matter and the date. A note that cannot be found is functionally the same as no note.
When the invoice is prepared, reference the instruction in the review notes or the adjustment record. That reference lets a later auditor connect the change to the approval. If the client asks about the adjustment, the team can respond with evidence rather than recollection. The link is the difference between a documented decision and an unexplained write-down.
Handle instructions that conflict with client rules
Sometimes a partner asks for something the client guideline does not permit, such as a narrative style the client has rejected or a rate above the agreed cap. Record the conflict in the note and pause the change until the relationship owner resolves it. Do not silently follow the partner and hope the client accepts the result. The assistant's role is to surface the conflict, not to choose which rule wins.
Document the resolution, including who spoke with the client and what was agreed. If the client grants an exception, record its scope and expiration. If the partner decides to absorb the difference internally, record that decision and the approver. Either way, the written record should show why the final action is defensible.
Review the routine after a difficult close
After a close with several verbal instructions, review whether the notes captured enough detail to prevent rework. Look for the instructions that required a second conversation or produced a correction. That pattern shows where the confirmation template needs another field. Update the template rather than asking people to remember more.
Share one anonymized example with the billing team so the standard is concrete. A good example shows the original words, the operational translation, the approval, and the final invoice action. The team can copy the structure without copying the content. Over time, the routine becomes part of how the firm handles billing decisions, not an extra step added at the end.
Common questions answered
Does every verbal instruction need a written note? Any instruction that changes a rate, write-down, narrative, approval path, or client communication should be recorded. Routine scheduling or formatting requests may not need the same treatment. Use the risk of a later dispute to decide.
Who should write the confirmation? The person who received the instruction should write it while the context is fresh, then send it to the partner for confirmation. The billing manager should review the routine and the template, not every individual note.
What if the partner refuses to confirm in writing? Record that the instruction was given verbally and note the date and participants. Escalate through the billing manager if the change is material. Do not treat an unconfirmed instruction as final authorization for a client invoice adjustment.
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


