Lessors and lessees
Maintain counterparties, contacts, related leases, sites, obligations, communications, options, documents, and activity according to approved access.
Sites, assets and stakeholders
Understand every agreement in the context of the people, places, and assets it affects.
PactKeeper connects contracts to lessors, lessees, suppliers, buyers, insurers, inspecting parties, sites, technologies, items, permits, and responsible organizational users. This relationship model helps teams move from an isolated agreement to a complete operational picture.
Selected schools, universities, and organizations working with White Mountain Technologies.
Overview
A contract becomes actionable when its relationships are visible
A lease may affect a physical site, a landlord, a tenant, permits, insurance, rent, inspections, technologies, photographs, and renewal options. A supplier agreement may involve locations, responsible units, service items, insurance, performance evidence, and recurring obligations. When these relationships are maintained only in documents or separate lists, teams cannot easily understand exposure, ownership, or the operational effect of change.
PactKeeper provides structured records for lessors, lessees, suppliers, buyers, sites, items, insurance parties, inspecting parties, users, and other approved stakeholders. Sites can include names, addresses, technologies, property information, contracts, leases, permits, dates, alerts, inspections, reports, and photographs. The exact model is configured to the organization’s portfolio and terminology.
Organizational and geographic hierarchies can support access, ownership, reporting, and portfolio segmentation where reliable source data is available. The objective is not to duplicate every enterprise system, but to maintain the relationships required to understand contracts, direct actions, and report by the business dimensions that matter. Site records can include property details, technologies in place, permits, contract relationships, inspections, reports, and photographs where those elements belong in the approved operational model.
Connected process
Maintain relationships from onboarding through change and closure
Stakeholder and site records should remain current as responsibilities, ownership, contracts, and operating conditions change.
- 01
Establish the entity
Create or import the approved lessor, lessee, supplier, buyer, insurer, site, item, technology, inspection party, or organizational record.
- 02
Verify identity and ownership
Confirm names, codes, contacts, addresses, status, responsible teams, hierarchy placement, and authoritative source.
- 03
Associate contracts and obligations
Connect active and historical agreements, dates, alerts, documents, insurance, inspections, rent schedules, permits, or other relevant obligations.
- 04
Monitor operational changes
Update ownership, contact information, location status, technologies, items, site conditions, stakeholder relationships, and responsibility changes.
- 05
Review portfolio exposure
Use reports to understand contracts, expiries, options, inspections, insurance, documents, open actions, and obligations by entity or location.
- 06
Close or retain the relationship
Confirm final obligations, documents, handover, status, historical access, and whether the entity remains active for other agreements.
Capabilities
Relationship records that explain the contract portfolio
Structured context makes it easier to identify who is affected, where the agreement applies, and which related records require attention.
Suppliers and buyers
Connect commercial counterparties to agreements, items, locations, insurance, documents, alerts, and responsible teams.
Operational sites
Record names, addresses, property details, technologies, leases, permits, commencement and termination dates, inspections, reports, and photographs.
Assets, technologies, and items
Associate the equipment, technology, service item, property component, or other approved subject affected by a contract.
Insurance and inspecting parties
Maintain relevant insurers, coverage details, inspection organizations, inspectors, findings, evidence, and follow-up relationships.
Organizational and geographic scope
Use reliable hierarchies, domains, groups, locations, or responsible units to support access, ownership, escalation, and reporting.
Governance
Keep relationship data authoritative and appropriately scoped
Duplicate counterparties, outdated contacts, ambiguous sites, and uncontrolled hierarchy changes can weaken alerts and reporting.
Authoritative source
Define whether PactKeeper or another system owns each stakeholder, site, hierarchy, asset, item, address, contact, and status field.
Duplicate prevention
Use stable identifiers, matching rules, approval, and periodic review to avoid duplicate parties, sites, suppliers, or insurers.
Sensitive information
Collect only the user and stakeholder information required for contract operations and protect personal, commercial, and security-sensitive data.
Change accountability
Trace changes to ownership, location, contacts, hierarchy, status, and contract relationships that affect visibility, alerts, or responsibility.
Implementation readiness
Start with the relationships needed for the highest-priority contracts
A focused data model is more reliable than importing every available enterprise record without a defined use.
Inventory entities and sources
Identify lessors, lessees, suppliers, buyers, sites, assets, items, insurers, inspection parties, hierarchies, and source systems.
Define required attributes
Agree identifiers, names, contacts, addresses, statuses, ownership, classifications, documents, and contract relationships.
Clean and reconcile
Deduplicate records, resolve naming variations, validate active status, confirm contract associations, and document unresolved exceptions.
Test change scenarios
Validate stakeholder replacement, site closure, address change, transfer, new insurer, changed inspector, merged supplier, and historical reporting.
Govern ongoing maintenance
Monitor duplicates, orphaned contracts, inactive contacts, unassigned sites, invalid hierarchy relationships, and synchronization failures.
Operational value
A portfolio view grounded in real operational context
Relationship management helps teams answer questions that a contract list alone cannot answer.
Site-level visibility
See the agreements, dates, permits, insurance, inspections, documents, and open actions associated with a location.
Counterparty understanding
Review active and historical agreements, obligations, options, documents, and communications connected to a lessor, lessee, supplier, or buyer.
Responsible ownership
Direct alerts, access, reporting, and escalation using approved organizational, geographic, domain, group, or role relationships.
Frequently asked questions
Questions about sites, assets and stakeholders
Can one site be connected to several contracts?
Yes. A site can be associated with multiple current or historical contracts, leases, permits, insurers, inspections, documents, technologies, items, and stakeholders.
Can one lessor or supplier have multiple agreements?
Yes. PactKeeper can maintain the entity once and associate it with multiple agreements, locations, events, documents, and responsibilities.
Does PactKeeper replace supplier or property-management systems?
Not necessarily. PactKeeper maintains the relationship data required for contract control and can integrate with authoritative systems where the architecture and scope support it.
Can access be limited by location or organizational unit?
Yes. Visibility can be aligned with approved roles, hierarchies, locations, domains, groups, contract types, or responsible units.
Can inspection parties and insurers be maintained as stakeholders?
Yes. Relevant inspection organizations, inspectors, insurance companies, coverage details, and related contract records can be maintained according to the configured model.
How are duplicate stakeholders prevented?
Use stable identifiers, controlled creation, matching and review rules, authoritative-source decisions, migration cleansing, and periodic data-quality monitoring.
Plan the next step
Connect contracts to the stakeholders, sites, and assets that give them meaning.
Review your lessors, lessees, suppliers, buyers, locations, technologies, items, insurers, inspectors, hierarchies, and data sources with WMT.