The last post went up weeks ago. Two finished captions sit in an email thread, and a DM about weekend availability has been waiting since last Tuesday. Every caption still has to pass through the same person before it can go live.
That situation usually gets called being busy. It is a symptom. The work below is about finding which cause sits behind yours.
Why "We're Just Busy" Is Not a Diagnosis
Five different problems produce the same quiet calendar:
- not enough hours
- posts stuck in approvals
- missing content inputs
- a skills gap in platform work
- nobody owning the day-to-day
Each one has a different fix. Adding hours to an approval problem just gives you more finished drafts waiting in the same inbox.
Treat these five as an editorial triage framework. It is built from published workflow guidance by Hootsuite, Sprout Social and Metricool. It is not a validated assessment, and it says nothing about which constraint is most common. Several can hold at once.
Outsourcing is one possible result of this diagnostic. Other results include cutting a platform, naming an owner or setting a review deadline, and some of those cost nothing. The diagnostic runs in five steps:
- Run a social media workload audit on the last 30 days of recurring work.
- Pick one delayed item and run it through the decision tree.
- Read the constraint section the tree points to.
- Compare fixes in the constraint-to-fix map.
- Decide whether an ongoing operating gap remains after the internal fixes.
Step 1: Audit the Recurring Social Media Workload
Block 30 minutes and open your last 30 days. That means the published posts, the sent replies, and the email threads where someone asked for a photo.
You are building a social media workload audit: a list of recurring work with an owner and a time figure on each line.
The goal is an accurate list. It is not a case for hiring anyone.
Done properly, the same document works as a handover sheet for a new employee or an outside provider.
The audit also exposes a common mix-up. What a scheduling tool does and what a person does are separate line items, and our comparison of scheduling tools versus management covers that split.
If you suspect whole categories are missing from your list, see what a social media management company actually does for the full task set.
List every recurring task, not every post
"Write captions and post" covers two lines of a much longer list. Hootsuite's workflow guidance describes day-to-day social media activities as running from brainstorming ideas to publishing posts and tracking their performance. Most of that happens before or after the post itself.
Start with these categories and keep only the ones in your real scope:
- Monthly planning, plus the review where the plan changes
- Asset requests for photos, video and product shots
- Copywriting
- Platform adaptation: resizing, rewriting hooks, re-cutting video
- Scheduling
- Approval chasing
- Comment and DM replies
- Monitoring mentions and tags
- Reporting
Split production into smaller pieces than feels natural. Practitioners who film most days often say editing is the part that slips. That tells you filming, editing, scheduling and engagement are four tasks, not one.
A five-minute fragment, such as checking comments between appointments, is still a task, and it still needs an owner.
Record active work time and flag single-person dependencies
Next to each task, log its active work time. That is the minutes someone actually spent working on it, taken from your last 30 days rather than from memory of a typical week. Then mark every task that only one person can do.
Approvals, product or service knowledge, and replies that need judgment usually land here.
Those marks can matter more than the totals. A single-person dependency is how a vacation or a resignation turns into a publishing outage.
The only hours benchmark in this guide is a UK survey covered in the capacity section, and it cannot stand in for your own log.
Count the hidden work: approvals, rewrites, and inbox triage
Some work rarely appears in anyone's job description but still takes real hours:
- approval rounds
- revision cycles
- chasing a location manager for photos
- scanning an inbox for the two messages that need a real answer
For each published piece, count how many times it was touched before it went live. That count is often the surprise.
Log community management separately from content production. Replying is its own workload. So is tracking what you already told the same person, and on which platform.
Small-business operators describe giving one customer two different answers on two platforms.
That is a coordination failure, not a writing one.
Note on reply expectations. Sprout Social's Q3 2026 Pulse Survey PDF describes an online Glimpse survey of 2,286 social media users in the US, UK and Australia, fielded August 11 to 18, 2026.
In it, 38% said they expect a brand to respond to a customer-care issue within one to two hours. That 38% includes 14% who want a reply within minutes.
Read that as what consumers expect for care issues raised on social. It is not resolution time, and it is not a survey of small-business customers specifically.
It is also not a service promise you are obliged to make.
The Social Media Workload Audit Worksheet below is designed to be printed and filled in by hand. Copy the recurring task entry once per task, recording the task, its owner, active work minutes and whether only one person can do it.
Copy the delayed item entry once per stuck item, noting any missing input, the date approval was requested, the date the decision arrived and how many times it was touched before publishing.
Waiting time has no box of its own. Work it out from the gap between the request date and the decision date, and never add that gap to active work minutes as labor hours. A caption that took minutes to write and then waited days for sign-off cost minutes of work, not days.
A short ownership block also records the day-to-day social owner, backup owner, final approver and agreed review time.
The decision tree takes one delayed item at a time, so keep your worksheet entry in front of you.
It asks up to four questions, in this order:
- Is a day-to-day owner named and authorized?
- Are the needed inputs in hand?
- Have finished drafts waited past the agreed review time?
- What does your work log show?
As you choose answers, it shows one outcome: the constraint to investigate first and a first remedy.
You can restart for the next item. Answers are not saved.
The question order is a practical way to investigate. It is not a ranking of how common each constraint is.
The tree does not read your worksheet. If neither final answer fits, stop and look at the log rather than forcing a result.
Which constraint is holding this delayed item back?
Use one delayed item at a time, with your worksheet entry in front of you. Several constraints can coexist, and the question order is a practical investigation order, not a ranking of how common each constraint is. The tree does not read your worksheet, and answers are not saved. If neither answer to the last question fits, stop and inspect your work log.
Question 1 of 4
Is a day-to-day owner named and authorized to produce, publish and watch the inbox (separate from who gives final approval)?
Investigate ownership
Name a day-to-day social owner and a backup, and separate calendar, reply and final-approval responsibilities. No savings are implied.
This is the first constraint to check for this item, not proof it is the only one. Other constraints may also apply, so rerun the tree once ownership is settled.
Investigate content inputs
Set a monthly inputs check (photos, offer details, brand guidance) with a supply date and a named supplier. Inputs remain a business obligation if you outsource.
This is the first constraint to check for this item, not proof it is the only one. Other constraints may also apply.
Investigate approvals
Name creator, reviewer and approver, agree a turnaround time per stage, and keep feedback in one place. Record request and decision dates for each item.
Keep time spent editing separate from elapsed time waiting for a decision. Do not add the two together as labor hours.
Investigate capacity
Compare active work time with available hours, then consider cutting scope, batching, dropping a platform or delegating recurring execution.
Use active work time from your own log and leave waiting time out. Survey figures about typical weekly hours should not decide this result.
Investigate platform skills
Identify which platform-specific adaptation tasks cause rework, then consider training, narrower platform scope or specialist help for those tasks.
Repeated rework points to a possible skills gap but does not prove one. Check the log for the specific tasks involved before acting.
Question and outcome reference
- Is a day-to-day owner named and authorized to produce, publish and watch the inbox (separate from who gives final approval)?
- No, or it is unclear who owns it
- Yes, one person is named and authorized
- Are the needed assets, offer details and brand guidance in hand for this item?
- No, something is missing or unusable
- Yes, everything needed is ready
- Have completed drafts waited longer than the review time you agreed?
- Yes, drafts are waiting on a decision
- No agreed review time exists yet
- No, decisions arrive within the agreed time
- What does your work log show for this item?
- Ready tasks exceed the hours actually available
- Required platform work repeatedly needs correction or outside skill
- Investigate ownership
Name a day-to-day social owner and a backup, and separate calendar, reply and final-approval responsibilities. No savings are implied.
This is the first constraint to check for this item, not proof it is the only one. Other constraints may also apply, so rerun the tree once ownership is settled.
- Investigate content inputs
Set a monthly inputs check (photos, offer details, brand guidance) with a supply date and a named supplier. Inputs remain a business obligation if you outsource.
This is the first constraint to check for this item, not proof it is the only one. Other constraints may also apply.
- Investigate approvals
Name creator, reviewer and approver, agree a turnaround time per stage, and keep feedback in one place. Record request and decision dates for each item.
Keep time spent editing separate from elapsed time waiting for a decision. Do not add the two together as labor hours.
- Investigate capacity
Compare active work time with available hours, then consider cutting scope, batching, dropping a platform or delegating recurring execution.
Use active work time from your own log and leave waiting time out. Survey figures about typical weekly hours should not decide this result.
- Investigate platform skills
Identify which platform-specific adaptation tasks cause rework, then consider training, narrower platform scope or specialist help for those tasks.
Repeated rework points to a possible skills gap but does not prove one. Check the log for the specific tasks involved before acting.
Constraint 1: You Don't Have the Hours (Capacity)
A capacity problem has a recognizable shape. The plan exists and the ideas exist, but publishing still slips. The same two people also answer email, update the website, run events and deliver the actual service.
Before you call it capacity, check whether drafts exist.
A team with a plan and no hours looks exactly like a team with no plan until you open the drafts folder. No drafts at all usually means a strategy gap.
If drafts exist, compare the hours you actually have against the active work time in your audit, and leave waiting time out.
About the one hours figure in this guide. Professional Beauty covered a survey commissioned by Markel Direct, in an article updated August 6, 2026.
It reports that 54% of 501 UK small-business owners and tradespeople spend one to three hours a week creating social media content.
Read that figure narrowly. It covers the UK only and content creation only, and it comes from trade-press coverage. The fieldwork dates and question wording were not established.
It is not a recommended budget or a US benchmark.
Capacity fixes fall into two groups:
- One-time process changes: cutting scope, batching production into set sessions, dropping a platform, setting up a scheduling tool.
- Ongoing operating changes: delegating recurring execution to an employee, a freelancer or a provider.
Could you just drop a platform or buy a scheduling tool?
Both can be the right answer. Dropping a platform removes real work. A tool helps publish content once it is ready, but it does not supply missing information, decide who approves, or provide skills nobody on the team has.
Constraint 2: Posts Are Stuck in Approvals, Not Production
The calendar looks empty, so the diagnosis becomes "we need more content." Then you find four finished drafts in the owner's inbox, and one has comments on a version that already changed.
That is an approval bottleneck, and it is easy to misread as a content shortage. The tells:
- More than one approver, with no agreed order between them
- Feedback split across text, chat and email
- No one named as the owner of the deadline
- Confusion about which version is the latest
- Content re-approved after small edits
Record approval turnaround time as the time between the request and the decision. Keep it in a separate field from active editing time.
A draft can take little work and still lose a week.
A quiet calendar can mean the drafts exist and the decisions don't.
Hootsuite's approval guidance says everyone should know who creates, who reviews and who approves. It also recommends writing down an expected turnaround time for each stage.
Any example deadlines in that guidance are examples, not proven limits, so agree on numbers that fit your week.
This is usually an internal fix. An agency brought in before approvals are defined can add a review step rather than remove one. Our guide to fixing a social media content approval process covers the setup.
If the real issue turns out to be who owns the work, the comparison of employees, freelancers and agencies helps you weigh the options.
Constraint 3: The Inputs Are Missing (Assets, Product Info, Brand Voice)
A fully staffed team still stalls when certain things don't arrive. The photos from Saturday's event never come in, or the launch date isn't confirmed, or the offer terms change after the caption is written.
Material that arrives unusable creates its own editing work.
Run a monthly content inputs check before you build the calendar.
For the month to be publishable, these should be true:
- Photos and video for planned posts are in hand or scheduled for capture, each with a named supplier.
- Launch dates, prices and offer terms are confirmed in writing.
- Brand voice guidance exists somewhere other than one person's head.
- Every outstanding item has a supply date.
This constraint does not go away when you outsource.
It becomes a standing obligation to hand over assets and context on a schedule. Robot Creative, an agency, describes one way to split the work.
The business captures everyday material, such as team celebrations and behind-the-scenes moments, and the agency handles copywriting and posting.
That is one operating example, not evidence of how common the setup is or what it saves.
Will delegating create more briefing and corrections than it removes? It can, when inputs aren't defined first.
One provider managing a local clinic's accounts described asking for photos again and again, then getting material that needed heavy editing. Before you hand anyone a supply schedule, judge honestly whether you can meet it.
Photos and video never showing up on time?
Our in-house studio shoots the photo and video your monthly calendar needs, so posts stop waiting on whoever has a phone free. It fits teams whose inputs check shows missing or unusable assets.
Request a shoot quoteConstraint 4: Platform Adaptation Takes Skills You Don't Have In-House
Exporting one asset to every platform tends to underperform. Format, hook, length and native behavior all differ from one platform to the next.
Metricool's March 2026 workflow guide lists adapting a single piece of content for different platforms under cross-platform posting in its scheduling and distribution phase, and your audit should track it as its own line item.
Platform-specific adaptation is a separate workload item, even when every post starts from the same idea. For small teams, the skill gap often shows up in short-form video editing and platform-specific copy.
Use the log to tell a skills problem from a time problem.
Some platform work keeps needing correction, or keeps getting sent to an outside freelancer. That points to skills. Work that gets done well but late points back to capacity.
Keep the boundary clear.
The recurring problem here is ongoing adaptation and a steady publishing rhythm. A single launch video that needs producing is a project, and you scope and buy it differently.
Not every business needs every platform, and dropping one is a legitimate remedy.
For the production side, see our guide to adapting one idea for each platform.
Constraint 5: No One Actually Owns Day-to-Day Social
Marketing posts the promotion, customer care handles complaints, and a store manager posts from the local account. Meanwhile a DM asking about a refund gets two replies, or none. Nobody owns day-to-day social.
The gap gets noticed only when a customer mentions it, and the calendar runs only while one particular person is around.
Three kinds of ownership tend to get merged. The calendar owner makes sure posts get produced and published. The replies owner handles community management: watching comments and DMs, and tracking what was already said.
The final approver makes the decision.
These roles do not come as a set. The day-to-day social owner is not automatically the final approver.
The approver is not automatically responsible for production or inbox coverage.
| Responsibility | Question it answers | Failure signal |
|---|---|---|
| Calendar and delivery | Who makes sure posts get produced and published? | Drafts exist but publishing slips and nobody chases them |
| Replies and community management | Who watches and answers comments and DMs, and tracks what was already said? | One person gets two different answers, or no answer at all |
| Final decision | Who approves content? | Finished drafts wait in one inbox with no agreed turnaround |
| Backup | Who covers absence? | The calendar stops whenever one person is away |
Sprout Social's workflow guidance recommends setting out what you expect from each person and agreeing who is responsible for what.
This article goes one step further: name a day-to-day social owner and a backup. That pairing is our recommendation, not a research finding.
For how responsibility splits across groups, see who owns social media across marketing, customer care and local teams.
If your main risk is continuity rather than daily volume, our guide to social media holiday coverage and backup planning is the better next read.
DMs getting two replies, or none?
Our community team monitors and answers comments and DMs, tracks what each person was already told, and escalates sensitive questions to you. It fits teams where the replies owner role is the one nobody holds.
Request a community quoteWhat Each Constraint Means for the Fix (and What Falling Behind Costs)
Approvals, ownership and platform scope usually start with an internal fix. Approvals need roles and deadlines. Ownership needs a name.
Platform scope can be cut.
Only some results point toward an ongoing management scope, and that is the honest reading of the diagnostic.
A team feeling busy cannot justify a retainer; only the log and the diagnosis can.
Before hiring, look at the alternatives:
- Write social into an existing role explicitly.
- Cut a platform.
- Use tools to speed up the owner's own production.
The constraint-to-fix map
Each row below starts with the first thing to try, and that is often internal.
| Constraint | What the work log shows | First thing to try | When an ongoing management partner becomes relevant |
|---|---|---|---|
| Ownership | Replies get two answers or none, and the calendar runs only while one person is around | Name a day-to-day owner and a backup, or write social into an existing role | When no internal owner can be named and the work recurs every month |
| Content inputs | Tasks wait on photos, offer details or brand guidance, and supplied material needs heavy editing | Run a monthly content inputs check with a named supplier and supply date for each item | When you can keep a supply schedule but still lack capacity for recurring copy and posting |
| Approvals | Finished drafts wait past the agreed review time, with feedback split across channels | Name who creates, reviews and approves, agree turnaround per stage and collect feedback in one place | Only if an ongoing gap remains after approvals are defined |
| Capacity | Ready work exceeds the hours available, measured by active work time | Cut a platform, batch production into set sessions or use a scheduling tool | When the work recurs monthly and no internal hire is coming |
| Platform skills | Platform-specific work repeatedly needs correction or goes to an outside freelancer | Cut a platform or build skills on the one platform that matters most | When ongoing adaptation and a steady publishing rhythm are needed rather than a one-off project |
Two or three constraints together behave differently from one. Ownership plus capacity is the combination where a recurring scope tends to make sense. Naming an owner does not create hours, and adding hours does not create an owner. This is still editorial triage, and several constraints can exist on one team at the same time.
The cost of another quarter of gaps
An unanswered question about availability may become a booking or order that went elsewhere. Staff who stop client work to check three inboxes lose time to context-switching. An account that posts in bursts and then goes quiet for weeks leaves visitors unsure whether the business is active. None of that means a missed post would have produced a sale.
Check your own case three ways:
- Look at how old your unanswered enquiries are right now.
- Ask new customers how they found you.
- For any question about bookings, set up a separate CRM workflow. Use actual enquiry records, response timestamps and booking records, and write down how you will decide which channel gets credit for a booking.
Tracking tags only identify tagged links. They don't show the untracked path that led someone to you, and clicks are not sales. For a fuller way to size the question, see what missed posts and unanswered messages cost a business. If you conclude the gap is now ongoing, read when to outsource social media management.
Map your social media workload. Finish the audit and run the decision tree on your own delayed items. Then talk to us about any gaps that remain. Recurring management only comes into the conversation if an ongoing operating gap is still there.
Can't say which channel earned a booking?
Our analytics team sets up KPIs, dashboards and a reporting call that connect social activity to your enquiry and booking records, with no specific tool required. It fits owners who want evidence before deciding how much social needs fixing.
Request a measurement planWhen an Ongoing Management Scope Makes Sense
Three conditions mark the point to stop treating this as a temporary crunch:
- The constraint is ownership or recurring delivery, not a one-time project.
- The work will continue every month.
- No internal hire is coming.
Before any handover, document:
- The recurring task list from your social media workload audit
- The approval workflow and the agreed approval turnaround time
- The content inputs schedule: what arrives, from whom, and by when
- Response expectations for comments and DMs
- Coverage for absences and off-hours
- Who holds account access, and what customer data, if any, the role needs
- Which decisions stay with the business
| Work area | Business still owns | Provider can take on if included in the agreed scope |
|---|---|---|
| Content inputs | Supplying photos, video, offer terms and brand voice guidance on a schedule | Requesting inputs and flagging gaps, if included in the agreed scope |
| Approvals | Naming the approver, agreeing turnaround time and making final decisions | Preparing drafts and routing them for review, if included in the agreed scope |
| Replies and escalations | Answering sensitive or judgment-based questions and deciding what needs owner input | Monitoring and answering routine comments and DMs and escalating the rest, if included in the agreed scope |
| Platform-specific adaptation and publishing | Deciding which platforms are in scope and controlling account access | Adapting content for each platform and publishing it, if included in the agreed scope |
| Monthly review and reporting | Reviewing results and deciding what changes | Preparing the monthly review and reporting, if included in the agreed scope |
This is the same groundwork an internal hire needs, so the diagnostic is not wasted either way. No handover takes the business out of social entirely, and this guide makes no promise of saved hours. Ask any provider, and yourself, to write down which tasks are included, which internal people still take part, and how you will measure change against your log.
Map your social media workload. Complete the workload-and-ownership diagnostic above, then bring the results to a conversation about whatever gaps remain. If an ongoing operating gap is still there, our ongoing social media management service and the wider services overview show what a recurring scope covers. If an internal fix closed the gap, that is a good result too.
Frequently Asked Questions
How do we tell whether our problem is capacity or strategy?
First check whether drafts exist. Then compare the active work time in your audit with the hours you actually have. Ready work that exceeds your available hours points to capacity.
No plan and no drafts points to strategy.
The audit and decision tree above walk through both checks.
Our content is ready but posts still don't go out. What is usually wrong?
The likeliest cause is approvals: an unclear approver, feedback split across channels, or no agreed approval turnaround time. Missing content inputs and the lack of a named day-to-day social owner are the other candidates.
Record the request date and the decision date for one delayed item to see which applies.
Can we just drop a platform or buy a scheduling tool instead?
Sometimes, yes. Dropping a platform cuts scope, so it fits when capacity is the constraint and that channel isn't earning its place.
A tool fits when content is ready and publishing is the slow step. It won't supply inputs, approvals, platform-specific adaptation skills or ownership.
Won't explaining everything to an agency take as long as doing it ourselves?
It can, if the task list, approvals and content inputs are undefined.
Documenting them first through a social media workload audit reduces rework. There is no guarantee the total effort will be lower.
How much time does social media still take from us after we outsource?
It depends on what is contracted and what you keep.
Retained work can include supplying offer details and material, making decisions, approving content within the agreed approval turnaround time, and handling anything excluded. No supported figure exists.
Ask the provider to define transferred and retained tasks and how change will be measured.
Do we need to fix our internal process before we hire anyone?
Fix it first when the bottleneck is approvals or ownership. That groundwork is needed either way, including naming a day-to-day social owner.
Hiring or outsourcing can come with or after the fix when recurring capacity or skills remain short.
If you want an outside read on which fix comes first, our social media consulting team reviews workload logs and delayed items with in-house teams.
Key takeaways
"We're busy" covers five constraints: capacity, approvals, content inputs, platform skills and ownership.
Each has a different first fix.
Log active work time and waiting time in separate fields, and never add them together.
Approvals and ownership usually start with an internal change, such as named roles, agreed turnaround times and a day-to-day owner with a backup.
Supplying content inputs stays with the business under any handover.
If your log shows repeated rework on platform-specific adaptation, content production support is one option to compare.
A recurring scope makes sense when your log shows an ongoing gap, most clearly ownership plus capacity. Feeling busy is not enough. If that gap remains after the internal fixes, see our social media management service.

