A vendor document checklist that stays useful after onboarding.

The short answer

A property-management vendor file commonly includes identity and tax information, insurance evidence, applicable licenses, the agreement or approved scope, property-specific requirements, key dates, reviewer notes, exceptions, and a recorded approval decision. The exact requirements must come from your organization and qualified advisers—not from a generic software template.

1. Vendor identity and contact record

• Legal business name and any approved trading name
• Primary operational and billing contacts
• Business address and service area
• Vendor category and the work the vendor may perform
• Properties, owners, or portfolios connected to the relationship

Use one stable vendor record. Avoid creating a new record every time the same vendor serves another property.

2. Tax and payment setup

• Current Form W-9 or the tax form your process requires
• Payee name matched to the payment record
• Payment instructions collected through an approved, secure channel
• Internal review status and the date of the review

The IRS describes Form W-9 as the request for a taxpayer identification number and certification. Restrict access to tax identifiers and never place them in reminder emails, analytics, or ordinary notes.

3. Insurance evidence

• Certificate or other evidence requested by your process
• Effective and expiration dates recorded separately
• Named insured and issuing source
• Required supporting pages or endorsements, when applicable
• A review result, reviewer, review date, and documented exception

A certificate is evidence for review, not a software-generated guarantee. Keep the source document and the human decision visibly separate.

4. Licenses, registrations, and qualifications

• License or registration type and issuing authority
• Identifier, jurisdiction, status, and expiration date
• Relevant training or qualification evidence defined by your team
• Verification source and date

Do not assume every vendor category has the same requirements. Tie each item to the location and work scope it affects.

5. Contract and property requirements

• Executed agreement, approved scope, or purchase authorization
• Start, end, renewal, and notice dates
• Property access and site-specific instructions
• Required acknowledgements and escalation contacts
• Exceptions approved by an authorized person

6. Status, ownership, and next action

For every requirement, record a status such as missing, received, expired, due soon, needs review, accepted with exception, or ready for final approval. Then record one owner and one next action. A checklist without ownership becomes a passive archive; a readiness queue turns it into an operating process.

A monthly maintenance rhythm

1. Review expired and missing evidence tied to active work.
2. Look ahead through the team’s chosen renewal window.
3. Pause reminders when a vendor responds.
4. Route new or changed evidence to the responsible reviewer.
5. Record exceptions and final decisions with dates.
6. Close or archive inactive relationships according to the retention policy.