The Everything vs OpenText Content Manager
The incumbent records system is not the thing slowing your agency down. Here is what actually is, and what to buy for it.
The short answer
OpenText Content Manager — the product that has also been HP TRIM, HPE Records Manager and Micro Focus Content Manager — is the statutory records system across a large part of Australian federal and state government. It exists to hold the record: capture, classification, retention and disposal, defensibly, for decades. The Everything is not a competitor to that and does not want to be. It is an AI automation layer over Microsoft 365 that runs the work around the record — the intake, the preparation, the approvals, the chasing and the decision trail. If you are being sold a replacement for your records system, be sceptical. If your problem is that the process around it runs on email and takes weeks, that is what The Everything fixes, in days rather than quarters.
Their strengths
What is OpenText Content Manager genuinely good at?
OpenText Content Manager is a statutory records management system with a very long lineage in Australian government, having previously been sold as HP TRIM, HPE Records Manager and Micro Focus Content Manager. Its job is to hold the record and prove it: capture, classification against a business classification scheme, retention and disposal against an approved authority, security and access control, and an evidentiary history that survives staff turnover, restructures and decades of time. That is a genuinely hard problem and it is the problem this product was built for.
Defensible retention and disposal
Records sentenced and disposed against an approved authority, with the evidence trail that makes the disposal defensible rather than merely convenient.
Longevity
Records outlive the systems that created them. A dedicated records platform is designed for custody measured in decades, which very little other enterprise software attempts.
Deep incumbency in government
Long-standing use across federal and state agencies means established practice, established integrations and staff who already know it. Incumbency is a real asset, not just inertia.
If your obligation is statutory recordkeeping, this category is correct and the incumbent is usually the safest thing in your estate. We are not here to talk you out of it.
The trade-offs
Where does a statutory records system get hard in practice?
None of this is a criticism of the product. It is what the statutory records category costs, and it costs the same wherever you buy it. A records system is configured against your business classification scheme, your retention authority and your security model — none of which the vendor can supply — and the configuration has to keep pace with every structural change the agency goes through afterwards.
The information model is a prerequisite, not an output
The classification scheme and disposal positions have to exist and be agreed before the system governs anything. That agreement is usually the longest part of the programme and it is agency work, not vendor work.
Capture competes with where people actually work
Staff work in Outlook, Teams and SharePoint. Anything that asks them to stop and file into a separate repository is a habit change, and habit change is where recordkeeping compliance slips regardless of vendor.
It holds the record, not the process
The approval waiting in an inbox, the supplier who has not replied, the internal chase for a missing attachment — that work is what makes a case take six weeks. A records system was never designed to run it, and it does not.
Configuration ownership never ends
Machinery-of-government changes, new record types and new workflow variants all return to the same configuration cycle, usually with an implementation partner. Someone has to own that capability permanently.
The useful question is not whether to keep the records system. It is what is actually causing the delay you are trying to remove — and in most agencies the answer is the process around the record, not the record.
Our approach
What does The Everything do instead?
The Everything runs the work. It is an AI automation layer on top of Microsoft 365 that executes a real process end to end — reading what arrives, doing the preparation, stopping for the human decisions that matter, and logging all of it. It does not ask for a classification scheme first, because the AI reads the work as it comes in rather than requiring the agency to model it up front.
Process definitions
The steps, owners, conditions and exceptions of a real agency process, written once and then executed rather than published as a procedure nobody reads.
Approval and authorization engine
Anything consequential stops and asks a named officer in Teams, with the context needed to decide. Approve or reject, and the process continues from where it paused.
Audit logging
Every action, input, decision and approval recorded as it happens, so the decision trail is available without a reconstruction exercise.
RBAC and permissions
Enforced per person and per action from existing Microsoft 365 identity, so the access model is the one the agency already administers.
Governed-asset stewardship
Approved templates, standing references and required wording the AI must use, so what comes out is consistent rather than improvised.
Microsoft 365 native
It works in Outlook, Teams and SharePoint over the content already there. No migration, no new system for staff to adopt.
A first workflow is live in days. That matters most in an agency that already carries a large records programme, because it means the automation work does not have to queue behind it or compete with it for the same budget cycle.
Our limits
What does The Everything explicitly not do?
The Everything is not a statutory records system and does not replace OpenText Content Manager. We have no business classification scheme, no retention schedules, no disposal authorities, no sentencing, no defensible disposal and no archival custody. If a vendor tells you an AI automation layer can absorb your legislated recordkeeping obligation, that vendor is either confused or selling you a risk you will carry at audit. Keep the records system. We automate the work around it.
It does not replace your records or document store
The records platform and SharePoint stay exactly where they are. The Everything works over them rather than asking anyone to migrate.
It is not evidence of recordkeeping compliance
Our audit log shows what happened inside a process. It is not a record register, it is not a disposal log, and it should never be offered to an auditor as either.
It does not take the decision off a human
Consequential actions require a named approver by design. Fully autonomous action with nobody accountable is not something we offer.
This is the honest shape of it: your records system holds the record, and it should. The Everything removes the weeks of email, chasing and waiting that happen before anything becomes a record at all.
Which should you pick?
| If your problem is | Pick | Why |
|---|---|---|
| Records must be sentenced and disposed under an approved authority | Your records system | The Everything does not do statutory recordkeeping and never will. Keep the incumbent. |
| You need decades-long defensible custody of records | Your records system | Long-term evidentiary custody is exactly what the records category exists for. |
| A case takes six weeks and most of it is waiting on people | The Everything | The approval engine routes decisions to named officers and chases the rest automatically. |
| You need to show who decided what, when, and on what evidence | The Everything | The audit log captures every action, input, decision and approval as it happens. |
| Staff will not file into a separate system no matter how many reminders you send | The Everything | It works where they already are — Outlook, Teams and SharePoint. |
| You want automation without opening another multi-year programme | The Everything | A first workflow goes live in days and does not depend on the records programme finishing. |
| You need the record held and the process around it automated | Both | Different jobs. Keep the records system, put the automation layer over the work. |
Common questions
Can The Everything replace OpenText Content Manager or HP TRIM?
No. The Everything is not a records management system. It has no classification scheme, no retention schedules, no disposal authorities and no archival custody. If you have a statutory recordkeeping obligation, keep your records system. The Everything automates the process work that happens around it.
Does The Everything work alongside an existing records system?
Yes, and that is the intended arrangement. It does not own a repository and does not require a migration, so it runs over the Microsoft 365 estate and the systems already in place while the records platform continues to hold the record.
What is the difference between an audit log and a record register?
An audit log records what happened inside a process — the actions taken, the inputs used, the decisions made and who approved them. A record register is the controlled account of records held, classified and sentenced under a retention authority. The Everything provides the former and explicitly not the latter.
Our records programme is already consuming our budget. Does automation have to wait for it?
No. The two are independent. The Everything does not depend on the classification scheme being finished, because the AI reads the work as it arrives rather than requiring it to be modelled in advance. A first workflow can go live in days regardless of where the records programme sits.
How are approvals handled for a regulated government process?
Anything consequential pauses and asks a named officer in Microsoft Teams with the context needed to decide. Permissions are enforced per person and per action from existing Microsoft 365 identity, and every action, input, decision and approval is written to an audit log.
Work out which one you need
Bring us the workflow that is actually costing you time. We will tell you whether it is an automation problem or a document platform problem — including when the answer is that you do not need us.
Last reviewed 2026-07-21. We describe OpenText Content Manager at the level its vendor publicly documents and do not assert specifics we cannot verify. If anything here is out of date, tell us and we will correct it.