What it does
A document product for a construction project team. Drawings are registered with their revision, and site teams always open the current one; superseded sheets are marked clearly. When the site raises a request for information (RFI), it is linked to the drawing and grid, similar past RFIs and the relevant spec clause are found, and it is routed to the architect or structural consultant with a due date. Answers are sent to everyone who holds that drawing.
The problem
Sites built from old drawing revisions, RFIs lived in email threads, and the same question was asked again a month later. Slow answers stopped work, and nobody could say how many RFIs were still open.
Approach
One register for drawings and one for RFIs, linked by drawing number and grid. AI suggests the related drawings, spec clauses and past answers, but a person writes every RFI and every answer. Overdue RFIs are escalated, and every revision change notifies the people who use that sheet.
- Input
- AI step
- Rules or code
- Person decides
- Result
Screens
Swipe sideways to see the whole screen.
Client work is shown under confidentiality agreements: no client names, and screens are recreated with sample data.
Stack
- Web app
- Semantic search (Gemini API)
- Document register
- Email notifications
Impact
Typical for systems like this.
