Independently designed the student reporter and maintenance team experiences.
Status
Self-directed campus maintenance concept; not commissioned or deployed.
Services
User Flows
Feature Map
Wireframes
Visual Design
Mockups
Prototype
Overview
A 2020 self-directed concept, revisited in 2026. CSUSB Maintenance System connects student reporting with maintenance coordination. I designed the feature map, flows, wireframes, visual design, mockups, and prototype. The case follows one service problem: how can a report describe the right place, reach the right team, and stay understandable until the repair is resolved? The project was not commissioned or deployed.
Retrospective flow map
ReporterDescribe + locate
→
Shared reportIssue + place + status
→
CoordinatorReview + assign
One report record connects the two roles while each surface keeps its own information hierarchy. This is a 2026 explanation of the documented relationship, not an original artifact.
Archived concept artifact: the feature map shows how student reporting connects to maintenance team coordination.Retrospective flow map
WhatCategory + short description
WhereBuilding + room or landmark
HelpPhoto or reporter note
These signals are small enough for a reporter to provide and structured enough for staff to act on. This is a 2026 explanation of the documented relationship, not an original artifact.
Original concept screenboard: current location, map selection, and manual address entry give the reporter three ways to describe place.Original concept screenboard: time selection and submission confirmation make the report's next step explicit.
Two sides of a maintenance report
UI flow
Student reporting
Create a report, describe the issue and location, then check its status.
Original UI screens with the documented navigation and submission paths.
Wireframes
Staff coordination
Review notifications, read feedback, and add an update to a report.
Original wireframes for incoming notifications, reporter evaluation, and report updates.
2026 follow-up: make edge states explicit
This follow-up is a 2026 design analysis and concept extension. It tightens three edge states around the original report flow while keeping the source concept's location paths, close, evaluation, and reopen behavior distinct from the new rules.
2026 concept extension
Make the report resilient after submit
Sample report · 2026 concept extension. This walkthrough re-presents the documented lifecycle and adds three 2026 rules: a duplicate suggestion, explicit recovery when location access fails, and reporter confirmation before resolution. It uses sample content and is not a historical prototype.
01Suggest a possible duplicate
Explain the match and let a different issue stay separate.
02Recover when location fails
Keep manual place entry available so the report can continue.
03Confirm before closing
Ask the reporter whether the repair resolved the issue.
Make a campus location as important as the issue itself, with a searchable fallback if location access is unavailable.
ReporterCampus user
‹ BackNew report9:41
REPORT A PROBLEM
Desk leg feels loose
Issue typeCarpentry
Describe the issue
One desk leg is loose.
Location
John M. Pfau LibraryLevel 2 · Study room 002
Fallback
Location access unavailable. Search building and room to continue.
Add a photo1 of 6
Possible related report
Same room · Carpentry · Today. Different desk or issue? Keep this report separate.
View existing reportContinue as separate report
Maintenance coordinatorFacilities operations
‹ BackMaintenance queue9:41
INCOMING REPORTNew
Desk leg feels loose
Normal priorityReceived 2 min ago
John M. Pfau LibraryLevel 2 · Study room 002
Issue typeCarpentry
Reporter noteOne desk leg is loose.
Review report
02
Assign: Turn signals into work
Keep the reporter's language intact while giving the coordinator a scannable record for triage and assignment.
ReporterCampus user
‹ BackReport status9:41
REPORT #283970359382Assigned
Desk leg feels loose
SubmittedToday, 10:12 AM
Assigned to Carpentry teamA coordinator is reviewing the location and issue.
John M. Pfau LibraryLevel 2 · Study room 002
View report
Maintenance coordinatorFacilities operations
‹ BackAssign work9:41
REPORT #283970359382Assigned
Desk leg feels loose
John M. Pfau LibraryLevel 2 · Study room 002
Assigned toCarpentry teamQueue · Campus repairs
PriorityNormal
TargetToday, before 4:00 PM
Acknowledge
03
Update: Show work in progress
A shared status and short progress note keep both sides aligned while the coordinator manages the queue behind the scenes.
ReporterCampus user
‹ BackReport status9:41
REPORT #283970359382In progress
Desk leg feels loose
Carpentry teamToday, 1:26 PM
We found the loose leg and are preparing a replacement fastener. We will return to secure it.
Last updatedJust now
John M. Pfau LibraryLevel 2 · Study room 002
Reply to update
Maintenance coordinatorFacilities operations
‹ BackUpdate report9:41
REPORT #283970359382In progress
Desk leg feels loose
Progress update
Replacement fastener ready. Returning to secure the leg.
Location verified
Issue evaluated
Repair in progress
Post update
04
Resolve: Close, acknowledge, reopen
Keep the original reopen path and add reporter confirmation before a resolution becomes final.
ReporterCampus user
‹ BackReport status9:41
REPORT #283970359382Awaiting confirmation
Desk leg feels loose
Desk leg secured and testedRepair update from Carpentry team · Today, 3:18 PM
Does the repair look fixed? Confirm the repair or tell the coordinator the issue remains.
Confirm repairStill needs work
Maintenance coordinatorFacilities operations
‹ BackRepair ready9:41
REPORT #283970359382Repair ready
Desk leg feels loose
Resolution
Repair note: desk leg secured and tested. Reporter response is tracked with the report.
The reporter can confirm the repair or send the report back to In progress.
Assigned toCarpentry team
View report history
All four stages remain visible when scripting is unavailable, so the product decisions and state model can still be reviewed.
Scroll to follow the report from submission to resolution. Reduced motion keeps the same information without animated movement.
Three boundary rules
Possible duplicatesSuggest a nearby report with the same category, explain why it may match, and let the reporter continue when symptoms or urgency differ. The aim is to reduce duplicate work without silently merging two potentially different issues.
Location deniedAdd an explicit denied state when precise location access is unavailable, then offer searchable building and room fields or a landmark description so submission can continue with useful context. This rule extends the source concept's location choices rather than replacing them.
Close and reopenAdd a confirmation step after staff propose a resolution; keep acknowledge, reopen, and related follow-up actions visible when the issue remains. This gives the reporter a voice in closure without removing staff ownership of the work queue.
