Data retention and readiness

Tend your data estate wisely.

Tendwise reads your documents and databases where they sit, builds one evidence-backed inventory, and judges every item against your retention schedule, with reasons a lawyer can read.

Read-only Runs inside your environment Nothing leaves
Why this?
Illustrative example
Loan_Agreement_48213_signed.pdf
Collaboration site › Lending › Closed loans
Record class
Loan agreement
Recognised from the document itself
Belongs to
Loan 48213
Linked to the system of record
Trusted date
14 Mar 2018
File date 2 Jun 2023 rejected: that was moving day
Clock starts
Loan paid off, 30 Sep 2019
Schedule: keep 7 years after payoff
Copies
3 found
Authoritative version identified · no hold
Judgment
Eligible for disposal
Awaiting owner approval

Most retention programs stall between the signed schedule and the estate.

01

Nobody knows what's really there

Interviews describe the data people think they have. The estate holds something else.

02

Dates can't be trusted

Files that were moved take moving day as their date, hiding their real age and breaking every retention clock.

03

Nobody will approve deletion

Without reasons for each item, signing off a disposal is a risk no owner wants to carry.

How it works

Facts first. People decide.

Tendwise starts from what your estate actually holds, not from what anyone remembers. Your people still set the periods, the triggers and the holds.

Step 1

Read

A read-only crawl of file shares, Microsoft 365, cloud storage and databases, in place. Every read is logged.

Step 2

Inventory

One picture of every document and table: what it is, the date to trust, the business record it belongs to, its copies, and the kinds of personal data inside.

Step 3

Judge

Record classes are proposed from the estate itself. Every item is judged against your schedule, with a "Why this?" trace beside it.

Step 4

Prove

Your owners approve. Your own tools act. Tendwise verifies each disposal item by item, issues the certificate, and shows drift on every re-run.

One inventory, many uses

The same picture answers the next question too.

An exam, a lawsuit, a migration, an AI rollout: each one asks what you hold and whether you can prove it. Tendwise builds that picture once and reads it different ways.

Data retention

Your schedule, applied everywhere, and proven. Clocks start from the linked business record: a loan's payoff, an account's closure.

AI readiness

Know what your AI may use: what is fit to embed, what needs redacting first, and what stays out of reach.

Privacy

Personal data found, counted and masked. Tendwise records the kinds in each item, never the values.

Migration

Before you move, see what exists, its real age, its copies and its orphans. Move less, and move the right things.

Built to pass your security review

Tendwise never writes, never deletes, and nothing leaves.

It runs inside your environment and reads in place. Fixes are produced as reviewed scripts and action lists for your own tools, and nothing runs until your people approve it.

Every number shows its work

"Why this?" and "How we know" sit beside every judgment. Confidence is computed from evidence, never from a model's opinion.

A tamper-evident record

Every read is logged in a tamper-evident chain. The policy is dated before each disposal, and the evidence is kept for as long as you set.

Honest about limits

Where the evidence is thin, Tendwise says so. An item with no reliable date is listed as exactly that, not guessed at.

Tested on every build

Tendwise is built to defined design principles, each one tested on every build. Read-only is the one every other bends around.

One answer for the three people who have to agree.

Legal and Compliance

Disposal you can sign

Holds respected, reasons on every item, a certificate for each disposition, and evidence ready for an exam or audit.

Records and data governance

A schedule that starts from evidence

Classes proposed from the estate, one decision at a time, sign-off by owner, and a view of whether the schedule is still being followed.

IT and Security

An install with nothing to fear

Read-only credentials, inside your environment, nothing sent to us. Re-runs read only what changed.

For records and governance consultancies

You write the schedule. Tendwise applies it everywhere and proves it.

Talk to us about partnering
About

Built by people who have done this by hand.

Tendwise's founders spent decades in data management software, working with customers worldwide across every industry, in data quality, governance and integration.

Mark Hensley

Co-founder

16 years with IBM, most recently as North American Governance Lead. Before that, 15 years with R. L. Polk & Co. as developer, technical lead and manager.

David Watson

Co-founder

13 years with IBM, including North American Technical Business Unit Executive. Earlier, Data Integration Director at Ascential Software and 21 years with General Motors and EDS.

See it on a demo estate before you share a single credential.

A short walkthrough: one document followed from discovery to a certified disposal, with the evidence at every step.