A building runs on service contracts. Janitorial, security, landscaping, HVAC and elevator maintenance, waste removal, snow clearance and parking management are bought separately, renewed at different times, and priced on different escalation mechanics. Together they make up most of the operating expense pool, which means they also form the basis of what a landlord can recover from tenants.
That double role is why weak vendor contract control is expensive twice. The first cost is operational. Scope drifts, service levels go unmeasured, escalations are applied without a check, and renewals pass on their own. The second cost arrives at reconciliation, when a charge cannot be tied to a contract, a scope or an invoice, and a tenant disallows it.
This datasheet sets out what a contract system holds for property services, who owns each element, what triggers a check, and what the check produces. It is written for property operations and asset services teams running hundreds of vendor agreements across a portfolio of buildings.
What a vendor services agreement has to carry
Most portfolios have a standard vendor services agreement and a long tail of vendor paper that predates it. Standardization is worth doing on its own merits, but the reason it pays here is recovery. A reconciliation is defended with documents, and documents drafted to a common structure can be produced quickly and read consistently. An agreement written on a vendor form is usually where the argument starts.
- Scope of work by cost category, written so each service maps to the operating expense category it will be charged to, because a scope that mixes recoverable and non-recoverable work forces an allocation nobody can evidence later.
- Service levels and measurement, stating frequency, coverage hours, response times and the method of measurement, so performance is testable and a credit for missed service is calculable rather than negotiated afterward.
- Pricing and escalation mechanics, recording the base price, the escalation basis and its frequency, any pass-through of fuel, materials or wage floors, and the evidence a vendor supplies with an increase.
- Insurance, indemnity and certificates, capturing required limits, additional insured status, waiver of subrogation where it applies, and the certificate expiry date that has to be watched rather than filed.
- Term, renewal and notice mechanics, holding the expiry date, the renewal type, the notice period and any termination for convenience right, since an automatic renewal at an escalated rate is a cost decision nobody made.
None of that is unusual drafting. The difficulty is scale. A single property carries dozens of vendor agreements and a portfolio carries hundreds, each with its own dates and escalation clock. Held as documents they are unmanageable. Held as records with fields they can be queried, sorted by expiry and reported by property, which is the difference between managing a portfolio and reacting to it.
Whether a cost is recoverable, and whether it is expense or capital, is decided by the lease terms and by the nature of the work. That decision belongs on the contract record, set once and reviewed when scope changes. Rebuilt each year at reconciliation, it drifts, and inconsistency is what an audit finds first.
Capabilities the contract system provides
The point of holding vendor agreements as structured records is that reconciliation becomes retrieval rather than reconstruction. Five capabilities carry that weight. Standardized paper, classified cost, monitored compliance, controlled escalation and assembled evidence. Each one shortens the distance between a tenant question and an answer somebody outside property operations can verify without a phone call.
- Template and clause standardization. One vendor services agreement with a controlled set of alternates. Deviations are requested rather than drafted, and the exceptions granted stay visible on the record instead of sitting inside a signed document.
- Recoverable classification carried as data. Each contract and cost category holds its recoverable status and its expense or capital treatment, so a charge reaching the reconciliation was classified at the source rather than at year end.
- Compliance and certificate monitoring. Insurance certificates, licenses and required approvals are tracked with expiry dates and owners. A lapsed certificate becomes an alert before the vendor is on site, rather than a discovery after an incident.
- Escalation and price control. Escalation basis, frequency and caps are held as fields and tested when an increase arrives. An invoice that moves ahead of the contract mechanics becomes an exception with a number attached to it.
- Evidence assembly for reconciliation. The agreement, scope, certificates, invoices and service records sit on one record, so the pack a tenant auditor requests is produced from the system rather than gathered from a dozen property folders.
A five-step rollout for vendor contract control
Step 1, Inventory Vendor Agreements By Property
Collect every active service agreement per property and record the vendor, the service, the term dates and the annual value. Expect to find agreements that expired years ago and are still being invoiced, and services running with no signed paper at all. That list is the scope of the program.
Step 2, Standardize The Agreement And Its Alternates
Move new and renewing vendors onto one services agreement with a controlled set of approved alternates. Do not attempt a portfolio wide repapering. Renewal dates give you a natural sequence, and working that sequence converts the tail over a normal cycle without a separate project.
Step 3, Classify Cost Categories Against The Lease Terms
Set recoverable status and expense or capital treatment for each service, checked against the caps, exclusions, base year and gross-up provisions in the leases at that property. Where lease terms differ across tenants, record the variation, because a single recovery rule will not hold across a rent roll.
Step 4, Put Dates And Certificates Under Monitoring
Load expiry, renewal, notice and certificate dates as dated obligations with named owners. Notice periods matter most, because they are the dates where missing by a week changes the cost for a full year. Route the alert to the person who can actually act on it.
Step 5, Assemble The Reconciliation Pack From The Record
Produce the annual recovery statement with supporting documents drawn from contract records rather than from folders. Run it internally before it goes out. A pack that is assembled once and reviewed twice is what turns a tenant audit into a short conversation instead of a project.
See vendor contract control across a property portfolio
Walk through agreement standardization, recoverable classification, certificate monitoring and reconciliation evidence on your own vendor population, using live contracts, dates and property level cost categories.
What a tenant audit asks for
Audit requests follow a pattern. Show the contract for this service. Show the scope, and show that the work billed falls inside it. Show how the charge was classified as recoverable and point to the lease provision that allows it. Show the escalation applied this year and its basis. Show the invoices supporting the pool, and show that capital work was excluded or amortized as the lease requires. Each is answerable in minutes when the agreement, the classification and the evidence sit on one record. It takes weeks when the answer lives in property folders, and the delay itself invites a broader request. Dates need the discipline set out in a guide to critical-date and lease obligation management.
What the system captures, and what it produces
The table below is the operating summary for property services. Each row names what is captured, who owns it, the condition that triggers a check, and the artifact the check produces. The portfolio reporting that sits on top of these records is described in a piece on portfolio intelligence for CRE contracting, and the lease side of the same model appears in a lease lifecycle management datasheet.
| What is captured | Owner | Monitoring trigger | Output artifact |
|---|---|---|---|
| Scope of work and service levels | Property operations | Scope change or complaint | Scope extract with service record |
| Recoverable and capital classification | Asset services and finance | New contract or scope change | Classification record per category |
| Insurance certificates and licenses | Vendor management | Expiry date approaching | Current certificate held on file |
| Escalation basis and caps | Property accounting | Price increase received | Escalation check against contract |
| Term, renewal and notice dates | Property manager | Notice window opening | Renewal decision with pricing |
Common area maintenance recovery is a documentation exercise wearing an accounting label. The number is only as defensible as the contract behind it, the classification applied to it and the evidence filed with it. A property operations team that holds vendor agreements as records with fields, owners and dates does not prepare for a tenant audit, it answers one. Getting there costs a repapering cycle and a classification review. Not getting there costs every year, in disallowed charges and renewals nobody chose.
For related guidance, see Property vendor service contracts, a controls datasheet, The CRE guide to CAM reconciliation and lease audits and CAM reconciliation and recovery clause tracking for CRE.
