Documents and inspections

Keep the evidence behind every agreement, inspection, and action connected.

PactKeeper links contracts and sites with executed agreements, amendments, permits, insurance records, inspection reports, photographs, findings, correspondence, approvals, and follow-up evidence. Authorized teams can retrieve the relevant record without searching disconnected folders and email chains.

Selected schools, universities, and organizations working with White Mountain Technologies.

  • Liwa University
  • Abu Dhabi University
  • Mohamed Bin Zayed University for Humanities
  • Al-Bayan Bilingual School
  • A'Takamul International School
  • Nouria

Overview

Treat documents and inspections as governed contract evidence

An executed agreement is only one part of the contract record. Amendments may change dates or values. Insurance documents may confirm required coverage. Permits may authorize operations at a site. Inspection reports and photographs may document condition, compliance, damage, maintenance, handover, or follow-up. Correspondence and approvals may explain why a contractual decision was taken.

PactKeeper allows these records to be associated with the relevant contract, site, stakeholder, date, alert, inspection, or action. Sites can maintain inspection parties, reports, photographs, permits, commencement and termination information, and related agreements. Insurance records can include type, provider, description, coverage period, and renewal date.

The implementation should distinguish between a document repository and an authoritative record. File naming, classification, access, retention, version handling, approval, and required evidence must be defined. Sensitive commercial, legal, personal, security, or property information should be available only to authorized roles and protected according to organizational policy. Document classification, confidentiality, replacement, retention, and inspection follow-up should be defined before migration so the repository remains usable rather than becoming another undifferentiated file store.

Connected process

Preserve evidence from receipt through review, action, and retention

A document or inspection record should have clear ownership, context, status, and retention—not merely a file location.

  1. 01

    Receive or create the record

    Capture the executed contract, amendment, permit, certificate, insurance document, inspection request, report, photograph, approval, or correspondence.

  2. 02

    Classify and connect it

    Associate the record with the correct contract, site, party, alert, inspection, date, obligation, asset, item, or lifecycle event.

  3. 03

    Validate completeness

    Confirm file readability, type, version, date, issuer, responsible reviewer, coverage period, required signatures, and mandatory metadata.

  4. 04

    Review and act

    Record findings, required correction, approval, rejection, follow-up, renewal, remediation, handover, escalation, or another authorized response.

  5. 05

    Confirm completion evidence

    Attach the final report, updated document, photograph, approval, insurance proof, correspondence, or other evidence that demonstrates closure.

  6. 06

    Retain and retrieve

    Apply retention and access rules while preserving the link between the evidence, contractual decision, site condition, and historical record.

Capabilities

Evidence connected to the agreement and its operating context

PactKeeper helps teams retrieve the right supporting record while they are reviewing the contract or completing an action.

Executed contracts and amendments

Store approved agreement files, annexes, schedules, addenda, amendments, and other documents that define the governing terms.

Permits and regulatory records

Connect permits, licenses, approvals, certificates, commencement dates, expiry dates, renewals, and responsible parties to sites or contracts.

Insurance documentation

Maintain insurance type, provider, description, coverage, effective dates, renewal dates, related contracts, and replacement evidence.

Inspection planning and parties

Identify the site, contract, inspection type, inspecting organization, inspector, schedule, scope, and responsible internal user.

Reports, findings, and photographs

Preserve observations, condition evidence, nonconformities, recommendations, images, attachments, and the relationship to the inspected site or asset.

Follow-up and closure evidence

Track corrective action, reinspection, acceptance, approval, communication, supporting files, and the authority that closed the finding or obligation.

Governance

Protect document authenticity, access, and retention

Contract evidence must be reliable enough to support operational, commercial, audit, and legal review.

Classification and metadata

Standardize document and inspection types, names, dates, issuers, sites, contracts, versions, status, findings, and required fields.

Access and confidentiality

Restrict sensitive agreements, personal data, pricing, insurance, property information, photographs, findings, and legal correspondence to authorized users.

Version and change control

Define how superseded, amended, corrected, replaced, or reissued records are identified and how the governing version is recognized.

Retention and disposal

Apply approved retention periods, legal holds, archive, secure disposal, and evidence-preservation rules by contract and document family.

Implementation readiness

Design the evidence model before migrating document folders

Document migration is useful only when files can be reliably identified, connected, secured, and retrieved.

01

Inventory repositories and file types

Review shared drives, email, paper archives, property files, inspection systems, insurance records, permits, and contract folders.

02

Define classification and metadata

Agree document types, naming, contract and site links, dates, parties, status, version, confidentiality, retention, and mandatory evidence.

03

Clean and map files

Remove duplicates, identify governing versions, resolve missing links, validate readability, and document files that cannot be confidently classified.

04

Test retrieval and access

Validate common searches, contract and site context, permissions, inspection evidence, replacement insurance, amendments, and historical documents.

05

Govern new records

Set responsibilities for upload, validation, review, versioning, follow-up, closure, retention, and monitoring of missing or inaccessible evidence.

Operational value

Evidence available when a contractual decision is being made

Connected documents and inspections reduce the time and uncertainty involved in reconstructing what happened.

Faster retrieval

Open the relevant agreement, amendment, permit, insurance record, inspection report, or photograph from the contract or site context.

Clearer follow-up

Connect findings and required actions to responsible users, evidence, reinspections, approvals, and closure status.

Stronger historical record

Preserve the documents and observations that explain changes, decisions, renewals, site conditions, and completed obligations.

Frequently asked questions

Questions about documents and inspections

Can PactKeeper store files as well as contract data?

Yes. Authorized documents and attachments can be stored or linked within the contract, site, inspection, insurance, or action context according to the approved architecture.

Can inspection photographs be associated with a site?

Yes. Photographs, reports, findings, inspecting parties, and follow-up evidence can be connected to the relevant site, contract, asset, item, or inspection record.

Can insurance documents trigger renewal alerts?

Yes. Insurance coverage dates and renewal dates can be connected to alerts, responsible users, replacement evidence, and the relevant contract.

How are amended documents handled?

The implementation should identify the governing document, preserve prior versions where required, connect amendments to the contract, and update affected terms, dates, and alerts.

Can sensitive documents have restricted access?

Yes. Access can be limited through roles, privileges, portfolios, domains, groups, locations, or other approved security scopes.

Can existing document folders be migrated?

Yes, after inventory, classification, duplicate review, mapping, access analysis, validation, and agreement on how unresolved or low-quality files will be handled.

Plan the next step

Connect every important contract decision to the evidence that supports it.

Review your agreements, amendments, permits, insurance, inspections, photographs, findings, access, retention, and migration requirements with WMT.