Temporary vs. Final Resolution
Distinguish between interim field workarounds and permanent engineered solutions to prevent temporary fixes from becoming permanent.
About Temporary vs. Final Resolution
Construction sites are full of temporary fixes—shoring that stays up too long, provisional drains that become permanent, fire-stopping patches that never get replaced. The problem isn't that temporary solutions exist; they're often necessary to keep work moving while awaiting engineered designs. The problem is that temporary fixes tend to become permanent because no one documents the boundary between "interim workaround" and "final resolution." This document creates that boundary by requiring every temporary fix to have a named expiration date, a linked permanent solution, and a tracking mechanism that prevents it from being forgotten.
The framework distinguishes between two categories: temporary resolutions (interim measures that keep the project safe and moving) and final resolutions (engineered solutions that have been formally approved, inspected, and accepted). Every temporary resolution must reference the pending RFI, submittal, or change order that will produce the final resolution. When that approval arrives, the temporary fix is removed, the permanent solution is installed, and the closure is documented. This lifecycle approach ensures that no temporary fix silently becomes permanent.
Core Purpose & Scope
- To label every field fix as either temporary or final, preventing interim workarounds from becoming permanent.
- To link each temporary resolution to the pending approval (RFI, submittal, change order) that will produce the final solution.
- To assign an expiration date and tracking responsibility for every temporary fix until the permanent solution is installed.
Critical Field Review Questions
Before implementing any field fix, the team must answer these questions:
1. Is this fix temporary or final?
Determine whether the proposed solution is an interim measure to keep work moving, or a permanent engineered solution. If it's temporary, it must have an expiration date and a linked pending approval. If it's final, it must have formal engineering sign-off and inspection documentation. Never leave this classification ambiguous.
2. What pending approval will produce the final solution?
Every temporary fix must reference the specific RFI, submittal, or change order that will yield the permanent resolution. Record the tracking number, the expected response date, and the person responsible for following up. Without this link, the temporary fix has no path to closure.
3. When does the temporary fix expire?
Set a specific expiration date for the temporary fix—typically tied to the expected response date of the pending approval. Assign a named individual to check on the approval status before that date. If the approval hasn't arrived by expiration, the temporary fix must be re-evaluated for safety and extended or replaced.
Step-by-Step Implementation Guide
Follow these steps to manage the lifecycle of temporary and final resolutions:
-
Classify the Fix:
When a field issue requires immediate action, determine whether the proposed solution is temporary (interim workaround) or final (engineered solution). Document the classification, the physical description of the fix, and the safety parameters on the resolution form.
-
Link to Pending Approval:
If the fix is temporary, record the RFI, submittal, or change order number that will produce the final solution. Set an expiration date based on the expected response timeline. Assign a named individual to track the approval and follow up before the expiration date.
-
Close the Loop:
When the final approval arrives, remove the temporary fix, install the permanent solution, and document the closure. If the approval is delayed past the expiration date, re-evaluate the temporary fix for safety, extend the expiration, or escalate. Never allow a temporary fix to remain in place without an active tracking record.
Discussion & Verification Logs
No logs or comments recorded yet. Be the first to start the discussion!
Add to the Log