Shared Product Blueprint

Repair Job Tracker

A read-only Product Blueprint created with IdeaMade.

Internal repair job tracker

Repair Job Tracker

A simple internal web app for a two-person phone and computer repair shop that replaces paper claim tickets. Signed-in staff record each customer's device at drop-off, track it through repair statuses, record quote approval and settlement, and keep an unchangeable history of every change.

Users and roles

The people who interact with the product.

Shop owner

Runs the shop and has full access to all repair jobs and their history.

  • See every repair job and its current status
  • Keep accurate records of quotes, approvals and settlements
  • Know who changed what and when

Technician

Repairs devices and has the same full access as the shop owner to create and update repair jobs.

  • Create a job quickly at drop-off
  • Update diagnosis, quote and status as work progresses
  • See the full history of a job

Key workflows

The main paths users take to reach an outcome.

Sign in to the trackerShop ownerCore
1

Open sign inThe staff member reaches the sign-in page.

2

Sign inThe staff member signs in with their account.

Outcome: The staff member is signed in and can see the repair jobs.
Create a repair job at drop-offTechnicianCore
1

Start a new jobFrom the repair jobs list, the staff member opens the new job page.

2

Enter job detailsThe staff member records customer name, phone, device model, serial number, condition at drop-off and reported problem.

3

Save the jobThe job is saved with status Received and a history entry records who created it and when.

Outcome: A new repair job exists with status Received and its creation recorded in history.
Track a job from drop-off to pick-upTechnicianCore
1

Find the jobThe staff member finds the job in the list, filtering by status if needed.

2

Open job detailThe staff member opens the job to see all fields, status, quote and history.

3

Record diagnosis and quoteThe staff member adds diagnosis notes and the quote amount.

4

Record customer approvalThe staff member marks the quote approved by the customer; the change is recorded in history.

5

Move to RepairingOnce the quote is approved, the staff member moves the job to Repairing; the status change records who did it and when.

6

Mark ready for pick-upWhen the repair is done, the staff member moves the job to Ready for pick-up.

7

Record settlementThe staff member records the settled yes/no flag. The app does not take payments.

8

Mark picked upAfter the job is settled, the staff member marks it Picked up; the status change records who did it and when.

Outcome: The job reaches Picked up with an accurate status, quote approval, settlement and full history.

Pages

4 pages in the MVP

Sign inLet shop staff sign in to the repair job tracker.
Public
Sign in
Repair jobsReview all repair jobs with their status, filter by status, and start a new job. When there are no jobs yet, staff are invited to create the first one.
Signed in
Repair jobs
Search
Customer nameCustomer phoneDevice modelSerial number or IMEI
New jobRecord a new repair job at drop-off with customer name, phone, device model, serial number, condition at drop-off and reported problem.
Signed in
New job
Job detailShow all fields of a repair job, its status, quote and approval, settlement, and the full immutable history of changes; let staff update fields, status, quote approval and settlement.
Signed in
Job detail
Customer nameCustomer phoneDevice modelSerial number or IMEI

Product decisions

Choices you can confirm directly in the Blueprint.

How should staff record that the customer approved the quote?ConfirmedHow should staff record that the customer approved the quote?
Staff toggle an approved flag; history records who and when
Should status changes be restricted to a forward sequence, or can staff move a job back to any earlier status?ConfirmedShould status changes be restricted to a forward sequence, or can staff move a job back to any earlier status?
Forward to any later status

Assumptions

Items that should be verified before implementation.

Staff record customer quote approval with a simple approved flag, and the history records who set it and when.

High impactAccepted

Status changes may move forward to any later status but not backward, subject to the quote approval and settlement rules.

High impactAccepted

The person recorded in history is the signed-in staff account; both the shop owner and the technician have identical full access.

Medium impactAccepted

Settlement is only a recorded yes/no fact; the app does not process or track payments.

Low impactAccepted