Social media manager portfolio for creator agencies

Define what each case is supposed to prove Choose cases for different decisions rather than collecting screenshots of the same result. One can show a dependable publishing batch, another a careful community escalation, another an account incident and another a weekly report. Together they show how you handle the work before, during and after publication.

Start each case with the context you are allowed to share, the dates, your exact responsibility and the permission basis for including it. State what you did not own when that matters to attribution. If an editor changed the video and a marketer changed the plan, explain their contributions rather than allowing the reader to assume every decision was yours.

A simple contents page can list the skill, case title, evidence type and limitation. This helps a reviewer find relevant material quickly. A short, readable case with a clear decision is more useful than a large archive requiring access requests, unexplained dashboards and guesses about which parts belong to the applicant.

Use account links without revealing private relationships An account may be public while the management relationship remains confidential. Ask for permission before identifying the account as client work. Save the agreed sharing scope and respect it. An authorized public link does not automatically authorize disclosing private results, internal approvals or the names of other people who worked on the account.

Bunny’s application requires account links. Prepare links you are allowed to share and describe your contribution without identifying real creators in narrative examples. If you cannot share a previous client account, explain that limitation to the hiring team. Do not publish a private link, disclose credentials or claim another person’s account to satisfy a form field.

Check the reviewer’s access path. A public portfolio should not ask for account login or require membership in a private workspace. Remove expiring share links, personal email addresses and unnecessary file permissions. Open the portfolio from a separate browser session before sending it so you can see what the reviewer will actually encounter.

Show the publishing workflow with one complete example A workflow case can follow a fictional SFW clip from editor delivery to verified publication. Include the clip identifier, version, approved caption, cover choice, platform, timezone, approval owner and final state. Explain which checks you performed and what would have caused a hold. A calendar screenshot alone cannot show those decision points.

Add an exception. Perhaps the scheduled upload timed out and you checked the native account before retrying. Explain how you avoided a duplicate and who received the handover. If the case is real, anonymize and share only authorized details. If reconstructed, label the reconstruction and avoid implying that its invented outcome is a historical fact.

Provide a small handover sample: completed items, held items, incident status, next owner and next check. Show that a colleague can continue without your private notes or a live call. This is evidence of multi-account readiness because consistency and transferability matter more than the number of tabs visible in a screenshot.

Present metrics with baselines and limits Every result needs a defined period, metric and denominator. Distinguish reach from impressions, profile visits from unique visitors and measured clicks from verified downstream actions. State whether the source was native analytics, a scheduler or another permitted reporting system. If definitions changed during the case, explain why comparison is limited.

For a fictional illustration, a portfolio could show twelve planned posts and ten published posts, giving 83.3% completion. The case should explain the missing work and response. It should not imply that completion alone measures content quality, nor claim that every held post was a mistake. A deliberate rights hold can be the correct operational decision.

Avoid before-and-after causality claims without supporting evidence. If several changes occurred together, describe association and your contribution. A strong reflection might say that publishing errors fell after introducing a checklist while audience outcomes remained inconclusive. Honest uncertainty lets a reviewer assess your judgment instead of spending the interview untangling an exaggerated claim.

Include community and account-health examples safely Community samples should be fictional or reconstructed with explicit permission and no private details. Demonstrate an ordinary question, a complaint and a situation requiring escalation. Explain the approved voice and why a response stays within scope. Do not include explicit fan messages or use a real person’s vulnerability as portfolio material.

An account-health case can show an incident timeline without private account identifiers. Describe the observed notice or failure, the immediate hold, the owner, the official support route and the prevention step. If reach changed without a confirmed restriction, say that. Do not call every decline a shadowban or imply that an appeal caused a later recovery without evidence.

For each sample, include the decision you would refuse: unsolicited mass messaging, concealed adult destinations, purchased engagement or replacement accounts used to evade restrictions. Keep the explanation operational and specific. The reader needs to see how your process handles a difficult request, not a generic paragraph claiming that you value professionalism.

Make the final package easy to review Use a brief introduction, a contents list, a few focused cases and contact information appropriate for the application. Add readable captions to evidence and descriptive link labels. Use text that remains understandable if the reviewer cannot open an image. Avoid oversized files, decorative animations and dashboards that expose information unrelated to the skill being assessed.

Perform a privacy review before sending. Search for names, handles, email addresses, tokens, private URLs, account IDs, recovery information and message screenshots. Check file metadata and sharing permissions. Remove anything you cannot justify sharing. Keep the unredacted originals in the authorized business system, not in a public portfolio folder.

End with what you learned and what you would verify in a new role. For example, ask how the agency defines approval, who owns incidents and how portfolio size is agreed. A portfolio is evidence for a conversation, not a promise of guaranteed growth. Update it when the underlying facts or sharing permissions change.

Related execution guides

• A workflow for multiple creator accounts
• Account health, strikes and appeals
• Social analytics and a weekly report template