The pay application arrives as a summary. The schedule of values, approved change orders, waiver, insurance certificate, and field tickets arrive on five different clocks.
Construction & Contracting
The pay application says ready. The lien waiver says not yet.
For project operations, project accounting, controllers, and project executives.
See the whole payment package — the schedule of values, the approved changes, the waiver, the certificate, the inspection — and exactly which piece has not arrived yet.
Works with
subcontracts · pay applications · schedules of values · change orders · lien waivers
Where the time goes
The hard part is finding the complete picture.
Compliance is a folder per sub, and the certificate that expired last week looks exactly like the one that did not.
Someone rebuilds the binder by hand, and the blocker surfaces only after the packet reaches accounting or the owner.
What reviewers see
One prepared review—not another packet to decode.
Contract sum, billed to date, approved change orders, waiver amount, and required support — lined up against the milestone they belong to.
Redwood Civic Center
Pay Application #7
Pay Application #7
Payment package
Required support
Schedule of Values · SOV-07.xlsx
Approved Change Orders (2) · CO-14.pdf, CO-15.pdf
Conditional Lien Waiver · Waiver-07.pdf
Insurance Certificate · COI-Redwood.pdf
Inspection record — not received
Package fields
Current contract sum
1,428,000.00
PAY-07 · p.1
Revised contract total
Disagrees with approved changes
PAY-07 · p.1
Current payment due
184,220.00
SOV-07 · summary
Conditional waiver amount
179,220.00
Waiver-07 · p.1
One item is open by disagreement, one by absence. Both stay visible.
In the example binder: the revised contract total does not match the approved change orders, the conditional waiver covers a different amount than the payment due, and the inspection record is missing.
What Alembic handles
Move preparation out of the review queue.
Alembic files each project document against the milestone it supports, so the binder assembles itself as the pieces land.
Schedule rows, approved changes, waiver amounts, and insurance periods come back structured, with arithmetic and completeness checks against them.
What is missing stays listed, with an owner. Entitlement, sufficiency, and payment release stay with your project accountant.
The accuracy question
We show you where we are unsure.
What this means for your team
A packet that only looks complete is the most expensive thing in this workflow, and Alembic will not hand you one. Where an amount traces back to a page, that page opens beside it. Where it does not, the record says so. A waiver that disagrees with the payment due stays a disagreement, and a required document that never arrived stays missing — visible, dated, owned — until someone decides what to do about it.
- The extracted amount and its source page, one click apart, wherever a reliable match exists.
- Missing support is shown as missing. It is never inferred to be satisfied.
- No score to interpret. Every item is prepared, open, or decided by someone with a name.
Before you build a business case
Measure your own preparation work first
How to calculate your own baseline
Packets per month, minutes actually spent preparing each one, loaded hourly cost of the people doing it. That is your current cost of preparation, and it is usually larger than anyone expects.
Set it against the review effort you expect to keep, and put software and setup cost in the same view. Illustrative, not guaranteed: this is a capacity scenario, not a promised savings rate.
Where the line sits
What stays human
- Alembic does not decide entitlement, percent complete, waiver sufficiency, statutory compliance, or payment release.
- Required-document and packet-completeness rules are set up for your contracts, projects, and jurisdiction. There is no built-in compliance ruleset.
- A named construction platform needs an adapter you configure. CSV, REST API, and signed webhooks are the supported primitives.
Construction & Contracting workflow questions
Does a complete packet mean the pay application should be approved?
No. Complete means the required support is present, or its absence is visible. Entitlement, sufficiency, and payment release still belong to your project and finance roles.
Can the workflow match how our projects actually run?
Yes. Document vocabulary, required-document checks, structured fields, review guidance, and outcome labels are all yours to set.
Can this feed our current systems?
CSV, REST API, signed webhooks, and generic HTTPS destinations, subject to plan. A named construction platform needs an adapter you configure — we do not imply native integrations we have not built.
What should a baseline measure?
Packet-preparation hours, missing-support loops, exception age, corrections, and the time between cutoff and review — on your own projects, before you model anything.
Show us what is slowing your team down.
We’ll help you start with the documents, checks, and review points your team already uses.