Set a weekly quality sample for written client updates

A weekly quality sample is a control, not a performance review. Pick a small number of updates that represent the week's work and check them against the same criteria. The sample should be large enough to reveal a pattern and small enough to finish in one sitting. Record the result and the action, not just a score.

Choose the sample before reading the updates so the reviewer does not pick only the interesting cases. Include one routine update, one update with an exception, and one update the client challenged. That mix shows whether the writing holds up when the facts are difficult. Write the deadline as a date and a local time.

A good update names what changed, what is still open, and what the client needs to do next. It should use the client's language for the work and avoid internal codes the client cannot resolve. The update should be dated and should name the owner of the next action. A cheerful summary without those elements is not complete.

Write the criteria as a short checklist with examples. Accuracy means the facts match the source record. Completeness means the open items and next steps are present. Tone means the update is clear and respectful without promising more than the team can deliver.

Pick one factual claim in the update and trace it to the source record. If the claim cannot be traced, mark it as unsupported. Repeat for the deadline and the owner. A sample that checks only grammar will miss the errors that damage trust.

Look for numbers that were copied from an old update. Look for a status that changed in the system but not in the message. A dated source check is more useful than a general impression of quality. Use the same format for every handover so the next reader can scan it.

Check whether the update tells the client what happens next and who owns it. Check whether it avoids commitments the team has not approved. A promise of a delivery date or a discount belongs outside a routine update unless the approval is recorded. Record the observation time so the next reviewer can tell when the evidence was checked.

Read the update from the client's point of view. Would the client know what to do after reading it? Would the client be surprised by a change that was not explained? The review should catch ambiguity before the client does.

Feedback should name the specific line and the specific fix. A comment that says be clearer is not actionable. A comment that says the third paragraph promises a date the team has not approved is actionable. Keep the feedback short and tie it to the checklist.

Review the same writer's next sample to see whether the fix held. If the same issue appears across writers, change the template or the source guidance. Coaching should improve the system, not just correct one message. Keep the evidence with the record rather than in a separate log.

Do not reduce the sample to zero when the week is busy. Reduce the number of criteria or the length of the review instead. A short check that happens every week is more useful than a thorough audit that happens once a quarter. Separate what was observed from what was assumed.

Record the sample size and the selection rule so the result can be interpreted. A week with three updates and a week with thirty are not directly comparable. The purpose is a trend and a fix, not a ranking. Update the template when the same question appears twice.

For the support model behind this work, review the [services page](/services) and the scope it describes. Use the [contact page](/contact-us) when the decision needs a written boundary or an approval. The [U.S. Small Business Administration](https://www.sba.gov/business-guide/manage-your-business/manage-your-finances) publishes public guidance on documenting recurring finance and operations work. Keep the links in the handover so the next reviewer can find the same reference.