For ID, renovation and D&B firms

Progress claim automation for renovation and D&B firms.

Lynqra builds systems for Singapore ID, renovation and design-and-build firms that draft each progress claim from your milestones, site photos and signed variation orders. You check and approve the claim, and the system tracks payment after it goes out.

Book a free consult All services for ID firms

Why progress claims go out late

A progress claim needs evidence from everywhere. The milestone list is in a spreadsheet. The photos are in three WhatsApp groups. The subcon invoices are in email, and the signed VOs, if they exist, are somewhere in a chat. Someone has to pull it all together, usually after hours, while the client asks what has actually been done.

With several jobs running, a claim slips by a week. Nothing dramatic happens. The cash just arrives a week later, on job after job.

What goes into a progress claim

Every contract is a little different, but a claim usually needs:

  • The contract sum and the payment stage being claimed.
  • The work done to date, with photos or a short site report as backup.
  • The approved and signed variation orders being billed this time.
  • What was claimed and paid before.
  • The amount now due and the payment terms.

If your contract falls under the Security of Payment Act

Singapore's Building and Construction Industry Security of Payment Act gives parties to construction contracts a statutory right to claim progress payments for work done, and a fast adjudication process when payments are disputed. BCA's Security of Payment page has sample forms showing what a payment claim and a payment response should contain.

Automation can prepare the draft and keep track of dates. It does not decide whether a contract is covered or what can be claimed. Check that against BCA's guidance and, if needed, with your lawyer.

How it runs

From a finished stage to a paid claim

The site team marks the stage done. The system gathers the backup and drafts the claim. A person approves before it is sent.

1

A stage is marked done

The supervisor marks the stage done on their phone and adds photos, the same way they would post them to the job chat.

2

The backup is gathered

Photos, site notes, subcon invoices and signed VOs for that stage are pulled into one place.

3

The claim is drafted

The claim is written in your format from the payment schedule, with the VOs being billed. Anything missing, such as an unsigned VO, is flagged.

4

You approve and it goes out

A person checks the amount and approves the claim. It is sent to the client and logged against the job.

5

Payment is tracked

If payment has not arrived by the due date, a polite reminder is drafted for your team to send.

What changes for the office

TaskTodayWith automation
Finding photosScrolling back through chat groupsGathered by job and stage
Billing VOsChecked from memorySigned VOs listed for the claim, unsigned ones flagged
Drafting the claimCopied from last month's claimDrafted in your format from the payment schedule
SendingWhen someone has timeReady when the stage is marked done, sent after approval
Chasing paymentWhen the bank balance looks lowReminder drafted when payment is late

The subcon side

Your own claims often depend on your subcons' claims and invoices. The same system can match subcon invoices to stages, so you can see what you owe against what you are claiming before you approve either. Our guide to the subcon and project billing handoff covers that step in detail.

What stays with your team

The amount you claim, how you handle a dispute, and every payment to a subcon or supplier. The system prepares the draft and keeps the paper trail. A person in your firm decides what goes out. For chasing payments that run late, see our guide to debtor chasing workflows.

How we work

Consult, build, then hand over

The same three steps for every firm. You know the scope and the price before any work starts.

01

Free consult

Bring one workflow. We map how it runs today, from the site to the client, and agree what to automate and what must stay with your team.

02

Fixed-scope build

You get a written quote and timeline. We build around your templates and the tools your team already uses, and add a small app only where something is missing.

03

Train and hand over

The new flow runs alongside your current one first. We train the people who will run it and watch the first jobs before anything expands.

FAQ

Progress claim questions

Does a claim go to the client without us checking?

No. Every claim waits for your approval before it is sent.

Can it handle a different payment schedule for each job?

Yes. Each job keeps the payment schedule from its own contract, and claims are drafted against that schedule.

What tools does this work with?

We usually build on what you already use, such as Google Sheets, Gmail and WhatsApp, and add a small app only where something is missing.

Does it tell us what we can claim under the Security of Payment Act?

No. It prepares drafts and tracks dates. Whether a contract falls under the Act, and what can be claimed, are questions for your contract and your lawyer.

How much does this cost?

The consult is free. If the workflow is worth building, you get a fixed-scope quote before any work starts.

Start with one workflow

Bring the quotation, VO, claim or update that takes your team the longest. There is no commitment, and a person in your firm stays on prices, payments and customer commitments.

Book a free consult