Relay
RFI Coordinator
Routes, drafts, and chases RFIs. Finds precedent in past answers, specs, and drawings before anything goes out, and keeps ball-in-court honest.
Now
Drafting a response package for RFI-142
Coordinate · Keep it moving
RFIs, submittals, and meetings that keep moving.
Questions to the design team, submittal reviews, meeting minutes, and correspondence in one connected workflow. Relay drafts and chases RFIs, Vetta checks submittals against the spec, and Scribe takes the minutes, so nothing waits on someone remembering to follow up.
Tools in Coordinate
6 tools, one set of records.
-
RFIs
Questions to the design team, with ball-in-court tracking and precedent search.
Relay · RFI Coordinator
-
Submittals
Register, review workflows, lead times, and spec compliance checks.
Vetta · Submittal Reviewer
-
Meetings
Agendas, minutes, and action items that carry forward to the next meeting.
Scribe · Field Reporter
-
Tasks
Action items for people and agents across every tool.
-
Correspondence
Transmittals, notices, letters, and project email, captured and filed.
Atlas · Document Controller
-
Coordination Issues
Clashes and coordination items from the model and the field.
Atlas · Document Controller
RFIs that get answered in one read
Relay writes every RFI with one question, the exact location, the sheet and spec references, and a suggested resolution. Before anything goes out, it searches past answers, specs, and drawings for precedent.
- Ball-in-court tracking with automatic reminders
- Schedule and cost impact on every RFI
- Precedent search across every past answer
Submittals checked before they are sent
Vetta compares every product attribute to the governing spec paragraph and schedule, cites the paragraph for each deviation, and tracks lead times against required-on-site dates.
- Spec compliance checks with citations
- Lead-time risk measured against the schedule
- Review workflows with ball-in-court
Decisions, not data entry
When an agent needs a person, the request lands in their Inbox with the proposed plan, the impact, and why the agent is asking. Approve and run, edit the plan, or hand it off.
- Every proposal shows its plan, step by step
- Impact stated in schedule days and dollars
- Approve, edit, hand off, or decline
Agents in Coordinate
The agents who work here.
Agents work inside Coordinate with the same records and permissions as your team. You choose how much they do on their own.
- Working
- Working
Vetta
Submittal Reviewer
Checks submittals against spec sections and the drawings before they reach the design team. Flags every deviation with the paragraph it breaks.
NowChecking 23 73 13-01 AHU product data against spec
- Working
Scribe
Field Reporter
Builds the daily log from crew check-ins, gate deliveries, weather, photos, and voice notes. Takes meeting minutes and assigns the action items.
NowCompiling today’s daily log from 14 sources
- Idle
Atlas
Document Controller
Ingests drawing and spec sets, splits and names sheets, slip-sheets revisions, clouds the deltas, and keeps everyone on the current set.
NextWatching for new drawing and spec uploads
Can agents send RFIs to the architect on their own?
Only if you allow it. By default, anything sent to another company needs a person’s approval. Relay drafts the package and it waits in the approver’s Inbox until someone sends it.
How does Fulcrum track ball-in-court?
Every RFI and submittal records who holds it and since when. Overdue items are swept every morning, and reminders go out with the schedule impact attached.
Can architects, engineers, and subcontractors work in Fulcrum?
Yes. Design teams, owners, and subcontractors get access through permission templates scoped to the tools and projects they work on, so they answer RFIs and review submittals in the same place.
See Coordinate on your projects.
See Fulcrum on your kind of work. We will walk through your projects, your roles, and where agents can take the legwork off your team.