// Right checks, right people

Smart approvals.
No more “who signed this off?”

Variations get agreed on site. Applications get submitted at month end. Invoices go out against both. DuoApp routes each one through the people who actually need to approve it - in order, on the record, with everything timestamped - so nothing gets paid or promised on a verbal.

Step by step
In the order you set
Per project
Custom approvers
From site
Raised on a phone
Full trail
Names, times, notes
Every approval carries who asked, who agreed, when, and what changed - so the Friday afternoon email hunt stops happening.
// How it works

Set the route once. It runs itself.

01

Set your approvers

Choose who signs off what, per project and per type - variations, applications, invoices, timesheets. Different jobs can have different routes.

02

Someone raises it

A site manager raises a variation from their phone with photos and notes attached, or an application is generated from the work that's actually been done.

03

It goes to the right person

DuoApp routes it to the first approver, notifies them, and holds it there. No group email, no wondering whose desk it's on.

04

It's on the record

Every step is stamped with the name, the time and any notes - so the trail is already there when somebody queries it months later.

// Why it matters

Why it matters.

Nothing sits in someone's inbox

Each approval has a named owner and a visible status, so you can see at a glance what's waiting and on whom. The list keeps itself current as colleagues sign things off, so nobody spends time on something that's already been dealt with.

Site can raise it there and then

Variations get captured at the moment they happen, with photos, instead of being remembered wrongly three weeks later.

Disputes have an answer

When a client queries a variation or a subbie queries a deduction, the timestamped record of who agreed what is already in the system.

Different jobs, different rules

Approval routes are set per project, so a small refurb doesn't have to follow the same chain as a multi-plot programme.

// In practice

What runs through approvals.

Variations

Raised from site with photos and notes, priced, and agreed before the work goes ahead.

Applications for payment

Built from the work recorded on the job, then routed for internal sign-off before submission.

Invoices

Approved against the application and the contract, with CIS and retention already applied.

Timesheets

Hours checked and approved by the right manager before they reach payroll.

Approvals connect to the work they came from - so a variation, the application it lands on and the invoice that follows are the same thread. Not three systems and a phone call.
// Questions

How it works in practice.

Can different projects have different approvers?
Yes. Approval routes are set per project and per type of item, so a small refurb can have a single approver while a large programme runs a multi-step chain.
Can site staff raise a variation from their phone?
Yes. On-site users can raise a variation with photos and notes from the mobile app at the moment it happens, and it enters the approval route immediately.
What record is kept?
Every step carries the person's name, a timestamp and any notes they added. That record forms part of the project's audit trail, so it is already there when a client or subcontractor queries something later.
Does an approval block the work or the payment?
It depends what you route. Variations are typically approved before the work proceeds, while applications and invoices are approved before they go out - so nothing is submitted or paid on an unrecorded verbal agreement.
Does this work with CIS and retention?
Yes. An approved application flows into an invoice with CIS deductions and retention already applied, so the approval and the money are the same record rather than two.

See approvals on a real variation.

Bring a live job and a genuine variation, and we'll wire the approval route up with you in 30 minutes.