PM Documentation Basics

How to write preventive-maintenance records that show what was actually inspected, tested, adjusted, replaced, and verified instead of leaving the next technician with nothing but “PM completed”

A preventive-maintenance work order should tell a story.

Back to Biomed Basics

What This Page Explains

This page covers:

The Simple Version

A useful PM record should answer:

What procedure was performed?

What significant results were obtained?

Did anything fail?

Was anything adjusted or replaced?

Was the final condition acceptable?

You do not need to write a novel.

You do need to leave enough evidence that:

PM completed

means something.

Documentation Is Part of the PM

The technical work and the documentation should agree.

If you performed excellent testing but recorded nothing useful, the organization loses much of the value.

Why PM Documentation Matters

A PM record can support:

It Creates a Baseline

Suppose a device develops:

NIBP inaccurate

six months later.

Previous PM record says:

Static pressure verified within specification across required test points.

That tells you the problem likely developed after that PM.

Weak Documentation

PM done.

What does that tell the next technician?

Almost nothing.

Better Documentation

Completed manufacturer PM procedure. Visual inspection satisfactory. Battery runtime and charge function passed. ECG, SpO2, NIBP, and temperature functions verified. NIBP static pressure and leak tests within specification. Electrical safety testing completed with passing results. No corrective action required.

Now there is substance.

Do You Need Every Measurement in the Narrative?

Not necessarily.

Many CMMS systems contain:

Use those when available.

The narrative should supplement the structured record.

Structured Data Is Valuable

If the CMMS has fields for:

record the actual values there.

This makes trending easier.

Actual Measurement vs Pass/Fail

A pass/fail result may be sufficient for some checks.

For others, actual measurement adds significant value.

Example

Battery test:

PASS.

Useful.

But:

Battery capacity 62%.

may become even more useful next year.

Trendable Measurements

Parameters worth recording may include:

depending on the device and procedure.

Do Not Record Meaningless Precision

If the analyzer is not accurate to:

Six decimal places,

do not document six decimals.

Match the measurement quality.

As-Found Values

An as-found value describes the condition before adjustment.

This can be extremely valuable.

Example

Flow rate required:

100 ±5.

As found:

93.

Adjusted.

As left:

100.

If you record only:

Passed after calibration

you lose the fact that the device arrived out of tolerance.

Why As-Found Matters

Repeated as-found failures may reveal:

As-Left Values

As-left results show the final condition after:

Calibration Documentation

If calibration was adjusted, document that clearly.

Example:

NIBP pressure calibration adjusted per manufacturer procedure. Verified all required pressure points within specification after adjustment.

Do Not Hide the Adjustment

A future technician needs to know the device required correction.

Part Replacement During PM

If you replace:

record it.

Why?

Parts history helps future lifecycle decisions.

Consumables vs Repairs

Some replacements are scheduled maintenance.

Others are corrective discoveries during PM.

Distinguish them when useful.

Example

Replaced annual intake filter per PM procedure.

is different from:

Replaced cooling fan after fan tach test failed during PM.

Failed PM Findings

If an item fails:

Document the failure before fixing it.

Weak

PM passed after repair.

Better

Battery capacity measured 28%, below required limit. Replaced battery and repeated capacity/operation verification with passing results.

Now the record preserves the original finding.

Corrective Work Order

Some organizations create a separate corrective-maintenance work order for failures discovered during PM.

Others document within the same work order.

Follow your facility process.

Make the Relationship Clear

If you open a CM ticket:

Reference it.

That keeps the history connected.

Device Removed From Service

If PM finds a problem serious enough to keep the equipment out of use:

Record that status.

Example

Audible alarm failed during PM. Device removed from service pending speaker repair.

Do not let the work order simply remain:

PM failed.

Test Equipment

Depending on your program, record test equipment used.

This may include:

Why Test Equipment Identity Matters

Suppose later your analyzer is found out of calibration.

You may need to identify which medical devices were tested with it.

Traceability

That connection supports the calibration traceability system.

Do Not Invent Analyzer Information

Use the actual equipment.

Procedure Revision

For highly controlled PM programs, the procedure version may matter.

This helps establish:

Software Version

For some devices, recording:

during PM can be valuable.

Why?

It creates a historical baseline for:

Do Not Fill the CMMS With Data Nobody Will Ever Use

Documentation should be useful.

The goal is not maximal text.

The goal is useful evidence.

PM Notes Should Reflect What Actually Happened

Do not use a boilerplate statement claiming:

All functions tested

if you did not actually test all functions.

Templates Can Help

A standard template improves consistency.

But templates become dangerous when technicians click through without verifying the content.

Never Document a Test You Did Not Perform

This sounds obvious.

It is one of the most important rules in technical documentation.

Pass/Fail Checkboxes

If you mark:

PASS,

you are asserting that the item met the applicable requirement.

Make sure you know what that requirement is.

“N/A”

Use N/A intentionally.

It should mean:

This item does not apply to this configuration or procedure.

Not:

I did not feel like testing it.

Missing Accessories

Suppose PM requires testing a function but the necessary accessory is not available.

Do not automatically pass it.

Document the limitation and handle according to procedure.

Example

Temperature channel could not be fully verified because required OEM probe was unavailable. Device held pending accessory/test completion.

depending on risk and requirement.

Environmental Conditions

Some calibration procedures require specific:

If relevant, document them.

Not every PM needs this.

Date and Technician Identity

The record should clearly establish:

Your CMMS may capture these automatically.

Department and Location

Location can help identify patterns later.

Example

Several devices in one area show the same fluid intrusion.

Without location history, that pattern may be harder to see.

Serial Number Matters

Ensure the PM is closed against:

The correct asset.

Wrong Asset Record

Documenting PM on the wrong asset creates:

Verify asset identity.

Barcode Scanning

When available, barcode scanning can reduce manual entry errors.

Still verify.

Asset Label Missing

If the asset tag is missing:

Resolve identity before closing the PM.

PM Sticker and CMMS Should Agree

If sticker says:

Due 2027

and CMMS says:

Due 2026,

someone will eventually be confused.

Resolve discrepancies.

Do Not Backdate Improperly

Record the actual service date according to facility policy.

Due Date

The next due date should follow:

not personal preference.

Documentation of Failed Inspection

Example:

Rear enclosure cracked near mounting point.

Do not simply write:

Cosmetic damage

unless you have actually determined its significance.

Be Objective

Describe what you observe.

Avoid Blame

Weak:

Nursing destroyed cord.

Better:

Power cord insulation cut approximately 3 cm from device strain relief.

Facts are more useful.

Avoid Guessing Root Cause

Weak:

Battery failed because staff leaves it unplugged.

unless that is supported.

Better:

Battery capacity below specification. Cause of early degradation not established.

Separate Fact From Interpretation

This makes records stronger.

Good PM Documentation Helps Future Troubleshooting

Suppose current complaint:

Ventilator overheating.

Last two PM notes show:

Filter heavily loaded.

Now environmental contamination may be relevant.

Another Example

Battery currently fails.

Previous PM:

Capacity 55%.

The degradation was already visible.

Trend Analysis

Good PM records can help identify:

Example

Ten devices repeatedly require the same calibration adjustment.

That may justify deeper investigation.

PM Documentation Helps Capital Planning

Repeated:

can support replacement decisions.

Vendor Communication

If you escalate a recurring issue, service history helps the OEM understand:

Audits

Good records can demonstrate that maintenance is being performed according to the approved program.

But documentation should reflect real technical work, not be written merely for an auditor.

Do Not Let Audit Language Replace Technical Language

Weak:

Performed all required checks in accordance with policy.

Better:

Use the checklist plus meaningful results.

How Much Is Enough?

Enough to answer:

You Do Not Need a Paragraph for Every PM

Routine pass:

Can be concise.

Example

Completed manufacturer PM procedure. Visual inspection and functional testing satisfactory. Battery, alarms, and applicable performance tests within specification. No corrective action required.

That may be plenty if detailed measurements are stored elsewhere.

PM With Findings

Needs more detail.

Example:

PM identified NIBP leak rate above specification. Internal tubing connection found loose and reseated. Repeated leak, static pressure, and functional tests within specification. All remaining PM checks passed.

That tells the real story.

PM With Failed Battery

Battery capacity measured 34%, below required acceptance limit. Replaced battery. Verified charging, AC/battery transition, and required runtime after replacement. Remaining PM tests passed.

Again:

Clear.

PM With Calibration Adjustment

Temperature input measured +1.8°C outside specification at reference point. Performed calibration adjustment per manufacturer procedure. Verified required temperature points within specification after adjustment. No additional faults noted.

That preserves both:

As-found problem

and:

As-left verification.

Common Mistakes

Writing Only “PM Completed”

You lose technical history.

Recording Only the Final Passing Value

Preserve significant as-found failures.

Marking Everything PASS Automatically

Each pass represents a technical conclusion.

Using Boilerplate That Does Not Match the Work

Documentation must reflect reality.

Failing to Record Parts Replacement

Parts history matters.

Recording a Repair Without Post-Repair Verification

Show that the repair was actually tested.

Putting PM on the Wrong Asset Record

Verify identity.

Writing Unsupported Root Causes

Document facts.

A Useful PM Documentation Framework

Think:

Procedure

What maintenance process was performed?

Condition

What was found?

Measurements

What significant values matter?

Actions

What was adjusted, cleaned, or replaced?

Verification

What testing showed the final condition was acceptable?

Status

Was the device returned to service?

Another Useful Question

Before closing the PM, ask:

If the next technician could see only this work order and not talk to me, would they understand anything important about the device's condition today?

If the answer is no:

Add the missing useful detail.

What Did You Actually Prove?

If your note says:

PM passed,

you are claiming the applicable maintenance requirements were satisfied.

That statement should be supported by:

If a battery failed and was replaced:

Your note should show both:

The failure

and:

The post-repair verification.

Documentation should not claim more than your testing proved.

But it should not hide what your testing discovered either.

Final Thoughts for Biomeds

PM documentation does not need to be long.

It needs to be useful.

Capture:

The PM record should help the technician who sees the device next year.

It should help the shop recognize a repeat problem.

It should help explain why the device was considered ready to return to service.

The best note is not the longest note.

It is the one that preserves the evidence somebody will actually need later.

So before you hit:

Complete Work Order

ask:

If this device comes back tomorrow, what did I leave behind that will help the next person understand what I found today?

— Jake

Important Note

PM documentation requirements, measurement retention, test-equipment traceability, work-order structure, corrective-maintenance linkage, sticker practices, and maintenance records vary by healthcare organization, CMMS, equipment type, manufacturer, and applicable requirements. Follow your facility's approved documentation practices and record only testing and service actions that were actually performed.

Related Biomed Basics

Back to Biomed Basics