Home / Product / How it works

From design submission to store opening, step by step.

Eight steps, one connected record. Here is who is involved at each point, what they produce, and what changes when the work runs through VRDnet.

01

Create Project

Set up the project, its assets, levels and delivery stages. Define who is involved and the key milestones the programme must hit.

Users involved

Retail developer · Project manager

Outputs

▪ Project structure

▪ Stage definitions

▪ Programme milestones

Benefits

✓ Consistent stages across assets

✓ Clear ownership from day one

02

Register Tenant / Unit

Register each unit with its tenant, lease milestones, requirements and key dates, creating the record that every later step builds on.

Users involved

Leasing team · RDD team

Outputs

▪ Unit records

▪ Tenant contacts

▪ Key dates

Benefits

✓ One record per unit

✓ No re-keying from leasing trackers

03

Submit Design

Tenants and their designers submit drawings against a checklist based on the design criteria, so reviews start with complete information.

Users involved

Retail brand / tenant · Design consultant

Outputs

▪ Drawing submission

▪ Completed checklist

▪ Revision record

Benefits

✓ Fewer incomplete submissions

✓ Clear current revision

04

Review

Reviewers from each discipline pin comments to drawings, assign owners and due dates, and issue a consolidated response.

Users involved

RDD reviewer · MEP consultant · Fire consultant

Outputs

▪ Pinned comments

▪ Action list

▪ Review response

Benefits

✓ Comments stay in context

✓ Every action has an owner

05

Approve

Approve, approve with conditions or request revision. Every decision is recorded against the unit with its full history.

Users involved

Landlord design team · RDD lead

Outputs

▪ Approval record

▪ Conditions

▪ Notifications

Benefits

✓ Clear status for everyone

✓ Complete audit trail

06

Deliver

Track fit-out against the programme. Coordinate contractors, capture progress and manage the actions that keep work moving.

Users involved

Project manager · Tenant contractor

Outputs

▪ Programme updates

▪ Site actions

▪ Progress records

Benefits

✓ Early sight of slippage

✓ Dependencies made visible

07

Inspect

Schedule and record inspections, raise HSE and snag actions, and close them out with evidence before handover.

Users involved

HSE / inspection team · MEP consultant

Outputs

▪ Inspection records

▪ Snag lists

▪ HSE actions

Benefits

✓ Nothing left to the last week

✓ Evidence attached to the unit

08

Open

Confirm readiness, complete closeout and handover documentation, and give everyone a clear view of what opens next.

Users involved

Retail developer · Retail brand · Operations

Outputs

▪ Readiness confirmation

▪ Handover pack

▪ Opening report

Benefits

✓ Openings you can plan around

✓ Confidence across stakeholders

Everyone involved, on the same journey.

Each role joins where it matters — and sees the same status as everyone else.

Roles involved at each step

Role

Create Project

Register Tenant

Submit Design

Review

Approve

Deliver

Inspect

Open

Retail developer / landlord

Leads

Leads

Contributes

Contributes

Leads

Contributes

Contributes

Leads

Retail brand / tenant

—

Contributes

Leads

Contributes

—

Contributes

Contributes

Contributes

RDD / delivery team

Contributes

Leads

Contributes

Leads

Leads

Contributes

Contributes

Contributes

Project manager

Leads

Contributes

—

—

Contributes

Leads

Contributes

Contributes

Design consultant

—

—

Contributes

Leads

Contributes

—

Contributes

—

Leads the step · Contributes

Questions teams ask

Something else on your mind? Talk to the VRDnet team.

Who uses VRDnet?

Retail developers and landlords, retail brands and tenants, RDD and delivery teams, project managers and design consultants — each with access to the parts of the journey relevant to them.

Can tenants and consultants work in VRDnet directly?

Yes. Tenants and consultants can sign up to a project, subject to approval by your delivery team, or your team can register them directly. Once in, they submit, respond to comments and manage their actions, so status stays current without email chasing.

Does VRDnet replace our existing trackers?

It can. Many teams start with one project or workflow alongside their current trackers, then retire those trackers once the information and reporting they need sit reliably in VRDnet. Others deploy VRDnet around a defined part of the work and extend it as the need grows.

Do we need our own delivery team?

VRDnet does not replace the people, professional judgement or delivery capability behind the work. Teams using it directly need people who remain accountable for review, coordination and delivery. Where that capability or capacity is also needed, Vindico can run a defined part of the work or a wider engagement.

What if we need Vindico to run part of the work?

Vindico’s work can cover design, fit-out and the management of the route. Where Vindico is appointed, VRDnet is configured around the workflows in scope. Vindico can run defined parts of the work, such as design review, tenant coordination or fit-out delivery, with VRDnet as the platform behind it. The right configuration is worked out in the first conversation. About Vindico ↗

Can the stages match our delivery process?

VRDnet is set up around your delivery stages, approval routes and roles during onboarding.

How is VRDnet deployed?

Deployment is scoped with your team based on portfolio size, modules and stakeholders. Book a demo to discuss what fits your business.

See it with your projects

See VRDnet in action.

Walk through the journey with your own stages, roles and retail units.