This service blueprint template connects customer actions, visible service, backstage work, and supporting records. The three-moment print-shop example shows the missing readiness record and a proposed prerequisite that keeps the gap unresolved until someone verifies it.
Choose one service and show its layers
The original fictional service is a neighborhood print shop preparing a poster order for collection. Its teaching job card is P01: 20 A3 posters. No actual order, printing, customer, notification, or ready package is represented.
Nielsen Norman Group's service-blueprint definition describes customer actions, frontstage and backstage actions, support processes, and service evidence. A blueprint aligns these layers so a team can examine the dependencies behind the customer experience.
For this example, the three service moments are Submit artwork, Receive pickup notice, and Collect posters. The layer view is:
| Layer | Submit artwork | Receive pickup notice | Collect posters |
|---|---|---|---|
| Customer actions | C1: supply artwork and requested job details. | C2: read the pickup notice, if actually sent. | C3: show the job ID. |
| Visible staff actions | F1: check job ID, poster size, and quantity with the customer. | F2: issue a pickup notice only after readiness is confirmed. | F3: match the presented job ID to the collection record. |
| Backstage work | B1: check artwork against the agreed print requirements. | B2: print and finish; B3: pack and record the job ready. | B4: retrieve the matching ready package. |
| Supporting processes/records | S1: paper-stock record. | S2: production queue; S3: job register and job-ready record. | S3: job register and matching ready-job identity. |
| Service evidence | Teaching job card P01. | Unsent notice preview and the required ready-record reference. | Matching job ID and package record; no actual handover supplied. |
All actions describe the proposed service arrangement. A cell in the blueprint is not evidence that the action happened.
Make the boundaries readable
The line of interaction separates customer actions from the visible staff interaction. The line of visibility separates the visible staff activity from work the customer does not directly see. The internal handoff boundary separates backstage production from its supporting processes and records.
Keep those labels readable when the map changes layout on a phone. The point is to see which layer a dependency crosses, not to shrink a wide diagram until its words cannot be read.
For your own service, identify the actual records, people, and systems behind each handoff. Do not infer a production action merely because the customer has reached the next step in the journey.
Follow the pickup notice back to readiness
Choose Pickup notice in the example. F2 depends on B2's print-and-finish work and B3's packed-and-ready state for the same job. The supporting ready record must identify P01 and the relevant readiness confirmation before staff can rely on it.
The supplied exercise has no completed job-ready record. A preview reading “Your posters are ready for collection — P01” is an unsent wording draft, not evidence that the posters are ready.
Compare these arrangements:
| Review view | Dependency shown | What remains unresolved |
|---|---|---|
| Flawed plan | F2 is scheduled after the printing step alone. | Finishing, packing, and the same-job readiness confirmation have not been established. |
| Proposed prerequisite | F2 requires the P01 ready-record reference confirming print/finish and packing readiness. | The required record is still not supplied. No ready state or sent notice is created. |
Choose Compare prerequisite to read those two views together. The proposed model improves the description of what must precede the notice. It does not complete B2 or B3, insert a timestamp, or create the missing record.
This is the review question for desk and production staff: Which actual same-job record authorizes the ready notice, and who maintains it? Answer it in the real service process before relying on the customer-facing promise.
Inspect the collection handoff too
Choose Collection. F3's job-ID check depends on the job register and the identity of the package retrieved in B4. Seeing a customer with an order number is not enough to establish that the matching package is available for handover.
Record that relationship without inventing a completed collection. The exercise supplies no handover time or receipt. If a real workflow uses a different verification method, represent that method and its evidence rather than importing the teaching arrangement unchanged.
Use the blueprint to choose the next service change
A customer journey map can show what the customer encounters. The blueprint asks which visible, hidden, and supporting activities make those encounters possible. Here, the useful finding concerns a notice's readiness prerequisite, not a new description of the customer's feelings.
Review the dependency with the people doing the work. Confirm its owner, record identity, and exception route. Keep proposed changes distinct from the current process and record what the team actually agrees. Add measured time, costs, or service outcomes only when the relevant data exists.
Copy a prompt for the layered map and dependency review
Create one complete HTML service-blueprint review page.
Bounded service and customer goal: [PASTE]
Service moments and customer actions: [PASTE]
Visible staff, backstage, supporting process/record layers: [PASTE]
Evidence artifacts and exact cross-layer dependencies: [PASTE]
Current gaps, proposed changes and actual process owners: [PASTE]
Align the layers by service moment. Label interaction, visibility,
and internal handoff boundaries. Explain dependencies in text as
well as arrows. Do not infer completed work from a planned step.
Include this original fictional print-shop poster-pickup example:
Teaching job card P01: 20 A3 posters. No actual customer/order/run.
Moments: Submit artwork; Receive pickup notice; Collect posters.
C1 supplies artwork/details; C2 reads notice if actually sent;
C3 shows job ID.
F1 checks job ID, size, quantity; F2 issues the notice only after
confirmed readiness; F3 matches presented ID to collection record.
B1 artwork preflight; B2 print and finish; B3 pack and record ready;
B4 retrieve matching ready package.
S1 paper-stock record; S2 production queue; S3 job register and
job-ready record. No completed P01 ready record is supplied.
Evidence: fictional job card; unsent notice preview; required
ready-record reference; matching package/ID record, no actual handover.
Unsent draft: Your posters are ready for collection — P01.
Keep Draft wording / readiness unresolved visible beside that text.
Pickup notice selection traces F2 through B2/B3 to the supporting
same-job ready record. Flawed plan schedules F2 after printing alone.
Compare prerequisite shows a proposed requirement for P01's record
confirming print/finish and packing readiness. The record remains
missing in BOTH views. Do not invent completion, timestamps, queue
updates, approval, sent notification or printing/handover outcomes.
Collection selection traces F3 job-ID matching to S3 and B4's
matching package identity; no collection receipt is supplied.
Show the complete map, layer legend, Pickup notice, Collection,
and Compare prerequisite views. Use clearly labeled service evidence
cards, not fake working job-system links or sending controls.
Add a separate blank blueprint and temporary review questions;
preserve typing across views and confirm reset. No customer data
collection, printing, booking, notification or export operation.
Use at least 16px text, native labeled controls, visible focus,
aligned layer cards at 720px and readable stacked moment/layer
records at 360px without page overflow. Inline CSS/JavaScript,
no external assets, network or storage. State notes are temporary.
Return complete HTML and the unresolved handoff/record questions.
Check the generated prerequisite view carefully. It should make the missing record easier to investigate while keeping readiness unresolved. A map that writes a completed timestamp to make the arrow work has changed the evidence instead of explaining the service.
Review the promise with desk and production colleagues
Put the sanitized HTML blueprint in your NOS workspace when desk and production staff need to inspect the same notice prerequisite. Ask them to point to the record that would justify the wording for P01.
If “After printing” conceals the packing dependency, clarify the static explanation to “After the same-job record confirms finishing and packing readiness” in visual editing mode. Save it so colleagues can reopen the existing link and read the condition. Update the maintained procedure after actual agreement; editing the page does not change the production queue or notify a customer.
Confirm the real record and exception route before using the ready notice. Keep the blueprint as a review of how the layers connect, alongside the operational records that establish what has happened.