Rug Journey — System Overview
Internal Operations System
Rug
Journey
From intake to delivery — nothing gets lost
A web application that tracks every hand-knotted rug through its full cleaning process, ensures quality standards, and alerts the team before anything falls through the cracks.
Multi-location
Real-time alerts
Mobile-first
Audit log
Why we need this
The problem we're solving
Without a tracking system, critical steps in the rug cleaning process get missed — affecting quality, trust, and delivery times.
📋

No visibility

Nobody knows at a glance where each rug is in the process, how long it's been there, or who is responsible for the next step.

01

Missed deadlines

Rugs sit in the workshop beyond the 2-week target without any alert. Customers wait longer than promised, with no one noticing.

02
📸

No photo documentation

Before & after photos are not consistently captured. Without them, there's no proof of work quality and no protection if a client disputes the result.

03
🔍

No accountability

When something goes wrong, there's no way to trace back who did what and when. No audit trail means no learning and no improvement.

04
What we're building
One system, full control
Rug Journey is a mobile-first web app designed for the workshop floor and management alike. Simple to use, impossible to cheat.
A
Core feature

Real-time tracking

Every rug has a unique order number and moves through defined checkpoints. The team sees live status at all times from their phone.

B
Core feature

Smart alerts

Automatic notifications reach the whole team when a rug has been waiting too long, an inspection is overdue, or a photo is missing.

C
Core feature

Flexible process routes

Each rug follows a defined route — Standard, Repair, or Rush. Steps can be added or skipped with a justification that stays on record.

D
Core feature

Full audit log

Every action is recorded: who did it, what they changed, and when. Skipped steps are flagged with a mandatory reason — nothing disappears.

E
Core feature

Client history

Each order is linked to a client profile. View how many rugs they've brought, past issues, special requirements, and full service history.

F
Core feature

Multi-location ready

Built for one location today, designed to scale to a franchise. Each branch runs independently, with a global view available to ownership.

How it works
The 5-checkpoint journey
Every rug passes through five defined stages. Tap each one to see what's required at that step.
1
Intake
Reception
Tap to expand ↓
Registered in Lightspeed?
Physically tagged?
Initial photos sent to WhatsApp?
Client profile linked
Order # + item # assigned (e.g. WO#3019 · 2 of 4)
2
Pre-wash Inspection
Operator
⚑ 48h SLA
Tap to expand ↓
Inspection date recorded
Report sent to client?
Pre-existing damage documented (photo check)
Alert fires if 48h pass without this step
3
Cleaning & Process Route
Operator
⚑ 2-week max
Tap to expand ↓
Route A — Standard wash
Route B — Repair (extended timeline)
Route C — Rush (priority flag visible)
Extra steps can be added mid-process
Steps can be skipped with mandatory justification
Special client notes / repair requirements
4
Quality Control & After Photos
QC / Supervisor
⚑ Missing photo
Tap to expand ↓
Final quality check
After photo confirmation (strongly encouraged)
Can advance without photo — with visible warning
Admin notified if photo is skipped
Logged permanently: "completed without photo backup"
5
Ready for Delivery
Reception / Admin
Tap to expand ↓
Full journey confirmed complete
Client can be notified for pickup
Permanent record of entire process stored
Proactive notifications
Alerts that reach everyone
No designated owner per stage — alerts go to the whole team so whoever is available can act. Both push notification and dashboard badge.
🕐
48h
Inspection overdue
The pre-wash inspection hasn't been completed within 48 hours of intake. This was a commitment made to the client.
Push notification
Email
All team members
📅
2 wk
Turnaround exceeded
A rug has been in the workshop for over 2 weeks. This is the maximum acceptable turnaround time for standard routes.
Push notification
Email
All team members
📸
QC
No after photo
A rug was marked as finished without an after photo. Admin is notified and the record is flagged permanently for reference.
Push notification
Flagged in log
Admins only
Special state
Waiting for client
When a rug is paused pending client approval (e.g. repair budget), it enters a "Waiting" state that pauses turnaround timers — so the team doesn't get unfair alerts. A reminder notification goes out to prompt a follow-up with the client.
User access
Four roles, clear boundaries
Each person logs in with their own credentials. Every action is tied to a name, a time, and a reason — always.

Reception

Branch-level access
Register new rugs at intake
Link clients and assign order numbers
Mark rugs as ready for pickup
View full status dashboard

Floor Operator

Branch-level access
Advance rugs through cleaning stages
Add or skip steps (with justification)
Confirm photos and inspections
Big-button mobile interface for gloved hands

Branch Admin

Branch-level access · Full control
All operator permissions
Override blocked steps with audit note
Manage branch users and their roles
Receive admin alerts (no-photo, overrides)

Super Admin

Global access · All locations
View all branches from one dashboard
Create and configure new locations
Assign branch admins to each location
Full audit log access across the network
Built for growth
Franchise-ready structure
One location today. The architecture already supports as many branches as needed — each completely isolated from the others.
Owner / Franchisor

Super Admin

Global visibility across all branches · No operational access

Current

Branch 1

Branch Admin
Reception
Operators (2–5)
Future

Branch 2

Branch Admin
Reception
Operators
Future

Branch N

Branch Admin
Reception
Operators
Complete isolation: Users in Branch 1 cannot see, search, or access any data from Branch 2 or beyond.
Interface preview
What it looks like
The management dashboard shows live status across all rugs. Tap a status card to filter the list below.
Rug Journey · Branch 1
Maria Lopez · Branch Admin
4
Intake
7
Inspection
12
Cleaning
3
QC
5
Ready
WO#3019 · Item 2 of 4 — Inspection overdue (61h)
48h SLA
WO#2987 — In workshop for 15 days
2-week limit
Order
Client
Journey
Status
Days
WO#3019
Anderson, J.
I
P
C
Q
D
Intake
1d
WO#3017
Martínez, R. Rush
I
P
C
Q
D
Cleaning
3d
WO#2998
Chen, L.
I
P
C
Q
D
Waiting
9d
WO#2987
Kowalski, A.
I
P
C
Q
D
Cleaning
15d ⚑
WO#2981
García, M.
I
P
C
Q
D
Ready
8d
Under the hood
How it's built
Built with proven, scalable technologies. Accessible from any browser — no app store required. Installable on mobile as a PWA.
User interface

Mobile-first web app

Works on any smartphone browser — no download needed
Can be installed on home screen as a PWA (app-like experience)
Large buttons designed for gloved hands or wet conditions
Minimal typing — most actions are taps and selections
Data & security

Secure cloud database

All data stored securely in the cloud — no local data loss risk
Individual login per user — no shared passwords
Complete branch isolation — data never crosses locations
Full audit log: who did what, and when
Notifications

Push + email alerts

Push notifications on mobile for users who install the app (PWA)
Email alerts as a reliable fallback — no installation required
Both channels work in parallel — no one misses an alert
Alert rules configurable as the business evolves
Photos

Existing workflow preserved

Photos continue to sync to Google Photos automatically as today
The app uses a simple checkbox confirmation — not a new photo system
No duplication of workflows — just accountability built on top
What comes next
Development roadmap
A phased approach — launching a complete system from day one, with room to grow as the business scales.
1
Phase 1 · Now

Define process routes

Map out the exact steps for Route A (Standard), Route B (Repair), and Route C (Rush). These are the core of the button logic in the app.

2
Phase 2 · Build

Full app development

Build all 5 checkpoints, the dashboard, alerts system, user management, client history, and audit log — complete from the start.

3
Phase 3 · Launch

Team rollout at Branch 1

Onboard the team, set up individual logins, install as PWA on team phones, and run live with Branch 1 as the pilot location.

4
Phase 4 · Scale

Multi-location expansion

As new branches open, each gets its own isolated environment, branch admin, and team — onboarding in minutes, not weeks.