Preventive Maintenance Reports for Small Property Portfolios

Picture a local property manager with seven buildings, four recurring service vendors, and 186 maintainable assets.

At the end of the month, the owner receives:

• a 46-page HVAC packet;
• six plumbing invoices;
• a spreadsheet labeled PM list final v4;
• two roof photos in a text thread;
• a fire-alarm proposal with no site reference;
• three work orders marked complete even though the technicians could not enter the rooms; and
• an email saying the elevator vendor is waiting for an electrician.

The owner technically has records. The owner does not have a report.

A useful monthly preventive maintenance reporting method has two layers:

1. asset-level work orders preserve the actual task, observations, measurements, access, labor, materials, photos, exceptions, and technician sign-off; and
2. one monthly portfolio summary tells the owner or property manager what changed, what is due, what is blocked, what needs authorization, who owns the next action, and what may affect operations or capital planning.

The second layer should not replace the first. A green dashboard tile cannot prove that a filter fit, a pump was isolated, a roof drain was accessible, or a vendor completed a required test.

For a small portfolio, the goal is not another layer of software. It is a stable reporting method that works whether the records begin in a CMMS, a spreadsheet, or a set of facilities work orders.

Documentorium can create the field and customer-facing documents that support that register. Use the facilities inspection report for asset condition, evidence, priority, and recommended action. Use the facilities proposal for covered buildings, tasks, frequencies, response assumptions, reporting, and price, then carry responsibilities, access, authorization limits, exclusions, and renewal terms into the facilities contract.

Issue one facilities work order per visit or related group of tasks. The general service work order guide explains how the accepted service promise becomes field instructions, and the HVAC filter log guide shows the asset-level evidence a monthly summary should point back to.

If the portfolio does not yet have a reliable recurring schedule, start one step earlier. The inspection-to-maintenance-proposal workflow shows how to turn baseline findings into asset-specific tasks, frequency sources, repair boundaries, visit deliverables, pricing, and approval before those tasks enter the monthly report.

Define what preventive maintenance means in the contract

Do not use maintenance as one undifferentiated service category. For reporting, separate at least the work types below. The labels are not universal legal categories, so define them in the contract and use them consistently.

The Department of Energy's federal-facilities guidance uses reactive/corrective, preventive, predictive, and reliability-centered maintenance as four basic approaches. That vocabulary is useful, but it does not decide the right strategy for a particular asset. Asset criticality, failure consequence, manufacturer instructions, actual condition, duty, environment, warranty, law, and owner risk tolerance shape the plan.

Write the service boundary into the facilities contract:

Scheduled PM includes only the asset-task-frequency combinations in Schedule PM-1. Findings requiring repair, required inspections, testing that requires a different credential, hazardous-material work, engineering, replacement, after-hours response, and access beyond the listed conditions are excluded unless separately authorized. A PM completion record documents performance of the listed task under recorded conditions; it does not certify the entire asset or building as code-compliant, safe, defect-free, or unlikely to fail.

Use a portfolio hierarchy that survives staff turnover

Main building rooftop unit is not an asset ID.

Use a stable hierarchy:

Portfolio
  Property
    Building or structure
      Floor, zone, room, roof area, or site area
        System
          Asset
            Component or maintainable item

For example:

PF-01 Harbor Portfolio
  PR-03 218 Oak Street
    BL-01 Main Building
      RF-01 North Roof
        HVAC
          RTU-03
            FIL-03A / FIL-03B

Put the same IDs on:

• baseline surveys;
• asset register;
• equipment labels where authorized;
• preventive maintenance schedules;
• work requests and work orders;
• photos and measurements;
• vendor proposals;
• permits and inspection records;
• warranty claims;
• invoices;
• monthly summaries; and
• capital plans.

Do not renumber assets when a vendor changes. When equipment is replaced, retire the old asset record, preserve its history, and link it to the replacement asset.

Make the asset register useful before making it large

Start with fields that drive work and decisions:

• asset ID and parent location;
• plain-language name and system;
• manufacturer, model, serial, capacity, rating, and configuration where relevant;
• installation or in-service date, with source and confidence;
• ownership, lease, warranty, and service-provider status;
• criticality and consequence of loss;
• occupants or operations affected, without storing unnecessary personal data;
• isolation, access, permit, and special-hazard notes;
• manufacturer instructions and the source for each current task;
• PM task, interval basis, and next due window;
• responsible party for legally or contractually required tests and inspections;
• spare, consumable, filter, belt, lubricant, battery, or other recurring part identity;
• estimated service life or capital-review year, clearly labeled as an estimate;
• condition and open-defect status;
• linked work-order history; and
• data owner and last verification.

An IFMA article on CMMS data quality emphasizes accurate, complete, and consistent property-level data as the foundation for maintenance, portfolio analysis, and capital planning. That principle matters more than the software brand.

Add fields only when someone will maintain and use them. A register full of guessed install dates, copied serial numbers, and unowned condition scores produces confident-looking errors.

Use a data-quality flag:

Give every PM task a documented basis

Quarterly is not a maintenance procedure.

For every asset-task row, record:

• task ID and revision;
• precise work steps or referenced procedure;
• applicable asset models and locations;
• interval: calendar, runtime, starts, cycles, or seasonal window;
• interval source;
• prerequisites, tools, parts, instruments, safety controls, and qualifications;
• acceptable result or escalation threshold;
• required readings and photos;
• whether shutdown or occupant notice is needed;
• whether the task can be deferred, and who may approve that;
• next due window; and
• review trigger.

Useful interval sources include:

• current manufacturer instructions;
• adopted law, code, permit, or authority requirement;
• insurer or warranty condition;
• lease or owner standard;
• engineering or commissioning record;
• water management, fire protection, elevator, pressure-vessel, environmental, or other specialized program;
• actual runtime, loading, environment, and failure history; and
• an approved reliability strategy.

Do not let a general facilities vendor invent the frequency for a specialized program it does not own. CDC guidance on Legionella water-management programs, for example, calls for a team, a description of the building water systems, control measures, regular monitoring, predetermined responses, checks that the program works, and documentation. A monthly plumbing walk-through may support that program; it does not become the program merely because the work order says water PM complete.

Freeze the monthly due list before field work starts

At the start of the reporting period, take a snapshot of every PM instance included in that month's reporting denominator:

The snapshot fixes the denominator before field work starts. It prevents teams from improving the reported result by deleting overdue tasks or moving their due dates after the month closes.

When scope changes legitimately, preserve:

• original due instance;
• reason for revision;
• authorizing person;
• source supporting the new interval or applicability;
• effective date; and
• effect on past-due status.

Do not backdate a new PM interval to make a missed visit disappear.

Give technicians a task-level work order

The technician should not receive Perform PM at Oak Street.

The facilities work order should include:

• portfolio, property, building, location, system, and asset IDs;
• work-order and PM-instance IDs;
• task revision and due window;
• approved scope and exclusions;
• site contact, access window, check-in location, parking, loading, keys, alarms, and escort;
• tenant, resident, patient, student, customer, production, or security restrictions;
• known hazards and employer-controlled safety procedure references;
• required qualifications, permits, coordination, and shutdown approvals;
• exact task steps;
• parts, consumables, and instrument fields;
• starting condition;
• readings, measurements, and observations;
• pass, exception, not applicable, no-access, and stopped-work choices for each task;
• approved minor-repair threshold, if any;
• photo requirements;
• as-left condition;
• notification and handoff; and
• technician sign-off and, when required, customer acknowledgment.

Under the reporting definition, completion should mean that every required step has a recorded result. A single Complete checkbox is not enough.

Use clear task-result statuses:

Under this reporting method, No access is not complete and stays out of the completed numerator.

Treat access as an operational record

Small portfolios lose maintenance time through locked roofs, occupied units, parked vehicles, missing escorts, changed codes, tenant refusals, alarm restrictions, and undocumented keys.

For every failed or limited access attempt, record:

• work order, property, area, and asset;
• scheduled window;
• notice sent and recipient;
• technician arrival and departure;
• check-in location and person contacted;
• access credential issued or missing;
• exact reason access was denied or unsafe;
• whether the asset was seen or any task began;
• temporary condition observed from an authorized location;
• known operational or schedule consequence, without guessing at a diagnosis;
• who was notified, how, and when;
• person responsible for rescheduling and the deadline; and
• whether an emergency or compliance escalation was triggered.

Do not photograph occupants, personal possessions, medical information, access codes, keys, alarm panels, or security layouts unless necessary, authorized, and securely handled.

Vendor requirements vary by account. Examples from public owners and institutions illustrate the range:

• the Housing Opportunities Commission of Montgomery County requires contractors and subcontractors awarded HOC contracts to follow its background-screening requirements before assigning personnel to the work;
• Seminole State College's vendor procedure requires campus check-in, company identification, and a time-limited badge;
• Wellesley College requires specified insurance evidence before vendors conduct business on campus; and
• a 2021 maintenance solicitation from Delaware's Newark Housing Authority required office check-ins, work-order-specific tasks, access coordination, reporting of out-of-scope conditions, return of completed work orders, and invoice details tied to those work orders.

These are examples, not universal rules. The facilities contract and property profile should state the actual onboarding, insurance, license, screening, badge, key, escort, resident, privacy, check-in, and work-order requirements for each account.

Check vendor requirements before every dispatch

A vendor can meet the onboarding requirements and still have insurance, license, or access records expire six months later.

Before dispatch, verify the records required for that property and scope:

• executed contract and current scope schedule;
• business and contractor licenses;
• trade credentials and permits;
• certificate of insurance and required endorsements;
• workers' compensation evidence;
• screening, orientation, training, badge, and access status;
• safety-plan or pre-task requirements;
• tax and vendor-registration status through approved channels;
• subcontractor approval;
• emergency contacts;
• rate schedule, not-to-exceed authority, and after-hours terms;
• warranty responsibility; and
• expiration dates.

The report should not expose insurance policy numbers, screening results, personal identifiers, or credential secrets. Use a dispatch status such as eligible through ___, hold, or scope restriction, and keep the source record in the appropriate restricted file.

Verify required records before dispatch, not after the vendor has already worked.

Keep findings separate from repair approval

Preventive maintenance often reveals a repair need. That does not automatically authorize the repair.

Each finding should include:

• finding ID;
• asset and precise location;
• observed condition;
• measurement, instrument, test condition, or photo supporting it;
• expected condition or procedure reference;
• immediate operational status;
• temporary measure, if authorized;
• limitation or uncertainty;
• likely consequence, stated in proportion to the evidence;
• recommended next step and required trade or professional;
• timing or priority;
• estimate status; and
• owner decision.

Do not diagnose beyond the vendor's scope:

• microbial growth should not become toxic mold without qualified identification;
• discoloration near panel should not become electrical fire imminent without qualified evaluation;
• roof membrane opening observed should not become warranty defect without warranty review;
• water temperature outside program control range should not become a public-health clearance; and
• device did not respond during vendor check should not become an official failed code inspection unless the vendor and procedure have that authority.

Use a simple approval ladder:

The technician should never infer spending authority from a tenant saying, Please just fix it.

Use priority labels without pretending they are engineering judgments

Use a portfolio priority system with defined response expectations. The labels below are one practical internal scheme, not a classification imposed by code, law, or an engineer:

Priority is not the same as asset condition, legal violation, or risk score. Document why the trigger applies.

Do not downgrade a P1 because the repair budget is unavailable. Budget affects the response plan, not the observed consequence.

Coordinate vendor handoffs explicitly

The elevator company says it needs an electrician. The electrician says the elevator disconnect is not in its work order. The property manager assumes both vendors are coordinating.

Create a handoff record:

• handoff ID and related finding or work order;
• originating vendor and receiving vendor;
• asset/system and exact boundary;
• condition found and supporting evidence;
• work completed by the originating vendor;
• as-left operational and isolation status;
• temporary protection or restrictions;
• remaining task;
• prerequisite and dependency;
• drawings, manuals, permits, readings, photos, or parts transferred;
• responsible coordinator;
• authorization and not-to-exceed amount;
• scheduled window and outage/access requirements;
• acceptance criteria;
• notification list; and
• closure evidence.

For hazardous-energy work, the handoff record is not the lockout/tagout procedure. OSHA's general-industry standard requires employers to control hazardous energy when the standard applies. For covered work by outside servicing personnel, the outside employer and on-site employer must inform each other of their respective lockout or tagout procedures, and the on-site employer has duties regarding its employees.

The portfolio report can state:

Handoff H-017 remains open. The HVAC vendor recorded AHU-02 as disabled after finding a damaged fan assembly. Electrical evaluation is scheduled. The site and contractor employers must coordinate any applicable energy-control procedures before work. This report does not authorize anyone to remove a lock or reenergize the unit.

Do not put lock combinations, key locations, or a step-by-step hazardous-energy procedure in a broadly circulated owner report.

Record equipment status before the technician leaves

Every work order should answer:

• Is the asset running, disabled, isolated, bypassed, in alarm, in manual, or under temporary control?
• Which functions were tested?
• Which covers, guards, doors, valves, breakers, controls, drains, access panels, and housekeeping conditions were restored?
• What materials, tools, debris, filters, fluids, or removed parts remain?
• What label or tag was added?
• What temporary condition has an expiration or inspection requirement?
• Who was notified?
• What should the next person not assume?

Do not write left operational if only one mode was observed. Say what ran, under what conditions, for how long, and what was not tested.

Put decisions first in the monthly summary

The portfolio owner should not have to open every work order to find the actions that need approval.

Use this report order:

Portfolio identification and reporting basis

• portfolio and properties covered;
• reporting period;
• data cutoff;
• contract and PM schedule revision;
• prepared and reviewed by;
• material data gaps; and
• distribution list.

Urgent exceptions and decisions

Start with only the items that require immediate attention or a near-term decision:

If there are no P1 or P2 conditions, say No P1/P2 conditions were open at the report cutoff under the defined priority system. Do not say All properties safe.

PM status

Show counts with denominators and definitions:

• PM instances due;
• completed with acceptable result;
• completed with exception;
• partial;
• no access;
• owner-deferred;
• stopped;
• overdue from prior periods; and
• newly added or removed tasks.

PM compliance does not have one universal formula. Define the metric before the reporting period starts. For example:

PM compliance = applicable PM instances due in the reporting window and completed within their due window with all required task results ÷ applicable PM instances due in the reporting window × 100. Any due instance ending as no access, partial, deferred, stopped, canceled, or overdue remains in the denominator unless the frozen schedule was formally corrected for a verified applicability error.

That definition prevents a 100 percent score created by closing inaccessible work orders. A completed PM can still produce a finding: count the completed scheduled task under the stated measure, but keep the resulting corrective action open until it receives its own disposition.

Property summary

One row per property:

Action and authorization log

Show finding, recommendation, estimate, owner, decision deadline, and current status. Keep rejected and deferred decisions visible with their reason and review date.

Access and vendor exceptions

List no-access events, expired credentials, missing escort, tenant or operating restriction, reschedule owner, and impact on due work.

Required inspection and program calendar

List only the programs the portfolio has verified:

• authority or program;
• asset or property;
• qualified provider;
• due event;
• submission or certificate;
• result;
• corrections and retest; and
• responsible person or team.

Do not label ordinary PM as an official inspection.

Vendor handoffs and outages

Show dependencies, planned shutdowns, cross-trade ownership, temporary conditions, and decision gates.

Financial reconciliation

Reconcile:

• recurring contract amount;
• included consumables;
• approved extra work;
• emergency callouts;
• materials and freight;
• credits;
• invoices received;
• invoice-work-order match;
• committed but not invoiced work;
• year-to-date operating spend; and
• capital recommendations kept separate from authorized spend.

Next-month plan

Show due PM, seasonal tasks, access coordination, shutdowns, inspections, renewals, long-lead parts, warranty deadlines, and owner decisions needed before dispatch.

Choose KPIs that cannot hide the backlog

An IFMA article collecting examples from facility managers names measures such as PM completion, open and on-hold work orders, completion time, complaint closeout, project completion, and vendor performance.

For a small portfolio, use a short set with written definitions:

Avoid rankings that pressure technicians to close work orders prematurely. A lower completion rate with honest exception data is more useful than a perfect score built from false closes.

Make photos and readings traceable

For each photo kept as evidence, record:

• work order and asset ID;
• location and orientation;
• before, during, after, or exception purpose;
• capture date and time preserved in the source record;
• photographer or technician ID;
• caption describing what is visible without unsupported diagnosis; and
• privacy and security review.

For each reading that supports a decision, record:

• parameter and units;
• asset and measurement point;
• operating state and relevant conditions;
• instrument ID and calibration or verification status where material;
• method or procedure;
• result and acceptance basis; and
• person who took it.

Do not paste a photograph into the monthly report with only bad. Cite the finding and preserve the original asset-level evidence.

Match invoices to work, not to visits

Match each invoice to the work order ID, asset IDs, service period, approved repairs or change orders, and any access exception or credit. For narrative that will still make sense months later, borrow the date, location, people, work, exception, evidence, and next-step discipline from the daily report guide.

For every vendor invoice, match:

• contract or purchase order;
• work order;
• asset and location;
• included PM versus extra work;
• authorization and not-to-exceed limit;
• labor date, class, and hours when required;
• material and part records;
• emergency or after-hours basis;
• subcontractor or freight charges where allowed;
• tax;
• credit or callback;
• completion or exception status; and
• customer acknowledgment where contractually required.

A vendor can make a visit without completing the PM. Whether the visit is billable depends on the contract, but the report should not convert attendance into completion.

Keep capital estimates out of current operating spend until approved. Keep warranties, callbacks, and rework visible rather than rebilling them as new PM.

Close the monthly report with decisions, not a blanket sign-off

The portfolio manager should acknowledge decisions, not be asked to certify technical work they did not perform or are not qualified to evaluate.

Use status fields:

• report received;
• factual correction requested;
• estimate approved or declined;
• access action assigned;
• outage window approved;
• capital review requested;
• program owner confirmed;
• invoice reconciled and approved, or discrepancy assigned; and
• unresolved item carried forward.

An electronic acknowledgment should identify the report version and the specific decision. It does not, by itself, resolve a technical exception or prove that the work was correct.

Preserve the issued report, corrections, revised version, recipient, delivery record, comments, and decisions.

Example: one month in a four-property portfolio

Assume PF-01 has four small commercial properties and 62 PM instances due.

At cutoff:

• 51 were completed on time with acceptable task results;
• 4 were completed on time with findings;
• 2 were partially completed;
• 3 had no access;
• 1 was stopped after a condition required specialized review; and
• 1 had been marked not applicable after the asset register was verified and the schedule correction was approved.

The report does not say 61 of 62 complete.

It shows 55 on-time completions under the defined measure—51 acceptable plus 4 with findings—out of 61 applicable due instances, or 90.2 percent. The two partial, three no-access, and one stopped instance remain open. The verified not-applicable row is shown as a schedule correction, not a completion.

The urgent exceptions and decisions are:

1. P2 — PR-02/EF-04: exhaust fan stopped after abnormal movement was observed; vendor left it disabled and notified the manager. Electrical and mechanical handoff H-021 is open.
2. P2 — PR-04/FACP-01: required fire-alarm service vendor could not access the locked communications room; property manager must provide escort before the program due date.
3. P3 — PR-01/RTU-02: repeated belt dust and alignment finding; estimate Q-188 awaits approval.

The monthly report links to the detailed records, identifies owners and deadlines, reconciles invoices, and shows next month's seasonal roof and drainage tasks.

The owner can act without reading 62 work orders. The work orders remain available to document what happened.

Monthly portfolio report checklist

• [ ] Portfolio, property, building, system, asset, PM, finding, and handoff IDs are stable.
• [ ] Asset data distinguishes verified, reported, inferred, and unknown values.
• [ ] Each PM task has a current source, revision, interval, prerequisites, and acceptance basis.
• [ ] The due-list denominator was frozen before field work.
• [ ] Technician work orders record task-level results and as-left status.
• [ ] No-access, partial, stopped, and deferred work remains visible and is not counted as complete.
• [ ] Findings are separated from repair authorization.
• [ ] Priority is based on a defined trigger, not a color alone.
• [ ] Vendor compliance and property-specific access status are checked before dispatch.
• [ ] Cross-vendor handoffs name the boundary, dependency, owner, and acceptance criteria.
• [ ] Specialized inspections and programs remain under qualified ownership.
• [ ] KPIs include denominators and cannot hide overdue work.
• [ ] Photos and readings are traceable to asset and work order.
• [ ] Invoices reconcile to contract, authorization, actual work, parts, and status.
• [ ] The monthly summary starts with decisions and carries unresolved items forward.

Sources

Sources were checked August 23, 2026. The DOE sources support the maintenance terminology, CDC supports the building-specific water-management boundary, and OSHA supports the employer-coordination statements. The IFMA articles provide the data-quality and KPI context. The owner and institution policies show how screening, access, insurance, work-order, and handoff requirements differ by account; they are examples, not universal rules.

• Occupational Safety and Health Administration, Recommended Practices for Safety and Health Programs, OSHA 3885, October 2016, accessed August 23, 2026, for proactive hazard identification and host-employer/contractor communication context. These are recommendations, not a substitute for applicable standards or an employer's program.
• Occupational Safety and Health Administration, 29 CFR 1910.147, Control of Hazardous Energy, especially paragraph (f)(2), accessed August 23, 2026, for the statements about coordination between outside servicing personnel and the on-site employer.
• Occupational Safety and Health Administration, Lockout/Tagout eTool — Outside Personnel (Contractors), accessed August 23, 2026, for the plain-language contractor coordination summary.
• U.S. Department of Energy, Federal Energy Management Program, Operations and Maintenance Challenges and Solutions, updated October 30, 2025, accessed August 23, 2026, for reactive/corrective, preventive, predictive, and reliability-centered maintenance terminology and site-specific program design.
• U.S. Department of Energy, Federal Energy Management Program, Operations and Maintenance in Federal Facilities, accessed August 23, 2026, for the current federal O&M resource context. Federal-facility guidance is a source of practice concepts, not a private-property requirement.
• Grace Jones, International Facility Management Association, Foundational Success: Improving CMMS Data Quality, February 9, 2026, accessed August 23, 2026, for accurate, complete, and consistent property-level asset data and portfolio analysis.
• Katherine Sproles, International Facility Management Association, KPI in Facility Management: Top Metrics Every Manager Should Be Tracking, December 12, 2023, accessed August 23, 2026, for practitioner examples including PM completion, open and on-hold work orders, completion time, complaints, projects, and vendor performance. These examples do not prescribe one universal KPI definition.
• Centers for Disease Control and Prevention, Overview of Water Management Programs, March 15, 2024, accessed August 23, 2026, for building-specific tailoring, team ownership, control measures, regular monitoring, intervention, program-performance checks, and documentation.
• Housing Opportunities Commission of Montgomery County, Contractors — Procurement and Background-Screening Requirements, accessed August 23, 2026, for an account-specific screening example.
• Seminole State College of Florida, Vendors and Contractors, Procedure 8.0600, adopted May 2025, accessed August 23, 2026, for an account-specific identification, key, check-in, and badge example.
• Wellesley College, Insurance Requirements for Vendors, accessed August 23, 2026, for an account-specific certificate-of-insurance and endorsement example.
• Newark Housing Authority (Delaware), Employment Opportunity for Building and Apartment Maintenance Services, December 14, 2021, accessed August 23, 2026, for a public solicitation example covering office check-ins, work-order tasks, access coordination, out-of-scope reporting, completed records, and invoice linkage.

This article provides a facilities-documentation framework, not engineering, safety, code, employment, environmental, public-health, insurance, licensing, privacy, contract, or legal advice. Verify every asset task, interval, qualification, inspection program, vendor requirement, access rule, safety procedure, approval threshold, and retention duty against the current property, contract, manufacturer, authority, employer program, and applicable law.