Worksheet columns
- Contract line / scope item
- Vendor count or support assumption
- Field-verified count
- Status
- Exception / owner question
- Recommended action
Use Case
Support Contract Reconciliation
Do not renew support contracts against an unknown installed base.
Recurring support scope can drift away from field reality after tenant work, system changes, vendor swaps, device replacements, and incomplete closeout. A reconciliation baseline gives the owner a practical comparison before renewal, rebid, or dispute resolution.
Contract reconciliation
Compare what is being paid for against what is actually installed.
Recurring support scope can drift away from field reality after tenant work, system changes, vendor swaps, device replacements, and incomplete closeout. A reconciliation baseline gives the owner a practical comparison before renewal, rebid, or dispute resolution.
WorksheetContract-vs-Field Comparison Worksheet
Status options
- Confirmed
- Mismatch
- Inactive
- Abandoned
- Unsupported
- Excluded
- Pending vendor confirmation
- Owner review required
Relevant deliverables
Relevant deliverables for this trigger.
The exact package depends on building size, systems, source records, access, and owner decisions. These are the deliverables most commonly useful for this use case.
Deliverable
Installed Base Inventory
Shows the field-verified count behind renewal or rebid discussions.
DeliverableSupport-Scope Comparison
Compares vendor scope to installed and active conditions.
DeliverableVendor & Platform Matrix
Clarifies which vendor/platform responsibilities are assumed.
DeliverableException Register
Captures mismatch, inactive, unsupported, and excluded items.
DeliverableSavings Calculator Link
Helps discuss recurring waste without making guaranteed claims.
Decision support
How the owner record changes this decision.
The same owner-record discipline is routed differently depending on what the trigger requires.
Before renewal
The owner can question stale counts, exclusions, and support assumptions before signing.
During reconciliation
Field counts and support scope are compared in one worksheet.
After adjustment
The owner keeps a cleaner support baseline for future renewals and rebids.
Before / after
A practical, fictionalized scenario.
This illustrates the decision pattern without implying a specific client result or guaranteed savings.
The owner renews a support contract based on a stale device list, inherited platform assumptions, and unclear exclusions.
The owner compares contract scope against field-verified counts, inactive equipment, unsupported devices, and open vendor questions.
Next step
Ready to scope this support contract review?
Start with the trigger, systems, floors, source records, access limits, and owner decisions. Globin Engineering can shape the field verification and deliverable package around the actual risk.