Hidden Staff Time: Measuring What Account Preparation Takes From Your People

Editorial team Spend Ledger

Treat preparation as work, not background admin

Preparing an advertising account in-house can look like a small collection of setup tasks. Someone checks account details, gathers documentation, responds to a platform request and waits for a review. If a step is rejected or needs clarification, the team may revisit earlier work. None of this necessarily appears in a campaign report, yet it takes time away from planning, creative work, analysis and other paid advertising tasks.

A useful measurement exercise starts by treating preparation as a defined work process. Decide what counts as preparation for your team. It might begin when a colleague is assigned an account and end when the account is ready for the intended, policy-compliant use—or when the team records that it cannot proceed. Include relevant follow-up and rework rather than counting only the initial setup.

Keep the boundary consistent. If the same team handles billing, campaign structure or creative production, record those activities separately unless they are genuinely part of the preparation process you are measuring. Clear boundaries make the resulting cost more useful for comparing workflows and deciding where staff capacity is going.

The purpose is not to judge an individual for time spent on a review or a request outside their control. It is to make the work visible, distinguish active effort from waiting, and identify process changes that could reduce avoidable effort without skipping platform requirements.

Use a simple time log by task type

A shared worksheet or other approved internal record can be enough. For each work session, note the account or internal case reference, the task type, the person or role doing the work, the date, active minutes, and a short description of what happened. Use a reference that is appropriate for your organisation and avoid putting sensitive identity or payment details in a general time log.

Keep the categories practical and stable. A short list could include:

• Initial review and setup
• Gathering or checking documents
• Responding to platform questions
• Monitoring a pending review
• Correcting or redoing work after a rejection
• Internal handoffs and coordination
• Recording the final status

Adapt the list to your actual process, but resist creating a category for every small action. If staff have to stop and interpret a complicated taxonomy, logging becomes another source of hidden work. A brief note can explain unusual cases without expanding the category list.

Record time soon after the task, rather than reconstructing it from memory at the end of a busy period. If exact tracking is impractical, use a consistent method for estimating active effort and label estimates as estimates. Consistency matters more than false precision.

Separate active effort from elapsed waiting

A review can remain pending while a staff member works on something else. The elapsed time between submission and a response is operationally relevant, but it is not automatically staff time. Logging the entire pending period as labour would overstate the team’s effort. Logging none of it could hide interruptions, repeated checking or the cost of keeping a case open.

Track two distinct measures. Active preparation time is the staff effort spent on the account: reviewing requirements, collecting materials, drafting a response, checking status or coordinating internally. Elapsed waiting time is the period during which the team is waiting for an external review or response. If a colleague checks the case, record the active check separately while leaving the broader wait in its own field.

This distinction supports better planning. A long wait may affect when a campaign can be scheduled, even if it requires little direct labour. Frequent status checks may consume meaningful staff time even when each check is brief. Both matter, but they describe different costs.

Use the platform’s official help and policy pages to understand what is required and how to follow up through its official support or appeal channels. Do not treat a pending review as permission to bypass a check, use a different identity or conceal a connection between accounts. The log should help the team manage compliant work, not find ways around platform controls.

Make interruptions and handoffs visible

Preparation work rarely happens in a perfectly uninterrupted block. A team member may pause campaign planning to answer a question, ask another department for a document, or explain the status to a manager. Those transitions can be easy to overlook because they do not look like account setup itself.

Record material handoffs and interruptions when they consume active effort. A short note can say that information was requested from an internal team, a case was transferred, or work resumed after a response. Avoid logging every momentary distraction; the aim is to understand recurring work, not to monitor people minute by minute.

Pay particular attention to repeat coordination. If several people independently check the same status, or if the same question is repeatedly routed between teams, the log may reveal an unclear owner or an incomplete handoff. That observation can lead to a process improvement, such as assigning responsibility for a case or keeping the current status in one approved internal record.

Protect the log as an operational document. Limit access to people who need it, keep sensitive documents in the appropriate secure location, and record only what is needed to understand the work. Do not copy identity documents, account credentials or private platform correspondence into an informal tracker.

Record rejection and rework without blame

A rejected submission or a request for more information often creates a second round of work. Record the original task and the follow-up separately, with a neutral description of what had to be changed or supplied. This helps distinguish a one-time setup from a process that repeatedly requires correction.

A useful note describes the work, not an assumed motive or fault. For example, record that a document needed clarification or that a response had to be revised to match the platform’s stated requirements. If the cause is uncertain, say so. Do not label a platform decision as arbitrary or conclude that a staff member made an error unless the evidence supports that conclusion.

Review recurring rework at the process level. Are instructions unclear? Is information being gathered too late? Are teams relying on an outdated internal checklist? Does the team need to consult the platform’s current policy guidance? These questions can improve preparation while preserving the requirement to provide accurate information and follow official review procedures.

If a decision appears mistaken, use the platform’s official appeal or support route and provide accurate, relevant information. The time log can record the effort involved in that process, but it cannot predict the outcome. Do not respond to rejection by opening replacement accounts to evade a restriction, changing or concealing identity, or submitting false documents.

Calculate labour cost per prepared account

Once the team has a consistent log, it can estimate the labour cost associated with preparation. Name the variables so that the calculation is understandable and can be updated when internal rates change.

Let Tᵢ represent the active preparation time for each task type. Let Rᵢ represent the fully loaded internal labour rate for the role doing that task. Let P represent any directly attributable preparation expense included in the analysis. Let A represent the number of accounts that reached the team’s defined prepared status during the reporting period.

The estimated labour cost per prepared account is:

Cost per prepared account = [Σ (Tᵢ × Rᵢ) + P] ÷ A

Use the same time unit for each Tᵢ and the matching rate Rᵢ. If staff rates are not available or should not be included in a shared report, calculate the total active hours per account instead. That still shows how much capacity the process uses, even without assigning a monetary value.

Define A carefully. If the denominator includes only accounts that reached the chosen status, the calculation describes the cost per prepared account, not the cost per attempt. For a fuller view, also report total preparation labour across all cases, including cases that could not proceed. Keep waiting time separate from labour cost unless your organisation has a defensible method for valuing its operational impact. Do not mix purchased-account costs with internal labour unless the comparison clearly separates both.

Find the work that crowds out campaigns

A total cost can show that preparation takes meaningful effort, but task-level results explain where the effort goes. Compare active time by category and role. Look for repeated document gathering, multiple rounds of responses, frequent handoffs or status checks that interrupt campaign work. The purpose is to identify a bottleneck, not to treat every minute as waste.

You can also record a simple capacity note alongside the log: which campaign task was delayed or paused when preparation work arose. Keep this qualitative unless your organisation has a reliable way to measure the impact. A log may show that preparation regularly interrupts campaign planning; it cannot, by itself, prove what revenue or performance would have resulted from the alternative use of that time.

Review the record with the people who do the work. Ask whether the categories reflect reality, whether an important task is missing, and whether the process encourages unnecessary checking. Avoid using a small set of observations to make sweeping claims about staff productivity or platform review quality. The record is a management aid, not a complete assessment of people or outcomes.

Compare routes and refine the process

The same measurement framework can help compare in-house preparation with sourcing an account that is already prepared or working through an agency arrangement. Compare like with like: include the relevant purchase or service cost, internal coordination, checks your organisation must still perform, and the work required to meet the platform’s rules. A supplied account does not remove your responsibility to understand its status, ownership, permissions and permitted use.

For any external arrangement, agree in writing what is being provided, who is responsible for support and documentation, what happens if the platform requests information, and what records your team should retain. Check the platform’s own policies before proceeding. An external provider’s assurances do not replace the platform’s requirements, and no route guarantees approval or uninterrupted access.

Revisit the log when the workflow changes, and keep the method consistent enough to compare periods. Use what it reveals to clarify ownership, improve internal instructions, reduce duplicative handoffs and plan campaign capacity. The goal is a transparent estimate of the work involved in preparing an advertising account—not a shortcut around review, verification or other platform rules.