Agency operations workshop / 5 MIN READ
Make the campaign cover plan usable on the first day
Transfer decisions, access and escalation routes before the usual owner becomes unavailable.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A cover plan should let another person carry the next real task without guessing which commitments matter. Practical rehearsal reveals gaps that a long handover document can conceal.
What you will leave with: A temporary ownership handoff with priority actions, decision limits and tested access.
Use this when
- A campaign lead is taking leave during active delivery.
- A project depends heavily on one person’s knowledge or inbox.
This does not authorize sharing passwords, expanding access beyond need or assigning approval powers that the substitute does not hold.
Define the period and the work requiring cover
Atlassian’s working-agreements guidance recommends revisiting expectations when work arrangements change. Identify the tasks and decisions that fall inside the absence period.
Separate work that must continue from work that can deliberately wait. List external commitments, scheduled reviews and dependencies with the latest useful action point. Avoid handing over the entire project history without priorities. The substitute should know what would create a material problem if missed and which routine decisions already have a stable approved plan.
Assign responsibility and authority separately
Name who owns each continuing task and who can approve its consequential decisions. A colleague covering coordination may still need a different authorized person for spending, scope or publication. Provide the relevant escalation route and backup.
Explain current uncertainties and any decision that must not be assumed complete. Keep personal or sensitive information out of the general handover unless the substitute genuinely needs and is authorized to access it. Use approved access delegation rather than sharing account credentials. Check whether suppliers and client contacts need an authorized notice of the temporary arrangement.
Rehearse the next realistic task
Ask the substitute to locate the current plan, open the relevant approved material and explain the next action. Verify access through their own account. A link that works for the outgoing owner may not work for the person covering them.
Walk through one likely exception, such as a missing supplier confirmation or a client request that changes scope. The substitute should know what they can decide and when to escalate. Resolve unclear responsibilities before the absence where possible. If a gap cannot be closed, document the limitation and agree a safe alternative rather than assuming the owner will remain available.
Return ownership with a concise change record
During the absence, keep a short record of material decisions, changed commitments and unresolved issues. Avoid making the substitute write a parallel diary of routine activity. On return, review those changes and confirm who now owns each remaining action.
Close temporary access or delegation through the authorized process when no longer needed. Tell affected collaborators when the ordinary contact route resumes. Preserve the decisions made within the substitute’s authority rather than reopening them simply because the original owner returned. A good cover arrangement maintains continuity while allowing both people to work within clear limits.
Make the reasoning concrete.
A fictional campaign lead prepares for leave by forwarding a large email folder. The substitute can read the messages but cannot approve a venue change or access the supplier agreement.
Rely on the forwarded history
Opening: Expect the substitute to contact the lead if anything is unclear.
Hypothesis: Preparation appears complete.
Risk: The lead remains an informal dependency and the substitute lacks practical authority.
Rehearse the imminent decision
Opening: Confirm the current venue status, contract access and authorized escalation owner.
Hypothesis: The substitute can handle the next likely event without guessing.
Risk: Some decisions may need to wait or be routed to another approver.
The team resolves the access gap through the approved administrator and names a separate commercial approver. The outgoing lead leaves a focused action list rather than an expectation of constant availability.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Period
Which tasks and commitments fall within the absence?
Priority
What creates a material problem if missed?
Authority
What can the substitute decide and what needs escalation?
Rehearsal
Can they perform the next task using their own access?
Return
How will changes and temporary permissions be reconciled?
Watch for the wrong conclusion.
- Forwarding history without identifying the next commitments.
- Sharing passwords instead of using approved delegation.
- Assuming the absent owner will remain the default escalation route.
Your next action
Ask the person covering you to perform the next campaign task from the handover instructions and fix the first access or authority gap they encounter.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Atlassian Team Playbook: Working Agreements →Primary framework-publisher guidance · Supports: Working agreements make collaboration expectations explicit and can be revisited when circumstances change; the agency application is original analysis.