On this page11 sections
Growth Operations ResearchA reproducible launch-readiness audit, not an industry benchmark.

Measuring How Often Launch Assets Are Approved Before the Publish Date

A bounded measurement design for counting launch assets that were still unapproved or unversioned when the campaign went live.

Published ••4 min read
Measuring How Often Launch Assets Are Approved Before the Publish Date research illustration

What this measurement covers

This design measures how many launch assets were fully approved before the campaign's publish date, and how many went live while still in draft, review, or an unversioned state. It does not measure the quality of the creative. The practical question is whether the approval process finished before the launch, or whether the launch relied on someone approving after the fact. A late approval is a process gap even when the asset is good. The count makes that gap visible and gives the team a baseline for the next launch.

Define the launch and the asset set

Start with one launch and list every asset that ships with it: landing pages, ads, emails, social posts, sales decks, and partner materials. Record the channel and the owner for each. Decide whether internal-only assets count, and write the rule. If an asset is reused from a previous launch, record that and check whether it was re-approved for this use. The asset set should reflect what actually went live, not the original wish list.

Define "approved" precisely

Write down what counts as approved before the publish date. At minimum, an approval by a named person, a recorded date, and the version that was approved. Decide whether a comment such as "looks good" counts, and whether a conditional approval counts. Record the evidence source, such as a ticket status or a signed-off document. A vague definition will produce a result the team cannot act on. The definition should be the same for every asset in the launch.

Capture the publish time

Record the exact time each asset went live, in a single time zone. For a scheduled email, use the send time; for a page, the deployment time; for an ad, the activation time. If the exact time is unavailable, use the closest documented timestamp and mark it as approximate. The publish time is the cutoff against which each approval is judged. Without it, a late approval can look on time because both occurred on the same day.

Capture the approval time and version

For each asset, record the approval timestamp and the version approved. Compare the approved version with the version that shipped. An asset can be approved on time and still fail this check if the shipped file is a later, unapproved revision. Record the person who approved and the channel where the approval lives. This step is where the most useful findings appear, because version drift is common and invisible in a simple yes-no review.

Classify the approval state at publish

Group each asset into approved before publish, approved after publish, approved version differs from shipped version, no recorded approval, and not applicable. Add a category for an approval that was conditional and whose condition was not met. The classification separates a timing problem from a version problem and from a missing-evidence problem. Each category points to a different repair, from a schedule change to a file-locking rule.

Measure the share approved on time

Report the number of assets in the launch, the number approved before publish at the shipped version, and the number in each failure category. Report counts alongside percentages and break the result down by channel. Do not describe the result as an industry benchmark or a target. It describes this launch at this time. A small launch with a clear version-drift pattern is more useful than a large aggregate that hides the channel responsible.

Check the review lead time

For each asset, calculate the time between approval and publish. A launch where most assets are approved in the final hour is fragile even if everything is technically on time. Report the lead-time distribution and the number of assets approved in the last day. This measure shows whether the team has room to catch an error or whether the schedule depends on everything going right at the end.

Investigate the pattern

Break the result down by channel, by asset owner, and by approval path. Look for a channel that always approves late, a template that changes after approval, or a reviewer who is a bottleneck. A pattern tied to one channel is a scheduling fix; a pattern tied to version drift is a file-control fix. Record the evidence for each pattern so the repair has a clear owner and a measurable test.

Choose one repair and retest

Pick the largest pattern and fix it at the source. That might mean setting an approval deadline before the publish date, locking the approved file, or adding a version check to the launch checklist. Retest with the same definitions on the next launch. Compare the share approved on time and the lead time with the baseline. A repair that moves approvals earlier without slowing the launch is a real improvement.

Document limits and data handling

The measurement depends on the accuracy of the approval and publish timestamps and on access to the version history. It cannot prove that an approval was thoughtful, only that it was recorded. State those limits in the method note. The asset list may include unreleased product details, so restrict access and avoid publishing the launch plan. Delete the working extract when the review is complete. A repeatable launch audit is one that another operator can run before the next launch with the same definitions.

Sources

  1. https://www.nist.gov/cyberframework
  2. https://www.ftc.gov/business-guidance/advertising-marketing
  3. https://www.w3.org/TR/NOTE-datetime
  4. https://www.census.gov/data/developers/guidance/api-user-guide.html
  5. https://www.ftc.gov/business-guidance/privacy-security