Behind this section, a construction site at dusk: a concrete frame going up beside a tower crane. As the page scrolls, notes appear on the site for the handoffs Plunq caught: an overdue RFI chased, a superseded drawing with 14 people told, a defect past its due date escalated, a submittal release held until approval, and all four handoffs recorded in the site office.
UK construction · information management
The AI layer between your construction systems.
Your platforms only automate inside their own walls. The work that crosses them — approvals, drawing revisions, defects, the evidence trail — still moves by hand.
What Plunq does
Plunq runs it: follows the rule your team signed off, does the chasing, and records every step.
Tell us what to fix first.
Fewer chasesCurrent drawingsComplete record
Works with Procore, ACC, Outlook & Slack
Works with the tools your projects already run
Procore
Autodesk ACC
Outlook
Slack
Asite
SharePoint
Teams
Aconex
Dalux
PlanRadar
Bluebeam
Fieldwire
All integrations →
The problem
Your tools each hold part of the record. People hold it together.
Every project runs a CDE, a project system, email and chat. None of them owns the handoff between them — so a person does, until they don't.
-
01 · Approvals
Approvals stall in inboxes
A submittal waits on a reviewer who's on site. Nothing prompts them until the programme slips.
-
02 · Drawings
Superseded drawings stay in use
The new revision is issued. The old PDF is still in an inbox — and on the bench on site.
-
03 · Defects
Defects sit open
Snags get logged. Closing them depends on someone remembering to chase.
-
04 · Evidence
The evidence lives in email
Who was told, and when, is scattered across threads — rebuilt by hand when someone asks.
What it takes off your plate
Plunq does the chasing, across the tools you already run.
A rule inside your project system stops at its own edge. Plunq works in the space between your CDE, your project system, your inbox and your chat — and keeps the record.
-
01 · Approvals
Plunq chases the review
Holds the release until it's approved, and chases the moment a review runs over.
-
02 · Drawings
Plunq keeps site on the current revision
Everyone working from the old revision is told — and that is on record.
-
03 · Defects
Plunq closes the loop
Assigns it, tells the contractor, and escalates when it slips past its date.
-
04 · RFIs
Plunq gets questions to the right person
Sends each RFI to the discipline that answers it, then chases the answer.
The cost of the gaps
The handoffs are where the week goes
5.5hrs
Every week, per person
Spent looking for project information rather than using it.FMI / PlanGrid · Construction Disconnected
796
RFIs on a typical project
At around eight hours of review and response each.Navigant Construction Forum · CMAA
33%
Of quality problems
Trace back to coordination between teams and systems.Dodge Construction Network · 2024
Zutec
Revizto
Newforma
ProjectWise
Trimble Connect
Sage
Xero
QuickBooksA day on site
The review slipped. The chase went out first.
Plunq follows the rule your team signed off, does the chasing, and writes it down.
| Time | What happened |
|---|---|
| 09:00 | SUB-0217 passes its 10-day review window in Procore, still "Under review" |
| 09:00 | The three reviewers are chased by email, with a link to the submittal |
| 09:01 | #submittals on Slack is told the release is on hold |
| 14:20 | The façade consultant approves it |
| 14:20 | The release goes out and the chase is closed |
| 14:20 | Who was chased, when, and the approval are on record |
- 3Reviewers · chased automatically
- 5hFrom overdue · to approved
- 0Chasing emails · written by hand
- 1Record · ready for the audit
| Time | What happened |
|---|---|
| Thu 14:12 | Revision C02 is issued in Autodesk Construction Cloud |
| Thu 14:12 | The 14 people who had C01 are emailed the new revision |
| Thu 14:12 | #site-team on Slack is told C01 is superseded |
| Thu 14:12 | Who was told, and when, is on record |
| Fri 07:30 | The morning site brief lists C02 as the current revision |
- 14People · told the same minute
- 0Transmittals · sent by hand
- 1Current revision · on site next morning
Example days, shown for illustration.
Proof
When the auditor asks, the answer is already written down.
Every handoff is recorded as it happens: what started it, who was told, what they approved, and when.
-
01 · On record
Evidence without the digging
A timestamped trail, ready for audits, client reviews and handover.
-
02 · Your call
Nothing runs until you say so
Plunq suggests the workflow. Your team signs it off before it does anything.
-
03 · Your tools
Nothing to migrate
Works alongside your CDE and project system. Logins are encrypted; disconnecting deletes them.
Who it's for
Built for the people who answer for the record.
01
Information Manager
Only current, approved information reaches site — and you can prove it.
02
Document Controller
The register stays current without the download-upload-email cycle.
03
Quality & Compliance Lead
Defects close on time, and the evidence is captured as it happens.
04
Handover Manager
A complete record at handover, without weeks of re-keying at the end.
05
Project Engineer
RFIs and submittals reach the right person, and get chased.
06
BIM / VDC Manager
Issues and revisions reach the people who need them, whichever platform they use.
Does this replace our CDE or project system?
No. Plunq works alongside the tools your projects already run — Procore, Autodesk Construction Cloud, Outlook and Slack today — and handles the handoffs between them. Your CDE stays the source of truth.
Will Plunq change things on our projects without asking?
No. Plunq learns how your projects run and suggests workflows. Nothing runs until someone on your team signs it off — and from then on it follows the same rule every time and records every step.
How is this different from the automations built into our CDE or project system?
Those automate what happens inside one platform. Plunq works across them, so a handoff can start in your project system and finish in someone's inbox or on Slack. And it learns your conventions, instead of handing you a blank rule builder.
We already sync our project system with accounting. Is this the same thing?
No. Those tools keep field and finance data in step. Plunq works on the delivery side — approvals, drawings, defects and the evidence trail your information manager answers for.
Does my team need technical skills?
No. Plunq is built for information managers, document controllers and quality leads. You review each suggested workflow on a visual canvas, adjust it with point-and-click, and test it before it goes live.
What happens if something fails?
Plunq retries automatically, so a slow system or a brief outage doesn't lose anything. If a step still fails, the record shows exactly where and why, and you can retry the run from the dashboard.
How do you look after our logins?
OAuth tokens, API keys and secrets are encrypted at rest with AES-256-GCM, kept separate for each organisation, and only decrypted in memory when a step runs. Disconnect a tool and its stored credentials are deleted straight away.
We use a tool that isn't listed. Can you add it?
Probably. Procore, Autodesk Construction Cloud, Outlook and Slack work today. Asite, SharePoint and Teams are next, with Aconex, Dalux and PlanRadar on the roadmap. Tell us what you run when you request access.
What does it cost?
Pricing is set to your projects. We are working with a small group of early-access teams on preferential terms while they help shape the product.