Site-readiness checklist before equipment installation

Why this decision needs structure

A smooth installation begins before the equipment arrives. A site-readiness review connects supplier data, facility work, delivery access, safety, schedule, and responsibilities so issues can be closed without holding engineers or equipment idle.

This guide does not replace an official method, risk assessment, manufacturer instruction, or applicable regulation. Use the cited sources as a starting point, then adapt decisions to the application, laboratory capability, and local requirements. The intended output is a requirements record that can be reviewed, tested, and updated.

A practical decision framework

Delivery and access

Record schedule, vehicle, unloading, lifts, doors, corridors, turning radius, floors, security, packaging, and storage. Treat this as a decision that can be verified, not a preference. Record the starting condition, acceptable value or limit, the person who confirms it, and the evidence required. Connect the decision to the method, safety, workload, and post-implementation work. Mark missing information as an open assumption so users, procurement, facilities, and suppliers do not interpret it differently.

Space and structure

Record footprint, weight, floor load, bench, level, service clearance, openings, anchoring, and lifting aids. Begin with evidence from real work, then separate mandatory needs from features that merely add convenience. Examine the effect on results, time, user competence, space, utilities, and recurring cost. Each conclusion should have a source, an owner, and a verification method so that later changes can be reviewed without reopening the entire discussion.

Utilities

Record type, capacity, quality, connection point, regulators, adaptors, isolation, labels, tests, and certificates. Consider normal operation, peak demand, credible failures, and conditions after future change. An agreement that works in only one scenario is fragile. Use numbers where available, state units and tolerances, and retain the decision rationale. This helps the team distinguish risks that require control from features that do not create practical value.

Environment

Record temperature, humidity, vibration, dust, light, fields, noise, heat, ventilation, and stabilization time. Treat this as a decision that can be verified, not a preference. Record the starting condition, acceptable value or limit, the person who confirms it, and the evidence required. Connect the decision to the method, safety, workload, and post-implementation work. Mark missing information as an open assumption so users, procurement, facilities, and suppliers do not interpret it differently.

Safety and permits

Record risk assessment, egress, emergency equipment, materials, waste, work permits, induction, and area control. Begin with evidence from real work, then separate mandatory needs from features that merely add convenience. Examine the effect on results, time, user competence, space, utilities, and recurring cost. Each conclusion should have a source, an owner, and a verification method so that later changes can be reviewed without reopening the entire discussion.

People, data, and acceptance

Record site contacts, operators, facilities, information technology, training schedule, documents, test samples, and acceptance criteria. Consider normal operation, peak demand, credible failures, and conditions after future change. An agreement that works in only one scenario is fragile. Use numbers where available, state units and tolerances, and retain the decision rationale. This helps the team distinguish risks that require control from features that do not create practical value.

Applying the framework to real work

A room can look finished while having the wrong outlet, a narrow doorway, an under-rated bench, or untested ventilation. Readiness should verify function and evidence, not appearance alone. Use a case like this in a short working session with users, method owners, facilities, safety, procurement, and technical support. Put known data beside open questions. This allows different expectations to be resolved before they become quotation revisions, rework, or downtime.

Maintain one decision table with requirement, rationale, evidence, acceptance limit, owner, and status. Do not combine facts, assumptions, and preferences in one sentence. When new information appears, update the relevant row and note its effect elsewhere. This simple discipline makes evaluation transparent and reduces dependence on meeting memory.

Mistakes to avoid

• Starting with a product name or feature list before agreeing the purpose and performance boundary.
• Using words such as good, complete, fast, or suitable without an acceptance measure.
• Ignoring user work, site conditions, recurring materials, documentation, and support after installation.
• Leaving decisions in conversation without a controlled document, owner, and review date.

Action checklist

• The delivery path is measured and confirmed
• Bench and floor suit the load
• Every utility is tested at the connection point
• Environmental conditions are within limits
• Work permits and safety controls are ready
• Technical contacts are present as scheduled
• Test materials and acceptance criteria are available

Bringing the decision together

A strong decision record need not be long, but it should connect the requirement, risk, evidence, and acceptance method. Start with the laboratory work, involve the right roles, and use data to narrow the options. When conditions change, revisit the documented rationale and limits rather than repeating an earlier choice by habit.

Implementation note

Before approval, arrange a cross-review by someone who did not prepare the first draft. Ask the reviewer to find missing units, limits that cannot be tested, terms with more than one interpretation, and dependencies without owners. Confirm that the requirement still matches the current method, workload, building conditions, user capability, and safety policy. Record the review outcome and next review date so the document remains active. If a change affects result quality or risk, reassess it before work continues.

Sources

1. Maintenance manual for laboratory equipmentWorld Health Organization
2. Selection of basic laboratory equipment for laboratories with limited resourcesWorld Health Organization
3. Design Requirements ManualNational Institutes of Health Office of Research Facilities
4. National Research Council Recommendations Concerning Chemical Hygiene in LaboratoriesOccupational Safety and Health Administration