Most content operations have a calendar and a pile of files, and no connection between them. The calendar says "Tuesday: blog post on pricing." The files are somewhere. Finding the graphic that went with a post from four months ago takes ten minutes, so instead someone makes a new one.
The fix is a single ID that appears in both places.
One ID, two systems
Give every piece of content an ID when it's first an idea:
2025-041Year, then a sequential number. That ID becomes the folder name and the first column of the calendar. Everything else — titles, dates, platforms — can change freely, and the connection holds.
05 Marketing/
Content/
2025/
2025-041 Pricing mistakes post/
2025-042 Client onboarding video/
2025-043 Q2 newsletter/Now the calendar row for 2025-041 and the folder for 2025-041 will always find each other, even after the post gets retitled twice and rescheduled three times.
The calendar: one row per piece, not per platform
The most common structural error is a row for every place a piece will appear — a blog row, a newsletter row, three social rows — for what is fundamentally one thing. That splits the status of a single piece across five rows and makes the calendar impossible to read.
One row per piece. Platforms are columns.
ID | Title | Pillar | Status | Owner | Publish date | Blog | Email | Social | Folder | Notes
2025-041 | 5 pricing mistakes | Pricing | Draft | Dana | 2025-04-22 | ✓ 4/22 | ✓ 4/24 | ✓ 4/22, 4/29 | link |Status with a fixed vocabulary: Idea → Outlined → Drafted → Edited → Assets ready → Scheduled → Live. Fixed words matter because you'll filter on them. Free-text status columns become useless within a month.
Pillar is the theme or topic bucket. This column earns its place at review time: sorting by pillar shows you that you've published nine pieces about one thing and none about another, which is the sort of drift nobody notices in the flow of weekly publishing.
Owner — one named person per piece, even in a one-person business, because you'll eventually hire.
Folder — a direct link to the folder. This one column is what makes the whole system work in practice. If finding the files takes one click, people use the library. If it takes navigation, they don't.
Inside a content folder
Same shape every time:
2025-041 Pricing mistakes post/
01 Draft/
02 Assets/
03 Published/
notes.md01 Draft — the working document, research links, outline.
02 Assets — images, graphics, screenshots, video, audio. Source files and exports.
03 Published — the final text as published, and the final exports for each platform. Keep the published text as a file even though it's live on your site. Sites get redesigned, migrated, and broken; the archive of what you actually said is worth more than the effort of saving it.
notes.md — the piece's own record:
Published: 2025-04-22
URL: [link]
Target keyword: small business pricing mistakes
Repurposed as: newsletter 4/24, 2 social posts, 1 short video (2025-058)
Performance @ 90 days: [fill in]
Update due: 2026-04The Repurposed as line is what stops the same work being redone. The Update due line is what turns evergreen content into an asset rather than a slowly rotting page.
The reusable asset library, separate from pieces
Some assets outlive the piece they were made for: a diagram you keep referencing, a headshot, a product photo, a chart you update quarterly. These shouldn't be buried in one post's folder.
05 Marketing/
Asset Library/
Diagrams/
Screenshots/
Charts/
Video B-roll/
Quote cards/The rule for promotion: if you use an asset a second time, it moves to the library. Not before — pre-emptively organizing a library of things you might reuse produces a folder of things you never did. Second use is the signal.
Name library assets descriptively, since they'll be found by search rather than by folder: diagram-3-2-1-backup-rule-v2.png, not diagram2.png.
Repurposing works better as a plan than as an afterthought
Decide the repurposing at the moment you plan the piece, and put it in the calendar row. A long-form piece typically supports:
- The main piece
- A newsletter version, cut down
- Three to five social posts, each on one point
- One visual asset (a diagram, a chart, a quote card)
- Optionally, a short video or audio version
If you plan those at outline stage, you write the piece so the parts exist — the three points that become three posts are actually separated in the draft. If you decide afterwards, you're excavating.
Give repurposed derivatives their own IDs when they're substantial enough to need their own files, and reference the parent in the notes: Derived from 2025-041.
A backlog that isn't the calendar
Keep ideas somewhere that isn't scheduled. A separate tab, same columns, no dates.
Ideas with dates attached create false pressure and get moved repeatedly; ideas in a backlog get picked when they're ready. The monthly planning move is to promote items from backlog to calendar, which is a much better conversation than looking at an empty week and inventing something.
Log every idea with one line of context on why it's worth doing. In three months you won't remember what "post about the thing clients ask" meant.
The quarterly review
Thirty minutes, once a quarter, and it's the part that turns a calendar into a strategy:
- Fill in performance numbers for pieces past 90 days. Do this in one sitting rather than continuously — content performance is noisy in the short term and legible in the long term.
- Sort by pillar. What's overrepresented? What's neglected?
- Look at your top five performers. What do they have in common? That's your next quarter's plan, and it's better information than any general advice about content.
- Check the update-due column. Evergreen pieces that rank well need refreshing, and updating a piece that already performs beats writing a new one that might not.
- Archive the finished quarter's folders if the year folder is getting unwieldy.
Keep the files, whatever tool you use
Your calendar may live in a spreadsheet, a project tool, or a dedicated content platform — any of them work. The files should still live in your normal drive structure.
Content tools change every few years, and migrations reliably lose attachments. The calendar is a working surface, and losing it costs you a rebuild. The asset library is an archive, and losing it costs you the work itself.
Next in this series: Version Control Without Losing Your Latest Draft