VPZ People Platform · Prototype
Decide.
Evidence.
Share.
A guided walkthrough of the working system, the decisions still needed and the pack that tells the platform story.
Today’s route
Decisions needed
Seven open answers
Audit trail
Financial change evidence
Marketing pack
One accurate platform story
15-minute guided presentation · live links included
The narrative
Three artefacts. One conversation.
Move from what needs deciding, to how the system evidences change, to what VPZ can share with stakeholders.
Decide together
Record each client answer, its date and exactly what it unblocks. Nothing is lost in meeting notes.
Prove the plumbing
Show who changed a financial record, when it changed and the values before and after.
Share the story
Use the marketing site and pack for a consistent, branded summary of the working prototype.
The working prototype
One system across the employee journey.
The marketing figures come from the same feature source as the platform story.
8
connected areas
62
features described
26
automations documented
My VPZ
Colleague self-service
People
From first application to final day
Workforce
Rota
Capability
Learning that proves people can do the job
Performance & engagement
Regular conversations
Operations
Keeping stores safe and running
Insight & UK compliance
Head office sees every store
Platform
Secure foundations
Acceptance pass: 43 business-rule tests · 46 static screens checked · live payroll, staff, site and task flows exercised.
01 · Decisions needed
Start with what needs an answer.
7
open client decisions
Each card explains why the answer matters and names the exact functionality it blocks.
4 already answered
Answers remain visible with their saved date and can be reopened.

Decisions needed
Seven answers unlock the next steps.
These are client inputs, not unfinished screens. Capture each answer on the page as it is agreed.
Sender email
Notifications, invites and scheduled reports
Leaver ownership
Till access, alarm codes and key collection
Till sales feed
Sales per labour hour and demand forecasting
Blocking skills
Which observations prevent rota publishing
Pay bands & week
Accurate budgets and outside-band flags
Official logo
Replace the typographic stand-in
RAG & area managers
Head-office thresholds and area scoping
Decisions needed
Capture the answer once. Use it everywhere.
The page becomes the shared decision log rather than a separate spreadsheet or follow-up email.
Discuss the blocker
Read the question and the affected workflow aloud.
Type the answer
Use the client’s wording, including “not yet” where appropriate.
Save and move on
The answer and date stay on the page; print for the meeting record.
Example already recorded
15-minute no-show alerts: “Not yet — leave off until told otherwise.” The decision is explicit, dated and reversible.
02 · Audit trail
Every financial change leaves evidence.
9
financial areas covered
Who made the change
When it happened
Before and after values
Filter by area, page through history and print the view. Automated actions are labelled “System”.

Audit trail
Traceability is designed into the flow.
The audit page is the visible end of a wider financial-control story.
Version the rule
Dated company settings preserve the rule effective for the period.
Calculate pay
Clockings, dated rates and approved deductions create explainable lines.
Lock the run
The calculation and its export dimensions stay historically stable.
Export evidence
The Intacct journal uses the account codes captured for that run.
A readable audit example
Pay period status: open → calculated
Inserts, updates and deletes are recorded. System-generated entries remain distinguishable from a signed-in person’s changes.
03 · Marketing pack
The same platform, ready to share.


13 pages
A branded A4 portrait pack with a cover, contents, one page per platform area, roadmap and back cover.
8 areas
62 features
26 automations
Use it after the live walkthrough, or print it for stakeholders who were not in the room.
Marketing pack
The public story matches the build.
One shared feature source
The homepage and feature pack use the same structured feature list, so counts and descriptions stay aligned.
Accurate prototype language
RBAC is described as a go-live step, and the kiosk photo is for manager review—not automatic face matching.

The route forward
Decision-led, not assumption-led.
The prototype is functionally presented as a prototype; client inputs and go-live controls remain explicit.
Confirm
- Record the seven open answers
- Confirm real rates, rules and data
- Supply the official logo and sender address
Control
- Remove temporary role buttons
- Define and test RBAC
- Enable sign-in controls and schedules
Share
- Publish the approved prototype
- Present with this guided deck
- Share the marketing pack and decision log
Ready when you are
Let’s walk
the prototype.
Decisions, evidence and the platform story—all in one presentation flow.