Calc-set version control
Structural, MEP, and specialty calcs versioned with issue dates. The set the AHJ saw is the set the field builds from.
For Project Engineers
Available on request
Calc sets, code compliance, and coordination — on one job record.
Project engineers juggle calc-set versions, AHJ requirements, and cross-discipline clashes while the GC's RFI clock keeps running. Engineer seats on AOS roll out with your firm on request — or when you're engaged on a GC's job.
Calc-set version control
Code compliance log
Cross-discipline review
RFI and submittal queue
Your reality today
Discipline by discipline, tool by tool.
PEs answer structural RFIs in one tool, MEP submittals in another, civil coordination on a shared drive. The cross-discipline trail — the thing that would prevent the next coordination failure — doesn't exist.
RFIs without discipline tagging.
GCs send RFIs through their tool. They don't tag discipline. The structural PE answers MEP RFIs by mistake; the MEP PE answers structural. The next clash is born.
Submittal calc trails lost.
You review a chiller submittal. Your calc check sits in your folder. The next PE doesn't find it. The next chiller submittal repeats the same calc.
Coordination on a shared drive.
Coordination drawings on a shared drive, named ad-hoc. The clash you flagged last week is in a PDF no one opened.
CA hours by discipline unknown.
Structural CA, MEP CA, civil CA — all roll up to one fee number. You can't tell the principal which discipline is bleeding hours.
What AOS does for you
Engineering CA on the same record as the architect and GC.
Project engineer workflows are available on request and roll out with your discipline leads. When you're on a GC's AOS job, calcs, RFIs, submittals, and coordination flags stay on one record.
Code compliance log
Code references tied to the permit set and AHJ comments. Open items age with the same SLA clock as RFIs.
Cross-discipline review
Coordination drawings on one record, with clash flags routed to the right discipline — before the GC's RFI.
RFI and submittal queue
Engineering RFIs and submittals threaded with spec section and drawing reference. Turn-time visible per project.
CA hours by discipline
Time entered once, rolled to CA hours vs. fee budget per discipline and phase.
Engineering issue log
Field and shop issues with photos, routed to the responsible engineer. Status tracked through resolution.
On request
A/E engineer seats roll out with your firm
On the job
CA workflows when engaged on a GC's AOS project
1 record
Calcs, RFIs, and submittals with the architect and GC
SOC 2-aligned
Security controls aligned to industry standards; full 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 Principal →
Practice dashboard, pipeline, billable hours, and profitability per project — when your firm runs on AOS.
For the Project Architect →
Drawing revision register, RFI and submittal tracking, and a design-issue log tied to the job.
For the Contract Admin →
Pay-app certification against the schedule of values, change-order review, and a full CA 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.
Keep engineering CA on the record, not in parallel folders.
30-minute walkthrough — calc-set control, code log, and coordination on the workflow we're rolling out with project engineers.