RFI queue across every GC
One queue of RFIs across every project. Pull from GC platforms where API access exists; manual otherwise. Spec section + drawing anchored.
For Project Architects
RFIs, submittals, drawings — in one register.
Project architects live in construction administration: RFIs to answer, submittals to review, drawings to update, owner calls to take. AOS gives the PA one register across every active project, with the trail every party needs.
RFIs + submittals in one queue
Drawings register anchored to RFIs
CA hours vs. fee budget
Owner-facing record built in
Your reality today
Five GC platforms, one PA, one register that doesn't exist.
Project architects answer RFIs in five GC tools, review submittals in three different platforms, and maintain a drawings register that's whatever's on the office server. The trail is fragmented.
RFIs in five tools.
Each GC sends RFIs through their own platform. You answer in theirs. Your own log of what you answered, when, and what spec section it touched — lives in your inbox.
Submittals don't tie to the drawing.
You stamp a submittal. The drawing register doesn't get updated. The next PA opens A-301 r3 and the door hardware submittal that made it possible is gone.
Drawings register on a shared drive.
Drawings r3, r4, r5 — on the office server. Whoever has the most recent file is the one with the truth. The owner has r2 from January.
CA hours bleed unseen.
Site visits, owner calls, RFI answering, submittal review — they pile up, and at quarter-end someone tells you the CA fee is gone.
What AOS does for you
One register. Every project. Every GC.
AOS gives PAs one register across every project — RFIs, submittals, drawings, owner calls, CA hours — regardless of which GC platform the contractor is using on their side.
Submittal log + drawing link
Submittals tied to spec sections and drawings. When you stamp it, the drawing register reflects it. The next PA finds the trail.
Drawings register with revisions
Drawings register with overlay annotations and revision history. Owner sees the same r-number you do.
CA hours vs. fee budget
Time entered once, rolled up to CA hours vs. the fee budget for that phase. The bleed surfaces before the principal asks.
Owner-facing record
Owner gets read-only access to the RFI log, submittal log, drawings register. No more owner calls asking 'what's the status of...'
Design coordination
Structural, MEP, civil consultants all reference the same drawing. Clashes flagged before the GC's RFI lands.
5 → 1
GC platforms managed from one register
100%
Of submittals anchored to drawings
0
Drawings register lost on a shared drive
SOC 2-aligned
Aligned controls; field-level audit trail
Related roles on the firm
Built for the whole firm, not just one seat.
AOS gives every role on the firm a screen tuned to their workflow — sharing the same record with the GC, the subs, the owner, and the design team. See how it fits the rest of your firm, or start at the architecture firms overview.
For the A/E Principal →
Project backlog, fee-burn vs. budget by phase, write-down forecast, and the BD pipeline on one screen.
For the Project Engineer →
Calc-set version control, code-compliance log tied to the AHJ permit set, and cross-discipline review.
For the Contract Admin (CA) →
Pay-app certification against the SOV, CO review with cost-and-time impact, and a full design-issue audit trail.
Work alongside other parts of the project? AOS also fits commercial general contractors, owners and developers, and subcontractors on the same shared record.
One register across every project.
30-minute walkthrough. We'll wire up one of your active projects and show you the RFI queue, submittal log, and drawings register — live.