Record the decision basis
Keep the observed problem, assumptions, constraints, alternatives and reasons for selection.
Evidence and continuity
Documentation and Recordkeeping
Good records preserve the reasoning, evidence, approvals and responsibilities that disappear when a project team leaves.
- Risk-firstbefore product choice
- Evidencebefore claims
- Lifecycleinspection and maintenance
Who this is for
Use the guidance within a defined role and scope.
- Contractors and consultants
- Owners and facility teams
- Inspectors and municipalities
- Credential candidates
RSM scope
Independent education and standards-informed practice guidance.
External authority
Law, code, municipal rules, permits, manufacturer instructions and qualified professional decisions remain controlling.
Project responsibility
Owners, designers, contractors, inspectors and authorities retain assigned duties.
Core principles
Build practice around clear decisions and verifiable outcomes.
Separate fact from recommendation
Identify source documents, observations, calculations, opinions and owner decisions.
Protect sensitive information
Control access to personal, building and infrastructure information.
Keep records usable
Use clear file names, versions, dates, locations and handover indexes.
Practice detail
Project record set
A useful set may include intake, history, observations, drawings, CCTV files, survey information, permits, locates, product data, contracts, changes, inspections, tests, photos, deficiencies, invoices, warranty and owner instructions. Required records should be defined before work.
Practice detail
Version and change control
Documents should identify author, date, status and revision. Superseded instructions should remain traceable without being mistaken for current direction. Field changes need approval and an updated record explaining why they occurred.
Practice detail
Retention and handover
Retention periods depend on law, contract, insurance, programmes and policy. Owners need a concise index and access to records needed for operation and maintenance. Avoid retaining unnecessary personal information indefinitely.
Working sequence
A repeatable pathway from question to maintained outcome
- 1
Define required records.
- 2
Capture sources and decisions.
- 3
Control versions and changes.
- 4
Complete close-out and handover.
- 5
Retain securely and review access.
Avoidable failures
Common ways good intentions become unreliable practice
- Photos without address or date
- Final drawings omit changes
- Private files mixed with public records
- No named maintenance owner
Related pathways
Connect guidance to the next responsible action.
Official and institutional references
Check the controlling source.
RSM summarizes concepts for education. Use current official documents, local authorities and qualified professionals for project decisions.
Frequently asked questions
Important scope and application questions
Are photos enough to prove compliance?
Not usually. They need context, criteria, dates, location and supporting records.
Should every change create a revision?
Material changes affecting scope, safety, approval, performance or maintenance should be traceable.
Can RSM store project records?
Only through a future service with defined purpose, consent, security, retention and access.
What should an owner receive?
Final scope, approvals, equipment information, evidence, limitations, maintenance and warranty information.
Standards-informed practice
Use guidance as part of a complete responsibility system.
Connect knowledge with competent roles, approvals, records, inspection, maintenance and transparent communication.
Published: July 19, 2026 Last reviewed: July 19, 2026
RSM provides independent educational and standards-informed guidance. Confirm current legal, code, municipal, professional, product and project requirements with the appropriate authority and qualified people.
Next steps
Use the standards system
Move from a single topic to the wider guidance, evidence and feedback process.