Learn LedgerCapture

From site work to payment evidence.

See how a daywork record moves from field capture to supervisor sign-off, then into office preparation without exposing field users to commercial values.

Evidence sequence

Capture, sign, prepare, replay.

  1. 1Capture
  2. 2Check
  3. 3Sign
  4. 4Prepare
  5. 5Replay

Workflow

The route from site record to office action.

Each step has a clear owner and a clear next action, so the record can move without asking field teams to become commercial administrators.

01

Capture the work

The site team records photos, quantities, notes, dates, and available location context while the details are still fresh.

02

Check the record

Missing information can be fixed before the record reaches the office and before memory becomes the only evidence.

03

Get sign-off

The supervisor signs, rejects, or returns the record with a clear reason so the next action is obvious.

04

Use external approval when needed

One-off approvers can use a scoped browser link without opening the office workspace or seeing commercial controls.

05

Prepare the office pack

Signed work moves into office queues for change packs, Applications for Payment, and supporting evidence.

06

Replay the trail

The team can return to who captured it, who checked it, what changed, and what supported the payment record.

Financial Firewall

The site can sign the work without approving the money.

LedgerCapture separates evidence from valuation. That keeps site approval practical and keeps commercial decisions in the office.

Foremen and site supervisors work with evidence, not prices.
Office users handle valuation, exports, payment applications, and change pack preparation.
Project assignment decides which field users can see each project.
Archived projects remain readable and no longer count against the live project limit.

Roles

Each role sees the work it needs.

Organisation access, project assignment, and commercial permissions stay separate so the right person can act without widening the Financial Firewall.

Office admin

Runs project setup, package recovery, valuation prep, exports, and payment-facing work.

Can

  • Open every active project in the organisation
  • Prepare commercial packs and payment records
  • Archive projects when package spaces need clearing

Cannot

  • Use field approval as a substitute for valuation review
  • Expose rates or totals to field roles

Site supervisor

Checks assigned project records and signs or returns evidence without seeing commercial values.

Can

  • Review assigned project daywork
  • Sign, reject, or return records with reasons
  • Keep the site evidence trail attributable

Cannot

  • See rates, totals, exports, or payment application values
  • Change organisation membership or package settings

Foreman

Captures assigned project work while the evidence is still fresh.

Can

  • Create daywork records on assigned projects
  • Attach photos, notes, quantities, and context
  • Fix returned drafts before resubmission

Cannot

  • Approve the commercial value of the work
  • Open projects they are not assigned to

Outcomes

What the team gets from the workflow.

The goal is simple: record work clearly, get it accepted quickly, and give the office the evidence it needs when payment gets difficult.

Fewer lost details

Capture happens while people still know what changed, who was there, and what needs to be signed.

Cleaner office queues

The office can filter signed work, group evidence, and prepare packs without chasing scattered messages.

Protected money controls

Rates, totals, exports, and payment-facing actions stay away from field roles.

Packages

Choose a package for the work you are running.

Start checkout from the package page, then create the workspace and invite your team.

View packages