Legal Services Offshore blog
Client status updates built from approved case fields
A field-based routine for client status updates that keeps the message accurate, avoids promises the firm has not approved, and preserves the source of every statement.
Decide which fields the client may see
A client update should be built from a small set of approved fields, not from a narrative someone writes from memory. The firm should decide which matter status, milestone, next action, and contact fields are suitable for client communication. Other fields may be internal, privileged, or simply too uncertain to share. Write the approved field list into the update template and mark the source of each value.
If a field is missing, the template should show that it is missing rather than allowing the writer to fill the gap with an assumption. A blank status is more honest than a cheerful sentence that the record cannot support. Review the field list when the matter management system changes or when a client asks for a different level of detail. The same client may need a short weekly note during an active filing and a longer monthly summary during a quiet period. The template can vary, but the source rule should not.
Use status words that mean the same thing every time
Status language drifts quickly. One person writes awaiting client, another writes pending, and a third writes in progress, even when the underlying situation is identical. A controlled status list with definitions reduces confusion and makes updates comparable across matters. A practical list might include received, in preparation, awaiting client input, awaiting internal review, filed, served, and closed.
Each status should have a definition and a next-action rule. For example, awaiting internal review should name the reviewer and the date the item was sent, while awaiting client input should name the specific item requested. Do not use a status that implies a legal outcome the firm has not reached. Filed does not mean accepted, and served does not mean the other side has complied. If the record only supports the narrower fact, use the narrower word. The client can handle uncertainty when it is explained clearly.
Attach the source before writing the sentence
Every factual statement in the update should trace to an approved record. The preparer should open the matter file, the calendar, the filing receipt, or the client communication and note the identifier before drafting. This order prevents a confident sentence from becoming the source of a later correction. If two records disagree, do not choose the more convenient one for the client message.
Flag the conflict internally and hold the statement until the owner resolves it. A delayed update is easier to explain than a wrong one. The internal note should record what was held and who is responsible for the decision. A source link can be a document identifier, a system reference, or a dated entry in the approved record. Avoid citing a private chat or an unrecorded phone call as the only support. If the information came from a call, write a short contemporaneous note and have the appropriate owner confirm it.
Keep promises out of routine updates
Routine updates often drift into promises about timing, cost, or outcome. The offshore preparer should not write that a filing will be completed by Friday unless the responsible attorney has approved that commitment. A safer formulation states what has been done, what is in progress, and what the next internal step is. When a client asks for a date, route the question to the owner rather than inventing a range.
The update can acknowledge the question and say that the responsible attorney will respond. That is more useful than a guess, and it protects the firm from a commitment it cannot keep. A promise that has been approved should be recorded with the approver and the exact wording. If the date changes, the update should explain the change without blaming the client or the court. The record should show who approved the new message and what evidence supports it.
Make the review step proportionate to risk
Not every update needs a partner review, but every update needs a rule. A routine status note built from approved fields may be reviewed by a senior paralegal or case manager. A message that discusses strategy, settlement, a filing error, or a changed deadline should go to the attorney. Write the review threshold into the procedure so the preparer does not have to guess.
Include examples of low-risk and high-risk updates, and name the person who can approve each. If the approver is unavailable, name a backup rather than allowing the update to sit indefinitely. The reviewer should compare the draft with the source fields, not rewrite it from scratch. If the draft introduces a fact that is not in the record, return it with a question. If the source itself is wrong, fix the source before sending the client a corrected message.
Record what the client received
The matter file should include the final message, the date sent, the channel, the recipient, and the approved source version. If the client replies with a question or a correction, link the reply to the update rather than starting a new thread with no history. This makes the communication trail reviewable. Do not rely on a sent-mail folder as the only record if the firm uses a client portal or a shared inbox.
Export or link the message into the approved location according to the retention rule. If the client received a document, record the document identifier and version as well as the message. A monthly sample can check whether updates are timely, sourced, approved, and recorded. Look for messages that promise dates without approval, statuses that do not match the matter file, and updates sent without a source note. Correct the template or the routing rule before coaching the same writer again.
Close the loop with the client and the team
A status update is not complete when it leaves the outbox. The team should record whether the client acknowledged it, whether a question remains open, and who owns the next response. If the client does not respond, the next update should reference the open question rather than repeating the same summary. Internally, the update should feed the weekly matter review.
A cluster of waiting-on-client statuses may point to a unclear request, a delivery problem, or a client contact who needs a different channel. A cluster of awaiting-review statuses may point to reviewer capacity. The update fields become useful management evidence when they are consistent. At the end of the matter, keep the final update with the close record. It shows what the client was told and when, which is often as important as the internal completion note. Review the sequence for accuracy and for any promise that remained unresolved.