# Workshop Ledger: five-piece weekly content plan

SkillPick-authored editorial application, 2026-11-10. Fictional exercise using weekly-content-brief.md only. Drafts for 16–20 November 2026; not a record of publishing or event delivery. Primary strategy: content repurposing. Every CTA uses an unresolved placeholder and must not be posted as-is.

## Monday 16 November — Start with the session list

Audience: independent ceramics-studio coordinators. Goal: explain the prototype's narrow job. Channel: owned-blog introduction. Angle: one list before a booking workflow. Owner: writer. Review: editor checks scope and avoids implied automation. Budget: 70 minutes including review. Facts: F1, F2, F3, F5.

### Draft copy

Planning an adult beginner workshop starts with a few concrete details: a title, a date and a capacity. Workshop Ledger is a fictional early-stage SaaS prototype for independent ceramics-studio coordinators. Its session list lets a coordinator enter those three details and export the list as CSV.

That is the scope of this prototype. It does not take ticket payments or participant bookings, connect to other tools, or send automated reminders. If you need those functions, the session list alone will not cover that workflow. The demo outline is the next place to inspect what the prototype is intended to show.

Read the demo outline: [DEMO_LINK_PENDING]

## Tuesday 17 November — Three fields, one limited prototype

Audience: coordinators browsing professional social feeds. Goal: make the core explanation easy to scan. Channel: professional-social text draft. Angle: adapt Monday's scope into a short checklist. Owner: writer. Review: editor verifies every capability and limitation. Budget: 40 minutes including review. Facts: F1, F2, F3, F5.

### Draft copy

A workshop title. A date. A capacity.

Those are the session details you can enter in Workshop Ledger, a fictional early-stage prototype for independent ceramics-studio coordinators. You can export the session list as CSV. Payments, participant booking, integrations and automated reminders are outside its scope.

Read the demo outline: [DEMO_LINK_PENDING]

## Wednesday 18 November — What the walkthrough covers

Audience: opted-in coordinators who asked for product information. Goal: set expectations before the fictional walkthrough. Channel: opt-in email draft; no email is actually sent. Angle: expand Monday's explanation into a practical agenda. Owner: writer. Review: editor checks date, UTC timezone, duration and consent assumption. Budget: 50 minutes including review. Facts: F1, F2, F3, F4, F5.

### Draft copy

Subject: A look at session entry and CSV export

The fictional Workshop Ledger product walkthrough is Thursday 19 November 2026 at 16:00 UTC. This free online session lasts 30 minutes and demonstrates entering a workshop title, date and capacity, then exporting the session list as CSV. There is time for questions.

This is a product demonstration, not a pottery lesson. The prototype does not include ticket payments, participant booking, integrations or automated reminders. Read the outline to decide whether its limited scope matches what you want to explore.

Read the demo outline: [DEMO_LINK_PENDING]

## Thursday 19 November — Before the fictional walkthrough

Audience: opted-in coordinators reviewing the outline. Goal: restate accurate logistics before the planned event time. Channel: pre-event reminder draft. Angle: time, purpose, limitations. Owner: writer. Review: editor must confirm event status and a real destination before any use. Budget: 35 minutes including review. Facts: F2, F3, F4, F5.

### Draft copy

The fictional Workshop Ledger walkthrough is planned for today, Thursday 19 November 2026, at 16:00 UTC: 30 minutes online, free to attend. It covers session entry, CSV export and questions. It is a product demonstration, not a pottery lesson. Payments and participant booking are not included in the prototype.

Read the demo outline: [DEMO_LINK_PENDING]

## Friday 20 November — Check the CSV scope

Audience: coordinators comparing the prototype with their session-list needs. Goal: offer an evergreen evaluation checklist. Channel: owned-blog checklist draft. Angle: practical questions without inventing an event recap. Owner: writer. Review: editor checks that questions do not imply unapproved features. Budget: 45 minutes including review. Facts: F1, F2, F3, F5.

### Draft copy

Before you use a session-list prototype, write down what you need to record. Workshop Ledger's fictional prototype covers workshop title, date and capacity, with a CSV export.

Use these questions when reading its demo outline:

- Do those three session details cover the list you want to keep?
- Is a CSV export useful for your next manual step?
- Do you also require payments, participant bookings, integrations or automated reminders? Those are not included here.

Read the demo outline: [DEMO_LINK_PENDING]

## Editorial handoff

The planned budgets total 240 minutes (70 + 40 + 50 + 35 + 45), including editor review; no working time was measured. F6 governs this constraint. Each day's fact list maps its claims to the source. Wednesday and Thursday use the exact event date, time, duration and purpose in F4. Friday makes no claim that the walkthrough occurred. All five drafts retain F5's placeholder. No SaaS price, testimonial, adoption metric, live booking or outcome is asserted. A real deployment needs approved real facts, a functioning destination and writer/editor sign-off before scheduling.
