For architecture firms
Construction administration, without the spreadsheet.
Agradium is the architect's record of construction. RFIs, submittals, ASIs, proposal requests, CCDs and change orders live in one place, the logs stay current on their own, and every document goes out in your letterhead.
- Excel export of every log
- Issued documents never change
- Built for small US firms
Why Agradium
A spreadsheet can't keep a contract record.
Most firms run construction administration on a CA log workbook and a folder of Word templates. It works until the project gets busy.
In the spreadsheet
In Agradium
- Document headers
- In the spreadsheet: The project, owner, contractor and contract date are retyped on every RFI, ASI and change order.
- In Agradium: Entered once on the project. Every document fills its header from there.
- Logs and totals
- In the spreadsheet: Each log tab is kept by hand, so the totals on two tabs can quietly disagree.
- In Agradium: Every log is a view of the same records, so every total agrees.
- Change order approval
- In the spreadsheet: A change order can be counted as soon as the owner signs, before the architect and contractor do.
- In Agradium: A change order counts only when the owner, architect and contractor have all signed.
- Overdue RFIs
- In the spreadsheet: Noticed when someone scrolls far enough down the log.
- In Agradium: Due dates and response times are computed, and anything overdue is flagged.
The product
Every CA log, in one place.
The documents your firm already issues during construction, each with its own log, all tied to the same project record.
RFIs
From the contractor's question to your reply. See when an RFI went to a consultant and when it came back, with response times and overdue flags.
Submittals
Logged by spec section, item and revision. Record the review action, from approved as noted to revise and resubmit, and keep every revision's history.
Change management
ASIs, proposal requests, contractor change order requests, CCDs and change orders, linked as one change from the first question to the signed order.
Field reports
Site visit reports with observations, photos and action items, and an issues log that tracks each item until it is corrected.
Meetings
OAC and pre-construction meetings with attendees, notes and action items, kept with the project they belong to.
Punch list
Items by room and location, with correction dates and the architect's check-off at the end of the job.
How it works
Enter it once. Issue it right.
Set up the project once
Enter the owner, contractor, consultants and contract dates. Every RFI, ASI and change order takes its header from here, so nothing is retyped.
Log the work as it happens
RFIs and contractor requests are numbered when you create them. ASIs, proposal requests and change orders stay drafts until you issue them, so numbers never skip.
Issue in your letterhead
Issuing renders the PDF in your firm's letterhead and stores it as the record. To correct an issued document, you void it and issue a new one.
Change management
One change, followed from question to signed order.
A change rarely starts as a change order. Agradium links every document a change produces, so the change order log, the change process and the contract sum always agree.
Architect's instruction
ASIProposal requestChange orderA proposal request follows when the contractor doesn't accept the ASI.
Contractor's request
Change order requestChange orderBecomes a change order once the owner and architect approve it.
Urgent work
Construction change directiveChange orderTakes effect once the owner and architect sign. Cost and time are settled in a later change order.
Contract sum math, done for you
Each change order shows the original contract sum, the net change from earlier orders, and the new contract sum and time. The next order starts where the last one ended.
Signed means all three
Totals include a change order only when the owner, architect and contractor have all signed. Voided orders never count.
Several changes, one order
Roll several proposal requests, contractor requests and CCDs into a single change order. Signing it closes every change it covers.
Your records
The architect's record, kept straight.
On every project your firm needs its own account of what was asked, answered, issued and signed, even when the contractor runs its own system.
- Issued documents never change
- The PDF is stored the moment you issue it. Later edits to project or party details never alter what you sent.
- Your whole CA log in Excel
- Export a project's logs to one Excel workbook at any time, a tab for each log. Your records are never locked in.
- Numbers you can rely on
- Numbers are assigned per project and per document type, with no gaps and no duplicates.
- Private to your firm
- Every record and file belongs to your firm alone. Files are stored privately and opened through short-lived links.
Questions
Frequently asked questions
Who is Agradium for?
Architecture firms in the United States that run construction administration themselves: the project architect or CA manager who keeps the RFI, submittal and change order logs.
How is Agradium different from Procore?
On most projects Procore is the general contractor's system. Agradium is the architect's own record of what was asked, answered, issued and signed, so it is useful even when the contractor runs Procore.
Will our documents still look like ours?
Yes. Every PDF carries your firm's letterhead and the project header, for the documents you already issue: RFIs, ASIs, proposal requests, CCDs, change orders and field reports.
Can we take our data with us?
Yes. A project's logs export to one Excel workbook at any time, and every issued document is kept as the PDF you sent.
What happens in the demo?
A 30-minute call. We walk through a project from the first RFI to a signed change order and answer questions about how your firm runs construction administration today.
See your next project in Agradium.
A 30-minute walkthrough, from the first RFI to a signed change order.