Crossways VMS

A visitor management system designed for care homes.

Care homes are busy, regulated environments.

Visitors can include family members, district nurses, contractors, social workers and other professionals. Each visit needs to be recorded, including who arrived, who they are visiting, why they are there and when they leave.

Yet many care homes still manage this with a paper visitor book at reception.

That creates obvious problems.

Handwriting can be difficult to read. Records are easy to lose. There is no reliable live view of who is currently in the building. Searching historical visits is slow. And during an emergency evacuation, staff cannot simply rely on a paper book to understand who is on site.

Crossways VMS was designed to replace that process with a dedicated digital visitor management system running on an iPad kiosk at reception.

The difficult part was not building a digital sign-in form.

It was making the system reliable enough to be trusted in the real environment it would be used in.

01. Designing for Three Different Users

The same system serves three very different audiences.

A visitor might use the kiosk once and never see it again.

Reception staff may interact with it throughout the day.

Managers need a completely different set of tools for reviewing records, managing settings and exporting information.

That meant the product could not be designed around a single “average user.”

we started with the most constrained experience: the visitor standing at the kiosk.

Every interaction needed to be obvious without instructions.

Controls had to be usable at arm’s length.

The interface needed to work comfortably with one hand.

And mistakes needed to be easy to correct without making the visitor feel like they had broken something.

Once that experience was established, the staff and management interfaces could be built around the operational requirements behind it.

02. Touch-First Kiosk Design

Crossways VMS was designed specifically for an iPad rather than treating the tablet as a smaller desktop computer.

The interaction model follows familiar iPad conventions, with large touch targets and controls that are easy to operate without precision tapping.

Touch targets are kept at a minimum of 44px.

Selectors use large, clear controls.

Where more complex selections are required, full-screen bottom sheets are used rather than small dropdowns that are difficult to operate on a touchscreen.

These sheets are rendered through React Portals so they aren’t accidentally clipped by parent containers or transforms.

The result is an interface designed around the physical context in which it will be used.

Someone should be able to walk up to the reception desk and understand what to do immediately.

03. Designing for an Unreliable Network

One of the most important decisions was made before thinking about visual design.

The kiosk cannot depend entirely on an internet connection.

Care homes do not always have perfect Wi-Fi, and a visitor should not be turned away because the network happens to be unavailable.

More importantly, a missed or lost visitor record creates a much bigger problem than a temporary connection failure.

Crossways VMS therefore uses an offline-first approach.

Check-in data is stored locally using IndexedDB.

If the connection is unavailable, the kiosk continues accepting visitors and queues the records locally.

Once connectivity returns, the queue synchronises with the server and reconciles the records.

The underlying rule is simple:

The kiosk should always accept the visitor.

The network is an optimisation, not a prerequisite.

04. Security and Permissions

Visitor information needs to be protected, but the system also needs to remain practical for staff.

The access model is based on user roles and the care home’s data rather than simply hiding controls in the interface.

Row-level security separates what different users can access.

Managers can access the records belonging to their home.

Reception staff can operate the visitor system.

Administrative permissions control sensitive actions such as deleting records.

The audit trail is treated as an important part of the product rather than just another database table.

During development, an overly permissive access rule caused check-ins to fail silently for reception staff.

That became an important lesson in the project.

Permissions need to be tested against the way people actually use the system, not simply against what the data model appears to allow.

05. Designing for Failure

The environment created another unusual problem.

An iPad at reception is not necessarily treated like a normal personal device.

It may be put to sleep.

It may sit untouched for hours.

It may be moved between rooms.

It may remain open for days.

Those conditions exposed issues that wouldn’t necessarily appear during normal development.

One example was a white-screen problem caused by WebKit after the iPad had been asleep for an extended period.

The solution was to listen for visibility changes and trigger a GPU repaint when the application becomes active again.

If the application has been in the background for more than five minutes, it performs a hard reload.

The objective was not to make the application impossible to break.

It was to make it capable of recovering when the environment inevitably behaves in unexpected ways.

06. Removing Unnecessary Visual Complexity

The early visual direction experimented with heavier grain effects and layered backdrop blur.

They looked interesting, but they were not appropriate for the hardware.

Stacked glass effects and heavy blur require additional GPU compositing, which can become noticeable on an ageing iPad.

The interface was therefore simplified.

Heavy grain was removed.

Backdrop blur was replaced with solid translucent surfaces.

The result was visually cleaner and technically lighter.

This was an important part of the design process.

The best visual decision is not always the most visually impressive one.

Sometimes it is the one that makes the product work better.

07. Designing the Experience Around Compliance

The visitor interface is only one part of the product.

Behind it is a record of who entered the building, when they arrived, who they were visiting and when they left.

That information needs to remain reliable and accessible to authorised staff.

The system therefore provides managers with the tools needed to review visitor activity, manage configuration and export records.

The interface is designed around the practical questions staff and managers need answered.

The product turns a paper process into something searchable and auditable.

08. The Real Design Challenge

The hardest part of Crossways VMS was not the interface.

It was designing for failure.

A normal consumer application can show a loading state when something goes wrong.

A reception kiosk in a care home has a different responsibility.

If the Wi-Fi disappears, it still needs to work.

If the iPad goes to sleep, it needs to recover.

If a visitor makes a mistake, they need to be able to correct it.

If the wrong user attempts an administrative action, the data needs to remain protected.

If a record is created, it needs to remain part of the audit trail.

That changed the way the product was designed.

Every major technical decision was considered alongside its failure state.

The Outcome

Crossways VMS replaces a fragile paper visitor book with a dedicated digital system designed for the realities of care homes.

Visitors get a simple kiosk experience.

Reception staff get a system that continues working when the network does not.

Managers get controlled access to records, reporting and configuration.

The underlying architecture protects the integrity of the visitor data while allowing the system to recover from the physical and technical problems that come with running an unattended iPad.

The result is not just a digital sign-in form.

It is a piece of software designed around a simple requirement:

When someone walks through the door, the system needs to work.

Designed and engineered by Evuve.