1.1Opening scenario#

This chapter teaches how to think through a morning like that: what you own, what the law expects, what to do first and who to call. Dana’s three problems return throughout the chapter.

1.2Learning objectives#

After this chapter you should be able to:

1. Define facility management and distinguish it from property management and construction project management.
2. List the major responsibility areas of a facility manager and the systems they touch.
3. Explain the difference between a law, an adopted code, a consensus standard, guidance and district policy.
4. Decide, for a stated building and task, which requirement layers to check.
5. Run a first-30-days baseline walk and document what you find in a consistent format.
6. Rank problems by risk and apply the life-safety override.

1.3Why the subject matters#

Four reasons make the role important beyond keeping the lights on.

• People. Buildings hold children, patients, residents and workers. Failures of exits, alarms, air and structure fall on them first.
• Law. Owners and employers carry legal duties. Missed inspections, undocumented repairs and ignored notices become the evidence in a dispute.
• Money. Deferred maintenance compounds. A small roof repair left alone becomes wet insulation, damaged finishes and a possible mold response. Spending early is usually cheaper, though only a condition assessment can tell you for a given building.
• Mission. A school cannot teach in a flooded wing, and a plant cannot ship from a locked-out line. Facility work protects the work the building exists to support.

1.4Plain-English technical explanation#

Facility management is the coordinated care of buildings, grounds and their systems so the people inside can do their work safely and the owner’s investment lasts. A useful analogy is a ship’s chief engineer: the vessel is built by someone else, but the chief engineer keeps it running, safe and seaworthy every day until it is retired.

The title overlaps with two others. The table separates them by the question each role asks every day.

In practice they overlap. A school facility manager often acts as owner’s representative on a renovation, and a property manager schedules repairs. The roles differ in what they are accountable for.

1.5Applicable laws, codes, standards and official references#

A facility manager works under many layers at once. This table lists the ones that shape the role itself. Later chapters take each in depth.

1.6How to decide whether a requirement applies#

Ask six questions, in order, before you tell anyone something is required.

1. Who owns and operates the building? Public entity, private non-profit or private for-profit.
2. What is it used for? Occupancy and activity decide the fire, egress and accessibility rules.
3. When was it built or last altered? Construction date triggers exemptions and lead-paint rules; alteration triggers current-code duties for the altered area.
4. What work is happening? Routine maintenance, alteration, demolition and new construction fall under different rules.
5. What hazards are present? Asbestos, lead, chemicals, hazardous energy, refrigerants, water systems.
6. Who is paying? Grants, bonds and insurance add contract conditions.

Then use Tool R-1, the Requirement Finder, to list which layers to check, and finish with the eight-step protocol in the framework above.

1.7Building systems, components and terminology#

Ten system families recur through the book. You do not need to be an expert in each, but you must know what they are, who services them and when to call a specialist.

Key terms for this chapter, with fuller definitions in the glossary:

1.8Step-by-step inspection demonstration#

A baseline walk is the first pass through a building you do not know. Its goal is not to fix things. It is to find what could hurt people today, learn what records exist and decide what to do first. Do the walk with a second person, a flashlight, a camera or phone, a notebook or tablet, and a copy of the floor plan.

1.9Annotated visual#

1.10Common defects and their warning signs#

At the program level, trouble announces itself in the records and routines long before a building fails. Learn these signs.

1.11Realistic case study: The Quiet Panel#

What happened. A trouble signal began at the fire-alarm panel in a 1980s middle school. The panel buzzed during classes, so the front-office assistant silenced it. Each morning it buzzed again and was silenced again. A work order was created but never assigned because it was marked “non-urgent, no smoke.” Three weeks later, a contractor working in the ceiling above the cafeteria bumped a detector wire. At the next monthly drill, several horns in the east wing did not sound. The drill was ended and the district called the alarm contractor. The contractor found two separate faults: the original ground fault, and the damaged circuit from the later work.

What went wrong.

• No one owned the response to a trouble signal. It was treated as noise.
• The work order had no risk classification, so a life-safety item sat in the same queue as paint touch-ups.
• No impairment procedure: no interim measures, no notifications, no log.
• Contractor work above ceilings was not coordinated with the alarm system.

Model answer. A well-run program classifies a trouble signal as critical on day one. The front office has a one-page response: do not silence repeatedly, call the facility manager, who confirms the condition, calls the alarm contractor and, per the adopted fire code and the district’s impairment procedure, notifies the required parties and arranges interim measures. A work order carries a risk field. Contractors are briefed on life-safety systems before ceiling work. The drill found the second fault, but the first could have been fixed three weeks earlier.

1.12Sample inspection findings and documentation#

1.13Risk classification and corrective actions#

Risk ranking turns a long list into an order of action. Multiply likelihood (how likely harm is) by consequence (how bad it would be). Then apply the life-safety override: any condition that could prevent occupants from escaping or being warned, or that exposes people to a serious hazard now, is Critical regardless of score.

Corrective-action planning. Each finding needs an owner, a date, a method of verification and a closure record. “Fixed” is not closure. Closure is a record showing who verified the fix and how.

1.14Common mistakes and professional lessons#

• Treating a model code as law. It is law only if adopted, in the edition adopted, with local amendments.
• Fixing the symptom. Painting a stain or silencing an alarm hides the cause.
• Letting the loudest complaint win. Rank by risk, then explain the order to complainants.
• Going beyond your qualifications. Opening panels, sampling suspect material or climbing onto a roof alone are classic ways to get hurt.
• Not writing it down. Undocumented work cannot be shown to an auditor or defended later.
• Promising what you cannot do. Policies stricter than your capacity become liabilities.
• Skipping contractor orientation. Contractors damage life-safety systems and disturb hazardous materials when no one tells them what is above the ceiling.

1.15Field checklist: first-30-days baseline walk#

Tap an item to mark it done. Progress is saved in your browser if storage is available. This list is a starting point; edit it for your building and jurisdiction.

1.16Knowledge check and practical calculation#

Practical calculation: Facility Condition Index

FCI is a simple comparison number: FCI = deferred maintenance cost ÷ current replacement value. Lower is better. It compares buildings but says nothing about life-safety urgency.

Knowledge check

1.17Key takeaways#

1.18Further reading and official sources#

2.1Opening scenario#

This chapter explains the difference, and how to move a portfolio from the first to the second without a bigger budget.

2.2Learning objectives#

1. Describe the phases of a building’s life and who owns the decisions in each.
2. Distinguish preventive, predictive, corrective and reactive maintenance, and say when each makes sense.
3. Explain why some maintenance is a legal or contractual duty and not a choice.
4. Compare maintenance strategies using a simple expected-cost model.
5. Audit a preventive-maintenance program using records and a short walk.
6. Choose a strategy for an asset from its criticality and failure behavior.

2.3Why the subject matters#

• Failures cluster at the worst time. Heating fails in the cold snap and cooling fails in the heat wave, because that is when systems work hardest.
• Emergencies cost more than plans. Rush labor, expedited parts and rental equipment usually cost more than the same work scheduled. How much more depends on the asset and the market, which is why you measure your own.
• Some maintenance is required. Fire protection, pressure vessels, elevators and backflow devices often carry inspection duties set by law, adopted codes or insurers.
• Warranties and insurance can depend on it. Many equipment warranties require documented service. Missing records can void them.
• Lifecycle decisions are hard to reverse. Choices made at design and purchase set what the building will cost to operate for decades.

2.4Plain-English technical explanation#

The building lifecycle

A building passes through phases, and the facility manager is involved in all of them even though most of the calendar is spent in one.

Four maintenance strategies

A common planning framework is reliability-centered maintenance: for each asset, ask what its function is, how it can fail, what happens when it does, and which task, if any, is worth doing. The tools in this chapter apply that thinking at a beginner level.

2.5Applicable laws, codes, standards and official references#

Most maintenance is a management choice. The items below are the exceptions: places where law, adopted code, contract or insurance make it mandatory.

2.6How to decide whether a requirement applies#

For any asset, work down this list. The first yes that carries a legal or contractual duty sets a floor you cannot go below.

1. Is it a life-safety system? Alarms, sprinklers, extinguishers, emergency lighting, exit hardware. Expect adopted inspection and testing rules.
2. Is it covered by a state inspection program? Boilers, pressure vessels, elevators, amusement or pool equipment.
3. Does it contain regulated substances? Refrigerants, fuel, chemicals.
4. Is there a warranty or service contract with conditions?
5. Does your insurer or lender impose conditions?
6. Only then choose a strategy by criticality and failure behavior (Tool 2.2).

2.7Building systems, components and terminology#

Illustrative service lives help with planning. They are broad ranges, not promises. Use manufacturer data and your own history where you have it.

2.8Step-by-step inspection demonstration#

2.9Annotated visual#

2.10Common defects and their warning signs#

2.11Realistic case study: The January Boiler#

What happened. Westbank Annex ran on two 1990s boilers. For three years the annual boiler service was deferred to save money, and one boiler had been shut down in each of the last two heating seasons for a “minor leak.” In the first week of January a cold snap arrived. The remaining boiler tripped on low water, and the technician found that a feedwater valve and the water-treatment program had both been neglected. Scale in the unit had been building for years. With temperatures near freezing, the school closed for three days while a rental boiler was craned onto the roof. Pipes froze in one wing. The district paid rental, rigging, emergency labor, plumbing repairs and lost instructional days.

Root causes.

• Service was cut first because it left no visible effect.
• Equipment with redundancy was left with a single working unit and no one noticed.
• The state inspection certificate was current, so leadership assumed the plant was sound. A certificate shows a legal minimum, not reliability.
• No condition data was reported to the budget committee.

Model answer. Treat boilers as critical assets with preventive service and water treatment that cannot be deferred without a documented risk decision. Track redundancy as a status: “N+1 available” or “no spare.” Report to the board when redundancy is lost. Present the cost of deferral in dollars and in days of closure.

2.12Sample inspection findings and documentation#

2.13Risk classification and corrective actions#

Use the matrix from Chapter 1. For maintenance findings, ask two extra questions: is a mandatory inspection overdue, and does the asset have a backup? Either answer raises the rating. An overdue mandatory inspection of a pressure vessel is never Low, even if the vessel looks fine.

Corrective-action planning. Write maintenance fixes as recurring tasks with an interval, a responsible person, a record and a verification. A one-time repair fixes today’s problem. A scheduled task fixes next year’s.

2.14Common mistakes and professional lessons#

• Cutting preventive service first. Its savings are visible now and its cost arrives later and elsewhere.
• Closing work orders without checking. “Complete” should mean verified.
• Copying intervals from the internet. Read the adopted standard or the manufacturer manual.
• Confusing a certificate with reliability. A current certificate is a legal floor.
• Ignoring redundancy status. Two boilers with one broken is one boiler.
• Servicing everything the same way. Spend effort where failure matters.
• No data to defend the budget. Track repeat repairs, emergency cost and downtime.

2.15Field checklist: preventive-maintenance program audit#

2.16Knowledge check#

2.17Key takeaways#

2.18Further reading and official sources#

3.1Opening scenario#

This chapter shows how to build that evidence in a way a skeptic can check.

3.2Learning objectives#

1. Explain what an asset register is and list the minimum fields each record needs.
2. Describe the hierarchy from site to component and why it matters for reporting.
3. Run a basic condition assessment with a consistent rating scale.
4. Define deferred maintenance, renewal need and replacement value, and keep them apart.
5. Calculate and interpret the Facility Condition Index and explain its limits.
6. Rank buildings using both FCI and criticality, with life-safety items handled separately.

3.3Why the subject matters#

• Budgets are won with evidence. A board funds a number with a method behind it faster than it funds a complaint.
• Failures hide in unlisted assets. The fire pump nobody counted is the one nobody tests.
• Insurance, grants and audits ask. Lenders, insurers and funders often want inventories and condition information. What each requires depends on the contract or program, so read it.
• Capital planning needs a baseline. You cannot plan renewal of equipment you cannot age.
• Comparisons need one yardstick. Without a common rating scale, every building looks worst to the person who works there.

3.4Plain-English technical explanation#

What an asset register is

An asset register (or inventory) is a list of the things you maintain, with enough information on each to find it, identify it, age it, value it and schedule its care. It is a living record, not a one-time project.

Hierarchy

Group assets so they can be reported at different levels. A common structure runs site, building, floor or area, system, component. The same rooftop unit then rolls up to the roof system, the HVAC system, the building and the portfolio, depending on who is asking.

Condition assessment

A condition assessment is a structured walk and records review that grades each system or asset on a fixed scale and estimates the work needed to bring it back to an acceptable state. A property condition assessment done for a purchase or loan follows an agreed scope, often built on a consensus guide such as ASTM E2018. Check the edition and the scope your lender or owner actually requires.

The Facility Condition Index

FCI compares need to value:

Organizations define the numerator differently (some count only deferred maintenance, others add near-term renewals), and the rating bands also vary. Chapter 1 used the common teaching bands of under 5, 5 to 10, 10 to 30 and over 30 percent. Treat any published band as a convention. Always state your definition when you quote an FCI.

3.5Applicable laws, codes, standards and official references#

Inventory and condition work is mostly a management practice. These are the places where an outside rule or contract can set content or timing.

3.6How to decide whether a requirement applies#

1. Does a statute or rule require a record? Asbestos plans for schools, certificates for regulated equipment. Those entries are mandatory fields.
2. Does a contract or funder require a format or a schedule? Bond covenants, grant terms, insurance schedules.
3. Does your finance office have a capitalization policy? Align the register to it so the numbers reconcile.
4. Is there an organizational standard? A district rating scale, if one exists, beats a new one.
5. Only then choose fields, scale and cycle that fit the staff you have.

3.7Building systems, components and terminology#

Minimum fields for each asset record

3.8Step-by-step inspection demonstration#

3.9Annotated visual and condition tool#

3.10Common defects and their warning signs#

3.11Realistic case study: The Two Buildings#

What happened. Pelican Parish Schools had limited capital funds and two candidates for the first project. Magnolia Annex had an FCI of 14 percent and was the largest request. Bayou Crossing Elementary had an FCI of 9 percent, mostly in one system: a 26-year-old fire alarm panel with failing devices, and a sprinkler valve that the last inspection had tagged for repair.

A first ranking by FCI alone funded Magnolia. Marcus noticed that the Bayou Crossing items were life-safety findings from a recorded inspection, not renewal wishes. He moved them out of the FCI queue and into the risk queue, where they were scheduled for correction first. The sprinkler repair cost a few thousand dollars. The alarm replacement was phased across two years with interim measures approved by the fire authority.

What went right. The register held test dates and findings, so the life-safety items were visible. The FCI was still useful. It guided the larger renewal money.

What went wrong at first. The initial list used one score for everything. The correction was to separate “is anyone at risk now?” from “what is the long-run renewal need?”

Lessons. (1) FCI ranks money. Risk ranks urgency. (2) Keep findings and test dates in the register. (3) When a life-safety system is impaired, notify the responsible authority, use the interim measures it requires, and fix it first.

3.12Sample inspection findings and documentation#

3.13Risk classification and corrective actions#

Two separate questions run side by side:

• Risk now: Does the condition endanger people or stop the mission? Use the Chapter 1 matrix and its life-safety override. Act first.
• Money over time: How much renewal is coming, and when? Use condition grades and FCI to plan capital funds.

An asset can score high on one and low on the other. A rusty but redundant storage-yard fence has a poor grade and low risk. A new-looking sprinkler valve closed by mistake has a good grade and a high risk.

Corrective-action planning. For each finding record the cause, the fix, an owner, a date, how you will verify, and whether the cost belongs in the operating budget or the capital plan. Reassess on a stated cycle, and after major work.

3.14Common mistakes and professional lessons#

• Using original cost as replacement value. It makes old buildings look cheap to replace and the FCI too high or too low.
• Skipping the grade definitions. Without written definitions, grades are opinions.
• Letting FCI rank safety. It ranks money.
• Treating the register as a one-time project. Update on every install, removal and assessment.
• Quoting FCI without its definition. Say what is in the numerator and what bands you use.
• Trusting a lone assessor. Calibrate two people on the same room and compare.

3.15Field checklist: inventory and condition assessment#

3.16Knowledge check#

3.17Key takeaways#

3.18Further reading and official sources#

4.1Opening scenario#

This chapter gives you that formula, the rule that sits above it, and a way to write down the reasoning so an auditor or board member can follow it.

4.2Learning objectives#

1. Score a deficiency by likelihood and consequence on a defined scale.
2. Apply the life-safety override and explain why it sits above any score.
3. Name the other factors that raise priority: overdue mandatory duties, exposure, redundancy and cost of delay.
4. Recognize what an imminent-danger condition is and who must be told.
5. Rank a mixed list of deficiencies and defend the order in writing.
6. Avoid the common biases: loudest voice, easiest fix, newest item.

4.3Why the subject matters#

• Resources are finite. Every list is longer than the crew and the budget.
• The squeaky wheel is not the risk. Complaints measure annoyance. Risk measures harm.
• A recorded decision protects people and the organization. If a dangerous item was known and left, the record shows who knew what, when and what they did.
• Consistency builds trust. Staff accept an order they can see the reasons for.
• Money follows ranked evidence. A ranked list with a method is a budget request that survives questions.

4.4Plain-English technical explanation#

The basic score

Risk score = likelihood × consequence. Both use a 1 to 5 scale with written definitions.

Bands used in this book, as in Chapter 1: Critical at 20 or more, High at 10 to 19, Medium at 5 to 9, Low below 5. They are illustrative. Adopt your own organization’s bands if it has them and keep them stable over time.

The life-safety override

Adjusters that raise or lower priority

4.5Applicable laws, codes, standards and official references#

4.6How to decide whether a requirement applies#

1. Is there an order, notice of violation or imminent-danger finding? Follow its deadline. Notify the responsible people at once.
2. Does the condition touch a life-safety system? Apply the override. Make it safe first.
3. Is a mandatory duty overdue? Raise one band.
4. Score the rest by likelihood and consequence.
5. Adjust for exposure, redundancy, cost of delay.
6. Record the score, reasons and who approved.

4.7Building systems, components and terminology#

4.8Step-by-step inspection demonstration#

4.9Annotated visual and tools#

4.10Common defects and their warning signs#

4.11Realistic case study: The Silenced Panel#

What happened. A fire-alarm panel at Oakline Elementary kept going into trouble every few days because of a failing detector. A staff member silenced the trouble signal each time. After two months, the trouble light was simply normal to everyone in the office. A week before a state inspection, a contractor found that one wing’s devices had been disconnected from the panel for six weeks.

Ranking. By the score, a trouble signal looked like a Low maintenance item. By the override rule it was Critical: an alarm that cannot warn a wing is an impairment of a life-safety system. The district notified the responsible people the same day, posted a fire watch with the approval of the authority, repaired the detectors and recorded the dates.

What went wrong. Nobody owned the question “what does this light mean?” Silencing became the response, and silence became the habit.

Lessons. (1) A trouble signal is a message, not a nuisance. (2) Treat impairments as Critical until interim protection is in place and the authority is informed as required. (3) Train front-office staff on what to do, not just how to silence.

4.12Sample inspection findings and documentation#

4.13Risk classification and corrective actions#

Write each decision so a stranger can follow it. A short record has five parts:

1. What is the condition? Location, evidence, date.
2. Who or what is exposed?
3. Scores and adjusters with the override noted.
4. Action and owner: interim measure now, permanent fix later, with dates.
5. Verification: how and when you will check it worked.

Review the register on a schedule: Critical items daily until safe, High weekly, Medium monthly, Low at each assessment cycle.

4.14Common mistakes and professional lessons#

• Ranking by complaint volume. Complaints measure annoyance.
• Letting a high score overrule a clear override. Safety rules sit above the arithmetic.
• Scoring alone. Two assessors on the same item catch drift.
• Rating everything High. A list with no Low items has no priorities.
• Skipping the explanation to requesters. People accept a lower rank when they can see the reasons.
• Leaving cheap fixes in the queue. Do them now.

4.15Field checklist: building a defensible priority list#

4.16Knowledge check#

4.17Key takeaways#

4.18Further reading and official sources#

5.1Opening scenario#

This chapter covers both: how to compare options over their life, and how to build a budget that has a place for renewal.

5.2Learning objectives#

1. Distinguish operating expense (OpEx) from capital expense (CapEx) and say who decides which is which.
2. Explain lifecycle cost and total cost of ownership.
3. Compute a present-value comparison of two options over a study period.
4. Estimate an annual renewal reserve from replacement cost and useful life.
5. Build a facility budget with operating, reserve and contingency lines.
6. Write a budget request that a board or auditor can follow.

5.3Why the subject matters#

• Low bids hide high costs. Purchase price is often a minor share of what an asset costs over its life.
• Deferred maintenance is borrowing. The cost does not vanish. It returns later, usually larger and at a worse time.
• Budget categories steer behavior. If there is no renewal line, renewal is skipped until failure.
• Public and grant money has rules. Procurement and appropriation law, bond terms and grant conditions limit what you can buy and how.
• Boards need a number with a method. A structured comparison turns an argument into a decision.

5.4Plain-English technical explanation#

Operating versus capital

Lifecycle cost

Lifecycle cost (or total cost of ownership) adds up everything an asset costs over a chosen study period: purchase and installation, operation, maintenance, repair, replacement at end of life, and any residual value at the end.

Time value of money

A dollar next year is worth less than a dollar today. Present value converts future costs into today’s dollars using a discount rate. If the discount rate is 4 percent, $1,000 spent in a year costs about $962 today. Escalation (cost inflation) works in the opposite direction. This chapter uses a simple model with both, and says plainly when a number is an assumption.

The reserve idea

If every system in a building will need replacement someday, the budget should set money aside each year instead of waiting for a surprise. Summed across systems, that annual amount is a rough renewal reserve. Compare it with what you actually spend to see the gap.

5.5Applicable laws, codes, standards and official references#

5.6How to decide whether a requirement applies#

1. Who is the owner and what is its legal type? Public body, charter operator, private owner. Procurement rules differ.
2. What is the funding source? Operating budget, bonds, grants, insurance proceeds, reserves. Each has conditions.
3. Is the purchase above a bid or approval threshold? Ask procurement for the current limits.
4. Is it capital under your policy? Ask finance.
5. Does an emergency exception apply? Emergency purchasing is usually narrow and needs documentation. Ask before assuming.
6. Then compare options by lifecycle cost.

5.7Building systems, components and terminology#

5.8Step-by-step inspection demonstration#

5.9Annotated visual and tools#

5.10Common defects and their warning signs#

5.11Realistic case study: The Cheapest Roof#

What happened. Delta Ridge chose the lowest bid for a gym roof. The product had a 12-year life, but the specification said only “roof, complete.” At year 11 the roof began to leak. The district found that the original warranty had expired and that the manufacturer’s upkeep schedule had never been followed. A replacement ate the next year’s capital fund and delayed a boiler project that had been scheduled for that year.

What a lifecycle comparison would have shown. Over a 30-year period, the cheaper roof needed two replacements and more upkeep. The premium option cost about a third more at the start and less over 30 years under most reasonable assumptions.

What went wrong. The specification did not require a minimum life or a maintenance plan, and nobody compared total cost. The budget had no reserve, so the replacement landed on a project that was ready to go.

Lessons. (1) Write minimum life and warranty terms into the specification, within procurement rules. (2) Compare total cost, not price. (3) Fund renewal on a schedule, not on failure.

5.12Sample inspection findings and documentation#

5.13Risk classification and corrective actions#

Financial findings follow the same discipline as physical ones: state the condition, the exposure, the action, the owner and the check. Two rules apply:

• Life-safety first. Chapter 4’s override still applies. A budget gap never lowers the rating of an unsafe condition. If money is short, choose interim measures and escalate.
• Show the options. When asking for funds, present the full set: fix now, phase over years, interim measures, and do nothing. Include the consequence of each.

A good budget request has six parts: need and evidence; options compared; recommended option and its lifecycle cost; funding source; what happens if it is not funded; who is accountable for delivery.

5.14Common mistakes and professional lessons#

• Comparing purchase prices only. The cheaper asset may cost more over its life.
• Hiding assumptions. Write the discount rate, escalation and life, and test how the answer changes.
• Calling a repair capital, or a replacement operating, without the policy. Ask finance.
• Treating a reserve as spare cash. Reserves are earmarked for renewal.
• Splitting a purchase to dodge a threshold. It is a procurement violation in many places. Ask first.
• Asking for money without options. A board with one choice feels cornered. Give it the set.

5.15Field checklist: budget and lifecycle review#

5.16Knowledge check#

5.17Key takeaways#

5.18Further reading and official sources#

6.1Opening scenario#

This chapter is about writing and managing agreements so that paying for work and getting work are the same thing.

6.2Learning objectives#

1. Write a scope of work that names the equipment, tasks, frequency and deliverables.
2. Include response times, reports and acceptance criteria in a service agreement.
3. Check a contractor’s license, insurance and authority before work starts.
4. Track warranties so claims are made in time.
5. Score vendor performance with a consistent method.
6. Spot weak clauses in an agreement and know when to ask a lawyer.

6.3Why the subject matters#

• Most building work is outsourced. Fire protection, elevators, HVAC, roofing and many other systems depend on vendors.
• A vague contract cannot be enforced. If it does not say what, when and how well, there is nothing to hold anyone to.
• Required inspections are done by vendors. If the vendor skips a test, the owner still carries the duty.
• Warranties expire quietly. A defect found on day 366 of a one-year warranty is the owner’s cost.
• Insurance and licensing protect you. An unlicensed or uninsured contractor moves risk to the owner.

6.4Plain-English technical explanation#

Types of agreements

What a good service agreement states

1. Scope: which equipment (by tag or list), which tasks, and the standard each follows (manufacturer instructions or an adopted code).
2. Frequency and schedule: how often, in what window, with advance notice.
3. Response times: for emergencies, urgent and routine calls, with how they are measured.
4. Reports: written report after each visit, with findings, readings and recommendations. Payment tied to receipt.
5. Qualifications: licenses, certifications (for example EPA refrigerant certification for technicians), background checks where required.
6. Insurance and indemnity: types and limits, with certificates on file.
7. Pricing: fixed fee, rate sheet, parts markup, what is excluded.
8. Term and renewal: start, end, whether it renews automatically, notice to cancel.
9. Acceptance and remedies: how work is accepted, what happens if it is not done.
10. Records: who owns them and how you get them if the vendor leaves.

Verification and oversight

A contract is a promise. Verification is how you find out whether it is kept: read the reports, spot-check the work, compare invoices with visits and keep a scorecard. Do not pay for work you cannot show was done.

6.5Applicable laws, codes, standards and official references#

6.6How to decide whether a requirement applies#

1. Is the buyer a public body? Procurement and public-contract law may apply. Ask procurement.
2. Does the work need a license? Check the licensing board for the trade and job size. Verify the contractor’s license number and status with the board.
3. Does the work touch a regulated system or substance? Fire protection, refrigerants, asbestos, pressure vessels, elevators. Require the credentials the rule or the AHJ requires.
4. Does warranty coverage depend on who does the work? Using a non-approved servicer can void a warranty.
5. What does the insurer or lender require?
6. Then write the scope and the oversight plan.

6.7Building systems, components and terminology#

6.8Step-by-step inspection demonstration#

6.9Annotated visual and tools#

6.10Common defects and their warning signs#

6.11Realistic case study: The Warranty That Expired on a Tuesday#

What happened. Bluewater Elementary had a new roof installed under a two-year workmanship warranty. Leaks began in month 23. The facility lead noted them and planned to call the roofer after the holiday break. The break lasted three weeks, the warranty ended on a Tuesday in month 24, and the roofer’s response was courteous: the warranty was over, and the repair would be billed at standard rates.

What went wrong. Nobody tracked the end date. The leaks were noted but not reported in writing. The warranty required written notice within the term.

What a tracker would have shown. A 90-day alert in month 21 would have prompted a roof walk with the contractor, and any defect would have been documented while coverage was valid.

Lessons. (1) Track every warranty end date and set alerts. (2) Give written notice of defects inside the window. (3) Schedule an end-of-warranty inspection a few months before expiry.

6.12Sample inspection findings and documentation#

6.13Risk classification and corrective actions#

Vendor risk comes in four kinds. Rate each with the Chapter 4 method and note which are life-safety.

• Safety and compliance: a vendor skips a required test or works without a required credential. Treat as high or as the override if a life-safety system is affected.
• Performance: reliability and response fall short. Medium to high, by criticality of the asset.
• Financial: overbilling, cost creep, lock-in. Medium.
• Continuity: a single vendor holds knowledge and records. Plan for transition.

Corrective-action planning. Send written notices, give a cure period if the contract provides one, record responses, escalate to procurement or counsel before terminating, and line up a replacement for critical services. Do not withhold payment contrary to the contract terms without advice.

6.14Common mistakes and professional lessons#

• Paying without reports. No evidence, no payment, if the contract allows.
• Signing a vendor’s form unread. Have counsel review indemnity, renewal and liability terms.
• Skipping credential checks. Verify the license and insurance on the source, not from a copy the vendor hands you.
• Losing warranty dates. Calendar them with alerts.
• Letting the vendor define success. Write measurable standards into the scope.
• Single-source dependence. Keep records yourself and know your second choice.

6.15Field checklist: vendor and warranty review#

6.16Knowledge check#

6.17Key takeaways#

6.18Further reading and official sources#

7.1Opening scenario#

This chapter covers how to design work orders, keep records that stand up to questions and pick a few measures that change decisions.

7.2Learning objectives#

1. Describe the life of a work order from request to analysis.
2. List the minimum fields of a work-order record.
3. Identify which records are required by law and which are good practice, and look up retention periods at their source.
4. Compute and interpret core maintenance KPIs.
5. Spot misleading metrics and avoid gaming.
6. Design a monthly report that leads to a decision.

7.3Why the subject matters#

• Records are the evidence of due care. Insurers, inspectors, auditors and courts ask for them.
• Required inspections are only as good as their records. A test done and not recorded is, for most purposes, a test not done.
• Patterns hide in single repairs. Repeat failures show up only when jobs are recorded against assets.
• Budgets follow data. Chapters 3 to 5 rely on a register and cost history that work orders feed.
• What is measured gets attention. The wrong measure gets the wrong attention.

7.4Plain-English technical explanation#

The work-order lifecycle

A work order is a written record of a job: what, where, why, who, when and what happened. Every job, from a changed lamp to a roof replacement, follows the same steps in some form: request, triage, approve, plan and schedule, perform, verify and close, analyze. Triage assigns the Chapter 4 priority. Verification confirms the work met the request. Analysis feeds the register and the budget.

Minimum fields

Records

Beyond work orders, a facility keeps: inspection and test reports, certificates, permits, drawings and manuals, warranties, training records, incident reports and contractor files. Some are required by law with set retention periods. Others are good practice. Know which is which, and keep a retention schedule approved by your organization’s records officer or counsel.

KPIs

A key performance indicator is a number that tells you whether you are meeting a goal. A few examples:

7.5Applicable laws, codes, standards and official references#

7.6How to decide whether a requirement applies#

1. Is a federal rule already verified for this record? Use Tool 7.2 and read the source.
2. Is your organization a public body? A state retention schedule probably applies. Ask the records officer.
3. Is there an adopted code or AHJ requirement for the record? Ask the fire marshal or building official.
4. Does a contract, insurer or funder require more? Use the longest period.
5. Is a dispute possible? Hold the records and ask counsel.
6. Then set your own retention schedule and apply it consistently.

7.7Building systems, components and terminology#

7.8Step-by-step inspection demonstration#

7.9Annotated visual and tools#

7.10Common defects and their warning signs#

7.11Realistic case study: The Missing Months#

What happened. Cedar Hollow had good inspectors and poor paperwork. After a minor incident, the district’s attorney asked for three years of fire-protection records. Inspectors had done the work. Reports for four of the 36 monthly checks were missing, and the annual alarm test report for one year existed only as an email attachment that nobody could find.

What it cost. The incident itself caused little harm. The district spent staff time reconstructing records from vendor files, and the attorney advised that the gaps could weaken its position if the matter became a dispute.

What changed. The district created a shared records folder with a standard naming rule, made the vendor submit the report before payment, and added a monthly check that every required record for the month existed.

Lessons. (1) A record that cannot be found does not exist. (2) Tie payment to receipt of the record. (3) Check completeness monthly, not after an incident.

7.12Sample inspection findings and documentation#

7.13Risk classification and corrective actions#

Records findings carry two kinds of risk. First, a missing record may hide a missed test on a life-safety system. Treat that as a possible override until the test is confirmed. Second, a missing record is a liability and audit risk in itself. Rate it Medium unless an authority or contract makes it mandatory.

Corrective-action planning. For each gap: confirm the work was done, obtain or recreate the record without back-dating, note the date of the new record, assign an owner, fix the process that caused the gap and verify next month.

7.14Common mistakes and professional lessons#

• Closing work orders without verification. “Complete” should mean checked.
• Reporting too many KPIs. Five measures that change decisions beat twenty that do not.
• Measuring speed without quality. Pair response time with the reopen rate.
• Keeping records in someone’s inbox. Use a shared, controlled place.
• Guessing retention periods. Look them up at the source and ask the records officer.
• Back-dating a missing record. Write an honest dated note instead.

7.15Field checklist: work-order and records review#

7.16Knowledge check#

7.17Key takeaways#

7.18Further reading and official sources#

8.1Opening scenario#

The engineer found settlement from soil that had been repeatedly saturated by the downspout discharge. Fixing the drainage came first. The cracks were then monitored. This chapter teaches Carlos’s and Janelle’s part of the story: what to notice, how to record it and when to call.

8.2Learning objectives#

1. Trace a load path from roof to soil and say what each element does.
2. Name the common structural systems found in schools and commercial buildings.
3. Describe the warning signs of settlement, overload, corrosion, moisture and fire damage.
4. Record cracks and movement so that an engineer can use the record.
5. Know the line between observation and engineering judgment.
6. Escalate correctly and follow up.

8.3Why the subject matters#

• Structure is the one system you cannot afford to lose. A failed pump can be replaced. A failed beam can hurt people.
• Most structural trouble gives warning. Cracks, sticking doors, sagging, rust stains and water are early signals if someone notices and writes them down.
• The cause is often water. Roof, drainage and plumbing leaks cause or speed up many structural problems.
• Alterations change loads. Heavy equipment, new roof layers, removed walls and stored materials can overload a structure that was fine before.
• Records matter. A dated photograph with a scale is worth more to an engineer than a description from memory.

8.4Plain-English technical explanation#

The load path

Every load, from snow and wind to students and equipment, must travel to the ground through a continuous chain: roof covering and deck, joists or trusses, beams, columns or bearing walls, foundations, soil. If any link is weakened, loads shift to its neighbors. Cracks and deflection show where the chain is strained.

Common structural systems

Why cracks happen

Cracks are the building’s way of showing strain. Five broad causes cover most of what you will see: shrinkage and temperature (usually harmless, common in new concrete), settlement or heave (soil movement), overload (too much weight or removed support), corrosion and moisture (rusting reinforcement, rotting wood) and lateral pressure (soil or water pushing on a wall). The pattern, width, location and whether the crack is changing help an engineer tell them apart. You cannot tell reliably from a photograph, so record and escalate.

What to record

1. Location: room, wall, grid line, height above floor.
2. A photo with a scale (ruler or crack card) and a wide view for context.
3. Crack length, direction and width at its widest point.
4. Date, time, weather in the last few days, and who observed.
5. Pencil marks at the crack ends with dates, or a crack gauge fixed across it.
6. Associated signs: sticking doors, gaps at windows, sloping floors, water.

8.5Applicable laws, codes, standards and official references#

8.6How to decide whether a requirement applies#

1. Is there any sign of imminent danger? Sudden movement, new loud cracking, sagging, collapse of any part. Clear the area, call for help and follow Chapter 4.
2. Is it structural or cosmetic? If you cannot tell, treat it as structural until an engineer says otherwise.
3. Is the crack or movement changing? Monitor with dated marks or a gauge. Growth means escalate.
4. Is a repair or alteration planned? Permits and the adopted code probably apply. Ask the building official.
5. Could the work disturb asbestos, lead or other regulated materials? Check the plan before any cutting or demolition.
6. Who is allowed to decide? Engineering judgment belongs to a licensed engineer.

8.7Building systems, components and terminology#

8.8Step-by-step inspection demonstration#

8.9Annotated visual and tools#

8.10Common defects and their warning signs#

8.11Realistic case study: The Sticking Door#

What happened. Over a summer, a wing at Pine Hollow Middle School developed sticking doors and a few hairline diagonal cracks. Staff planed the doors and filled the cracks with patching compound. In the fall, the cracks reappeared wider and a window frame began to gap. Only then did the principal call the district.

What the engineer found. A leaking underground water line had saturated soil under part of the foundation, and a downspout had also been discharging next to the wall. The soil had softened and the footing had settled unevenly. The structure was not in imminent danger, but if left, movement would have continued.

What was done. The leak was repaired, the downspout was extended away from the building, the soil was allowed to stabilize while the cracks were monitored, and the engineer designed a limited repair.

What went wrong. Cosmetic fixes hid the message. Nobody recorded the first cracks or measured them, so the engineer had no history.

Lessons. (1) Do not paint over movement. Record it first. (2) Check water sources at any crack. (3) Monitor, because a stable crack and a growing crack call for different responses.

8.12Sample inspection findings and documentation#

8.13Risk classification and corrective actions#

Use the Chapter 4 scale with these structural adjustments:

• Critical (override): any sign of imminent failure or sudden movement; a falling-object hazard over a walkway or entrance; collapse of any part. Clear the area now.
• High: cracks that are wide, offset, growing or accompanied by sticking doors; sagging that is getting worse; corrosion with section loss; any alteration that removed or cut structure without engineering.
• Medium: stable cracks of unknown cause awaiting evaluation; drainage problems near foundations; wood decay that has not yet affected members.
• Low: hairline shrinkage cracks documented as stable by an engineer or by monitoring.

Corrective-action planning. Record, make safe, notify, engage an engineer, remove the cause where you can safely do so (water first), monitor, and close only on the engineer’s written finding or a monitoring record that shows stability.

8.14Common mistakes and professional lessons#

• Patching the crack and forgetting it. Record and monitor first, then repair on advice.
• Shaving the door. A sticking door is a message about movement.
• Guessing the cause from a photo. Escalate with a record and let an engineer decide.
• Ignoring water. Roof, drainage and plumbing leaks drive many structural problems.
• Adding load without checking. Roof equipment, storage racks and new roof layers need engineering.
• Cutting or removing members to run services. Never without an engineer.

8.15Field checklist: structural walk-through#

8.16Knowledge check#

8.17Key takeaways#

8.18Further reading and official sources#

9.1Opening scenario#

This chapter is about reading water, protecting the layers that keep it out, and doing it without anyone falling.

9.2Learning objectives#

1. Name the layers of a roof and a wall that control water, air and heat.
2. Describe common roof types and their typical failure points.
3. Trace a leak from the stain back to its likely source.
4. Inspect windows, doors, sealants and drainage from safe positions.
5. Plan a roof access decision using the fall-protection rules in this book.
6. Write a repair scope that a contractor can price and a manager can verify.

9.3Why the subject matters#

• Water is the most common cause of building damage. It rots wood, rusts steel, grows mold, ruins ceilings and equipment and weakens structure (Chapter 8).
• Roofs are expensive and short on warning. A small leak can mean wet insulation across a large area.
• Envelope problems drive energy and comfort complaints. Drafts, condensation and hot rooms often start at the envelope.
• Roof work is dangerous. Falls are a leading cause of serious injury in construction and maintenance.
• Small, cheap maintenance prevents big repairs. Clearing drains and resealing a joint cost far less than replacing a roof early.

9.4Plain-English technical explanation#

The four control layers

A building envelope controls water, air, heat and vapor. Each job is done by a layer or a set of layers, and the weak points are where layers meet: edges, corners, openings and penetrations.

Roof types you will meet

Windows, doors and sealants

Windows and doors are openings in the envelope. Check the head, jamb and sill for flashing and sealant, the glazing seals for fogging, the weatherstripping for gaps and the thresholds for drainage and corrosion. Sealant is a maintenance item: it ages, hardens and loses adhesion. A joint with a crack, gap or loose edge needs replacing. Sealant is not a substitute for flashing.

Drainage

Roofs need working drains, scuppers and gutters, with overflow paths. Grade at the building should slope away. Downspouts should discharge well away from foundations. Blocked drains cause ponding, overloading and leaks. They are the cheapest thing to maintain and the most often neglected.

9.5Applicable laws, codes, standards and official references#

9.6How to decide whether a requirement applies#

1. Does anyone need to go on the roof? If the question can be answered from the ground, a window, a lift or drone photographs by a qualified operator, do that.
2. Is a fall hazard present? Edges 4 feet or more above a lower level, skylights, openings, ladders. Assume yes.
3. Who may go? A trained person with the right equipment, a written plan and a partner. Otherwise a qualified roofer.
4. Will the work disturb roofing materials in an older building? Check the asbestos plan first.
5. Is a permit needed for the repair? Ask the building official.
6. Does the warranty or insurer require a specific contractor?

9.7Building systems, components and terminology#

9.8Step-by-step inspection demonstration#

9.9Annotated visual and tools#

9.10Common defects and their warning signs#

9.11Realistic case study: The Painted Skylight#

What happened. A maintenance technician went on the roof of Harlan Ridge Middle School to check a rooftop unit that had tripped. He had been on the roof several times and trusted the path he knew. A re-roofing project the previous summer had left a dome skylight in a new spot, painted over by the roofer to match the membrane. He stepped within a foot of it before he noticed the curb, and stopped.

What came next. Nobody was hurt. The technician reported the near miss. The district found there was no roof-access plan, no marked safe path, no guardrail around the skylight and no fall protection in the maintenance shop.

What changed. The district stopped routine roof access by maintenance staff, hired a roofing contractor for inspections twice a year and after storms, added guards to skylights and wrote an access plan that required fall protection and a second person.

Lessons. (1) A near miss is a free lesson. Record it. (2) Familiar roofs change. (3) The safest way to inspect a roof is often not to be on it.

9.12Sample inspection findings and documentation#

9.13Risk classification and corrective actions#

• Critical (override): sagging ceiling or roof; water around live electrical equipment; unguarded skylight or roof opening where people can reach it; egress doors that no longer open.
• High: active leaks over occupied rooms; ponding with signs of overloading; wet insulation spreading; fogged or broken glazing that creates a hazard.
• Medium: sealant failure, minor flashing defects, blocked drains without active leaks, drafts.
• Low: cosmetic weathering and isolated minor staining that has dried and not recurred.

Corrective-action planning. Make people and equipment safe, stop the water, notify, scope the repair with the contractor, plan safe access, verify after the next rain and record the closure date. Schedule drain clearing, sealant replacement and roof inspections so that they stop being emergencies.

9.14Common mistakes and professional lessons#

• Fixing the stain. Replace the tile after the leak is found and fixed.
• Using sealant instead of flashing. Sealant ages and often hides the real problem.
• Walking the roof “just to look.” Use the ground, a window, a lift or a qualified contractor.
• Ignoring drains. The cheapest maintenance prevents the costliest leaks.
• Skipping the asbestos check. Old roofing and flashing can contain it.
• Not verifying after rain. A repair is proven by the next storm.

9.15Field checklist: envelope and roof review#

9.16Knowledge check#

9.17Key takeaways#

9.18Further reading and official sources#

10.1Opening scenario#

This chapter teaches how to read an air system from the outside, so that the right specialist is called for the right reason.

10.2Learning objectives#

1. Describe the path of air through a typical air-handling system and the job of each component.
2. Explain what ventilation, filtration, heating, cooling and controls each do.
3. Describe the refrigeration cycle in plain language and the legal limits on refrigerant handling.
4. Estimate ventilation per person from a carbon dioxide reading and state the limits of the method.
5. Diagnose common comfort complaints in the right order.
6. Know when to call a technician, an air-balance specialist or an engineer.

10.3Why the subject matters#

• HVAC is usually the largest energy user and the largest source of complaints.
• Air quality affects people. Ventilation, filtration and humidity influence comfort and how people feel and perform.
• Failures are expensive and seasonal. Chillers and boilers fail on the hottest and coldest days (Chapter 2).
• Refrigerants are regulated. Handling them without certification is a legal problem and an environmental one.
• Controls hide problems. A system on a wrong schedule or with a stuck damper can waste energy for years without a single breakdown.

10.4Plain-English technical explanation#

The air path

Most buildings move air through the same sequence: outdoor air and return air mix; the mixture passes through a filter; a coil heats or cools it; a fan pushes it through ducts to supply diffusers in rooms; return air goes back through grilles and ducts; some air is exhausted and replaced with outdoor air. Figure 10.1 shows the path with six places to check.

What each function does

The refrigeration cycle, briefly

Cooling equipment moves heat from inside to outside using a refrigerant that changes between liquid and gas. A compressor pressurizes the refrigerant gas. In the condenser it gives up heat and becomes a liquid. A metering device drops its pressure. In the evaporator coil it absorbs heat from the air passing over it and becomes a gas again. The cycle repeats. Anything that cuts airflow (dirty filter, dirty coil, failed fan) or changes the charge changes how well this works.

Ventilation and a carbon dioxide reading

People breathe out carbon dioxide (CO2). In an occupied room, the indoor CO2 reading above the outdoor reading is a rough indicator of how much outdoor air each person is getting. It is not a measure of air pollutants and it does not replace a ventilation measurement. It is useful for a quick screen, with a calibrated meter, after the room has been occupied long enough for the reading to settle. Tool 10.1 uses the steady-state idea.

Humidity and filtration

Too humid air feeds mold and feels clammy. Very dry air is uncomfortable. Filters are graded with a MERV number from 1 to 16: a higher number catches smaller particles but resists airflow more. A unit designed for one grade may not move enough air through a denser filter. Ask the manufacturer or an HVAC technician before changing grade.

10.5Applicable laws, codes, standards and official references#

10.6How to decide whether a requirement applies#

1. Is there a risk to people right now? Gas smell, carbon monoxide alarm, smoke, flooding, loss of heat in extreme cold. Evacuate or protect people, then call. Follow Chapter 4.
2. Does the work involve refrigerant? Only certified technicians. Venting is prohibited.
3. Is it a boiler or a pressure vessel? State inspection rules and a qualified technician.
4. Is it a change to the system (new equipment, new ductwork, new capacity)? Codes, permits and an engineer probably apply.
5. Is it ventilation or air quality? Find out which code or standard is adopted and what the design basis was.
6. Otherwise follow manufacturer instructions and the strategy chosen in Chapter 2.

10.7Building systems, components and terminology#

10.8Step-by-step inspection demonstration#

10.9Annotated visual and tools#

10.10Common defects and their warning signs#

10.11Realistic case study: The Schedule Nobody Changed#

What happened. Mill Creek Elementary had a year of complaints about warm classrooms in the afternoon and a high electric bill. The district considered adding another rooftop unit. A technician reviewed the building automation schedule instead and found that during a summer renovation someone had set all units to run in an “occupied” mode around the clock and had left the outdoor-air dampers fully open. In humid weather the system was cooling and drying large volumes of outdoor air all night.

What it cost. The units were wearing out faster and humidity control was poor. The extra unit would have cost many times the schedule fix.

What was done. The schedule and damper settings were corrected, filters changed, a test-and-balance specialist adjusted airflows and the district began recording BAS changes with a reason and a name.

Lessons. (1) Check controls before buying equipment. (2) Log changes to schedules and setpoints. (3) A complaint about comfort is a request for investigation, not a request for a bigger unit.

10.12Sample inspection findings and documentation#

10.13Risk classification and corrective actions#

• Critical (override): gas odor, carbon monoxide alarm, combustion fumes or smoke; loss of heat during dangerous cold when people cannot be kept safe; flooding near live electrical equipment. Evacuate or protect people, call the utility, emergency services or qualified help.
• High: overdue boiler or pressure-vessel inspection; blocked combustion air; refrigerant leak signs; large areas with no ventilation; recurring equipment trips.
• Medium: comfort complaints with a clear cause, loaded filters, wrong schedules, minor control faults.
• Low: cosmetic issues, noise without a trend, minor insulation damage.

Corrective-action planning. Check controls and filters first because they are cheap and common. Use a qualified technician for equipment and any refrigerant. Measure before and after. Record changes to schedules, setpoints and overrides.

10.14Common mistakes and professional lessons#

• Buying equipment before checking controls. Schedules and dampers cause many “capacity” complaints.
• Using higher-grade filters without checking the unit. Too much resistance cuts airflow.
• Closing outdoor-air dampers to save energy. This can shortchange ventilation.
• Leaving overrides on. Review them weekly.
• Letting a non-certified person handle refrigerant. It is illegal in many cases and unsafe.
• Treating CO2 as a pass-fail air test. It is a screen, not proof of air quality.

10.15Field checklist: HVAC walk-through#

10.16Knowledge check#

10.17Key takeaways#

10.18Further reading and official sources#