Onboarding

Create a weekly operations digest for a virtual assistant

A digest format that fixes the window and the audience, limits the numbers to the ones that earn a line, gives every item an owner, and keeps the same shape from week to week.

By OnboardingEmployees editorial team | | 6 min read

Create a weekly operations digest for a virtual assistant
On this page
  1. Set the digest window and the audience
  2. Choose the five numbers that earn a line
  3. Write each item with an owner and a next step
  4. Keep the format stable across weeks
  5. Review the digest in the Monday stand-up
  6. Key takeaways
  7. Related reading

A weekly operations digest is not a longer status email. For a virtual assistant, the digest is the one page that tells a reader what changed, what needs a decision, and who owns the next step. A report that lists everything with equal weight forces the reader to do the sorting. The digest does the sorting once so the reader can act quickly.

Set the digest window and the audience

Fix the window before writing anything, such as Friday noon to the following Friday noon. A digest with a moving window cannot be compared with the week before it. The assistant should write the start and end timestamps in the header. Two readers should be able to agree on what the week contains.

Name the primary reader and the decisions that reader makes. A digest written for everyone is usually read by no one. The assistant should ask the reader which two questions the digest must answer each week. A report that answers a real question earns its place in the inbox.

Keep a secondary list for people who only need the exceptions. A finance lead may not need the full digest but must see a missed approval. The assistant should mark the items that require a decision from each group. A single audience field prevents a long report from being sent to the wrong list.

State the cutoff for late items in the header. Work that arrives after the cutoff belongs in the next digest unless it changes a decision this week. The assistant should record where a late item was reported instead. A clear cutoff protects the digest from becoming a live feed.

Choose the five numbers that earn a line

Pick no more than five measures and keep the same five for at least a month. A rotating set of numbers makes every week look like a new study. The assistant should write why each measure is included and what a bad value would trigger. A number with no trigger is decoration.

Show the current value, the prior value, and the direction of change. A single number cannot tell the reader whether the week improved. The assistant should use the same source and the same definition each time. A changed definition should be announced rather than slipped into the total.

Keep the raw count beside any percentage so the reader can judge the base. A rate on four items looks dramatic and means very little. The assistant should show the denominator when the base is small. A percentage without a base invites the wrong conclusion.

Drop a measure that no one has acted on for two months. A number that never changes a decision is taking space from one that would. The assistant should ask the reader before removing it and record the reason. A digest that defends every old measure stops improving.

Write each item with an owner and a next step

Open every item with the outcome rather than the activity. A line that says reviewed the queue describes effort, while a line that says three invoices are waiting on approval describes a state. The assistant should write the state first and the activity second. A reader should not have to infer the result.

Name one owner for each follow-up and the date the owner will act. A team name or an inbox is not an owner because no one accepts the task. The assistant should confirm the name before the digest is sent. A follow-up with no owner will reappear next week in the same words.

Write the next step as a verb with a finish line. A step such as follow up cannot be checked, while a step such as send the revised quote by Tuesday can. The assistant should keep the step short enough to scan. A testable step is the difference between a report and a plan.

Separate decisions needed this week from updates that need no reply. A digest that mixes the two trains readers to skim everything. The assistant should group the decision items at the top with a deadline. A clear ask is more likely to get an answer.

Keep the format stable across weeks

Use the same headings in the same order every week. A reader who knows where to look finds the exception in seconds. The assistant should keep a template file and copy it rather than rebuild the layout. A new layout each week adds work and hides change.

Record the date and the author at the top of the file, not only in the email. A forwarded digest often loses the message that explained when it was written. The assistant should include the digest window and the send time. A file with no date is hard to trust later.

Keep a short archive with one file per week and a consistent name. A searchable archive turns the digest into a history rather than a series of emails. The assistant should link the current digest to the prior one. A reader can then check whether an issue is new or recurring.

Review the template once a quarter instead of editing it every week. A format that changes constantly cannot be compared across months. The assistant should collect suggestions and test them together. A stable format is what makes a small change visible.

Review the digest in the Monday stand-up

Walk through the decision items first and confirm the owner for each one aloud. A written owner who never confirms the task is only a name in a table. The assistant should record the confirmation in the digest follow-up. A short read-back prevents a week of silent delay.

Ask which number changed for a reason the team did not expect. The answer is often more useful than the number itself. The assistant should record the explanation beside the measure for the next digest. An unexplained change tends to be rediscovered later.

Check the items that were due last week and mark them done, late, or dropped. A digest that never closes its own follow-ups teaches readers to ignore them. The assistant should carry open items forward with a new date. A carried item without a new date is a hidden backlog.

End with one change to the digest and one change to the work. Limiting the review to two changes keeps the meeting short and the follow-through real. The assistant should record both changes and who owns them. A review that produces a long list usually produces no change.

Key takeaways

Fix the digest window, the primary reader, and the cutoff before writing. A digest written for everyone is usually read by no one. Keep a secondary list for people who only need the exceptions. A clear window lets two readers agree on what the week contains.

Limit the digest to five measures and show the current value, the prior value, and the raw count. A percentage without a base invites the wrong conclusion. Drop a measure that has not changed a decision in two months. A number with no trigger is decoration.

Give every follow-up one owner, one date, and a next step with a finish line. Separate decisions needed this week from updates that need no reply. Confirm the owner aloud in the Monday stand-up. A follow-up with no owner reappears next week in the same words.

Keep the headings, the archive name, and the send time stable across weeks. Review the template once a quarter rather than editing it every week. Close last week's items as done, late, or dropped. A stable format is what makes a small change visible.

Continue building the workflow

Related support: onboarding operations support, contact us. The U.S. Office of Personnel Management - Training and development describes how agencies plan, document, and evaluate recurring briefings and training activities.