[{"data":1,"prerenderedAt":1084},["ShallowReactive",2],{"blog:\u002Fblog\u002Fsocial-media-approval-process":3,"blog:related:\u002Fblog\u002Fsocial-media-approval-process":286},{"id":4,"title":5,"author":6,"body":7,"date":272,"description":273,"draft":274,"extension":275,"image":276,"meta":277,"navigation":278,"path":279,"seo":280,"stem":281,"tags":282,"updated":276,"__hash__":285},"blog\u002Fblog\u002Fsocial-media-approval-process.md","A social media approval process clients actually follow","SelfSM",{"type":8,"value":9,"toc":259},"minimark",[10,14,17,22,25,32,38,44,50,53,57,60,69,72,76,79,82,88,91,95,98,101,123,131,135,138,141,144,148,151,157,163,166,170,173,176,184,191,195,198,216,219,223,229,235,241,247,253],[11,12,13],"p",{},"Every agency has the same story. The posts were ready Tuesday. The client approved them the following Monday, by which point two were stale and one referenced a webinar that had already happened. Nobody was negligent. The process just had no mechanism for making Tuesday matter.",[11,15,16],{},"Approval gets treated as a courtesy step bolted onto the end of production. It is actually the most fragile part of the operation, because it is the only step that depends on someone who does not work for you and has no deadline.",[18,19,21],"h2",{"id":20},"the-four-ways-approval-breaks","The four ways approval breaks",[11,23,24],{},"Almost every stall is one of these. They have different fixes, and treating all of them as \"the client is slow\" fixes none.",[11,26,27,31],{},[28,29,30],"strong",{},"The client does not know they are the blocker."," They received a link, filed it mentally under \"read later\", and have no sense that anything is waiting. Nothing in the message said what happens if they do nothing.",[11,33,34,37],{},[28,35,36],{},"The client does not know what \"approved\" means."," Are they checking the claim, the tone, the timing, or all three? Is silence consent? Can they edit? An unclear ask gets deferred, because deferring is cheaper than guessing wrong.",[11,39,40,43],{},[28,41,42],{},"Approval is spread across three surfaces."," The draft is in a doc, the comments are in Slack, the sign-off is in email. Nobody can tell what state anything is in without reconstructing it from three histories, so everyone waits for someone else to do the reconstructing.",[11,45,46,49],{},[28,47,48],{},"The wrong person is approving."," A marketing coordinator with no authority over claims is asked to approve a post making a claim. They cannot, so they escalate, and the escalation has no deadline either.",[11,51,52],{},"Only the first of those looks like slowness. The other three look like slowness and are design faults.",[18,54,56],{"id":55},"rule-one-one-surface-one-state","Rule one: one surface, one state",[11,58,59],{},"The highest-leverage change is not a reminder cadence. It is putting the draft, the comments and the decision in the same place, so that \"what is the status of Thursday's post\" is something you look at rather than something you ask.",[11,61,62,63,68],{},"That is the real argument for approval links over email attachments. Not convenience — ",[64,65,67],"a",{"href":66},"\u002Fblog\u002Fcontent-approval-workflow","state",". A post that carries its own status can be counted, filtered and chased. A post whose status lives in someone's inbox cannot.",[11,70,71],{},"If you take one thing from this: stop asking clients to reply in order to approve. A reply creates a second surface immediately.",[18,73,75],{"id":74},"rule-two-name-the-decision-narrow-the-question","Rule two: name the decision, narrow the question",[11,77,78],{},"\"Let me know if you have any thoughts\" is not a request for approval. It is an invitation to an open-ended review, and open-ended reviews are what produce the eleven-comment thread about a comma.",[11,80,81],{},"Ask for a specific decision on a specific scope:",[83,84,85],"blockquote",{},[11,86,87],{},"Three posts for next week. You are checking two things: are the facts right, and is anything commercially sensitive. Tone and structure are ours. Approve, or tell us which one to change.",[11,89,90],{},"That does three jobs. It bounds the review, it tells the client what is not their problem, and it gives them a verb. Clients given a narrow question answer it in minutes. Clients given \"thoughts?\" answer it never.",[18,92,94],{"id":93},"rule-three-a-default-for-silence","Rule three: a default for silence",[11,96,97],{},"Every approval step needs a documented answer to \"what happens if nobody responds by Thursday.\"",[11,99,100],{},"There are three honest defaults, and each is defensible:",[102,103,104,111,117],"ul",{},[105,106,107,110],"li",{},[28,108,109],{},"Hold."," Nothing publishes without explicit approval. Correct for regulated clients, claims-heavy accounts and anything legal has touched. Accept that output will be lumpy.",[105,112,113,116],{},[28,114,115],{},"Publish on silence after N days."," Written into the contract, not assumed. Works when the client has said outright that they trust the editorial line and would rather have volume than veto.",[105,118,119,122],{},[28,120,121],{},"Publish a safe subset."," Evergreen posts go out on silence; anything with a number, a customer name or a comparison holds. This is the option most agencies want and few write down.",[11,124,125,126,130],{},"Which one you pick matters less than that the client agreed to it during ",[64,127,129],{"href":128},"\u002Fblog\u002Fsocial-media-client-onboarding","onboarding",", in writing, before the first stall. A default invented during a stall is a negotiation, and negotiations take longer than the approval would have.",[18,132,134],{"id":133},"rule-four-approve-in-batches-on-a-rhythm","Rule four: approve in batches, on a rhythm",[11,136,137],{},"Ad-hoc requests arrive at random and get treated as interruptions. A standing slot gets treated as work.",[11,139,140],{},"One batch a week — same day, same time, same size — is far more reliable than seven posts arriving individually as they are finished. The client learns that Wednesday morning means twenty minutes of approving. That is a habit. Individual pings are noise, and noise gets muted.",[11,142,143],{},"Batching also makes capacity legible. Nine posts a week approved on Wednesday is a number both sides can plan around. Nine posts approved on scattered days is a permanent low-grade negotiation.",[18,145,147],{"id":146},"rule-five-separate-changes-requested-from-rejected","Rule five: separate \"changes requested\" from \"rejected\"",[11,149,150],{},"Most tools and most agencies collapse these, and they are entirely different events.",[11,152,153,156],{},[28,154,155],{},"Changes requested"," means the post is fine in principle and one thing needs fixing. It should come back with the specific fix, and it should not restart the review from zero.",[11,158,159,162],{},[28,160,161],{},"Rejected"," means the angle is wrong and the post should not exist. That is feedback about strategy, not about a draft, and it belongs in a different conversation than the one about Thursday.",[11,164,165],{},"When both are the same button, every piece of feedback reads as a rejection, writers get defensive, and clients start softening real objections into vague ones to avoid the friction. Two words on one screen prevent a surprising amount of relationship damage.",[18,167,169],{"id":168},"what-the-trail-is-for","What the trail is for",[11,171,172],{},"A recorded approval trail is usually sold as accountability, which makes it sound like a device for blaming clients. It is more useful than that.",[11,174,175],{},"It answers, without anyone reconstructing anything: which posts are waiting, how long each has waited, who was asked, whether they were the right person to ask, and what changed between the draft that was rejected and the one that shipped. That last one is how a writer learns a client's boundaries in six weeks instead of six months.",[11,177,178,179,183],{},"It also matters on the day something goes wrong. When a claim turns out to be false, the difference between an agency that survives it and one that does not is usually whether they can show ",[64,180,182],{"href":181},"\u002Fblog\u002Fwho-is-responsible-for-a-wrong-claim","who approved what"," without a forensic exercise across three tools.",[11,185,186,187,190],{},"That is what ",[64,188,6],{"href":189},"\u002Ffor\u002Fagencies"," is built around: the draft, the approval link, the decision and the reason all sit on the post itself, and the client sees a page rather than a login. Not a novel idea — just rarely all in one place, which is exactly why approvals stall.",[18,192,194],{"id":193},"the-version-to-steal","The version to steal",[11,196,197],{},"If you change one thing this week:",[199,200,201,204,207,210,213],"ol",{},[105,202,203],{},"Send one batch, one day a week, at the same time.",[105,205,206],{},"In the message, name what the client is checking and what they are not.",[105,208,209],{},"Include the deadline and what happens after it.",[105,211,212],{},"Give them a link that carries the decision, not a document that needs a reply.",[105,214,215],{},"Keep \"needs a change\" and \"kill this\" as separate answers.",[11,217,218],{},"None of that requires new software. It requires deciding that approval is a designed step rather than the bit that happens after the real work.",[18,220,222],{"id":221},"faq","FAQ",[11,224,225,228],{},[28,226,227],{},"What is a social media approval process?","\nThe defined sequence a post moves through between being drafted and being published: who reviews it, what exactly they are checking, how they record the decision, what happens on silence, and where the record lives. Without those five things written down it is not a process, it is a habit that works until someone is on holiday.",[11,230,231,234],{},[28,232,233],{},"How long should a client have to approve social media posts?","\nTwo to three working days for a normal batch is realistic for most clients, and worth agreeing in the contract rather than discovering. Shorter windows work only where a named person owns approvals as part of their job. Whatever the window, the default action when it expires matters more than its length.",[11,236,237,240],{},[28,238,239],{},"Should social media posts be approved individually or in batches?","\nBatches, on a fixed weekly slot. Individual requests arrive as interruptions and get deferred; a standing slot becomes a habit. Batching also makes capacity and turnaround measurable instead of anecdotal.",[11,242,243,246],{},[28,244,245],{},"Who should approve social media content at a client company?","\nWhoever has authority over the claims being made — usually a marketing lead, with legal involved only for regulated claims. The common failure is routing approval to a coordinator who cannot approve claims, which turns every post into an escalation with no deadline.",[11,248,249,252],{},[28,250,251],{},"What should happen if a client never responds to an approval request?","\nWhatever you agreed in advance: hold everything, publish after a stated number of days, or publish only the posts carrying no claims, numbers or customer names. All three are defensible. Deciding during the stall is what turns a delay into a conflict.",[11,254,255,258],{},[28,256,257],{},"Is email approval good enough for social media content?","\nIt works for one client and one approver, and stops working at three. Email splits the draft, the discussion and the decision across separate threads, so status becomes something you reconstruct rather than read. The failure is not email itself, it is that nothing carries state.",{"title":260,"searchDepth":261,"depth":261,"links":262},"",2,[263,264,265,266,267,268,269,270,271],{"id":20,"depth":261,"text":21},{"id":55,"depth":261,"text":56},{"id":74,"depth":261,"text":75},{"id":93,"depth":261,"text":94},{"id":133,"depth":261,"text":134},{"id":146,"depth":261,"text":147},{"id":168,"depth":261,"text":169},{"id":193,"depth":261,"text":194},{"id":221,"depth":261,"text":222},"2026-08-25","Why approval stalls have almost nothing to do with lazy clients, the four failure modes that cause them, and how to design a process that survives contact with a busy person.",false,"md",null,{},true,"\u002Fblog\u002Fsocial-media-approval-process",{"title":5,"description":273},"blog\u002Fsocial-media-approval-process",[283,284],"workflow","agencies","lJfhO0TxD4AGVai-dFIUrqeXxyjRclGDz3967R7FjfE",[287,516,803],{"id":288,"title":289,"author":6,"body":290,"date":272,"description":509,"draft":274,"extension":275,"image":276,"meta":510,"navigation":278,"path":511,"seo":512,"stem":513,"tags":514,"updated":276,"__hash__":515},"blog\u002Fblog\u002Fwhite-label-social-media-reporting.md","White-label social media reporting that survives a renewal conversation",{"type":8,"value":291,"toc":500},[292,295,298,302,305,311,317,323,326,330,333,339,349,355,361,367,373,376,380,386,392,398,404,408,411,417,423,429,440,444,447,450,454,457,460,468,470,476,482,488,494],[11,293,294],{},"\"White label\" in most reporting tools means one thing: your logo instead of theirs, and a custom domain if you pay more. That is branding, not reporting, and it does not change the outcome that matters. The client still opens the PDF, scrolls to nothing in particular, and closes it.",[11,296,297],{},"A report earns its cost in one moment: the conversation about whether to keep paying you. Everything else it does is secondary. Most agency reports are not built for that moment at all.",[18,299,301],{"id":300},"what-the-client-is-actually-checking","What the client is actually checking",[11,303,304],{},"When a client opens your report, they are answering one of three questions, and it is almost never the one the report is designed around.",[11,306,307,310],{},[28,308,309],{},"\"Is this working?\""," Meaning: is anything happening that would not have happened otherwise. Not whether impressions went up.",[11,312,313,316],{},[28,314,315],{},"\"Am I exposed?\""," Did anything go out that shouldn't have, is anything unanswered, is there a comment from an angry customer sitting there since Thursday.",[11,318,319,322],{},[28,320,321],{},"\"What do I have to do?\""," Is there a decision waiting on me, and did my not-deciding cost anything.",[11,324,325],{},"A dashboard of platform metrics answers none of these. It answers \"what did the numbers do\", which the client did not ask, and which they cannot act on. That is why engagement charts get skimmed and the follower count gets a glance. It is the only number on the page that feels like a score.",[18,327,329],{"id":328},"what-belongs-in-the-report","What belongs in the report",[11,331,332],{},"Order matters more than content here, because most clients read the first screen and stop.",[11,334,335,338],{},[28,336,337],{},"One paragraph, in words, at the top."," What happened, what it means, what you are doing next. Written for someone who will read only this. If you cannot write it, the month did not have a story and the report will not invent one.",[11,340,341,344,345,348],{},[28,342,343],{},"What shipped, and what didn't."," Posts published against posts planned, with the reason for any gap. Naming a gap you caused builds more trust than hiding it; naming a gap the client caused — four posts held eleven days waiting for approval — is the single most useful line in the whole document, and it belongs there rather than in a tense call. You only have that line if ",[64,346,347],{"href":279},"approvals leave a record","; otherwise it is your word against their memory.",[11,350,351,354],{},[28,352,353],{},"Decisions made and their outcome."," \"We moved to Tuesday\u002FThursday, engagement per post rose, volume held.\" This is the only section that demonstrates judgment, and judgment is what a retainer buys.",[11,356,357,360],{},[28,358,359],{},"Numbers, with a comparison and a denominator."," A number alone is decoration. Against last month, against the previous quarter, or against the account's own baseline, it becomes information. Three or four metrics that connect to the client's actual goal beat twenty that do not.",[11,362,363,366],{},[28,364,365],{},"What needs the client."," Approvals waiting, facts to confirm, decisions pending. Explicit, with dates. This section does more for next month's turnaround than any reminder email.",[11,368,369,372],{},[28,370,371],{},"Next month's plan, in one list."," Short. It is a commitment, so it should be small enough to keep.",[11,374,375],{},"That is a two-page document. Two pages that get read beat twelve that get filed.",[18,377,379],{"id":378},"the-parts-to-cut","The parts to cut",[11,381,382,385],{},[28,383,384],{},"Vanity screenshots."," A grid of your best-performing posts is a portfolio, not a report.",[11,387,388,391],{},[28,389,390],{},"Platform metrics with no line to the goal."," Impressions matter if the goal is reach. If the goal is inbound leads, impressions are context at best and misdirection at worst.",[11,393,394,397],{},[28,395,396],{},"Anything the client cannot act on."," \"Best time to post: 9am\" is either already implemented, in which case say so, or it is an admission you haven't.",[11,399,400,403],{},[28,401,402],{},"Percentages without absolutes."," \"Engagement up 240%\" on a base of five interactions is a sentence that damages your credibility the moment someone checks.",[18,405,407],{"id":406},"where-white-label-actually-matters","Where white-label actually matters",[11,409,410],{},"There are three places where the label genuinely changes the outcome, and none of them is the logo.",[11,412,413,416],{},[28,414,415],{},"The client should not need an account."," The moment a report requires a login, half of the stakeholders never see it. A link that opens to a page is the difference between a report the CMO reads on their phone and a report only your day-to-day contact sees.",[11,418,419,422],{},[28,420,421],{},"The data should be yours, not the platform's story."," Reporting tools present the metrics they can collect most easily, which shapes what your report argues. If a channel has no usable API, and several do not, an honest report says the number was read manually or is unavailable, rather than quietly omitting the channel.",[11,424,425,428],{},[28,426,427],{},"Your process should be visible in it."," A white-labelled dashboard makes you interchangeable with any agency using the same dashboard. A report that shows what was decided and why makes the case that the thinking came from you. That is the actual anti-churn mechanism, and it is invisible in a logo swap.",[11,430,431,432,434,435,439],{},"This is roughly the shape ",[64,433,6],{"href":189}," generates: a client-facing link with what shipped, what is waiting on them and what was decided, on the agency's own framing rather than a platform's default dashboard. The reason it looks unlike a typical reporting tool is that it is built from the approval trail rather than from platform analytics, which also means it knows ",[64,436,438],{"href":437},"\u002Fblog\u002Fagency-roles-for-social-content","who did what"," without anyone logging it separately.",[18,441,443],{"id":442},"cadence","Cadence",[11,445,446],{},"Monthly is right for most retainers. Weekly reports are usually a symptom. The client does not trust that work is happening, and the fix for that is visibility into the pipeline, not more documents. If a client wants weekly, give them a live view of what is drafted, approved and scheduled and keep the report monthly.",[11,448,449],{},"Send it within three working days of month end, always on the same day. A report that arrives on a predictable date gets read. One that arrives when you get to it gets skimmed, because the client has already stopped expecting it.",[18,451,453],{"id":452},"the-renewal-test","The renewal test",[11,455,456],{},"Before sending, read your report and ask: if this client were deciding today whether to renew, does this document help them say yes?",[11,458,459],{},"If the honest answer is \"it shows we were busy\", rewrite the top paragraph. Busy is not the case for renewal. A decision you made, its result, and the thing you are doing next — that is.",[11,461,462,463,467],{},"For the writing side of the same problem, ",[64,464,466],{"href":465},"\u002Fblog\u002Fclient-reporting-that-gets-read","what clients actually read"," covers the report itself. This piece is about the version with your name on it.",[18,469,222],{"id":221},[11,471,472,475],{},[28,473,474],{},"What does white-label social media reporting mean?","\nStrictly, a report delivered under the agency's brand rather than the tool's: logo, colours, sometimes a custom domain. In practice the label is the least important part: what determines whether the report works is whether the client can open it without an account and whether it answers the renewal question.",[11,477,478,481],{},[28,479,480],{},"What should be in an agency social media report?","\nA one-paragraph summary, what shipped against what was planned with reasons for gaps, decisions made and their outcomes, three or four metrics with comparisons, an explicit list of what needs the client, and next month's plan. Two pages is usually enough.",[11,483,484,487],{},[28,485,486],{},"How often should agencies send client reports?","\nMonthly, within three working days of month end, on a consistent date. Requests for weekly reports normally mean the client lacks visibility into work in progress; solve that with a live view of the pipeline rather than by sending four times as many documents.",[11,489,490,493],{},[28,491,492],{},"Should client reports include failures?","\nYes, and specifically the gaps the client caused: posts held waiting on approval, facts never confirmed. Reported neutrally with dates, it is the section that most improves next month's turnaround, and hiding it means the same delay recurs while you absorb the blame for lower output.",[11,495,496,499],{},[28,497,498],{},"Do clients need a login to view a white-label report?","\nThey should not. Any login requirement drops the number of stakeholders who ever see the report, usually to one. A tokenised link that opens directly to a page is what gets a report read by the person who decides on renewal.",{"title":260,"searchDepth":261,"depth":261,"links":501},[502,503,504,505,506,507,508],{"id":300,"depth":261,"text":301},{"id":328,"depth":261,"text":329},{"id":378,"depth":261,"text":379},{"id":406,"depth":261,"text":407},{"id":442,"depth":261,"text":443},{"id":452,"depth":261,"text":453},{"id":221,"depth":261,"text":222},"Most white-label reporting is a logo swap on a dashboard nobody reads. What clients actually check, what belongs in the report, and how to build one that answers the renewal question before it is asked.",{},"\u002Fblog\u002Fwhite-label-social-media-reporting",{"title":289,"description":509},"blog\u002Fwhite-label-social-media-reporting",[284,283],"EzYekyLUGzuj3J4pMiL3BJn_c0Us80YrPhH2-0oScyo",{"id":517,"title":518,"author":6,"body":519,"date":796,"description":797,"draft":274,"extension":275,"image":276,"meta":798,"navigation":278,"path":437,"seo":799,"stem":800,"tags":801,"updated":276,"__hash__":802},"blog\u002Fblog\u002Fagency-roles-for-social-content.md","Agency roles for social content: who drafts, who approves, who releases",{"type":8,"value":520,"toc":787},[521,524,531,535,538,544,550,556,562,569,573,576,582,588,594,601,605,608,675,682,686,689,692,695,709,713,719,725,731,737,741,744,755,757,763,769,775,781],[11,522,523],{},"Small agencies run on one person per account. That person writes, decides, sends to the client and publishes, and it works beautifully right up to the point where they are on holiday, or leave, or make one mistake at scale.",[11,525,526,527,530],{},"The fix is not more process. It is separating four things that are usually one thing: ",[28,528,529],{},"drafting, internal approval, client release, and publishing",". Once they are separate permissions rather than stages in one person's head, juniors can do real work, seniors stop being a bottleneck on every post, and no single mistake reaches a client feed unaccompanied.",[18,532,534],{"id":533},"the-four-permissions","The four permissions",[11,536,537],{},"They are worth naming precisely because most tools and most agencies collapse them into two.",[11,539,540,543],{},[28,541,542],{},"Draft."," Create and edit content. The permission a junior or a freelancer should have on day one, on real accounts. There is no faster way to train someone and no reason to withhold it, because drafting is reversible.",[11,545,546,549],{},[28,547,548],{},"Approve internally."," Assert that this is good enough to show the client: on brand, factually sourced, within scope. This is a quality and risk judgment and it belongs to whoever is accountable for the account, not to whoever wrote it.",[11,551,552,555],{},[28,553,554],{},"Release to client."," Send it out of the agency. Separate from internal approval because it is the moment work becomes visible to someone who is paying, and because the person who should own client communication is often not the person who owns editorial quality.",[11,557,558,561],{},[28,559,560],{},"Publish."," Put it on the account. The narrowest permission, and the one most agencies hand out most casually.",[11,563,564,565,568],{},"The important claim: ",[28,566,567],{},"approve and publish must not be the same permission."," A post can be approved on Tuesday and correct, and publishing it on Thursday can still be wrong because the client announced a layoff on Wednesday. Someone has to own the moment, not just the artefact.",[18,570,572],{"id":571},"the-three-roles-this-produces","The three roles this produces",[11,574,575],{},"Map the permissions onto people and you get a shape that works from three people to thirty.",[11,577,578,581],{},[28,579,580],{},"Writer"," — drafts. Junior, freelancer, or a senior on a client they know well. Has access to that brand's voice definition, fact file and forbidden list, and nothing else. Cannot release, cannot publish.",[11,583,584,587],{},[28,585,586],{},"Account lead"," — approves internally and releases to the client. Accountable for the account: the editorial standard, the factual sourcing, the client relationship. One named person per client, always, including holiday cover assigned in advance.",[11,589,590,593],{},[28,591,592],{},"Publisher"," — publishes on schedule. Often the same person as the account lead in a small agency, and that is fine. What matters is that it is a distinct act with its own check, not a side effect of approval. On larger books this is genuinely a separate role with a daily pre-publish sweep.",[11,595,596,597,600],{},"Plus the client, who approves what the account lead released. That flow is a different problem with its own failure modes — see ",[64,598,599],{"href":66},"the approval workflow that doesn't lose the client",".",[18,602,604],{"id":603},"what-each-stage-actually-checks","What each stage actually checks",[11,606,607],{},"Roles without checks are just job titles. Each gate is looking for something specific, and the specificity is what makes it fast.",[609,610,611,627],"table",{},[612,613,614],"thead",{},[615,616,617,621,624],"tr",{},[618,619,620],"th",{},"Stage",[618,622,623],{},"The question",[618,625,626],{},"Blocks on",[628,629,630,642,653,664],"tbody",{},[615,631,632,636,639],{},[633,634,635],"td",{},"Draft",[633,637,638],{},"Does this say something, in this brand's voice?",[633,640,641],{},"Generic content, wrong register",[615,643,644,647,650],{},[633,645,646],{},"Internal approve",[633,648,649],{},"Is every factual claim sourced and in scope?",[633,651,652],{},"Unsourced numbers, over-generalised claims",[615,654,655,658,661],{},[633,656,657],{},"Release",[633,659,660],{},"Is this the right thing to send this client this week?",[633,662,663],{},"Bad timing, scope creep, tone against context",[615,665,666,669,672],{},[633,667,668],{},"Publish",[633,670,671],{},"Has anything changed since approval?",[633,673,674],{},"News events, client announcements, live incidents",[11,676,677,678,681],{},"The internal approval gate is where ",[64,679,680],{"href":181},"wrong claims"," get caught, and it is the gate most often skipped when the account lead is busy. If one gate has to be defended, defend that one.",[18,683,685],{"id":684},"give-juniors-real-work-not-fake-work","Give juniors real work, not fake work",[11,687,688],{},"The common failure is over-correcting: juniors get research and scheduling, seniors write everything, and the agency has a capacity ceiling equal to its senior headcount plus a training programme that produces nobody.",[11,690,691],{},"A permission model makes the safe version possible. A junior drafting on a live account with no release permission cannot cause an incident, so there is no reason to hold them back from the work that actually teaches — writing in someone else's voice against real constraints and getting edited.",[11,693,694],{},"Two things make this work in practice:",[102,696,697,703],{},[105,698,699,702],{},[28,700,701],{},"Edits go back with reasons."," \"Cut this, it's puffery\" teaches; a silently rewritten draft teaches nothing and is the most common way agencies fail to develop people.",[105,704,705,708],{},[28,706,707],{},"The voice definition and fact file are accessible to the writer."," If the standard lives only in the account lead's head, the junior cannot hit it and the feedback loop is arbitrary. Writing it down is what makes delegation possible at all.",[18,710,712],{"id":711},"where-the-model-breaks","Where the model breaks",[11,714,715,718],{},[28,716,717],{},"One person is every role on eight accounts."," Common, and usually described as being busy. It is a single point of failure with no holiday cover and no second read on any claim. The first fix is not hiring — it is assigning a named second approver per client, even if that person only reads.",[11,720,721,724],{},[28,722,723],{},"The gates exist but everyone has every permission."," Then the model is documentation, not a control. Permissions that are not enforced are conventions, and conventions collapse exactly when the week is bad.",[11,726,727,730],{},[28,728,729],{},"Approval lives in chat."," The gates ran, the record did not. Six weeks later nobody can say who approved what, which is the state you are in during precisely the conversation where it matters. Approvals belong attached to the post.",[11,732,733,736],{},[28,734,735],{},"Nobody owns publish."," So it happens automatically at the scheduled time, including the morning of a client's outage. Automation is fine for the mechanics; someone still has to own the last look.",[18,738,740],{"id":739},"scaling-it-across-a-book","Scaling it across a book",[11,742,743],{},"At three clients the model is a shared understanding. At fifteen it needs to be enforced by something, because the number of people-times-brands combinations exceeds what anyone tracks reliably, and the failure is silent — nobody notices a missing gate until an incident.",[11,745,746,747,749,750,754],{},"What that requires is per-brand scoping rather than agency-wide roles: a writer added to two accounts sees two accounts, and permissions travel with the brand rather than with a job title. That is how ",[64,748,6],{"href":189}," models it — draft, approve and client release are separate per-brand permissions, and every transition is recorded against the post itself, so the trail exists without anyone maintaining it. When ",[64,751,753],{"href":752},"\u002Fblog\u002Fhanding-over-a-social-account","an account changes hands",", that record is most of what makes the handover survivable.",[18,756,222],{"id":221},[11,758,759,762],{},[28,760,761],{},"What roles does an agency need for social media content?","\nAt minimum three: a writer who drafts, an account lead who approves internally and releases to the client, and someone who owns publishing. In small agencies the last two are the same person, but they should remain distinct acts with distinct checks.",[11,764,765,768],{},[28,766,767],{},"Should approval and publishing be the same permission?","\nNo. A post can be approved and correct on Tuesday and wrong to publish on Thursday because circumstances changed. Someone has to own the moment of publishing, not just the approval of the artefact.",[11,770,771,774],{},[28,772,773],{},"Can juniors draft on live client accounts?","\nYes, and they should. Drafting is reversible and it is the only thing that actually trains someone. What juniors should not have is release or publish permission — that separation is what makes real delegation safe.",[11,776,777,780],{},[28,778,779],{},"How do you stop client approvals from living in Slack?","\nAttach approvals to the post rather than to a conversation. The gate running is not enough; if the record is in chat, nobody can reconstruct who approved what six weeks later, which is exactly when it is asked.",[11,782,783,786],{},[28,784,785],{},"How many approvers should a client have?","\nOne named approver with a defined tiebreak, plus assigned cover for absence. Two peers who can both comment and disagree with no stated precedence is the most common cause of stalled approvals.",{"title":260,"searchDepth":261,"depth":261,"links":788},[789,790,791,792,793,794,795],{"id":533,"depth":261,"text":534},{"id":571,"depth":261,"text":572},{"id":603,"depth":261,"text":604},{"id":684,"depth":261,"text":685},{"id":711,"depth":261,"text":712},{"id":739,"depth":261,"text":740},{"id":221,"depth":261,"text":222},"2026-08-19","The three-role split that lets juniors do real work without release risk, why approval and release are different permissions, and how to scale it across a book of clients.",{},{"title":518,"description":797},"blog\u002Fagency-roles-for-social-content",[284,283],"eyiBKklu-EKdbjB8AgAXGqewqg7Cmv5JK7FEY6Z0SsY",{"id":804,"title":805,"author":6,"body":806,"date":796,"description":1078,"draft":274,"extension":275,"image":276,"meta":1079,"navigation":278,"path":465,"seo":1080,"stem":1081,"tags":1082,"updated":276,"__hash__":1083},"blog\u002Fblog\u002Fclient-reporting-that-gets-read.md","The client report that actually gets read",{"type":8,"value":807,"toc":1069},[808,811,814,817,821,827,830,835,838,842,845,851,857,863,869,875,879,882,887,919,924,950,954,957,960,966,972,978,985,989,995,1001,1007,1011,1014,1021,1027,1029,1035,1041,1047,1053,1059],[11,809,810],{},"The monthly report is the most-produced and least-read artefact in social media work. Twelve slides of charts, an impressions number nobody can act on, and a client who skims for the one line that says whether this is working.",[11,812,813],{},"That skim is the whole document. Everything else is you demonstrating effort, which is a bad thing to be paid for and a worse thing to be judged on. A report is not evidence of work; it is an instrument for making the next month's decisions.",[11,815,816],{},"Here is the version that gets read, and the parts to delete.",[18,818,820],{"id":819},"start-with-the-answer","Start with the answer",[11,822,823,824],{},"The first line of the report answers the question the client actually has: ",[28,825,826],{},"is this working, and what are we changing?",[11,828,829],{},"Not \"here's what we did in March.\" Something like:",[83,831,832],{},[11,833,834],{},"March: the customer-story posts outperformed everything else by a wide margin, so April shifts to two of those a month and drops the industry-commentary slot. One post drove 14 profile visits and 3 inbound messages — the highest of the year.",[11,836,837],{},"Everything after that first paragraph is support for a claim already made. If a client reads only the top of the page, they have the answer, and they will trust the rest more for not having to hunt for it.",[18,839,841],{"id":840},"the-one-page-structure","The one-page structure",[11,843,844],{},"Five blocks, one page, same order every month. Consistency matters more than completeness — a report whose shape changes each month cannot be compared with the last one, which is most of what a report is for.",[11,846,847,850],{},[28,848,849],{},"1. The verdict."," Two or three sentences. Working, not working, what changes.",[11,852,853,856],{},[28,854,855],{},"2. What went out."," Volume and mix, stated plainly. \"11 posts: 4 customer stories, 3 product, 2 opinion, 2 hiring.\" This is the only place effort belongs, and one line is enough.",[11,858,859,862],{},[28,860,861],{},"3. What worked, with the actual post."," Not a chart — the top two posts, embedded or quoted, with one sentence on why you think each landed. Clients engage with their own content far more than with any metric about it, and \"why it landed\" is the part they cannot get from a dashboard.",[11,864,865,868],{},[28,866,867],{},"4. What did not, and the hypothesis."," The block most people delete, and the one that builds the most trust. A named underperformer with a specific reading — \"the two product posts led with the feature rather than the problem\" — proves you are reading results rather than collecting them.",[11,870,871,874],{},[28,872,873],{},"5. Next month, and what you need."," Three to five bullets of what you will do, plus an explicit list of what you need from them and by when. This is where the report stops being a rearview mirror and starts causing something.",[18,876,878],{"id":877},"which-metrics-to-keep","Which metrics to keep",[11,880,881],{},"Report metrics the client can act on and that are plausibly caused by the work.",[11,883,884],{},[28,885,886],{},"Keep:",[102,888,889,895,901,907,913],{},[105,890,891,894],{},[28,892,893],{},"Reach or impressions",", as context only, one number, no chart.",[105,896,897,900],{},[28,898,899],{},"Engagement rate",", because it is comparable across post sizes in a way raw likes are not.",[105,902,903,906],{},[28,904,905],{},"Profile visits and follows from content"," — the nearest honest proxy for \"people wanted more.\"",[105,908,909,912],{},[28,910,911],{},"Anything countable that touches pipeline:"," inbound messages, demo requests, link clicks to the page that matters, applications for an open role.",[105,914,915,918],{},[28,916,917],{},"A qualitative line."," Who engaged, not how many. \"Two heads of engineering at target accounts commented\" outranks a thousand impressions and no report format captures it automatically.",[11,920,921],{},[28,922,923],{},"Drop:",[102,925,926,932,938,944],{},[105,927,928,931],{},[28,929,930],{},"Follower count as a headline."," It moves slowly, it is easy to game and it rarely causes anything.",[105,933,934,937],{},[28,935,936],{},"Every chart with fewer than three months of data."," Two points is not a trend; presenting it as one trains the client to over-react to noise.",[105,939,940,943],{},[28,941,942],{},"Platform-native \"engagement scores.\""," Different definitions per platform and not comparable.",[105,945,946,949],{},[28,947,948],{},"Anything you cannot explain the cause of."," If you cannot say why it moved, it is decoration.",[18,951,953],{"id":952},"reporting-a-bad-month","Reporting a bad month",[11,955,956],{},"Every account has them, and how you report the third bad month determines whether there is a fourth.",[11,958,959],{},"Three rules:",[11,961,962,965],{},[28,963,964],{},"Say it in the first line."," Burying a bad month in slide nine reads as concealment when it is discovered, and it always is. Leading with it reads as control.",[11,967,968,971],{},[28,969,970],{},"Distinguish the two kinds of bad."," \"The content underperformed\" and \"we published four posts instead of eleven because material never arrived\" are entirely different problems with different owners. Conflating them is either taking blame you do not deserve or hiding a dependency that needs fixing. Say which one it was, without editorialising.",[11,973,974,977],{},[28,975,976],{},"Bring a change, not a reassurance."," \"We'll keep at it\" is what a client hears as nothing. One specific alteration, with what you expect it to do, is what keeps the next month funded.",[11,979,980,981,984],{},"The failure mode worth naming: smoothing a bad month by finding a metric that happened to go up. Everyone can tell, and it costs more credibility than the bad month did. If the data is thin, say the data is thin — ",[64,982,983],{"href":189},"honest measurement"," survives a quarter of noise far better than a curated one does.",[18,986,988],{"id":987},"frequency-and-format","Frequency and format",[11,990,991,994],{},[28,992,993],{},"Monthly, not weekly."," Weekly reporting on social is mostly noise and turns into a treadmill that consumes bucket-four time you are not being paid for.",[11,996,997,1000],{},[28,998,999],{},"One page, in the body of an email or a shared doc."," Not a PDF attachment, not a slide deck, not a dashboard link. The report should be readable on a phone in ninety seconds without a login. Dashboards fail as reports for one reason: a dashboard shows numbers, and a report makes an argument.",[11,1002,1003,1006],{},[28,1004,1005],{},"Quarterly, go longer."," Once every three months there is enough data for an actual trend, and that is the meeting where you discuss strategy, scope and rate. The monthly one-pager is not the place for that conversation.",[18,1008,1010],{"id":1009},"the-compounding-benefit","The compounding benefit",[11,1012,1013],{},"There is a second reason to write reports this way, and it shows up months later.",[11,1015,1016,1017,1020],{},"A year of one-page reports that each name a hypothesis and a result is an argument for your rate that no proposal can match. It is also the record that settles disagreements about what was agreed, which is the same reason ",[64,1018,1019],{"href":66},"approvals need a trail",". Reports written as decisions accumulate into evidence; reports written as dashboards accumulate into nothing.",[11,1022,1023,1024,1026],{},"Across a book of clients this is exactly the part that decays under load — the fifth client's report gets written at 11pm and quietly becomes a metrics dump. ",[64,1025,6],{"href":189}," keeps what was published, what was approved and what it produced attached to each brand, so the monthly report is assembled from a record rather than reconstructed from memory.",[18,1028,222],{"id":221},[11,1030,1031,1034],{},[28,1032,1033],{},"What should be in a social media report for a client?","\nA verdict in the first two sentences, what went out, the top posts with why they worked, what underperformed and your hypothesis, and next month's plan with what you need from the client. One page, same structure every month.",[11,1036,1037,1040],{},[28,1038,1039],{},"Which social media metrics actually matter to clients?","\nEngagement rate, profile visits and follows from content, and anything countable that touches pipeline — inbound messages, demo requests, relevant link clicks. Follower count and raw impressions are context at best and misleading as headlines.",[11,1042,1043,1046],{},[28,1044,1045],{},"How often should I report to a social media client?","\nMonthly for the one-pager, quarterly for the longer strategic review. Weekly reporting on social is mostly noise and consumes unbilled time without improving decisions.",[11,1048,1049,1052],{},[28,1050,1051],{},"How do I tell a client a month went badly?","\nIn the first line, distinguishing content that underperformed from work that could not happen because material never arrived, and paired with one specific change you are making. Burying it reads as concealment; leading with it reads as control.",[11,1054,1055,1058],{},[28,1056,1057],{},"Should I send a dashboard link instead of a report?","\nNo. A dashboard shows numbers; a report makes an argument about what to do next. Clients who receive dashboard links stop opening them within about two months.",[11,1060,1061,1064,1065,1068],{},[28,1062,1063],{},"What about reports going out under the agency's own brand?","\nSame structure, plus two things the logo swap does not give you: the client must be able to open it without an account, and your reasoning has to be visible in it. ",[64,1066,1067],{"href":511},"White-label reporting"," covers the difference.",{"title":260,"searchDepth":261,"depth":261,"links":1070},[1071,1072,1073,1074,1075,1076,1077],{"id":819,"depth":261,"text":820},{"id":840,"depth":261,"text":841},{"id":877,"depth":261,"text":878},{"id":952,"depth":261,"text":953},{"id":987,"depth":261,"text":988},{"id":1009,"depth":261,"text":1010},{"id":221,"depth":261,"text":222},"Most social media reports are dashboards nobody opens. A one-page structure built around decisions, which metrics to drop, and how to report a bad month without losing the account.",{},{"title":805,"description":1078},"blog\u002Fclient-reporting-that-gets-read",[283,284],"WZEBzJQKRUXqNCXuiO-elAtcvy4JqtHdwbCjo_36foA",1787652584732]