Reassessment, Updating, Documentation, and Recordkeeping
RBI is a living assessment
An RBI assessment has a shelf life. Reassessment is triggered by: management-of-change events (process, feed, materials, equipment modifications); inspection findings that differ from expectations (unanticipated damage, higher rates than modeled); failures or near misses; changes in consequence (population, occupancy, environmental sensitivity, product value); new knowledge about damage mechanisms; changes in codes or regulations; and the expiry of the planned reassessment interval.
Interval logic should follow both risk level and the rate at which the inputs are expected to change. High-risk items with fast mechanisms need short cycles; stable, low-risk items with well-understood mechanisms can go longer, provided the basis is documented.
Documentation
A complete record includes: scope and boundaries, methodology and version, team and qualifications, data used and its sources and confidence, assumptions, damage mechanisms considered, POF and COF results, risk ranking and criteria applied, inspection recommendations, mitigations recommended, the date, and the approval. Documentation must be sufficient for an independent reviewer to reproduce the analysis.
Recordkeeping
Records are retained per owner/user policy and applicable regulation, and must be retrievable and auditable. Version control matters: superseded assessments should be identifiable, not silently overwritten.
Traps
- Treating the reassessment interval as a fixed number for all equipment.
- Skipping the update when inspection finds unexpected damage, even though the finding changes POF.
- Recording only results without the assumptions and data sources.
- Losing traceability between a recommendation and the inspection actually performed.
Rule of thumb
If a new inspector could not repeat your analysis from the file alone, the documentation is incomplete.