The Bus Factor in Account Operations: Finding Knowledge Only One Person Holds

Editorial team Spend Ledger

Why a team can depend on one person

An advertising operation may look like a team effort while relying on one person for the knowledge that keeps it running. That person may know which account belongs to which business, how an agency relationship is arranged, where a supplier agreement is recorded, or what to check when a campaign stops delivering. If they become unavailable, others may be left unable to act confidently.

This vulnerability is often called the bus factor: the number of people whose absence could interrupt important work because essential knowledge is concentrated with them. The phrase is not a forecast about any individual. It is a way to ask whether the operation can continue safely when someone is away, changes roles, or leaves.

In paid advertising, the consequences can reach beyond missed tasks. Confusion about account ownership, billing, permissions, campaign history, or support responsibilities can lead to rushed decisions. A team might duplicate work, overlook an important obligation, or make a change without understanding its effect. The aim is not to make everyone an expert in everything. It is to ensure that critical work is documented, authorized, and transferable.

An advertising account is a work tool and, where relevant, a purchased good. It is not a means of avoiding platform requirements. Continuity planning should preserve legitimate ownership, access, and operating practices—not conceal who is responsible or work around a restriction.

Map the work before mapping the people

Start by listing the recurring work that keeps the account operation functioning. Include setup and administration as well as campaign tasks: maintaining access records, confirming who is responsible for billing, preparing campaign changes, checking performance, documenting decisions, handling supplier communications, and responding to account issues.

For each task, record who currently performs it, who can explain it, and where the relevant records are kept. These roles may belong to different people. Someone may carry out a routine without understanding why it exists, while another person may know the rationale but not have permission to act. A useful map makes those differences visible.

A simple working table can include:

• The task and the situation that triggers it.
• The person responsible for carrying it out.
• A colleague who can provide cover.
• The approved access needed to do the work.
• The location of the instructions and supporting records.
• Any decision that requires a manager, account owner, or external partner.

Keep the map focused on operational knowledge rather than sensitive credentials. Do not put passwords, payment details, identity documents, or recovery information into a general handover file. Record where authorized access is managed and who is permitted to request or approve changes. Follow the platform’s official security and access processes.

The map should also distinguish between routine work and exceptional decisions. A colleague might be able to pause a planned change or gather information without being authorized to alter ownership, payment arrangements, or account structure. Clear boundaries reduce the risk that a handover becomes an invitation to improvise.

Look for single points of failure

A single point of failure is not always a login. It can be any necessary step, relationship, or judgment that only one person can supply. Ask what would stop if the person who usually handles a task were unavailable, and what the next person would need in order to continue.

Watch for signs such as:

• A supplier relationship exists only in private messages or one person’s memory.
• The team cannot explain why an account is arranged in a particular way.
• A recurring task has no written steps or named backup.
• Important campaign decisions are not recorded with their rationale.
• Only one person knows how to find current billing or ownership information.
• Others have access but are unsure what they are allowed to change.
• A support issue depends on one person knowing its history or previous responses.

Access deserves careful attention. A team may assume that several people can cover a task because they can log in, but access alone does not provide context or authority. Conversely, a colleague may understand the work but lack approved access. Both gaps matter.

Review account and business structures through the platform’s permitted administrative processes. Confirm that roles reflect current responsibilities and that access is granted only where appropriate. Do not use shared credentials as a shortcut to continuity. If access or ownership is unclear, pause consequential changes and consult the platform’s official help or support channels.

Record the knowledge that matters

Documentation is most useful when it helps someone act, rather than merely describing what the experienced operator already knows. Keep notes short enough to maintain, but specific enough to guide a colleague through a familiar task.

A practical note can state when the task applies, what information to gather, what checks to complete, and what conditions mean the work should stop for review. It should identify the approved location of records and the role responsible for decisions. Where a task involves a platform setting, describe the purpose and the expected checks without inventing interface labels that may change.

Record the reasoning behind important choices. For example, note why a campaign structure was selected, what business objective it serves, which assumptions informed a test, and what evidence would prompt a review. For financial planning, label estimates and assumptions clearly. Keep actual results distinct from forecasts, and record who approved material changes.

Supplier notes should capture the scope of the relationship, agreed responsibilities, relevant correspondence, and unresolved questions. If an account or service was sourced from another party, retain the written terms and clarify who is responsible for access, support, billing, and compliance. Do not treat a purchase or handover as permission to ignore platform rules or to misrepresent ownership.

Documentation needs an owner. Assign someone to review it when processes, roles, agreements, or platform requirements change. Store it in an approved location with appropriate access controls. Keep sensitive information out of general notes and follow internal security practices for anything that could affect account control.

Use pair work to transfer judgment

Written instructions cannot capture every decision. Pair work lets a colleague observe how an experienced operator handles normal tasks, notices exceptions, and decides when to escalate. It also reveals where the routine depends on tacit knowledge that has not yet been recorded.

Begin with observation and explanation. The person who usually performs the task can walk through the process while describing the purpose of each check and the risks it is intended to manage. The colleague should ask questions and update the notes afterward. This turns the session into a test of whether the explanation was clear, not just a demonstration.

Then reverse the roles. Let the colleague carry out the task while the experienced operator watches. The observer should avoid taking over at the first hesitation. A pause can reveal a missing instruction, an unclear boundary, or a decision that needs a named approver.

Pair work should not create unnecessary access. Use the colleague’s own authorized account and permissions, and avoid exchanging credentials or exposing confidential information beyond what the task requires. If the task involves a sensitive change, practice with a harmless review or a documented scenario rather than making an unneeded live alteration.

The goal is not identical working styles. A backup should understand the required checks, decision limits, and escalation route, while retaining room to use sound judgment within those boundaries.

Test whether someone can really take over

A handover is not proven by a folder of notes or a colleague saying they understand. Test it in a controlled way. Choose a routine task with a clear purpose and limited consequences, then ask the backup to complete it using the documentation and their own approved access.

Observe whether they can find the relevant records, explain what they are checking, recognize when a decision is outside their authority, and leave a useful record of what they did. Avoid testing by creating a real account problem, changing ownership, altering billing, or making a campaign change that the business does not need.

After the exercise, ask what was difficult to locate or interpret. Update the instructions while the details are fresh. If the backup could complete the task only because the usual operator supplied an undocumented answer, the process is not yet transferable. Repeat the exercise after the notes or role boundaries have been clarified.

A useful test also covers communication. Can the colleague identify who needs to be informed, where to record the action, and how to hand the matter back? Can they distinguish a routine issue from a situation requiring the account owner, manager, supplier, or platform support? These checks matter as much as the mechanical steps.

Testing should be proportionate to risk. A low-impact review can be practiced routinely; a sensitive administrative action may require formal approval and a different control process. Follow the organization’s policies and the platform’s official requirements.

Make supplier and account arrangements legible

Supplier relationships are especially vulnerable to concentration because key details can remain in private correspondence or informal conversations. Keep a central record of the agreed scope, who owns each responsibility, how changes are approved, and what happens when a service or relationship ends. Put material expectations in writing rather than relying on one person’s recollection.

For agency-provided accounts or other externally managed arrangements, clarify who holds the relevant permissions, who is responsible for billing and support, what records the business can access, and how continuity is handled if the arrangement changes. The exact terms depend on the arrangement; do not assume that access, ownership, or transfer rights are interchangeable. Check the written agreement and applicable platform policies.

If the business prepares its own accounts, document the internal ownership and approval path just as carefully. If it sources a ready-made account or other account-related service, establish what is being provided and whether the arrangement is permitted before relying on it. Do not attempt to preserve continuity by hiding links between accounts, replacing an account to evade a restriction, or misrepresenting a responsible party.

When an account is restricted, verification is requested, or ownership is disputed, use the platform’s official appeal and support channels and address the underlying issue. Keep a clear record of the case and the steps taken. A continuity plan can help the team gather accurate information; it cannot substitute for required verification or guarantee a particular outcome.

Keep the map current and proportionate

Knowledge maps and handover notes become unreliable when roles change but documents do not. Review them when responsibilities, supplier arrangements, account structures, or internal approval processes change. Also revisit any task that has caused confusion, required an undocumented decision, or depended on a colleague who is no longer available.

Keep the process proportionate. Not every task needs a long manual, and not every team member needs access to every account or record. Prioritize tasks whose interruption could affect business operations, financial control, compliance, or the ability to respond to an account issue. Use concise checklists for routine work and more careful records for consequential decisions.

Current platform requirements, access options, and support procedures can change. Check the platform’s own help and policy pages for current information rather than relying on an old note as a substitute. Update internal instructions to reflect what the team has verified, and flag anything that remains uncertain.

The practical measure of resilience is straightforward: when the usual operator is unavailable, can an authorized colleague locate the right information, understand the limits of their role, and either complete the task safely or escalate it to the right person? If not, the gap is useful information. Document it, arrange a supervised handover, and test again without creating unnecessary risk.