What does it mean to seal a property record?

Sealing a property record means permanently locking its contents so that no changes can be made. A cryptographic hash is computed from the entire record contents, and this hash serves as a digital fingerprint. Any modification to the record, no matter how small, would produce a completely different hash, making tampering immediately detectable.

Can a sealed record be unsealed or edited?

No. Once a record is sealed, it is permanently immutable. The sealing process is irreversible by design. Neither the record creator, the counterparty, nor the platform itself can modify a sealed record. This is what gives sealed records their evidentiary strength.

How does cryptographic hashing work in simple terms?

A cryptographic hash takes any amount of data and produces a fixed-length string of characters, like a unique fingerprint. The same data always produces the same hash. Change even a single character in the data, and the hash changes completely. This one-way function means you cannot reverse-engineer the original data from the hash, but you can always verify that the data has not changed.

Can anyone verify a sealed Sawyl record?

Yes. Every sealed Sawyl record includes a public verification link. Anyone with this link can access the record and independently verify that its hash matches the original seal. No account or special software is required to verify a record.

Is a sealed record legally admissible?

While admissibility varies by jurisdiction, a sealed record with cryptographic verification provides strong evidence of data integrity. The combination of structured documentation, photographic evidence, counterparty acknowledgment, timestamps, and a tamper-proof seal creates a comprehensive evidence package that tribunals and courts can evaluate.

Sealed Property Records Explained

How cryptographic sealing creates tamper-proof property condition records that both parties can trust.

A property condition record is only as valuable as its integrity. If a document can be edited after creation — items added, photos removed, descriptions changed — then its usefulness as evidence is fundamentally compromised. Both parties need confidence that the record they are relying on is exactly the same as the record that was created at handover.

This is the problem that sealed records solve. By making a record permanently immutable after both parties have reviewed it, sealed records eliminate the possibility of post-hoc modification. The record that exists today is provably identical to the record that existed at the moment of sealing.

The Problem with Editable Records

Most property condition reports are created in editable formats: Word documents, PDF forms, paper templates, or general-purpose inspection apps. Even when a report is "signed" or "submitted," the underlying document often remains modifiable. A PDF can be edited with widely available software. A photo folder can have images added or removed. A database entry can be updated.

This creates a trust problem. If a dispute arises months after the handover, how does either party know the report they are reviewing is the original version? The landlord might suspect the tenant modified their copy. The tenant might suspect the landlord added items after the fact. Without a mechanism to verify document integrity, neither party can be certain.

Traditional signing — whether physical signatures or digital acknowledgment — addresses authentication (confirming who created the document) but does not address integrity (confirming the document has not changed since creation). A signed document that can still be edited offers authentication without integrity, which is insufficient for reliable evidence.

What Cryptographic Hashing Does

Cryptographic hashing is a mathematical process that takes any amount of data — text, images, structured records — and produces a fixed-length string called a hash. Think of it as a digital fingerprint. The hash has several important properties:

Deterministic: The same data always produces the same hash. If the record has not changed, the hash will not change.
Sensitive: Changing even a single character in the data produces a completely different hash. There is no way to make a "small" change that goes undetected.
One-way: You cannot reconstruct the original data from the hash. The hash serves only as a verification tool.
Unique: It is computationally infeasible for two different sets of data to produce the same hash.

When applied to a property condition report, cryptographic hashing creates a verifiable seal. The hash is computed from the entire record — every room, every item, every observation, every photograph reference, every timestamp. If anything in the record changes after sealing, recomputing the hash will produce a different result, immediately revealing the modification.

How Sawyl Sealing Works

The sealing process in Sawyl follows a defined sequence:

Record creation: The property condition is documented room by room, following the Sawyl Condition Record Standard. Items are assessed, notes are added, and photographic evidence is uploaded.
Counterparty review: The other party reviews the record and may acknowledge it or flag specific items with concerns. This step ensures both parties have seen the same information.
Canonical representation: The entire record is serialised into a canonical (standardised) format. This deterministic serialisation ensures that the same record always produces the same input for the hash function, regardless of how the data is stored or displayed.
Hash computation: A SHA-256 cryptographic hash is computed from the canonical record. This hash becomes the record's unique seal identifier.
Immutability enforcement: Once sealed, the record is locked at every level — database triggers prevent modifications, access policies block edits, and the user interface removes all editing capabilities.

Multi-Layer Immutability

Sawyl does not rely on a single mechanism to prevent modification. Instead, immutability is enforced at four independent layers:

Database triggers: Server-side triggers automatically reject any attempt to modify data in a sealed record. This operates at the database level, below the application code.
Access policies: Row-level security policies restrict modification operations on sealed records for all users, including the record creator.
Storage controls: Evidence files associated with sealed records cannot be added, replaced, or deleted through storage access policies.
Application enforcement: The user interface disables all editing controls for sealed records, preventing even the initiation of a modification attempt.

This defence-in-depth approach means that even if one layer were somehow bypassed, the remaining layers would still prevent modification. The cryptographic hash serves as the final verification — regardless of how data is stored, if the hash does not match, the record has been altered.

Public Verification

Every sealed Sawyl record generates a public verification link. This link allows anyone — the other party, a tribunal, a legal advisor, an insurance provider — to independently verify the record's integrity without needing a Sawyl account.

When someone accesses a verification link, the system retrieves the sealed record, recomputes the hash from the current data, and compares it to the stored seal hash. If they match, the record is verified as unmodified. If they differ, the record has been tampered with. This verification process is transparent and does not require trust in the platform itself — the mathematics of cryptographic hashing are independently verifiable.

Why This Matters for Disputes

Property damage disputes often come down to one question: what did the property look like at handover? When both parties have access to a sealed record with photographic evidence and acknowledgment from both sides, this question has a clear, verifiable answer.

A sealed record removes the arguments about whether the report was modified, whether photos were added later, or whether the other party ever saw the document. The seal timestamp proves when the record was finalised. The acknowledgment record proves both parties reviewed it. The hash proves nothing has changed since.

For landlords, this means stronger evidence supporting legitimate damage claims. For tenants, it means protection against claims for pre-existing damage that was already documented. For both parties, it means a faster, fairer resolution process.

The Broader Context

Sealed records are not unique to property management. The same cryptographic principles underpin document notarisation, software distribution verification, financial audit trails, and blockchain technology. What Sawyl does is apply these well-established principles specifically to the property handover context, where immutable evidence has clear practical value.

The technology is not new or experimental. SHA-256, the hashing algorithm used by Sawyl, has been in widespread use since 2001 and is one of the most thoroughly analysed cryptographic functions in existence. The innovation is not in the cryptography but in its application: making tamper-proof property records accessible to anyone, without requiring technical knowledge or specialised software.

Getting Started with Sealed Records

Creating a sealed property record with Sawyl follows the same process as creating any condition report. The sealing happens at the end, after both parties have reviewed the record. The move-in and move-out checklist guide provides a practical walkthrough of the documentation process, and our guide on documenting rental damage covers best practices for creating strong photographic evidence.

The result is a property condition record that both parties can trust, that any third party can verify, and that stands as permanent, tamper-proof evidence of what was observed at handover.