Built on our own platform.

The conventional sign schedule goes out as a PDF. Comments come back in an email, or three emails, or a marked-up print. Someone rebuilds the schedule by hand and it goes out again. Four rounds, five rounds, a fortnight each, and by the time it settles the fit-out programme has moved underneath it.

In our platform a sign is a record, not a row in a document. The client, the architect, the project manager and our designers all look at the same schedule, live. Comments attach to the individual sign rather than to a version of a file, so nothing has to be rebuilt between rounds. Approval is given sign by sign, and it is dated and attributed.

That is how approvals come down from months to days, and why the average package clears in 1.8 design rounds. The waiting and the re-typing have been taken out.

The platform ties into the construction management system the main contractor already runs. Sign status, outstanding approvals and programme dates surface where the site team is already working, alongside every other package.

No separate login to remember, no parallel spreadsheet drifting out of date, and no weekly email asking where the signage is. If it has moved, you can see that it has moved.

We work natively from CAD. Your floorplans and fire drawings come in as geometry, and every sign is placed against the real building rather than traced onto a flattened image. When the layout changes, the schedule knows.

Output goes to BIM. The wayfinding package arrives in the federated model as objects with locations, types and attributes, so it can be coordinated with services, clash-checked and interrogated like any other trade. For an architect or a developer this is the difference between wayfinding as a document handed over late and wayfinding as part of the design information from the start.

Each sign carries its own history: who designed it, who approved it and when, what it was manufactured from, who installed it and on what date, and which certificate it sits under.

This is the part that underwrites the commercial promises. The price holds because the scope is known sign by sign rather than estimated. The programme holds because status is visible before it becomes a delay. Certified handover is possible because the record was built as the work happened, not assembled afterwards from memory.

At completion the client receives the O&M documentation, the as-built sign schedule and the certification records, all generated from the same data that ran the project.

It stays useful after practical completion. When a sign is damaged in year four, the replacement is specified from the record rather than from a site measure and a guess.