A repair reported.
A return visit planned.
We designed the resident and manager views around the same repair.
A resident needs to know what will happen at home; the property team needs the assignment, access instructions and outstanding action. We kept those perspectives separate without changing the underlying story.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Residential property maintenance
- DESIGN FOCUS
- Connecting resident repair requests to an operational queue
The access problem stays in the record.
The repair timeline includes a failed visit and a confirmed return. We retained that interruption because it explains the next appointment. The denser manager queue adds property and status filters, while the selected dossier keeps the contractor and handover details together.
The pages we designed.
The build brings resident home, populated maintenance report, repair timeline and operational queue into one workspace.
Populated maintenance report
View the screen ↓Repair timeline
View the screen ↓Operational queue
View the screen ↓Project scope.
We designed and built 4 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
4 views Select any view to exploreHave a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.



