Submittal log across every GC
One log of everything you've submitted, to whom, when. Status pulled from each GC's portal where API access exists; manual where it doesn't.
For Subcontractor Project Managers
Every GC's portal, plus your own, on one screen.
Sub PMs juggle GC platforms by day. Submittals in Procore, RFIs in Sage, COs by email, pay apps in whatever the GC wants. AOS gives sub PMs one record that talks to all of them.
Submittals + RFIs across every GC
Change orders → pay app, end-to-end
Schedule of values from the contract
Daily logs that satisfy each GC
Your reality today
Eleven jobs. Eight GCs. Twelve portals.
Sub PMs run jobs across GC platforms they don't own. Each GC's portal is configured slightly differently. Your version of the truth is whichever portal you logged into last.
Submittal logs in their portal.
You submit through the GC's tool. The GC's tool emails you when it's reviewed. Your own log of where everything stands is your inbox.
CO chases are by email.
You issue a CO. The GC's PM says they'll get to it. You email weekly until it lands on a pay app. The aging clock isn't yours to enforce.
Pay apps in twelve formats.
Every GC wants a slightly different G703. Your cost record is one truth; you re-format it twelve ways every month.
Daily logs are an afterthought.
Each GC wants a daily log in their format. Your foreman writes one paper log. Your office types it into whichever platform the GC uses.
What AOS does for you
Sub PM workflow on one record.
AOS gives sub PMs the workflow they actually need — submittals, RFIs, COs, pay apps, daily logs — on one record, with output formats that match each GC's platform.
RFIs with the spec section
Issue an RFI tied to a spec section + drawing. The GC's PM gets the trail; your next pay app references it.
Change orders with aging
CO with aging clock against the contract. Push notifications to the GC PM when aging hits SLA. Land on the next pay app automatically.
Pay app in any GC format
Cost record in one place. G703 formatted to the GC's exact spec (Procore, Sage, Foundation, paper PDF). Pay app drafted from your job cost, not retyped.
Schedule of values from contract
SOV pulled from the contract amount + approved COs. Pay app line completion driven by the daily log + foreman tally. No retyping.
Daily log in GC format
One daily log, formatted for whichever GC needs it. Crew, weather, photos, conditions — entered once, output anywhere.
12 → 1
GC portals managed from one record
100%
Of COs with aging against the contract
0
Pay app re-typing per GC format
SOC 2-aligned
Aligned controls; field-level audit trail
Related roles on the trade
Built for the whole trade, not just one seat.
AOS gives every role on the trade 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 trade, or start at the subcontractors overview.
For the Subcontractor Owner / Executive →
Backlog, gross-margin by GC, bid hit-rate by trade, and cash position without waiting for month-end close.
For the Sub Foreman →
Geofenced timesheets, voice-to-log daily reports, drawing markup from the field, and a crew-of-the-day view tied to payroll.
For Sub Accounting →
Pay-app posting straight into the GL, retention rollforward by GC, AP automation against the PO, and 1099 prep.
Work alongside other parts of the project? AOS also fits commercial general contractors, owners and developers, and architecture firms on the same shared record.
One record across every GC you work with.
30-minute walkthrough. We'll wire up three of your active jobs and show you the submittal log, CO aging, and pay app formatting — live.