Home/Platform/Coordination
AQ.CRD.001

Every open item. Who it is waiting on.

RFIs, submittals and the questions between the companies on a project, each with who it is waiting on and for how long. The architect, the sub and the owner sign in free and see only what they owe. Keep Procore as the system of record, or let Coordination own the log, one project at a time. Integrations connects it to the systems you run and Exchange carries items to your partners' systems, so nobody on the job juggles another login.

Two people in high-visibility vests looking at a tablet together under a concrete structure
COORDINATION / 10.26 BETWEEN THE PARTIES

What you can do with Coordination.

01

See what is waiting on whom, across every project

One list of the items waiting on you, on your company, and on the people you are chasing, across every project you are on. Overdue first, then due this week, then later. One digest in the morning, a reminder when something goes overdue, and an escalation to the accountable person when it stays that way.

02

Work RFIs and submittals to a close

An RFI with its rounds, its responders and its official answer. A submittal with its revisions, its review steps and the stamped PDF, returned approved, approved as noted, or revise and resubmit. Packages and spec sections, required-by dates, and a log you can export with its filters kept.

03

Bring in the architect, the sub and the owner for free

Outside firms sign in with their own company's identity provider, or with a sign-in of their own, with nothing to buy and no password to rotate. Each sees only the items that name their company, and nothing else in your account. Every answer, review and upload is recorded with who did it, for which company, and when.

04

Keep Procore as the system of record, if you want

In mirror mode Coordination reads your Procore RFIs and submittals and writes RFI answers, new RFIs and closes back to it. Every mirrored item says so, and when it was last updated from Procore. When the team trusts it, a project moves to Coordination as the owner, one project at a time.

One list. Three ways an item gets on it.

Every item names who it is waiting on, and only that company is told. Coordination can own the log, mirror Procore while it stays the system of record, or take items from a partner's system through Exchange. All three land on the same list.

COORDINATION WAITING ON OWNED · MIRROR FROM A PARTNER
One open item between a general contractor, an architect and a subcontractor, showing who it is waiting on; and the three modes an item can be in: owned, mirrored from Procore, or from a partner through Exchange ONE ITEM · WHO IT IS WAITING ON SUBMITTAL Curtain wall shop drawings Revision two · due this week General contractor Logs it, forwards it, chases it Architect Reviews it, signs in free Subcontractor Submits it, signs in free SUBMITTED WAITING ON · ARCHITECT WAS WAITING ON · GC Each company sees only what it owes. The one the item is waiting on is told, not a distribution list. THREE WAYS AN ITEM GETS HERE OWNED Coordination keeps the log The item lives here. Responses, reviews and closes happen here, and the history starts on the day it was logged. MIRROR Procore stays the system of record Coordination reads RFIs and submittals from Procore and writes back the RFI actions Procore accepts. Every mirrored item says so, with the time it was last updated. A project moves to owned when you choose. PROCORE ⇄ FROM A PARTNER Through Exchange A partner on Procore, Autodesk Construction Cloud or Newforma logs the item in their own system. Exchange carries it in and carries your answer back, so nobody on either side takes on another login. THEIR SYSTEM ⇄ Whichever way it arrived, it is on the same list with the same "waiting on".
Left, one submittal moving between the companies on a job. Right, the three modes an item can be in.
Everything you are chasing, with who it is waiting on and a reminder one click away
An RFI with the question, the official answer and its sketch, ready to close
A submittal returned revise and resubmit, with the reviewer's comment and the next revision opened

Coordination for every company on the project.

The same app, used by the owner, the general contractor and the subcontractor. One example each.

For owners

The program's log, run by the owner

An owner runs the log across its program, every RFI and submittal from every contractor, with who each is waiting on and for how long. Closeout submittals, O&M manuals and warranties build the handover record as they come in, checked against the owner's own template.

For general contractors

One log, inside and outside the company

The project team runs the RFI and submittal logs. The architect answers in place, the sub uploads revision 1, and the project manager's morning starts with one list of what is overdue across every project. Procore stays the owner where you want it to.

For subcontractors and suppliers

Only what your company owes

A sub's office signs in and sees the submittals and RFIs that name their company, uploads the revision that was asked for, and sees when the review came back. Nothing else in the account.

Everything you need to close the open items on a project.

CRD.01 — Open items

One list of what is waiting on you

Mine, my company's, the items I am chasing, and overdue, across every project, with the waiting time and the due date on each row. Remind, request more time, or answer from the list.

CRD.02 — Waiting on

Companies first, then people

Every item names who it is waiting on, how long, and when it is due. Several holders show as one line. When nobody holds an item, the manager is asked to assign a responder.

CRD.03 — RFIs

Rounds, responders and the official answer

Questions with their rounds, the parties on each, the answer marked official, follow-ups, and a close. Draft an RFI from pasted text with Aquifer AI, and summarize a long thread before you close it.

CRD.04 — Submittals

Revisions, review steps and the stamp

Each revision with its review steps, the reviewer's stamped PDF or a stamp Coordination applies for you, and the return status. Revise and resubmit sends it back to the sub with what was asked for. Packages and spec sections organize the log.

CRD.05 — Outside users

Free for the architect, the sub and the owner

Invited by your company, signed in with their own identity provider or a sign-in of their own, and shown only the items that name their company. No seats to buy for the people you need answers from.

CRD.06 — Notifications

Notify by responsibility, not distribution list

The party an item is waiting on gets it, in a morning digest by default and at once when urgent. Overdue reminders on a cadence you set, and an escalation to the accountable person after a threshold you set.

CRD.07 — Mirror mode

Procore stays the owner until you say otherwise

Coordination reads from Procore and writes back the RFI actions Procore accepts. Each mirrored item carries its mode and freshness, and a project moves to Coordination as the owner one at a time, when you are ready.

CRD.08 — Partners

Items from a partner's system, through Exchange

A partner on Procore, Autodesk Construction Cloud, Newforma or their own Aquifer sends and receives RFIs and submittals through Exchange. Both numbers show, each field says whose it is, and you see what will cross to whom before anything is sent.

CRD.09 — One sign-in

No more juggling logins

Integrations connects Coordination to the systems your company runs, and Exchange carries each item to the system your partner runs. The architect answers in their system, the sub submits in theirs, and your team works one list, with one sign-in, instead of a login for every project and every partner.

CRD.10 — The record

A dispute-ready record for every item

A PDF per item and a ZIP of its files, with every response, review and change, who made it, for which company, and when, and each file's name, size and hash. Log exports to CSV or XLSX with the filters kept.

CRD.11 — Mentions and notes

Mention a colleague, keep a note internal

Mention people in a response or a review comment, only ever people who can already see it. Internal notes stay inside your company, and a mention never widens who can see an item.

CRD.12 — Meetings and handover

Decisions, action items and the closeout record

Decisions go in the minutes, and each action item becomes an open item owed by a person or company. Closeout submittals, O&M manuals, warranties and as-builts build the handover, exported to the owner's template and checked before it goes.

CRD.13 — In the field

Observations, punch and the daily log on a phone

Observations and punch items are raised in the Aquifer app on your phone, with photos and a drawing location, and worked like any other open item. The daily log is kept from the site in the same app.

Coordination works with the systems you already run.

All connectors →

From kickoff to first result in weeks, not quarters.

Step 01 — Mirror

Start in mirror mode

Connect Procore and Coordination reads your RFIs and submittals as they are. Your team gets open items and internal notes on top, notifications when you switch them on, and Procore stays the system of record.

Step 02 — Invite

Bring the other companies in

Invite the architect, the subs and the owner. They sign in free, with their own identity provider or a sign-in of their own, and work the items that name their company.

Step 03 — Own

Flip ownership when you are ready

When the team trusts it, we move a project to Coordination as the owner. Partners on their own systems keep receiving items through Exchange.

Something useful before any sales call.

Pick one live project. Coordination mirrors its RFIs and submittals from Procore, and you get the open-items list with who each one is waiting on and for how long, plus a morning digest for the people you name. Procore stays the system of record.

Open items on one project

Connect Procore for one project. Get every open item, who it is waiting on, and the morning digest.

  • One project's RFIs and submittals as open items, each with who it is waiting on, for how long, and when it is due
  • A morning digest for the people you name, and a reminder when an item goes overdue
  • What we would change first on the project, written down

Pricing follows what you use. Every part of the platform can be taken on its own and kept in sync with the systems you already run. Talk to us about pricing for your company.

Talk to us →

Common questions about Coordination.

FAQ.01

Do we have to leave Procore?

No. In mirror mode Procore stays the system of record. Coordination reads your RFIs and submittals from it, writes RFI answers, new RFIs and closes back, and says on every item that Procore owns it and when it was last updated. A project moves to Coordination as the owner when you choose, one at a time.

FAQ.02

What does an outside firm see?

Only the items that name their company, in the projects they are on, and nothing else in your account. They sign in with their own company's identity provider or a sign-in of their own, at no cost.

FAQ.03

How do people find out what is waiting on them?

A morning digest of their open items, at once when something is urgent, a reminder when an item goes overdue, and an escalation to the accountable person when it stays overdue past the threshold you set. The party an item is waiting on is notified, not a distribution list.

FAQ.04

What is the record if there is a dispute?

A PDF per item with every response, review and change, who made it, for which company and when, and a ZIP of its files with each file's name, size and hash. For mirrored items it states where its history begins.

FAQ.05

Can a partner on their own system take part?

Yes. A partner on Procore, Autodesk Construction Cloud, Newforma or their own Aquifer sends and receives RFIs and submittals through Exchange, so nobody on their side signs in to anything new. The item shows both numbers, each field says whose it is, and you see what will cross before it is sent.

Start with the open items.