Vendor and Contract Tracking: What Every Community Should Keep on File

Every community depends on vendors.

Landscapers.

Roofers.

Plumbers.

Electricians.

Insurance agents.

Waste management companies.

Elevator companies.

Property managers.

The list can become surprisingly long.

And every one of those relationships creates information the community needs to manage.

A contract.

An insurance certificate.

A scope of work.

Invoices.

Contact information.

Renewal dates.

Performance issues.

Board decisions.

The problem is that this information often doesn't live together.

The contract might be in a shared drive.

The insurance certificate might be attached to an old email.

The board member responsible for maintenance may have the vendor's cell phone number.

Someone else remembers that the vendor had a serious problem two years ago.

And the renewal date?

Hopefully someone put it on their calendar.

This works until the person who knows where everything is leaves the board—or until something goes wrong.

A vendor file is more than administrative paperwork

It's easy to think of vendor records as routine paperwork.

Save the contract.

Pay the invoice.

File the insurance certificate.

Move on.

But vendor records can become extremely important when questions arise.

Is the vendor still under contract?

What exactly were they supposed to do?

Was this repair included in the scope of work?

When does the contract expire?

Does the contract automatically renew?

What insurance documentation did the community receive?

Has this problem happened before?

Who approved the work?

How much has the community spent with this vendor?

Those questions are difficult to answer when the information is scattered across email, folders, spreadsheets, and individual board members.

A well-maintained vendor record gives the community a place to start.

What should a vendor record include?

The exact requirements will vary depending on the type of vendor and the community's needs.

But every significant vendor relationship should generally have a centralized record containing the information the board needs to manage that relationship.

The current contract

The community should have access to the current, signed version of the agreement.

Not just a proposal.

Not an unsigned draft.

Not a copy of an email saying:

"We agreed to move forward."

The actual agreement matters.

And just as importantly, the board should be able to identify which version is current.

Over the years, contracts can be amended, renewed, extended, or replaced.

A folder containing three versions of the same agreement isn't particularly helpful if nobody knows which one is in effect.

A clear scope of work

Many vendor disputes begin with a simple question:

"Is that included?"

The answer shouldn't depend entirely on someone's memory.

The vendor's scope of work should be available alongside the contract.

What is the vendor responsible for?

How often will the work be performed?

What is specifically included?

What is specifically excluded?

What work requires additional authorization?

A clear record can prevent misunderstandings before they become disputes.

And when the board changes, the next board doesn't have to guess what the previous board agreed to.

Insurance and other required documentation

Depending on the type of work and the relationship, the community may collect insurance certificates, licenses, permits, bonds, or other documentation.

Collecting the documentation once isn't necessarily enough.

Some documents expire.

Insurance policies may change.

Licenses may need renewal.

Requirements may vary depending on the work being performed.

The important thing is to know:

What documentation is required?

When does it expire?

Who is responsible for reviewing it?

A certificate sitting in a folder is not the same thing as an actively managed record.

Communities should establish their requirements with appropriate professional advice and periodically review vendor documentation according to those requirements.

Renewal and termination dates

This is one of the easiest things to overlook.

A contract may have:

• A fixed expiration date
• An automatic renewal clause
• A notice period for termination
• A deadline for requesting changes
• A pricing adjustment date

Missing one of those dates can create unnecessary problems.

Imagine a board that is unhappy with a vendor and plans to look for alternatives.

The contract automatically renews unless the vendor receives notice 60 days before the renewal date.

Nobody notices.

The deadline passes.

The board may now have fewer options than it expected.

This isn't necessarily a contract problem.

It's often a tracking problem.

Important dates should not exist only in a paragraph on page twelve of a contract.

They should be visible and actively monitored.

A history of the relationship

This is where vendor tracking becomes much more valuable than simply storing documents.

A vendor relationship has a history.

Perhaps the landscaping contractor has performed well for five years.

That's useful to know.

Perhaps the contractor has repeatedly missed scheduled visits.

That's useful, too.

Perhaps the board received three complaints about incomplete work.

Perhaps those complaints were resolved.

Perhaps they weren't.

Perhaps the vendor was given additional work because they performed exceptionally well on an earlier project.

All of that is organizational knowledge.

Without a history, each new board evaluates the vendor from scratch.

With a history, the board can see the pattern.

Connect the vendor to the work

A vendor record becomes even more useful when it connects to the actual work the vendor performs.

Imagine searching for a roofing contractor and being able to see:

• The current contract
• Previous contracts
• Work orders completed by the contractor
• Projects involving the contractor
• Related invoices or costs
• Performance issues
• Board decisions involving the vendor
• Important communications

Now the vendor is no longer just a name in a contact list.

The community has a history of the relationship.

This is especially valuable when the board is considering whether to renew a contract or solicit new proposals.

Instead of relying on:

"I think they've done a pretty good job."

the board can review what actually happened.

Connect contracts to board decisions

Significant vendor relationships usually involve a board decision.

The board reviewed proposals.

Considered costs.

Discussed the scope of work.

Selected a vendor.

Authorized someone to sign the contract.

That decision should be traceable.

A future board member should be able to understand:

Who approved this contract?

When?

What alternatives were considered?

What information did the board review?

Why was this vendor selected?

This doesn't mean every routine purchase needs a complicated governance record.

But significant contracts should not appear out of nowhere.

The agreement and the decision that authorized it are part of the same organizational story.

The danger of relying on one person's calendar

Many communities manage vendor renewals through individual calendars.

The maintenance chair sets a reminder.

The treasurer remembers when the insurance certificate expires.

The secretary keeps track of contract deadlines.

This can work.

Until someone leaves the board.

Or changes responsibilities.

Or forgets to transfer the reminder.

Important organizational dates shouldn't depend on one person's calendar.

They should belong to the organization's records.

The question should never be:

"Who was keeping track of that?"

The question should be:

"What does our vendor record show?"

Make vendor review part of the board's routine

Vendor management doesn't require a procurement department.

For most communities, it simply requires a regular process.

For example, the board might periodically review:

• Contracts expiring in the next 90 days
• Contracts approaching renewal deadlines
• Insurance or other documentation approaching expiration
• Vendors with unresolved performance issues
• Major contracts scheduled for review
• Significant upcoming work

The specific schedule will depend on the community.

The important thing is that vendor management becomes a routine activity rather than something the board reconstructs when a problem occurs.

A few minutes of regular review can prevent a great deal of unnecessary scrambling later.

Don't turn the vendor record into another filing cabinet

There's an important distinction between storing documents and managing information.

A shared folder full of contracts is useful.

But it still leaves the board asking:

Which contract is current?

When does it renew?

What action is required?

Has the insurance documentation expired?

What work has this vendor performed?

Has the board had problems with them?

A useful system should help connect the answers.

The goal isn't simply to create a better digital filing cabinet.

It's to make the information usable.

Vendor records are institutional memory

Like board decisions, work orders, and reserve information, vendor history is something a community should not lose when board members change.

A long-serving board member may know:

"We stopped using that company because of problems with their previous contract."

A new board member won't know that.

Unless the organization remembers.

The vendor may submit a new proposal five years later.

The price may look attractive.

The new board may have no idea about the previous problems.

A centralized vendor history gives the board context.

It doesn't prevent the board from giving the vendor another opportunity.

But it allows the board to make that decision with information rather than missing history.

The bottom line

Vendor and contract tracking isn't exciting.

Most communities don't think about it until a contract deadline is missed, paperwork can't be found, or a dispute raises the question:

"What did we actually agree to?"

By then, the board is trying to reconstruct history.

A better approach is to maintain that history as the relationship develops.

Keep the current contract.

Track important dates.

Maintain required documentation.

Record significant performance issues.

Connect the vendor to the work they perform.

Connect significant contracts to the decisions that authorized them.

Review important dates before they become emergencies.

The goal isn't more paperwork.

It's fewer surprises.

And, like everything else in a well-managed community, the information should belong to the organization—not to the board member who happens to remember where the contract is.

A vendor relationship may begin with a contract.

But over time, it becomes part of the community's institutional memory.