Beta

This is a new service and pages are being tested and improved.

Site-wide search

Guidance

How to write a blog post

Guidance, a template, and AI prompts to help you write a good blog post for the Government Project Delivery website

Published: 01 September 2025
Last modified: 21 April 2026

Overview

Use a blog post when you want to share a personal view, experience or reflection.

Blog posts are written in the first person and offer a more conversational tone than news articles. They’re a space for you to reflect on their work, share lessons learned, or encourage others to get involved.

While news articles often present an organisation’s position or official guidance, blog posts add value through your personal insight. They still need to be relevant to project delivery professionals in government and help others understand, reflect or take action.

Submit a blog

What makes a good blog

A good blog:

  • shares a personal view or experience
  • explains why it’s relevant to project delivery professionals
  • adds value by offering insight, reflection or practical advice
  • focuses on one clear topic or takeaway

Blog posts are more relaxed than news articles, but they’re still published on the homepage of the Government Project Delivery website. That means they should be useful to others working in project delivery, helping them understand how things work in practice, and encouraging them to explore tools, frameworks and guidance that support better delivery.

Try to link it to wider resources like The Teal Book, the Project Delivery Capability Framework or departmental strategies. Blogs are a good way to show how these are used/implemented and how they help solve real problems.

Keep it focused

Try to centre your blog around one idea or experience. This helps readers understand the takeaway and keeps the content clear.

If you’re covering multiple points, like in a listicle, make sure it’s for a specific audience and adds context they can use. Avoid writing a list just for the sake of it.

Think about the reader

Before you start writing, ask yourself:

  • why does this matter to someone working in project delivery?
  • what might they learn or take away?
  • is there a call to action, something you want them to do, think about or explore?

Blog formats

You can write your blog in different formats, depending on what you want to share. Some common ones are listed here.

Reflections

Your thoughts on how best to do something, what you’ve learned, or what stood out at an event.

Spotlight

A short overview of an ongoing initiative, or an update from a portfolio, programme or project. This is usually less detailed than a case study.

Interview

A summary of a conversation or interview with someone else. Think about how journalists report interviews with people.

Listicle

A structured list with context and explanation. This works well when aimed at a specific audience with a clear purpose. For example: ‘5 things I learned from delivering X’.

Case study

A more detailed look at something that’s happened, often with lessons learned. This is usually more historical than a spotlight.

Visit write-up

A summary of a team visit with reflections on what you saw or learned.

Template

Blog post template for the Government Project Delivery website

File type: docx

File size: 2.81 MB

Using AI to help write your blog post

Step 1

Start by telling the AI what you’re writing, who it’s for, and what tone you want to use. This helps it give you better suggestions.

I’m writing a blog post for the Government Project Delivery website (projectdelivery.gov.uk).

It’s for project delivery professionals working in UK government.

I want the tone to be [reflective/conversational/practical/encouraging].

The blog should follow GOV.UK style, use plain English, and be suitable for a secondary school reading age.

It’s a personal reflection on [brief summary of your topic].

You can upload a sample of your writing to help it understand your personal voice. Another option is to add a sample of a blog post or posts that you like the style of.

You can also add:

I want it to sound like me — not too formal, but still professional.

I want to share what I’ve learned and how others might use it.

It should support the use of our body of knowledge hosted on projectdelivery.gov.uk, like The Teal Book, without being too formal or prescriptive.

Step 2

Blog posts are personal, so there’s no single right way to write one. You might already have a rough draft, a few bullet points, or just an idea. AI can help you shape that into something useful without taking over your voice.

Start by uploading or pasting your ideas. Then use prompts like these to help you develop it:

Help me:

  • find the main message or takeaway
  • suggest a clearer structure
  • check if it’s relevant to project delivery professionals
  • show how it could link to guidance like The Teal Book
  • keep the tone personal and engaging

Ask me questions about it so I know what else to add.

You can also ask follow up questions, like asking:

  • what’s the most useful part of this for someone else?
  • does this feel like something I’d say to a colleague?
  • are there any gaps or things I should explain more clearly?
  • is there a better way to start or end this?

This step is about shaping your story, not rewriting it. Use AI to help you reflect, organise and improve what you already have.

Step 3

Once your blog post has a clear structure and message, use AI to help you refine it.

Paste your draft into the AI tool and ask it to challenge your thinking. You want it to help you spot gaps, improve clarity and make sure your tone works for the audience. Use prompts like these:

Here’s my draft blog post: [paste your content].

Help me:

  • check if the format is right for what I’m trying to say
  • review the tone of voice — does it feel personal, clear and appropriate for project delivery professionals?
  • identify any jargon or overly formal language
  • suggest where I could use active voice instead of passive
  • highlight anything that’s unclear or could be explained better
  • ask questions that a reader might still have
  • suggest anything I could add to make it more useful
  • check if it’s too long or could be more focused

You can also ask:

  • does this feel like something I’d say to a colleague?
  • is there a better way to structure this?
  • have I made the takeaway clear enough?

This step helps you polish your blog post while keeping your voice and message intact.

Back to top