PreflightTalk to Preflight

Payroll preparation & assurance

Payroll starts before payroll.

Find payroll risks earlier, with structured checks around the payroll system you already use.

Preflight is in early development and discovery. The workflows shown here describe a proposed direction, not live product functionality.

Illustrative payroll review

Example interface · proposed

Review in progress

Draft payroll check

Illustrative review · no real payroll data

Needs review

Inputs

Sources linked

Readiness

Check gaps

Draft

Compare

Example findings

!

Conflicting effective date

Source instructions need confirmation

Resolve
!

Expected change not matched

Check against the approved source

Review
Example only · proposed controlsOpen evidence →

Our services

Assurance across the payroll journey.

Payroll teams work across files, provider outputs and individual knowledge. Preflight is being designed to make preparation, checks and decisions more structured and traceable.

Proposed benefits: fewer last-minute payroll chases, less manual reconciliation, clearer accountability and stronger evidence for approval.

01

Prepare

Bring fragmented payroll inputs together, map them into a controlled dataset and keep their sources traceable.

Explore Prepare
02

Core

Check changes, variable pay, absence and confirmations before the payroll is ready to calculate.

Explore Core
03

Verify

Challenge a draft against confirmed instructions, source evidence and structured controls before sign-off.

Explore Verify
04

Evidence

Keep the source trail, control history, exceptions, reviewer notes and authorised decisions together.

Explore Evidence

Two assurance checkpoints

Check before. Challenge after.

Preflight is designed to wrap around your payroll engine: check whether inputs are ready, then verify the draft against confirmed instructions and evidence.

Before calculation · Core

Is this payroll ready to calculate?

The proposed Core checkpoint tracks employee changes, variable pay, absence and confirmations, surfacing missing inputs and conflicts for people to resolve.

ChangesVariable payAbsenceConfirmations

After draft · Verify

Does the draft reflect what was approved?

The proposed Verify checkpoint compares a draft with confirmed instructions, source evidence and applicable controls, making findings and limitations visible before sign-off.

Expected vs actualExceptionsSource evidence

Proposed product direction; Preflight is not yet a live payroll service.

Prepare · proposed direction

Many sources. One controlled handoff.

Payroll information can arrive in different formats, at different times and from different people. Prepare is being explored as a way to organise and map inputs while keeping source traceability and human review for ambiguity.

No silent guesses: conflicting dates, unclear mappings and missing approvals should be surfaced for an authorised person to decide.

Explore the proposed workflow

Illustrative preparation journey

Many sources → one controlled dataset

Concept

Could arrive from

HR exportOvertime workbookAbsence fileManager instruction

Proposed checks

01

Link each value to its source

02

Identify gaps and conflicts

03

Request human confirmation

Conflicting instructions? Stop and ask. Don’t silently guess.

Evidence-led accountability

Every check has a story. Keep the receipts.

A green tick isn’t enough. Evidence is being designed to preserve what was received, which controls were applied, what they could assess, who investigated a finding and exactly which version was authorised.

See the evidence approach

Illustrative evidence record

From a conflicting instruction to a reviewed decision

01

Original sources

Keep the received instructions and their source context together.

02

Control assessment

Record the check, its outcome and any limits on what it assessed.

03

Human resolution

Retain the authorised decision, reviewer and supporting evidence.

Source lineageControl historyReviewer notesAuthorised sign-off

Example of a proposed record, not a live audit or compliance service.

Why Preflight

Built for assurance, not another payroll calculation.

01

Earlier visibility

Surface gaps while there is still time to investigate.

02

Explainable findings

Connect each flag to the source or control behind it.

03

Human decisions

No silent guesses, automatic overrides or unverified sign-offs.

04

Works around your engine

Add assurance around existing payroll software, not another calculation engine.

For payroll teams working across too many places.

We’re speaking with UK payroll teams, bureau operators and finance professionals managing recurring changes, variable inputs, multiple source documents, external providers or growing assurance needs.

Join the conversation

What still needs chasing before payroll is ready?

We’re looking for candid conversations about payroll inputs, readiness checks, draft verification and the evidence teams need to sign off.

Talk to Preflight