Records Governance & Disposal

Destroy what your authority allows, and prove it

Agencies hold years of Microsoft 365 content that their records authorities allow them to destroy, and keep it because nobody can show who decided, under which class, and that no hold applied. T365 runs that decision as a recorded, approved process, Microsoft Purview carries out the disposal, and the evidence stays behind.

Records disposal — sentenced, approved, certified
On-demand scan
Stage 1 · Scan
SharePoint
OneDrive
Exchange
Teams
Purview Content Search + Graph
Stage 2 · SentenceRules, with optional AI

Destroy — disposal class matched · AFDA Express V2

Optional AI — off until connectedyour own Azure OpenAI endpoint required for PROTECTEDAdvisory — officer sign-off required
Stage 3 · Batch & holdsDisposal batchBATCH-0042 · 1,284 items
Preparer cannot approveDuties segregated
Hold attestation — approverconfirms no freeze or legal hold applies
Stage 4 · Certify
Certificate of destruction
CERT-0042
  • Sequentially numbered
  • Hash-chained to CERT-0041
  • Cites delegation instrument — Archives Act s.24
Grounded in AFDA Express V2 — 7 functions · 41 disposal classes · Archives Act 1983Disposal freezes acknowledged before approval
Sample tenant: Department of Example
Awaiting officer approval…Batch certified — 1,284 SharePoint items destroyedIllustrative — sample data

What you get

Why teams choose Records Governance & Disposal

01

Disposal you can defend

Every destruction traces back to a records authority class, the people who approved it and the delegation instrument it was authorised under.

02

Proof of what was destroyed

A numbered certificate, a register entry for each record and a minimum metadata set export answer the question of what went, when and on whose authority.

03

Holds stop disposal

A legal hold or disposal freeze is checked at each step, so held content does not move through to destruction while the matter is open.

04

People make every decision

Rules and optional AI only propose a class. A records officer accepts or rejects it, and separate people review, approve and authorise the batch.

05

Less content to hold and search

Destroying what your authority allows you to destroy leaves less content to store, secure and search when a discovery or FOI request arrives.

06

Works with Purview, not around it

Purview retention labels and eDiscovery holds do the work in Microsoft 365, and T365 keeps the approvals and the evidence.

How it works

From connection to evidence

  1. 1

    Discover

    Run a discovery scan to list SharePoint, OneDrive, Exchange and Teams items with their metadata.

  2. 2

    Sentence

    Rules, and AI suggestions if you connect a provider, propose a disposal class that a records officer accepts or rejects.

  3. 3

    Review, approve, authorise

    People other than the preparer review and approve the batch, and a delegate authorises it under a delegation instrument.

  4. 4

    Dispose through Purview

    After holds and freezes are checked again, T365 applies retention labels and Purview disposes of the content.

  5. 5

    Keep the evidence

    T365 issues a numbered certificate, writes each record to the destroyed-record register and exports the metadata.

In detail

How Records Governance & Disposal works

Discover and sentence against your authorities

T365 scans SharePoint, OneDrive, Exchange and Teams content when you run a discovery, and records each item it finds with its title, location, dates, owner, format and Purview sensitivity label. The content itself stays in Microsoft 365.

Items are sentenced against records authorities held in T365. Classes from AFDA Express Version 2 are loaded as a built-in authority, and you can add your own authorities and classes. Every item in a disposal batch must carry a class before the batch can go to review.

Classes marked Retain as National Archives cannot be destroyed through T365, and items carrying a SECRET or TOP SECRET label are excluded from disposal.

Rules first, AI only if you connect it

Sentencing runs on rules you configure for each tenant: conditions on an item’s metadata, such as its location, age or content type, evaluated in the order you set. Rules work with no AI connected at all.

AI suggestions are optional and off until your organisation configures a provider. When they are on, each suggestion names a disposal class and a reason, and a records officer accepts or rejects it. Nothing an AI suggests reaches a disposal batch until an officer has accepted it.

Separate people at each step

A disposal batch moves through preparation, review, approval and authorisation, and each step is recorded against the person who took it. The person who prepared a batch cannot review it, approve it or authorise it, and T365 platform administrators cannot approve disposal.

A batch that contains PROTECTED content needs a second approver, who must be a different person from the first. Authorisation is the legal act: the delegate records the delegation instrument they are acting under and confirms their identity with a fresh sign-in.

Holds and freezes stop disposal

Records managers place legal holds for FOI requests, litigation, regulatory matters, investigations, subject access requests and child abuse inquiries. A hold can cover an organisation, a tenant, a site, a path or a single item, and it records its reason, owner and authority. Releasing a hold needs a reason and is written to the audit log.

T365 checks holds at review, at each approval, at authorisation and again immediately before disposal, and a batch with a held item does not move forward. A hold placed while a batch is open removes the retention labels T365 applied to the held items. T365 also asks Microsoft Purview to place an eDiscovery hold on the same content, and records whether that succeeded.

Disposal freezes work alongside holds. Reviewers must acknowledge every active freeze, approvers attest that no freeze or hold applies, and a freeze created after review is checked again before disposal.

Purview carries out disposal, T365 keeps the evidence

T365 publishes a Purview retention label for each disposal class, and applies labels to items only after a batch is fully authorised, so Purview’s disposition clock never starts on an unapproved decision. Purview then disposes of the content.

T365 confirms each destruction by matching it in the Microsoft 365 unified audit log. Where the audit log cannot confirm it, a records officer confirms by hand, with a justification and a fresh sign-in, and records any item that was not destroyed with its reason.

Disposal through T365 covers SharePoint and OneDrive documents today. Mail and Teams items are discovered and reported, but are not yet disposed of through T365.

Proof that outlasts the record

Each completed batch produces a numbered certificate of destruction that states the records authority, class and dates for each class in the batch, the officers involved and the delegation instrument. Certificate records are hash-chained, and the SHA-256 of the issued PDF is stored and checked every time the certificate is downloaded.

Each destroyed item is written to an append-only register of destroyed records, which is kept even if the scan, batch or tenant it came from is later removed. The register and each batch can be exported as CSV or JSON using the National Archives of Australia minimum metadata set, and disposal, hold and export actions are written to a hash-chained audit log.

Proof of disposal — certificate and destroyed record register
AFDA Express V2

Disposal certificate

DC-2026-0042

  • Class 62391 Routine asset management812 destroyed
  • Class 62543 Routine procurement471 destroyed
  • Not destroyed, reason recorded1 item
Total
1,283 SharePoint and OneDrive items
PDF SHA-256
9c41e0…a7d2 · checked on every download
Chain
Linked to the previous certificate record

Destroyed record register

Append-only. One row per destroyed item, kept after the content is gone.

  • Stocktake 2019 — Level 3.xlsx62391 · SharePoint
  • Minor equipment log FY19.docx62391 · SharePoint
  • Quote comparison — stationery.pdf62543 · OneDrive
  • PO 41877 supporting notes.docx62543 · SharePoint

Export the minimum metadata set as CSV or JSON.

Illustrative — sample data. Copies held in T365 backups are listed on the certificate as out of scope.

Who it is for

Built for the people accountable for it

Records managers

Run sentencing and disposal as one recorded process, with holds checked at each step and a register of what was destroyed.

Delegates who authorise disposal

Authorise a batch knowing it was prepared, reviewed and approved by other people, and that your delegation instrument is on the record.

Legal and FOI teams

Place a hold on a site, path or item and know that disposal will not proceed on that content while it stays in place.

Internal audit

Check certificates, the destroyed-record register and a hash-chained audit log without relying on anyone’s recollection.

Frameworks

The frameworks it helps you evidence

Federal Register of Legislation

Archives Act 1983

Section 24 allows Commonwealth records to be destroyed in accordance with a records authority. T365 requires each item in a disposal batch to carry a records authority class before review, and records the authority and class on the certificate.

Read the source (opens Federal Register of Legislation in a new tab)

National Archives of Australia

AFDA Express Version 2

Classes from AFDA Express Version 2 are loaded as a built-in records authority, so you can sentence common administrative records against it from the start.

Read the source (opens National Archives of Australia in a new tab)

International Organization for Standardization

ISO 16175-1:2020 Records management functionality

T365 addresses specific functions the standard describes for Microsoft 365 content: controlled disposal with separated duties, holds and freezes on disposal, a register of destroyed records and minimum metadata export. Others are not yet built, including a persistent identifier for each record, a history of metadata changes and transfer to the National Archives. Our gap analysis lists each one, and we make no claim of conformance with the standard.

Read the source (opens International Organization for Standardization in a new tab)

National Archives of Australia

Building trust in the public record

The policy asks agencies to make sure business systems capture minimum metadata and can export it. T365 exports the destroyed-record register and each disposal batch using the minimum metadata set properties; Rights and Integrity Check are not yet filled.

Read the source (opens National Archives of Australia in a new tab)

Office of the Australian Information Commissioner

Privacy Act 1988 and the Australian Privacy Principles

After a confirmed destruction, T365 removes the extracted text and search index entries it held for that record, so it does not keep a readable copy of content you have destroyed. Subject access requests can be placed as holds.

Read the source (opens Office of the Australian Information Commissioner in a new tab)

T365 measures, maps and records evidence against these frameworks. Your organisation remains responsible for its own assessment and authorisation decisions.

Questions

What buyers ask us

Does AI decide what gets destroyed?

No. AI is optional and off until your organisation connects a provider. When it is on, it suggests a disposal class and a reason, and a records officer accepts or rejects each suggestion. Disposal then needs separate review, approval and authorisation by people.

Who approves a disposal?

A batch is prepared, reviewed, approved and then authorised by a delegate. The person who prepared it cannot review, approve or authorise it. A batch with PROTECTED content needs a second approver who is a different person from the first, and the delegate records their delegation instrument and signs in again to authorise.

What proof do we get?

A numbered certificate of destruction for each batch, stating authority, class, dates and officers; an entry in an append-only register for each destroyed record; and CSV or JSON exports using the NAA minimum metadata set. Certificate records are hash-chained, and the PDF’s SHA-256 is checked on every download.

What happens when a legal hold applies?

T365 checks holds at review, approval, authorisation and again before disposal, and a batch with a held item does not proceed. A hold placed on an open batch removes the retention labels T365 applied to held items, and T365 asks Purview to place an eDiscovery hold on the same content.

Does it work with Microsoft Purview?

Yes. Purview carries out the disposal. T365 publishes a retention label for each disposal class, applies labels only after a batch is authorised, and confirms each destruction from the unified audit log or by an officer’s recorded confirmation.

Does destruction reach every copy?

Not every copy. T365 removes its own extracted text and search copies of a destroyed record. Copies in T365 backups are not yet removed, and records still under a hold keep their copies; the certificate lists T365 backup copies as out of scope and states the copies kept under hold.

Evidence: where each claim on this page comes from
  • AFDA Express Version 2 classes built in

    packages/db/drizzle/0022_seed_afda_express_v2.sql

  • Rule-based sentencing configured per tenant

    apps/web/src/lib/governance/sentencing-rules-engine.ts

  • AI provider is optional; clearing it switches AI off

    apps/web/app/api/governance/[tenantId]/ai-config/route.ts

  • Officer accepts or rejects each AI suggestion

    apps/web/app/api/governance/[tenantId]/ai-sentencing/suggestions/[suggestionId]/route.ts

  • Preparer cannot review or approve; PROTECTED second approver differs from the first; RNA cannot be destroyed

    apps/web/src/lib/governance/batch-state-machine.ts

  • Platform administrators cannot approve; approver attests no hold or freeze applies

    apps/web/app/api/governance/[tenantId]/batches/[batchId]/approve/route.ts

  • Authorisation records a delegation instrument and needs a fresh sign-in

    apps/web/app/api/governance/[tenantId]/batches/[batchId]/authorise/route.ts

  • Legal hold types and scopes

    packages/db/src/schema/governance-legal-holds.ts

  • Holds created, mirrored to Purview eDiscovery and released with a reason

    apps/web/src/lib/governance/hold-service.ts

  • Holds and freezes checked at review, approval, authorisation and execution

    apps/web/src/lib/governance/execution-preconditions.ts

  • Retention labels applied only after authorisation

    apps/web/src/lib/governance/purview-labelling.ts

  • Destruction confirmed from the unified audit log

    apps/web/src/lib/governance/purview-disposition-worker.ts

  • Manual confirmation with justification and fresh sign-in

    apps/web/app/api/governance/[tenantId]/batches/[batchId]/confirm-disposition/route.ts

  • Certificate records and audit log are hash-chained

    packages/db/src/schema/governance-audit.ts

  • Issued PDF SHA-256 stored and checked on download

    apps/web/src/lib/governance/certificate-store.ts

  • Append-only register of destroyed records with no foreign keys

    packages/db/src/schema/governance-destroyed-register.ts

  • NAA minimum metadata set export as CSV or JSON

    apps/web/src/lib/governance/mms-export.ts

  • T365 removes its own extracted text and search copies after destruction

    apps/web/src/lib/governance/destroyed-register.ts

Buying for government? We are on the DTA Digital Marketplace.

  • Software
  • Cloud
  • Professional services
  • Labour hire
  • Hardware
How to buy

Ready to Secure Your Microsoft 365?

Start your free 14-day trial or talk to our team about your needs.