The deliverable

See how a finding becomes an action.

This illustrative report uses a fictional booking app. It shows the structure and detail of a Plain Morrow report, without presenting invented findings as client work.

Download sample PDF ↓Read the report below

REPORT 01 / SAMPLE

Release Readiness Review

Illustrative sample · Fictional product

Product

Demo booking application

Environment

Staging demo · Desktop Chrome and mobile Safari

Scope

Appointment booking and password reset journeys

Date

Sample prepared November 2026

This sample contains two functional findings and one usability observation. The examples demonstrate reporting format only. They do not describe a real client, real product, or completed Plain Morrow engagement.

1High

1Medium

1Observation

Coverage

What was in the sample scope.

A useful report states what was checked and what was left out.

Journey	Environment	Sample result
Book an appointment	Desktop Chrome, mobile Safari	F-01 and O-01
Reset a password	Desktop Chrome	F-02
Outside this sample	Other browsers and devices	Payment processing, security, load, and accessibility certification

Example findings

The detail developers need.

Each bug records the observed result, expected result, environment, impact, and a repeatable path.

F-01 · Functional bug

Booking confirmation is missing after payment

High priority

Environment

Mobile Safari · demo staging build

Steps

Choose an available appointment.
Complete the demo checkout.
Return to the booking flow.

Expected

A confirmation page with the booking reference appears.

Actual

The confirmation area is blank.

Customer impact

A customer may pay but lack a visible confirmation or reference.

Suggested next action

Inspect the post-checkout redirect and confirmation state; retest the full booking flow after the fix.

Evidence in a real report: annotated screenshot or short recording, with sensitive details removed. This demo does not include fabricated screenshot evidence.

F-02 · Functional bug

Password reset gives no confirmation after submission

Medium priority

Environment

Desktop Chrome · demo staging build

Steps

Open the password reset page.
Enter a valid demo account email.
Select “Send reset link.”

Expected

The page explains that a reset link has been requested.

Actual

The form clears without feedback.

Customer impact

Users may repeat the request or abandon account recovery.

Suggested next action

Add clear, privacy-safe confirmation text and verify the submission state.

O-01 · Usability observation

Available dates are hard to distinguish

Observation

The calendar uses similar colours for available and unavailable dates. During the illustrative journey, this could make appointment selection slower. This is an observation about clarity, not a confirmed functional bug.

Suggested next action: Use stronger visual distinction and a text label for unavailable dates; review with actual users before treating it as a measured usability outcome.

How priority works

Severity with context.

Priority combines the impact on a user journey, how often the issue is likely to occur, and whether there is a practical workaround. The final priority is discussed with the product team.

High

Blocks or seriously disrupts an important journey.

Medium

Causes meaningful friction or an incomplete outcome, with a possible workaround.

Low

Limited impact or a narrow condition that still deserves a tracked fix.

Observation

A possible experience improvement, clearly separated from confirmed bugs.

Your product

Want this clarity for your release?

Tell us about the journeys that matter, and we will propose a scoped review.

Discuss your project