Lien Waivers and Retainage: One Is Tracked, One Is Not

These get discussed in the same breath and are not the same capability. ServiceIQ tracks retainage at Enterprise. Lien waivers it does not, and knowing that before closeout matters.

Retainage and lien waivers turn up in the same conversation so often that people assume one system handles both. It does not, and the gap is worth knowing before closeout rather than during it.

Retainage: tracked

ServiceIQ carries retainage and schedule of values at its Enterprise tier, alongside the AIA-style pay application. That means retainage runs as a ledger across applications rather than as a figure somebody recalculates each month and occasionally gets wrong.

Which matters more than it sounds. Retainage is typically the single largest sum a contractor is owed at any moment, and in most companies it is tracked in a spreadsheet maintained by one person who is also doing four other things.

The failure is rarely dramatic. It is a job that closed eight months ago where nobody chased the final release, discovered when somebody finally reconciles.

Lien waivers: not tracked

ServiceIQ does not publish a lien waiver workflow, and we are not going to imply it does.

A waiver workflow is its own discipline:

Conditional against unconditional, which are different legal instruments
Progress against final, at different points in the job
A different statutory form in most states, several of which mandate exact language
Notarisation where required
Collection down every tier of subcontractor and supplier before the GC releases payment

That is a compliance workflow with legal consequences, not a document folder. It belongs in construction accounting or in dedicated software such as Levelset or Siteline, and it stays there.

Why does the distinction catch people out?

Because both are closeout money problems and both get raised in the same meeting. "Can the system handle retainage and waivers" gets a yes, and the yes was about retainage.

The discovery usually happens at final billing on a job with eleven subcontractors, when somebody asks who has waivers outstanding and the honest answer is that nobody was tracking it centrally.

What can the CRM and field platform honestly do?

Hold the status, not run the process. Which is worth having, as long as nobody mistakes it for the process.

A property recording whether waivers are outstanding on a job
A flag on a pay application that should not release until they land
An alert when a job reaches final billing with waivers still open

That is status reflection. It catches the specific failure of nobody noticing, which is the most common one. It does not generate the right form for the right state, and calling it waiver management is how a contractor finds out at closeout that nobody was actually collecting them.

How to decide what you need

Two questions.

How much retainage is open right now, and who maintains that number? If the answer is a spreadsheet and one person, the ledger is worth buying on its own.
How many tiers of subcontractor do you collect waivers from, in how many states? One tier in one state is a checklist. Three tiers across four states is dedicated software, and the cost of getting it wrong is a payment that does not release.

The rule

Where money and statute meet, use the system built for it. Where the question is whether anyone is paying attention, a property and an alert will do.

Knowing which of those two you are solving is most of the decision.

Knowledge Base