Keep a client update note that survives a shift change

A client update note should let the next assistant continue without reading every message. Start with the change, the next step, the owner, and the date. A note that says updated the client is not a handoff. Keep the boundary visible in the place where the work is assigned. Test the brief on one real task before applying it to the whole role. The client should know who is handling the question and when to expect an answer.

Keep the note short and use the same format. The next shift should know what changed and what is still open. Separate what was observed from what was assumed. Record the date and the source so the next reviewer can repeat the check. The handoff should say what the next person may decide without asking. The client should know who is handling the question and when to expect an answer.

Write what changed for the client and the source of the change. A schedule move, a new contact, or a revised scope should be named. A general update hides the detail. Use the same format for every handover so the next reader can scan it. Keep the source link with the task so the next reviewer can check it. The handoff should say what the next person may decide without asking.

Record the date and the person who made the change. A later reviewer may need the timeline. Write the deadline as a date and a local time. Review the first few notes together before the process expands. The assistant should record the owner and the date before the next shift.

Every open item needs a next action and a named owner. A next step without an owner will be missed. The client should know who is handling the question. A short note with four fields is easier to use than a long narrative. Keep the source link with the task so the next reviewer can check it. Test the brief on one real task before applying it to the whole role.

Record the deadline and the channel. A reply due today should be at the top of the note. Write the deadline as a date and a local time. Ask whether a new reviewer could act on the record without a conversation. The handoff should say what the next person may decide without asking. The client should know who is handling the question and when to expect an answer.

Keep sensitive client information in the approved system. Do not copy it into a chat or a personal note. The handoff should point to the record. Separate what was observed from what was assumed. The assistant should record the owner and the date before the next shift. Test the brief on one real task before applying it to the whole role.

If a message is ambiguous, pause and ask. A delayed reply is safer than a disclosure. Keep the boundary visible in the place where the work is assigned. Write the deadline as a date and a local time. The handoff should say what the next person may decide without asking. A short note with the requester and the next action is easier to use.

Read the last few notes with the next assistant. Ask them to explain the open items. If they cannot, improve the format. A note that cannot be used is not a handoff. The handoff should say what the next person may decide without asking. Keep the source link with the task so the next reviewer can check it.

For the support model, review the [services page](/services) and the scope it describes. Use the [contact page](/contact-us) when the decision needs a written boundary. The [U.S. Small Business Administration](https://www.sba.gov/business-guide/manage-your-business/manage-your-finances) publishes public guidance on documenting recurring work. Keep the note with the task so the next reviewer can find it. The handoff should say what the next person may decide without asking. Test the brief on one real task before applying it to the whole role.