QuickSupply

Product redesign case study

Follow a school's request for cover through agency assignment and a teacher's response, without losing track of who needs to act next.

Watch the recorded prototype without installing anything.

Before using this

Historical redesign case study, not a live staffing service or a validated startup.

Historical case study with fictional data. The public source is not a deployment-ready staffing service.

Recorded prototype: school request, agency assignment and teacher response.

My contribution Product and full-stack engineer
Status Recorded demo and public source
Focus School cover operations

Why I built it

A local booking process split same-day cover across dated screens and manual follow-up. QuickSupply separates school, agency and teacher work, then makes each assignment and status handoff visible.

What I chose

I gave the school, agency and teacher separate views of the same booking. The agency manages offers and exceptions; each role sees its next action instead of editing an undifferentiated list.

What the example shows

The recording follows a fictional cover request across the three roles. The shared booking status makes it possible to see whether a request is waiting for assignment or a teacher response.

What I learned

The product problem was the handoff, not just the appearance of the old screens. A useful next test would observe real school and agency staff handling a declined offer or a last-minute cancellation. This case does not establish adoption or time savings.