Service blueprints - Free Template

The toolkit includes a clear visual framework showing how the six layers of a service blueprint connect, plus a quick-reference summary card you can use during mapping sessions. You'll see how physical evidence, user actions, and touchpoints sit above the line of visibility, while backstage actions and support processes reveal the hidden work that makes frontline delivery possible.

The summary card gives you a scannable overview of what each layer captures, practical tips for running a blueprinting session, and common pitfalls to avoid. It's designed to be printed or shared digitally as a reference during collaborative mapping.

If you're looking at service design as part of a broader improvement programme, the blueprint is often the starting point that makes everything else more focused.

• Start with friction, not perfection. Pick a journey your team already knows is causing problems. The blueprint will reveal why - and the conversation will be more energising when it's solving a real issue.
• Use the theatre test. For each activity, ask: "Would the person using the service see this happening?" If yes, it's frontstage. If no, it's backstage. This simple question resolves most placement debates.
• Map in pairs across the curtain. For every frontstage action, ask what backstage work makes it possible. This reveals dependencies that are invisible until you draw them.
• Time-stamp the blueprint. Services evolve. A blueprint from six months ago might not reflect today's reality. Date it, and schedule a revisit.