# Plan what to post each week from real work Version 1.1 ยท Kramaniti Kosh > How to use this file: fill in the Working template section below. It opens in any text editor, or you can paste the whole file into ChatGPT, Claude or Gemini and ask it to help you fill it in for your business. ## Intended outcome A short weekly plan for Instagram, LinkedIn or WhatsApp status where every post starts from something the business actually did that week. AI can turn your notes into drafts, but each post points back to a real job and an approved fact, and a named person approves anything that makes a claim or mentions a customer before it goes out. ## Before you begin - Where you post and roughly how often you can keep it up without strain - A simple way to collect notes from the week's work, such as a WhatsApp group with yourself or a shared sheet - Your approved facts: services, prices you are happy to show, areas you cover, things you never claim - Written permission from any customer before you use their name, photos, event or words - One person who approves posts, and a backup for weeks they are away ## How to use 1. Through the week, whoever does the work drops a line in the notes: what happened, a photo if the customer agreed, and anything a customer asked or said. One line is enough. 2. On a fixed day, pick three to five notes that would help a future customer understand what you do or decide whether to call you. Fill in one row per post below. AI can write the first draft from the note and your approved facts. 3. The approver reads every draft against its note. Any post with a claim, a number, a price or a customer mention needs their yes before it is scheduled. Anything nobody can back up is cut or rewritten, not posted and fixed later. ## Working template ## Business and people Business: What you do and for whom (one line): Where you post (Instagram, LinkedIn, WhatsApp status, Google Business Profile, other): How many posts a week you can keep up: Person who collects the week's notes: Person who approves posts: Backup approver: ## Approved facts to draw from Only these can appear in a post as fact. Anything else needs the approver's yes first. - What we do: - Areas or cities we cover: - Prices or starting prices we are happy to show (or "not shown"): - Things we never claim (for example "best", "cheapest", guaranteed results): - Words we use for our work, and words we avoid: ## Notes from this week's work One line per thing that happened. Leave out phone numbers, addresses and anything private. - Date: - What happened (a job finished, a problem solved, a question a customer asked, a behind-the-scenes step): - Who did it: - Customer mentioned? (no / yes, permission on file / yes, permission not yet asked): - Photo or video available, and does the customer agree to it being shown: ## This week's posts Copy this block for each post. - Post day and channel: - Starts from which note: - What a future customer should take away (one line): - Draft (written by a person, or by AI from the note and approved facts): - Claims or numbers in the draft, and where each one comes from: - Customer mention or photo, and the permission for it: - Approved by and date: - Status (draft / approved / posted / cut): ## Rules for AI drafts AI may: - Turn a note into a short draft in the business's usual tone - Suggest a caption, a question to ask readers, or a simpler way to say something AI may not: - Add facts, numbers, prices, results or customer names that are not in the note or the approved facts - Write customer quotes or reviews, or reword a real one so it says more than the customer said - Describe a photo as showing something it does not show - Claim the business is the best, the cheapest, or certain to get a result ## Stop rules - No permission on file means no customer name, face, event detail or quote in the post. - If a draft has a claim nobody can point to a note or approved fact for, cut the claim or cut the post. - If the approver and the backup are both away, nothing new goes out that week. Missing a week is fine. - A complaint, a refund or a dispute is never turned into a post, even with the details changed. ## Owner and review Plan owner: Once a month, look back at what was posted: which posts brought questions or enquiries, which notes were never used, and whether any post said more than the work could back up. Change the plan, not just the captions. ## Demonstration This is an illustrative scenario, not a client case study or a measured result. Do not reuse its details as facts about your work. A sample boutique wedding and event planner in Bengaluru, run by two partners with a small team, posts on Instagram and WhatsApp status. Posting has been patchy: a burst before the wedding season, then weeks of nothing, and some captions written by a freelancer promised things the team does not actually do. ### Sample inputs Demonstration inputs only. Notes from one week: a mehendi setup finished on a rainy afternoon after moving it indoors at short notice; a couple asked how early they should book a venue; the team tested a new flower supplier for a small engagement. Approved facts: the cities and kinds of events they plan, and that they do not publish prices. One couple has given written permission for photos without names; the others have not been asked. ### Example output #### This week's plan [Fact within this demonstration] Post 1 (Instagram): the rainy-day mehendi move, told as the steps the team took, using the photos the couple agreed to and no names. [Fact within this demonstration] Post 2 (WhatsApp status): a plain answer to "how early should we book a venue", written from the partners' own advice, with no promise about availability. [Fact within this demonstration] Cut: the flower supplier test, because the result is not known yet and the engagement couple has not been asked about photos. #### What the approver changed [Inference] The AI draft for post 1 said the team "never lets weather ruin a wedding". The partner cut that line because no one can promise it, and kept the factual description of what was done that day. #### Next step [Recommendation] Ask for photo permission at the booking stage instead of after the event, and add "we do not publish prices" to the AI's instructions so it stops suggesting price posts. This recommendation is not the business's decision. ## Quality check Every post points to a note from real work; every claim, number or price comes from a note or the approved facts; every customer name, photo or quote has permission on file; a named person approved each post with a claim or customer mention before it went out; nothing was posted from a complaint or dispute. ## Limits and human review The template helps you post about real work without overstating it; it does not grow your following, guarantee enquiries or tell you what will perform well on any platform. It does not replace a proper consent form or legal advice on using customer images and details; take that to a qualified adviser. Keep the final call on every claim and every customer mention with a named person. ## Edition notes New in Kosh at version 1.1. Provider-neutral Markdown instructions; no installation or platform compatibility is implied. Runtime behaviour has not been verified across AI providers or social platforms. Reuse terms have not yet been published. Background reading: [The Content Calendar Needs a Source Route](/insights/the-content-calendar-needs-a-source-route/), on starting a content plan from real operating signals, and [Route the Claim Before You Polish the Message](/insights/route-the-claim-before-you-polish-the-message/), on checking what a message promises before it is published. Keeping posts, messaging and the systems behind them steady month after month is part of Kramaniti's [Complete Lifecycle Retainer](/retainer/).