Onboarding And Retention Research

How often do newsletter drafts reach a virtual assistant without a named approval owner?

A measurement design for counting newsletter drafts that arrive without a final approver, a backup approver, or a written rule for which edits require review.

| 4 sources

How often do newsletter drafts reach a virtual assistant without a named approval owner?
4weeks observed
40newsletter drafts reviewed
3approval states
On this page
  1. Key takeaways
  2. Question and scope
  3. What counts as an approval owner
  4. How the sample was built
  5. What the counts showed
  6. Where the approval path breaks
  7. What to change next
  8. Limitations
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Count a draft as ready only when it names a final approver, a backup, and the edit rule that requires review.
  • Separate a missing approver from an approver who was named but never confirmed the role.
  • Record the first request time and the actual approval time, because a late owner changes the cycle.
  • Test one required owner field in the newsletter template and recheck the next ten drafts.

Question and scope

This study asks how often a newsletter draft reaches a virtual assistant without a named final approver. It treats the draft as the unit and the first assignment as the event, not a later repaired version. The scope is one assistant, one editorial team, and a fixed four-week window. The result describes that setting and should not be read as an industry benchmark.

A draft is eligible when it is intended for an external audience and has a planned send date. Internal notes and test messages are excluded because there is no external approval. A draft is counted once even if it is corrected before the first review. The study records the state the assistant received rather than the state after a cleanup.

The study also records who supplied a missing approver and how long before the send the name arrived. An approver confirmed by the team lead is different from one inferred from the sender list. The source of the correction is part of the result. Counts are reported by newsletter type and by audience size.

A draft with an approver but no backup is treated as partial rather than ready. The assistant may know who reviews the copy but not who covers an absence. The study records the missing part instead of filling it in. This keeps a familiar name from being mistaken for a complete approval path.

Draft stateWhat is presentNext action
ReadyApprover, backup, edit ruleSend at the planned review time
PartialApprover named, no backupAsk the owner for a backup
MissingNo named approverReturn to the requester
StaleNamed approver has leftReassign before the next draft

What counts as an approval owner

A complete record names the person who may approve the final copy and the person who may approve in their absence. It also names the role that gives each person authority over the subject matter. A name without a role is not enough because the assistant cannot tell who decides a disputed claim. The coding requires both the person and the basis for authority.

The final approver is the person whose acceptance allows the send. An editor who improves the copy may not hold that authority. The study codes the final approver separately because a fast edit should not be mistaken for a decision. A draft that confuses the two is coded as partial.

The edit rule is part of the record because a small change may need the same review as the original text. The study records whether the rule names specific triggers, such as a new claim or a changed quotation. A general instruction to use judgment is coded as missing. This prevents a vague rule from appearing complete.

A delegation is recorded as a change to the owner, not as an error. The original approver, the delegate, and the person who confirmed the delegation are all noted. The study counts a delegated approval only when the delegation is written. A verbal delegation is coded as unverified.

How the sample was built

The sample starts from a frozen list of every external newsletter draft with a send date in the study window. Drafts are included regardless of audience size so the study does not overrepresent large lists. The list is exported before the first review and stored with a hash. Later additions are tracked separately and are not used to change the original denominator.

Each draft is reviewed in the order it appears on the list rather than the order it becomes urgent. That rule prevents the sample from being dominated by issues that are already close to sending. The assistant records the first state before opening the draft. The draft is then read to verify the named approver and the edit rule.

A second reviewer checks a random subset of ten drafts against the request thread. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the thread together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.

Drafts that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. This keeps the denominator stable and makes the comparison across weeks honest.

What the counts showed

Most drafts arrived with a sender name and a send date but no named final approver. Those drafts looked ready because a person was attached to the message. The missing role only became visible when the assistant tried to confirm a claim. This is the central failure the study was designed to expose.

A smaller group named an approver who had left the team or changed roles. The name looked specific and was often months out of date. The study codes this as stale rather than ready. A familiar name can be more dangerous than a blank field because it discourages a check.

Drafts with a named approver were more likely to include a backup, but the two fields did not always travel together. A draft could name a backup without saying when the backup takes over. The assistant then had to ask a question that the record should have answered. These partial drafts accounted for a meaningful share of the review time.

Only a small share of drafts were ready at first arrival. Readiness improved after the first request because the assistant asked for the missing name. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.

Where the approval path breaks

The first break happens when the request names a team rather than a person. A shared inbox looks like an owner but cannot accept responsibility. The assistant can send the draft but cannot tell who has read it. A named person with a backup would remove most of this delay.

The second break happens when the approver changes during the cycle. A new manager may inherit the role without inheriting the context. The assistant should record the change and confirm the new owner before the next send. The study treats an unconfirmed change as missing.

The third break happens at the edit rule. A reviewer may accept the draft while asking for a softer claim, and the assistant may not know whether that counts as approval. The study records a conditional approval as open until the condition is closed. A draft that leaves with an open condition is coded as a process failure.

The fourth break happens at the send deadline. A draft that reaches the approver an hour before the send cannot receive a real review. The study treats timing and ownership as separate results. A complete record that arrives late is still a late record.

What to change next

Add a required final-approver field to the newsletter template and require a named backup. The field should include the role that gives the person authority. A draft should not be saveable as ready without both names. This turns a hidden assumption into a visible task.

Add an edit-rule field with a short list of triggers, such as a new claim, a new link, or a changed quotation. Require the assistant to record whether each trigger applies. A general instruction to use judgment should be flagged. The rule should be reviewed when the newsletter format changes.

Record the first request time and the actual approval time in the cycle log. Compare the gap with the planned review window. A recurring gap points to a deadline that is set too late. The goal is not a faster approval but enough time for a real one.

Test the revised template on the next ten drafts and compare the ready share to this baseline. Record how long the assistant spends repairing each incomplete draft. A template that adds fields without reducing repair time is not an improvement. The comparison should use the same coding rules.

Limitations

The study covers one assistant and one editorial team, so the counts describe that setting rather than a market. A team with a different newsletter mix may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as an editorial benchmark.

Some requests are genuinely ambiguous about who holds approval authority. The study codes ambiguity as missing rather than guessing the intent. That choice may overstate the gap in a team with unusual but clear practices. The reviewer notes record where ambiguity drove the code.

The four-week window may not include a full quarter of campaigns. A team with most newsletters in one season could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.

The assistant knew the study was running, which may have changed how carefully drafts were reviewed. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.

Sources and methodology

The study follows newsletter drafts handled by one virtual assistant across a fixed four-week window, coding the named approver, the backup, and the written edit rule at the moment each draft first arrived.

  1. U.S. Small Business Administration - Manage your business current.
  2. U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
  3. Federal Trade Commission - Advertising and Marketing Basics current.
  4. National Institute of Standards and Technology - Cybersecurity Framework current.

Source count: 4. Last verification date: November 19, 2026.

Questions about the findings

Is an editor the same as an approver?

No. An editor improves the copy, while an approver accepts the claims and authorizes the send. A draft can have an editor and still lack an approver.

Should the backup be copied on every draft?

The backup should be named and briefed, but copying every draft can create noise. The entry should say when the backup takes over.

What counts as an edit rule?

A written rule names which changes require a second review, such as a new claim, a new link, or a changed quotation.

How many drafts are needed to see a pattern?

The forty drafts in this study show the intake pattern for one team. A larger sample is needed before treating the rates as a benchmark.

Which measure is most useful?

The share of drafts ready at first arrival plus the median time to approval. The pair shows both the gap and its effect on the cycle.

Put the finding to work

Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.

newsletter productionapproval ownersvirtual assistant research