Project content planner
DC Digital · Planning template · October 2026
One project can answer several different customer questions. Use this planner to identify those stories, gather the material and decide what is worth publishing. It works for a building project, installation, event, service engagement or another piece of real work.
Make a copy for each project. Keep confidential client information out of it. Check permission before photographing people, sharing a location or publishing someone else's words or work.
Type in the notes boxes, then print or save as PDF. Your entries stay on this page and are not submitted. The text download is a blank template. Save your work before closing this page.
1. The project in plain English
Internal project name:
Public client or project name, if permission is confirmed:
What did the customer need?
What did you do?
What made the job interesting or difficult?
What changed as a result? Record only what you can show or support. If the outcome is still unknown, say so.
Who would find this useful to see?
2. Find the stories
Do not force every angle into the plan. Choose those that say something useful about the work.
| Possible story | The detail from this project | Evidence or material available |
|---|---|---|
| The starting problem | ||
| A decision and why it mattered | ||
| Work people do not normally see | ||
| A common customer question | ||
| A detail that shows care or skill | ||
| The finished result | ||
| A lesson for someone planning similar work |
Choose the strongest three stories:
1.
2.
3.
3. Plan the photographs and video
For each chosen story, ask what someone would need to see to understand it. Capture the real work rather than recreating something unsafe or misleading for the camera.
| Capture needed | What it explains | Who will capture it? | When is it available? |
|---|---|---|---|
| Wide view of the setting | |||
| Relevant detail or process | |||
| Before and after, where available | |||
| Short explanation from someone involved | |||
| Other |
Practical checks:
4. Permission and accuracy
Who owns the photographs, video and other material?
Who has agreed to be identified, and where may the material be used?
Can the client, location and project value be named? Leave them out if permission is unclear.
Are any claims supported by a record or measurement? Note the source, dates and context.
Who checks the factual details and approves publication?
Anything that must be blurred, removed or kept private:
5. Turn each story into a post
Complete this short outline for each selected story:
Story title:
The customer question it answers:
Opening line: say what happened or what the reader will learn.
Useful detail: explain the decision, problem or process.
Evidence: identify what the picture, video or source actually shows.
Next step: choose one useful action, such as viewing the project, reading an explanation or asking about similar work.
Avoid adding a sales instruction to every post. Some posts should simply help the reader understand your work.
6. Publishing plan
| Story | Platform and format | Asset needed | Approver | Target date | Next step or link |
|---|---|---|---|---|---|
What can be adapted later without repeating the same post? Examples: a short process clip, a detailed project page or an answer to a question in the comments.
7. Review what happened
Review date:
Which posts prompted relevant questions, useful conversations or website visits?
What feedback did the sales or customer-facing person hear?
What worked well enough to repeat, and what needs changing?
Keep reach and likes in context. A popular post and a useful business conversation are different things.
Next project to capture:
Person responsible: