BusyIncorporated
BUSYIndustries / Construction
Every submittal and RFI,
worked before the call.
Items go quiet in a submittal log because everyone on the project is on a site somewhere. A Busy teammate works that log inside the record your team already keeps — Procore, the drawing set, Dropbox and the inbox — reviewing each item the day it posts and handing back memos, agendas and drafts. You sit down to the reviews already done and the open items already sorted. Everything stays inside the company: nothing ever goes to a sub, a vendor or the city.
The work
What is finished
when you open the project.
Submittal review
Pulled from Procore the day it posts and compared line by line to the spec section and the approved set. What comes back is a one-page memo with the markup attached, so nothing sits in the log waiting for someone to find an hour for it.
RFI review and tracking
The question read against the current drawings and the governing spec section, an answer drafted with the sheet and section it cites, and ball-in-court tracked until it closes. An RFI stops going quiet on its own.
Drawing-set review
Each revision checked sheet against sheet and against permit conditions, across architectural, structural and MEP. Every finding is placed on the sheet with its reference, which is how a conflict gets caught on paper instead of in the field.
Pre-call agendas
Open RFIs, pending submittals and last week's commitments, pulled fresh before every call, with the items blocked on you separated from the items that are not. You walk in already knowing which ones are yours.
Email drafting
Written from the thread, the drawings and the log, in the firm's voice. Every draft lands in your team's inbox; a person decides what goes out.
Site-diligence lookups
FEMA flood panels and zoning maps pulled from the official source, the zone, panel and effective date recorded, and the PDF filed in the project folder — where the next person to ask will find it.
The teammate
Roan works the documents
your projects run on.
A construction management associate for a builder or developer: submittals, RFIs, drawing sets, pre-call agendas and the email around them, pulled the day they post, checked against the governing documents, and returned to your team as memos and drafts. He holds the same projects month after month, so the reasoning behind an old revision is still in the file when it matters. He works with your team, and no one outside it.
Meet Roan →The boundary
Everything he writes
stays inside the company.
The question worth asking about any of this is what happens when a review is wrong — a spec section misread, a finding cited to the wrong sheet. Every deliverable names the document it was checked against, so a mistake is visible to the person reading it rather than buried in a summary, and the only place it can travel is your own team.
Subcontractors, vendors and the city never hear from a Busy teammate. Memos, agendas and drafts go to your team; when something should leave the building, a person reads it and sends it. That is the design, and it does not loosen with time.
- Every deliverable carries the document it was checked against
- Every finding cites the sheet, rev and spec section
- Findings go to your team and nowhere else
What the teammate may do
- Read Procore — submittals, RFIs, drawingsAlways
- Compare documents and draft the memoAlways
- File finished work in DropboxAlways
- Send email as himself to your teamAsk every time
- Contact a subcontractor or vendorNever
- Contact anyone outside the companyNever
Case study
A residential land developer
in the Southwest.
Roan sits on the development team's projects week to week. The work below is what he actually does there, on the cadence the projects set.
Every submittal and RFI reviewed against the drawing set, with the findings written up in a memo before the team sits down.
Built from the open items — RFIs, pending submittals, last week's commitments — and in the inbox the morning of the call.
FEMA flood panels and zoning maps pulled into the project folder as PDFs, with the zone, panel and effective date recorded.
Read-only in Procore and drafts-only in email. A person reads and sends anything that leaves the building.
Playbooks
Recurring lookups become
written procedure.
A recurring site-diligence job becomes a playbook: the source of record, the steps, the file naming, where the artifact is filed and how it comes back to the requester. The teammate writes and revises it as the job changes.
Playbook / FEMA flood map
The official FIRMette pulled for a property, with the zone, panel and effective date recorded — filed in the project folder and returned on the thread where it was asked.
Playbook / Zoning map
The jurisdiction's own GIS map of record, with the district and overlays noted — and the new jurisdiction retained, so the next run starts farther ahead.
Tools
The project record,
worked where it already lives.
| Service | What the teammate does with it | Access level |
|---|---|---|
| Procore | Submittals, RFIs and drawing sets | Read only |
| Gmail | Reads the thread, drafts the reply | Drafts only |
| Microsoft 365 | Word and Excel memos — real files | Read / write |
| Dropbox | Project files, specs and photos | Read / write |
| Phone and text | His own line, your team only | Internal only |
Security and permissions are set at the user level, the same way they are for any hire. See the full list on the connections page.
Capabilities
The equipment this work leans on.
Busy Browser
A real, signed-in Chromium browser with CAPTCHA handling and a residential IP — if it's on the web, she can get it.
Proactivity
She notices, schedules and follows up on her own — reports, reminders and checks that come to you.
MS Office & PDF
Word, Excel, PowerPoint, PDF — real files on a real desktop.
Agent Memory
One chronological memory that carries every channel, decision and correction forward.
Fit
Worth a conversation
if this sounds like your projects.
A good fit
- The submittal and RFI logs are the record, and items in them go quiet without anyone noticing
- Project documents live in Procore, Dropbox and the inbox rather than in someone's head
- You want the paperwork worked internally, with your team sending anything that leaves
Probably too early
- You want a teammate talking to subs, vendors or the city — that never happens here
- A project engineer already reviews every submittal the day it posts
- You are looking for another platform to log into rather than a seat on the project
Put a teammate on the log.
A thirty-minute intro covers the projects, the documents they run on, and what the first month of memos and agendas looks like.