US
UK
CH
AI agent at work · Project records / United States
Two RFI deadlines, traced back to the field report.
ArchX consolidated RFIs and changes, identified the follow-ups at the review date and kept the evidence behind each reported status in an editable register.
Inside the original output
| Record | Reported due date | At 13 October 2026 |
|---|---|---|
| RFI 015 · roof drain sump depth | 22 September | 21 days past, if still open |
| RFI 016 · shelving blocking height | 1 October | 12 days past, if still open |
| CR 003 · Extra shelving blocking | No due date supplied | Pending owner review |
The latest status evidence is the September 29 field report. Later closure records were not supplied; the register does not establish that either RFI remains open today.
What you can do with it
Chase the roof-drain and shelving responses, record any later closure evidence, and keep the pending change separate from signed changes.
The deliverable
Open what ArchX produced.
Original files from this run. No sign-up.
No prior register was supplied. This is a new consolidation of the available test documents, not an update to an unseen live register.
The starting point
What ArchX received.
Read the original request and file list
The request
Pay app #4 from Gulf Coast Builders for Riverside Library came in (Pay application/). Review it against the payment terms in our agreement excerpt (Contract/), the change order log and our field report from 9/29 (Site/). Recompute what's actually due, line by line, and tell me what I can recommend for certification and what I can't, and why. Then update our CA register with the RFIs and change items from the field report so we know what's overdue. Editable files, please.
The project files
- Site observation notes 09-29.docx
- Change order log.pdf
Try it on a job you know
Give it the task.
Then keep going.
Describe the work in your own words. Start with a project you know, inspect the result and ask for the next change in the same conversation.
Bring these files
A field report, change log and any existing RFI or change register.
What to check
Follow one RFI back to its source. Check its status, deadline and next action against what your team knows.
Before using client files, review how ArchX handles project data.
What could you ask next?
A suggested follow-up, once you have reviewed the result and added the new files:
I have added the latest RFI responses and change log. Update the register from those records and prepare a short follow-up list for the next meeting.
Download for Mac or Windows, connect your ChatGPT account or API key, then give ArchX this request with your files. AI usage runs through your connected account. Pricing and account requirements.