Community visit planner / Interface design
Plan the visits.
Plan the visits.
Allow for the journey.
We organised the community visit planner around a schematic territory and exact intervals.
The day plan gives travel a place between visits rather than treating appointments as unrelated blocks.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Community visit planner
- DESIGN FOCUS
- Planning community visits around travel and access
01 / THE DESIGN DECISION
An available hour includes travel and access.
The access detail and conflict review explain why the schedule needs a change. We kept those constraints visible beside the proposed visit, without claiming live navigation or route optimisation. The records concern administrative planning, not personal health information.
02 / THE BUILD
The pages we designed.
The build brings east territory community visits, day, park visit access detail, park schedule conflict review and community service territory into one workspace.
Day
View the screen ↓Park visit access detail
View the screen ↓Park schedule conflict review
View the screen ↓Community service territory
View the screen ↓03 / PROJECT NOTES
Project scope.
We designed and built 5 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.
06 / ON SCREENA closer look.
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.
5 views Select any view to explore
Have 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.