Product Designer
VELOCITY · INSPECTION SCHEDULING
MY ROLE
Product design · UX & UI
PRODUCT CONTEXT
Velocity / Link Logistics
FOCUS
Scheduling, coordination & contact management
SCREEN 02
Vendor overview
Image placeholder
Show the full overview, then crop one property summary for detail.
Each property summary shows invitation status, tenant confirmations and requests to reschedule.
Vendors needed to know where to go, when they could visit and who to contact. Tenants needed to confirm the visit or ask for another time. Property teams needed to see what was still waiting for a response.
Some contact details were missing or incorrect. I had to include a way to deal with this, rather than assume that every tenant had one contact with the right details.
How could I help people see what they needed to do next when responses came at different times or contact details were missing?
02
The workflow
The process starts with an inspection request. The vendor then plans the visit and contacts the tenants. I designed different views so each person could see the information and actions they needed.
SCREEN 01
Inspection request
Image placeholder
Show the request fields and property-selection context.
I grouped the vendor’s overview by property. Each property shows whether invitations have been sent, how many tenants have confirmed and how many have asked to reschedule. The vendor can expand it to see individual tenant responses.
This lets the vendor check progress across the request, then look at a particular tenant when needed. It also makes the difference between an invitation being sent and a tenant confirming it clear.
SCREEN 02
Vendor overview
Image placeholder
Show the full overview, then crop one property summary for detail.
SCREEN 03
Tenant acknowledgement
Image placeholder
Show the acknowledgement form alongside the rescheduling variation.
SCREEN 04
Tenant rescheduling
Image placeholder
Pair with placeholder 03 to explain the two response paths.
I designed a screen where the acting property manager could add missing tenant contacts. It shows which tenants still need contact details and which already have them. The manager can add a contact directly from the screen.
An email asks the property manager to provide the missing information. The screen then shows the property and tenants that need their attention.
SCREEN 05
Missing-contact recovery
Image placeholder
Crop the tenant cards so the missing and complete states remain readable.
I explored ways to select an existing contact, add someone else or correct their details. I also designed an option to delegate to an on-site contact. When confirming the visit, tenants could provide instructions for accessing their space.
I also had to consider how contact changes affected Yardi. The design notes discuss whether a new contact should be temporary or added to Yardi. Other notes specify that updated phone details should stay in Velocity without being sent to Yardi.
These options helped separate changes to the tenant’s records from choosing a contact for one inspection.
SCREEN 06
Multiple-contact exploration
Image placeholder
Choose two or three frames and label them as design exploration.
SCREEN 07
Contact review
Image placeholder
Show the review form with multiple contact cards.
I designed emails for vendors, tenants, property managers and inspectors, along with Outlook invitations. I worked on these alongside the app screens so people could understand which visit the message was about and what they needed to do.
The calendar designs show property information alongside the planned visit dates. Tenants can confirm the proposed time or ask for another time within the vendor’s availability.
SCREEN 08
Inspection calendar
Image placeholder
Export the dialog and keep dates, property details and time windows legible.
SCREEN 09
Tenant invitation email
Image placeholder
Show the message and response action. Crop the repeated footer content.
Alongside the main process, I designed cases where contacts were missing or there were several contacts to choose from. I also covered rescheduling, cancellation and removing a tenant from the visit. The Figma files include separate pages where I explored different options.
The main design challenge
The main challenge was helping people follow a process that depended on several others. Vendors needed an overview of each property and a way to check individual responses. Property managers needed to know when contact information was missing. People receiving emails needed to understand what to do next.
The designs bring these tasks together in the inspection scheduling tool.
08
Screen references
Each placeholder links to the relevant Figma screen or page. The experiment pages show options I explored during the design work.
Product context: Bermwood Inspection Tool. The public page describes the wider inspection product, including mobile inspections. This case study covers the scheduling and contact-management work shown here.