A vibration file should be assembled for the person who may have to defend the project after the site team, plant and subcontractors have gone. Its purpose is not to maximise paperwork; it is to preserve a reliable account of what was assessed, what actually happened, what was measured, how decisions were made and how concerns were resolved.
A vibration file should be assembled for the person who may have to defend the project after the site team, plant and subcontractors have gone. Its purpose is not to maximise paperwork. It is to preserve a reliable account of what was assessed, what actually happened, what was measured, how decisions were made and how concerns were resolved.
The file should contain three separated but cross-referenced strands: occupational exposure, third-party receptors and project execution. Separation protects worker health information and prevents building-monitoring data being mistaken for personal exposure evidence. Cross-referencing allows an event to be traced through activity, monitoring, decisions and any complaint.
The occupational strand should hold risk assessments and every material revision, with the reason for each change. Superseded versions should remain identifiable so that the project can show which assessment applied when a task occurred. A final document silently overwritten throughout the job cannot demonstrate what was known or decided at an earlier stage.
Tool and plant registers should identify the equipment, configuration and source of vibration information used in the assessment. The register should connect that information to the attachment, consumable, working condition and maintenance state rather than treating a model name as complete evidence.
Trigger-time records should identify the worker, task, equipment and actual operating exposure information needed by the assessment. Planned task duration or attendance on site is not automatically trigger time. Records should be sufficiently contemporaneous to reveal combined exposure from different tools rather than reconstructed from memory after the reporting period.
Training and briefing records should show the subject, presenter, attendees and task-specific content. A signature proves attendance, not implementation, so supervision records may be needed.
Health surveillance arrangements should be documented, but personal health information must be held confidentially and released only with the employee's written signed release. The project file may record that the required arrangement and referral route existed without circulating clinical material among project personnel. Occupational exposure and health-surveillance context is addressed on the hand-arm vibration page and the whole-body vibration page.
Equipment maintenance records should cover components that influence vibration, while calibration records should identify measurement equipment used. Maintenance and calibration are different and neither term should be used as a vague substitute for the other.
The third-party strand begins with the receptor inventory and the evidence used to keep it current. It should identify buildings, occupancies, sensitive operations, relevant equipment, points of contact and physical connections observed at the boundary. The sensitive receptor page explains how unusual occupancies and precision equipment alter project planning.
Pre-condition survey records should preserve the agreed scope, access limitations, method, photographs, location references, observations and issue history. Closing survey records should be capable of comparison with the opening record. Survey purpose and evidential limitations are covered on the pre-condition and dilapidation survey page.
Notification and complaint logs should record what was issued, to whom, by what route, and the response. A complaint entry should capture the reported location and effect, relevant activity, checks, findings, actions and closure status. The separate notification and complaints page covers the process.
Where monitoring is undertaken, the file should preserve the complete configuration history: monitor location, mounting method, orientation where relevant, channels, settings, communications arrangements, relocation, interruption and any change in configuration. Instrument identity and applicable calibration certificates should be linked to the period of use. A certificate belonging to a different unit or an instrument calibrated after an unexplained event does not establish the status of the equipment at that time.
Event records should retain alarms, peaks, annotations and investigated anomalies. If an event is classified as non-project, it should remain with the reason and supporting evidence recorded. Classification should distinguish evidence from inference.
Data gaps must be disclosed rather than hidden. The record should state when data were unavailable, why, which receptor and work period were affected, what activity occurred and what alternative evidence exists. A seamless chart created by omitting an outage is less defensible than a report that clearly describes its limitations.
The adopted criterion must be preserved with its provenance, version, protected receptor, selector and contractual or technical basis. No published United Arab Emirates instrument was located that sets a ground-borne vibration damage threshold for neighbouring buildings, none was located that imposes a general duty to monitor vibration on adjacent structures, and no UAE authority publishes a vibration trigger or alarm value. Recognised practice may be adopted contractually or specified project by project, but it must not be mislabelled as a UAE requirement. PPV criteria carry a frequency dependence.
The project strand should hold method statements as executed, not only the tender proposal or an early generic version. Revisions should show changes to plant, attachment, consumable, sequence, work location, ground treatment, isolation measures and operating constraints. The governing risk assessment should be revised when those changes affect its assumptions.
Activity logs should be time-aligned with monitoring and detailed enough to explain what happened at the source. They should identify the activity, location, plant and significant pauses, changes or unusual events. The activity log is the single most commonly missing document. Without it, a technically sound monitoring trace may show when an event occurred but not whether the project caused it or which method was operating.
Time alignment must be managed deliberately because instruments, site logs, photographs and complaints may use different devices. Clock checks and corrections should be documented; a monitoring event connected to the wrong activity can distort investigation and control decisions.
Decision records should state what was decided, who had authority, evidence considered, conditions attached and how the decision was communicated. Method changes should record why they occurred and whether the risk assessment, trial, monitoring configuration, neighbour notification or permit needed revision. Informal direction can be captured contemporaneously in a site record rather than left as an undocumented conversation.
Permits, approvals and relevant correspondence should be retained. Their presence does not prove that work followed the approved method, so they must be read with activity logs and executed revisions.
In the Emirate of Abu Dhabi, the Abu Dhabi Public Health Centre Code of Practice 53.1 OSH Construction Management Plan requires the plan to discuss vibration control measures and procedures for notifying potentially impacted receptors. It applies to all employers within the Emirate of Abu Dhabi. This is a planning and notification duty, not a numeric limit and not a monitoring duty. The associated project-plan requirement is examined on the construction management plan page.
A defensible record is contemporaneous, attributable, legible, complete, time-synchronised and unaltered. Contemporaneous means made at or close to the event. Attributable means the author or source is identifiable. Complete means relevant adverse and favourable information is retained together rather than selected to support a preferred conclusion.
Corrections should be shown as corrections, preserving the original entry, reason, author and timing where the system permits. Replacing a value without trace, retyping field notes into a clean sheet and discarding the original, or editing an annotation after a complaint can undermine confidence far beyond the individual entry.
Deleting an inconvenient monitoring event destroys the value of the whole set because a later reviewer cannot know what else was removed. The proper response is to retain the event, classify it transparently, state the evidence and preserve raw data. The same principle applies to aborted trials, failed controls, complaints, instrument outages and method departures.
Stable identifiers should link worker, tool, plant, receptor, instrument, activity and decision without exposing health information. A register should show version, status, owner and relationships between records.
Reports should answer the decision that caused monitoring or review to be undertaken. A routine report may need to show coverage, configuration, activities, events, gaps, criteria and actions. An event report may need a tighter chronology connecting source activity, receptor response, verification and decision. A complaint report should not be reduced to whether an alarm activated, because perception and a project alarm serve different questions.
Charts and summaries should be reproducible from preserved raw data. Any filtering, exclusion, aggregation or manual annotation should be described. Visual presentation must not conceal gaps or compress events until they disappear. The monitoring page covers configuration and defensible monitoring reports in detail.
Reports should distinguish fact, calculation, professional judgement and contractual decision. Where a criterion derives from DIN 4150-3, BS 7385-2, BS 5228-2 or another recognised source, the report should cite the controlled source and project adoption without reproducing numeric tables. Such material can be project practice but is not automatically a UAE requirement.
Close-out should include the closing condition survey where required, final monitoring report, resolution or clearly documented status of outstanding complaints, and handover of the indexed record. The closing survey should address comparable areas and limitations so that absence of access is not mistaken for absence of change.
The final report should describe executed works, monitoring coverage, criteria and provenance, significant events, data gaps, investigations, method changes and unresolved limitations. It should not claim that monitoring proves the absence of every possible effect. Its conclusion must remain within the evidence actually collected.
Handover should identify who receives the record, who remains its custodian, access controls, format, indexes and responsibility for later enquiries. Record retention periods are set by the contract and applicable requirements; no figure is published here. A claim can arrive long after the site has gone, when personnel, temporary records and subcontractor systems are no longer available. Planned custody is therefore part of project close-out, not an administrative afterthought.
Personal health information must be held confidentially and released only with the employee's written signed release. No published United Arab Emirates instrument was located that sets a ground-borne vibration damage threshold for neighbouring buildings, none was located that imposes a general duty to monitor vibration on adjacent structures, and no UAE authority publishes a vibration trigger or alarm value, so every adopted criterion must be preserved with its provenance. In the Emirate of Abu Dhabi, ADPHC Code of Practice 53.1 OSH Construction Management Plan requires the plan to discuss vibration control measures and procedures for notifying potentially impacted receptors — a planning and notification duty, not a numeric limit and not a monitoring duty. Record retention periods are set by the contract and applicable requirements.
ADPHC Codes of Practice 3.1 and 53.1; contract and applicable requirements govern retention
The activity log is most commonly missing. Without a sufficiently detailed and time-aligned account of plant, work location and method, monitoring events cannot reliably be connected to project operations or method changes.
No. It should be retained, classified and supported by the reason and evidence for that classification. Deletion makes the dataset selective and weakens confidence in every remaining event.
The report should disclose its timing, cause, affected receptor and relevant project activity, together with any alternative evidence. It should not bridge the gap graphically or imply continuous coverage.
Arrangements and completion status can be recorded, but personal health information must remain confidential and be released only with the employee's written signed release. General project access should not expose clinical information.
The contract and project governance should identify the receiving party and continuing custodian. Handover should define the indexed content, format, access controls and route for later enquiries so that evidence remains usable after the site team disperses.