These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Construction PM
- Features
- RFIs and construction risks
RFIs and construction risks
Route raised site issues and keep construction risk mitigation owned.
OverviewOpen RF is & Site Issues×
Construction PM · RFIs and construction risks
New
Open RF is & Site Issues
RF is site issues
| Issue key | Title | Severity | Construction project | Owner | Reported date | |
|---|---|---|---|---|---|---|
| IK-319 | Open rsi-383 | Critical | CP-8478 | TC-4227 | 06 Oct | |
| IK-925 | Open rsi-353 | High | CP-4295 | TC-3149 | 08 Oct | |
| IK-936 | Open rsi-615 | Medium | CP-5662 | TC-5283 | 12 Oct | |
| IK-833 | Open rsi-151 | Low | CP-2505 | TC-7187 | 21 Oct | |
| IK-944 | Open rsi-927 | Critical | CP-1585 | TC-8390 | 22 Oct |
6 of 6 records
IK-319RF is site issues · RSI-33346
CriticalTitleOpen rsi-383
Construction projectCP-8478
OwnerTC-4227
Reported date06 Oct
StatusOpen
What you can do
Put site uncertainty in the right record
An RFI or site issue belongs to a construction project. It records the title, severity, reporting date, reporter’s note, person who raised it and owner. Its status distinguishes Open, Triaged, in progress, Fixed, Verified and Closed. The site manager can work the open list before an unresolved question becomes a task delay. The Site Exception Triage page also brings fixed but unverified issues into the same operational review as overdue tasks and milestones.
A construction risk is a different record. It carries a category, probability, impact, numerical scores, rating, mitigation, identified date, project and owner. It may be Open, Monitoring, Mitigated or Closed. An immediate site question should not be buried in a risk register; a longer exposure needs an owner and mitigation even when no task is blocked today.
How the work is organized
- Raise with context. Link each RFI or issue to its project and give the owner enough detail to understand the site decision required.
- Triage from Open. Setting the issue to Open triggers triage. The workflow checks its current status and severity before moving it to Triaged and recording a receipt.
- Keep mitigation visible. Assign risk ownership and review probability, impact and mitigation as the site programme changes.
What to agree during setup
Agree who raises an issue, who sets severity and who becomes its owner. Define when a request for information should be handled as an RFI rather than a task or a risk. Set a practical review cadence for open and fixed-but-unverified issues. Agree who verifies a fix and what inspection evidence should accompany the decision. The status change after triage needs a human operating convention because the configured automation covers the Open-to-Triaged step.
For risks, define the meaning of Low, Medium and High for probability and impact in the context of the project’s programme. Decide which categories need escalation to the project manager and what constitutes an adequate mitigation. Record the owner and a concrete next action in the mitigation text.
Check the handoff on an actual case
During foundation work, a crew member finds a drawing conflict. They raise a site issue against the project and describe the conflicting location. The site manager sets High severity before the issue is set to Open. That status triggers the workflow, which moves it to Triaged and writes a successful receipt. The manager assigns the design coordinator as owner and follows the question through in progress and Fixed. The quality inspector checks the corrected drawing and records verification before the issue closes.
Now replay the triage step with a second issue that has no severity. The attempt must be blocked and a failed receipt must explain what happened. Replay it with an already Triaged issue; it must not create a second successful transition. If the drawing conflict threatens the programme beyond the immediate question, the project manager opens a separate construction risk with a Schedule category, owner and mitigation. Both records stay linked to the project but answer different questions.
What your team sees
- Open RF is & Site Issues — Raised questions needing severity, owner and initial triage.
- Issues Awaiting Triage — Open issues prepared for the configured transition.
- Leading Construction Risks — Open and monitored exposures with their rating and mitigation owner.
Follow the work through
RFI triage and verification follows the issue. Milestone and exception review shows when an issue joins the site delivery discussion.
What it keeps track of
Data model- RF is site issues
- RF is and site issues raised against construction work, with severity, owner and resolution status.
- Construction risks
- Construction risks with probability, impact, score and mitigation for the project risk register.
- Construction projects
- Construction projects and sites with contract value, programme dates and delivery progress.
- Trades crew
- Trades, site staff and crew available to construction projects, with trade and crew capacity.
- Inspection receipts
- Inspection receipts recording that an authorised construction operation was executed.
- Inspection evidence
- Inspection evidence, submittals, drawings and other documents attached to construction records.
Who uses it
Permissions- Site Manager
- , Quality Inspector, Project Manager, Crew Member.
- Crew members raise observations; the site manager triages; the quality inspector checks verification; the project manager owns wider programme exposure.
Set up Construction PM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.