Fire Protection Engineering Editing and Proofreading Services

A rubber wedge holds the fourth-floor lobby door open in a building that has been occupied for eight years. The fire strategy assumed that door would be closed, or held by a device that releases on the alarm, and that a member of staff would sweep the floor before evacuating. Neither assumption reached the facilities manager, who arrived in year six and received a set of drawings and a maintenance schedule. Those two sentences sit in section 11 of a 140-page report that nobody now in the building has opened.

The documents we edit for Fire Protection Engineering

Fire strategy reports and design statements make up most of what arrives here, together with fire safety management requirements and building operator obligations. Means of escape and evacuation strategy documentation reaches us next, along with compartmentation and fire resistance schedules, smoke control and ventilation design documentation, and sprinkler and suppression system design narratives. We also edit fire engineering analysis and performance-based justifications, evacuation modeling and occupant behavior assumptions, submissions to the authority having jurisdiction, and information handover documentation. Fire risk assessments, remedial action plans, and operational procedures and staff instruction material are part of the same work. Our editors work on the part of a strategy that depends on people.

What the editing involves

Every assumption a strategy makes about management, maintenance, or human behavior belongs in one section that can be handed over intact and read as a list of duties. Section 11 of a 140-page report is not that section, because the person who needs it is a facilities manager rather than an approving official. We do not decide which assumptions matter or whether a design is sound. The fire engineer decides that, and our part is to see that each assumption appears in the handover section in the same words it carries in the body of the report.

Each assumption reads best as a task with an owner and an interval attached to it. "The corridor shall remain clear" describes a condition, while "the unit manager checks the corridor and records it at each shift handover" names a person, an action, and a frequency. We recast wording of that kind where the engineer's intent is plain, and we query it where the report does not say who is meant to act. Anything depending on staff numbers, training, or presence should state the number, the training, and the hours. The consequence of an assumption failing belongs beside it, in the engineer's own words, because a manager who knows which door protects the only stair treats that door differently.

The strategy should also record which assumptions cannot be relaxed without the fire engineer being consulted again. An operator reading section 11 in year eight has no way to separate a design-critical requirement from a recommendation unless the document separates them. Where the engineer has drawn that distinction, we keep it visible in the handover section and worded the same way in the body. Where the report is silent, we mark the passage and ask.

Confidentiality and the limits of our role

Everything you send us is treated in confidence, including designs, strategies, and building information. We are editors, not fire engineers or code consultants, and we offer no opinion on fire strategy, life safety design, or compliance. What we can do is make the human half of a strategy legible to the people who inherit it.