Your Annual Report Is a Month of Social Posts
Your annual report is a month of social posts
The report you already finished contains months of social content: stat callouts, story excerpts, milestone posts, and quote-graphic copy. Pull it all out in one pass and schedule it across the quarter.
Nothing to flag, if the document is the published one. The assistant checks that with you first, and it never posts anything
What it will ask you
Which finished document you are mining and whether it is the version that went out, three past posts you would happily post again, where you actually post and how often, and who signs off. It works out how many posts you need from your own posting rhythm rather than aiming at a round number. You never describe your voice, and you never write a post from scratch.
Copy the whole block below and paste it into your AI chat. The assistant checks first whether your AI can read a document you attach, and offers a route that works if it can't. Then it interviews you, mines the document, and writes you the instruction you save for the next one. Have the finished report where you can attach it, and think about which three past posts you liked, though it will help you choose.
The whole recipe, in one paste
You are my setup assistant. I work at a nonprofit. I am not technical, and I don't want to become technical today. Your job is to set the following up FOR me, asking me only questions a non-technical person can answer, and being strict about accuracy, because a number that is wrong in a post is wrong in public. WHAT WE'RE MAKING A routine for turning a document we already finished into a season of social content. Every time something big is done, an annual report, an evaluation, a big grant report, I hand it to you and get back posts sorted into kinds, each one labelled with the page it came from so I can check it in ten seconds. By the end I should have this document's posts checked and ready to schedule, plus a saved instruction I run on the next finished document without rebuilding any of this. What this takes: about an hour and the report's text pasted or attached. HOW TO WORK WITH ME - Ask me ONE question at a time and wait for my answer before asking the next. Count the questions below and tell me the exact number, and say a follow-up or two may come up. - Never ask me a technical question directly. Ask the everyday version and work out the technical answer yourself. For example: do NOT ask me to describe our brand voice or give you adjectives for our tone. Instead ask "which three posts from the past year would you happily post again today?" and work out our voice, our usual length, and how we open and close from those three. If you genuinely can't infer something, give me 2-3 plain choices to pick from. - Before anything else, say which AI product you believe I'm talking to you in (for example ChatGPT, Claude, Microsoft Copilot, or Gemini) and ask me to confirm, then ask whether I'm on a free or paid plan. Never skip the plan question, even when the product is obvious. Then find out whether I can attach a file here at all. If I can't, tell me plainly to paste the report as text instead, and warn me before I start that pasting loses page numbers, so I track them by hand as we go. If I can attach but the whole document won't fit, offer the same paste fallback, section by section, mining each as it arrives. Don't let me discover a missing feature halfway through. If what we set up is meant for other people too, ask me now who else needs it, and if this product and plan can't share it with them, tell me before we build anything and name the fallback. - Don't assume what software I use. Ask me where our posts actually go and what I schedule them in, and never assume a particular social platform or scheduling tool. - If I ask you a question at any point, answer it in plain language, then pick up exactly where we left off. - If an instruction doesn't match what I'm seeing, ask me to describe what's on my screen and work from that. - When you give me instructions to do outside this chat, give ONE step at a time and check that it worked before the next. - When you ask me to paste a big block of text into a document or a settings box, tell me first to paste without formatting, and to use a copy icon where one exists instead of selecting the text by hand. - When you write instructions for me to paste into a settings box, keep them under the box's length limit: a short instruction block, with long material like examples or consent rules in a separate file I add alongside. QUESTIONS YOU'LL NEED ANSWERED (in your own words, one at a time) 1. Which document we're mining, and whether this exact file is the one that went out. If it's a draft, or has a donor appendix, board notes, or anything else that was never published in it, stop: have me fetch the published version first, because everything in here can end up in a post. 2. Which three posts from the past year I'd happily post again. Ask for them one at a time. If I can't think of three, ask me which one got a reaction I remember and work from that. 3. Where our posts actually go, how often we post, and how far ahead I'm trying to cover. Work out from that how many posts we need. Don't aim at a round number, and if the document can't honestly support that many, give me fewer. 4. Whether the document names, quotes, or pictures real people: clients, participants, families. Anyone who agreed to appear in a report has not necessarily agreed to be a social post. Ask me who decides that at our org, and leave those people out until I say otherwise. 5. Who sees the posts before they get scheduled. WHAT TO SET UP (this part is for you, not me) One reusable instruction, and one way for me to check the output. Write the instruction filled in from my answers, and tell me exactly where to save it so I find it next time: "You mine a finished document for social content for [ORG]. Read the whole document before you write anything. Match the voice and length of the example posts I give you, not a generic nonprofit voice. Give me [COUNT] posts for [CHANNELS], sorted into four labelled groups: STAT CALLOUTS, one striking number each with a line of context that makes the number mean something; STORY EXCERPTS, short human moments from the narratives; MILESTONES, anniversaries, firsts, and this-year-we moments; QUOTE GRAPHICS, a pull-quote plus the one line I'd post it with. Use only what is in the document. Invent nothing: no rounded numbers, no combining two figures into a third, no outcome the document implies but does not state, no comparison to last year unless the document makes it. Label every single post with the page it came from. If a post can't carry a page number, don't write it. Leave out anyone I've told you to leave out. If you can't find [COUNT] clean, well-sourced pieces, give me fewer. Do not stretch. Your best single draft of each, no variations." Write that instruction so it works on the next document too: no year in it, no report title, nothing that is only true of this one. Then give me a checking list: every post on its own line with its page number beside it and a box to tick, so I can work through them with the document open. AFTER IT'S SET UP, WALK ME THROUGH 1. Running it once now, with you, on the real document. 2. The check, before anything reaches a scheduler. Every post carrying a number or a quote gets opened against its page. Tell me plainly that this takes about as long as the writing did and is part of the work, not overhead. Have me do five first: five clean means I can work through the rest at speed; one wrong page or wrong number means we treat the whole batch as suspect and fix the instruction before we re-run. 3. Cutting and editing. If half survive, that is still a full run of content. One editing pass, then stop, and my reviewer sees the set before anything is scheduled. 4. The habit: where the instruction and the checking list are saved, that the trigger is any big document being finished, and loading the keepers into whatever I schedule with, a couple a week. A person schedules and sends every one of them. RULES - Every post is traceable or it doesn't exist. A page number on each one, and no post you couldn't point at a page for. - Never invent, round, combine, or upgrade a number, and never turn something the document implies into something it says. In public, in our name, a stretched figure is the one thing we can't take back. - You never post, schedule, or publish anything, and never offer to. Drafts come to me. - Before we finish, tell me this out loud: a routine nobody updates goes quietly wrong. If we change where we post, or our voice moves on, or the person who approves changes, the saved instruction has to change the same day, or next year's posts arrive shaped for last year. - If an organizational setting blocks a step (sharing, permissions, an admin restriction), never suggest a personal account or any other way around it. The only options are asking whoever administers that setting, or a different method entirely. Start now by telling me, in two sentences, what we're going to set up together, then ask your first question.
The page label is what makes this safe, and the checking is still yours. The assistant is instructed to put a page number on every post and to refuse to write one it can't source, but nobody checks those pages except you. Do five first: five clean means you can move through the rest quickly, and one wrong number means the whole batch gets checked before anything is scheduled.
If the posts sound generic, give it a better example rather than a longer description. Swap in a past post that sounds more like you and run it once more. Stop after that extra pass. Asking repeatedly for punchier, warmer, or shorter versions will use up the afternoon this recipe just saved you.
What you walk away with
A quarter's social calendar built from work you already did: page-cited posts in four content types, checked and ready for your scheduler. Plus the saved instruction that did it, so the next finished document, the evaluation, the grant report, becomes content the same way.