Contract records and repository
Manage contract identity, type, values, terms, dates, special conditions, status, responsibilities, related entities, and authorized documents.
Features overview
A connected feature set for the complete contract operating picture.
PactKeeper organizes contract lifecycle management around connected records rather than disconnected files. Contract definitions, terms, parties, sites, dates, alerts, documents, inspections, insurance, users, dashboards, and reports work together so each authorized user can understand both the agreement and the action it requires.
Selected schools, universities, and organizations working with White Mountain Technologies.
Overview
Organize features around contract decisions—not isolated screens
A list of features is useful only when the relationships between them are clear. A renewal alert depends on the correct contract, date rule, lead time, responsible user, decision status, and supporting documents. An inspection record has value when it is linked to the right site, agreement, inspecting party, findings, photographs, and required follow-up. A dashboard is credible only when the underlying definitions and ownership are consistent.
PactKeeper therefore combines contract records with operational context. Contracts can be associated with lessors, lessees, suppliers, buyers, sites, technologies, items, insurance parties, documents, and inspections. Alert types can reflect rent schedules, options, insurance, renewals, rights of first refusal, single events, intervals, yearly milestones, or custom obligations.
The feature set is configurable. Organizations decide which contract families, fields, terminology, date calculations, alerts, roles, hierarchies, documents, reports, and integrations belong in the approved scope. This allows PactKeeper to align with the actual contract-management process without implying that every organization must adopt the same structure. The same connected model supports controlled expansion by contract family, location, stakeholder group, alert type, and reporting responsibility.
Connected process
How the feature families work together
Each capability contributes to a continuous operating model from contract intake through action, renewal, and historical review.
- 01
Define the portfolio
Establish contract families, codes, statuses, terms, values, parties, sites, assets, items, responsible units, and required information.
- 02
Capture contractual logic
Record commencement, expiry, options, rent schedules, insurance periods, recurring milestones, variable dates, durations, special conditions, and custom rules.
- 03
Connect evidence and context
Link documents, amendments, permits, inspection reports, photographs, insurance records, communications, and stakeholder information.
- 04
Direct attention
Generate alerts and reminders using approved dates, lead times, categories, recipients, escalation, visual status, and decision ownership.
- 05
Complete and document actions
Record decisions, approvals, comments, evidence, completion, deferral, renewal, extension, purchase, termination, or closure.
- 06
Analyze and improve
Use dashboards and reports to review the portfolio, upcoming events, overdue items, workload, exceptions, data quality, and operating patterns.
Capabilities
Core PactKeeper capability families
The feature architecture supports both day-to-day action and portfolio-level oversight.
Alerts and obligation tracking
Configure alert types, trigger rules, lead times, recurring events, reminders, recipients, escalation, status, completion, and pending action.
Dates, durations, and options
Support commencement, expiry, end-of-year, contractual-year, extended termination, custom dates, intervals, options, and calculated time frames.
Sites and stakeholder relationships
Maintain lessors, lessees, suppliers, buyers, sites, technologies, items, insurance parties, inspection parties, and relevant organizational context.
Documents, insurance, and inspections
Connect executed agreements, amendments, permits, coverage details, inspection evidence, photographs, findings, and follow-up records.
Dashboards, reporting, and access
Present actionable views while controlling visibility, privileges, user activity, portfolio scope, and approved reporting dimensions.
Governance
Configure flexibility without sacrificing consistency
Flexible software is valuable only when the organization controls definitions, ownership, access, and change.
Master-data ownership
Assign owners for contract types, stakeholder records, sites, alert categories, date rules, statuses, insurance definitions, and reporting dimensions.
Configuration authority
Limit who may add fields, change calculations, alter alerts, update privileges, or modify controlled terminology.
Portfolio standards
Document the minimum information and evidence required for each contract family and stage of the lifecycle.
Quality monitoring
Review incomplete records, invalid dates, duplicate parties, missing documents, unassigned alerts, overdue actions, and inconsistent classifications.
Implementation readiness
Select features according to operational priority
A phased feature roadmap allows teams to establish reliable control before expanding breadth.
Prioritize contract families
Rank agreements by financial, legal, operational, renewal, insurance, property, or compliance consequence.
Map feature dependencies
Identify which dates, parties, sites, documents, alerts, inspections, users, reports, and integrations each priority family requires.
Configure a governed minimum
Define the fields, classifications, access, alerts, evidence, and reports required for initial operational control.
Validate with real scenarios
Test renewals, options, insurance, rent schedules, overdue actions, document retrieval, inspection follow-up, and access boundaries.
Expand through measured releases
Add portfolios, workflows, reporting depth, external data, and advanced configurations only after the foundation is stable.
Operational value
A feature model that stays connected to the work
The objective is not to activate the largest number of features, but to make each configured feature support a real contract-management decision.
Less fragmentation
Replace separate trackers for dates, documents, inspections, insurance, counterparties, and action status with connected records.
More consistent action
Use common alert definitions, ownership, evidence, and completion rules across departments and locations.
Clearer portfolio insight
Compare contract families, sites, stakeholders, date horizons, open events, overdue actions, and data quality using approved classifications.
Frequently asked questions
Questions about the PactKeeper feature map
Must every PactKeeper feature be implemented at once?
No. The system can be implemented in phases, beginning with the contract families, dates, alerts, documents, and reports that carry the greatest operational consequence.
Can fields and terminology be configured?
Yes. Contract types, labels, classifications, fields, alerts, dates, documents, privileges, and reports can be aligned to the approved business model and implementation scope.
Can the same contract have multiple alert types?
Yes. An agreement may contain several alert categories and events, such as rent schedules, insurance renewals, extension options, purchase options, yearly obligations, and custom dates.
Can documents and inspections be linked to sites?
Yes. Sites can be associated with contracts, permits, lessors or lessees, inspections, inspecting parties, reports, photographs, technologies, and related records.
Can dashboards be tailored by role?
Dashboard content and reporting scope can be configured around authorized responsibilities, portfolios, locations, contract types, and management needs.
How are feature changes controlled?
The organization should define configuration ownership, testing, approval, documentation, release, and regression-review rules for any change that affects contract logic or access.
Plan the next step
Choose the PactKeeper capabilities that solve your highest-priority contract risks.
Map your portfolio, dates, obligations, parties, documents, inspections, access, reporting, and implementation phases with WMT.