Field staff
Submit RFIs referencing the relevant drawing or spec, and confirm when an answer resolves the issue.
An RFI sent by email gets buried in someone's inbox, so a question that's blocking work on-site sits unanswered because nobody's tracking response deadlines. Build a system where an open RFI is always visible until it's actually resolved.
An RFI sitting in someone's inbox looks the same as every other email, regardless of how much site work it's blocking. Without a tracked deadline and visible open status, urgent questions get answered on the same schedule as routine ones.
Route RFIs with a response deadline that escalates when it's missed, and require field confirmation before an RFI can close.
Submit RFIs referencing the relevant drawing or spec, and confirm when an answer resolves the issue.
Respond to routed RFIs within their tracked deadline.
An open-RFI dashboard, and response-time reporting across the project.
RFIs, drawing/spec references, responses, closure status.
Response-due reminders, overdue-RFI escalation, and closure confirmation.
Document storage, and email notifications. See supported integrations.
Discipline-specific routing rules, and response-time SLAs by RFI priority.
Roles and permissions you define, on infrastructure P2HS secures and audits. See security & compliance.
Deploy as a securely hosted application on your own domain. See hosting & domains.
Connect GitHub and keep developing the application yourself. See how code ownership works.
General contractors and design teams that need RFIs tracked to a deadline, not lost in email.
Yes—give the architect, engineer, and contractor scoped access to the same RFI record.
RFIs and submittals are different workflows. Consider a similar dedicated tracking structure for submittal review if needed.
See how RFI management fits into the wider P2HS platform.
Describe the workflow. Review the foundation. Launch it on your own domain.