Records you can defend.Decisions you can trace.

Governance, compliance, and information architecture built for accountability at scale. When an auditor, a regulator, or a court asks how a decision was made, the answer is already documented, retrievable, and defensible.

Request a briefing

20+ years in regulated industriesWork delivered personally, never offshored

Capabilities

The discipline behind information you can stand behind.

StructureGovernance & information architectureRecords management, taxonomy, metadata, and retention designed so the right information is findable and the wrong information is not kept longer than it should be.

DefensibilityRisk, compliance & audit readinessControls, classification, and eDiscovery-ready records so audits, FOIA and public-records requests, and legal holds are routine, not fire drills.

DeliveryStrategy & delivery that shipsRoadmaps that survive contact with reality. Migrations, capture, and contract lifecycle work that gets implemented, not just diagrammed.

Our approach

Assessment to managed services, on one accountable path.

01AssessmentUnderstand the records, the risk, the systems, and the obligations you operate under.

02ArchitectureDesign the taxonomy, retention, security model, and information architecture to fit them.

03ImplementationMigrate, configure, and capture. SharePoint architecture, OpenText, and EzeScan where they fit.

04Managed servicesKeep it healthy. Governance is not a project you finish. It is a standard you hold.

Where this depth comes from

Two decades of regulated work, named plainly.

Enterprise and government buyers usually arrive here by referral. This is the one place the depth of the background leads rather than hides.

RecordsGovernance & eDiscoveryClassification, retention schedules, legal holds, and defensible disposition across large document estates.

ContentCapture & contract lifecycleHigh-volume document capture with EzeScan, and contract lifecycle from intake through renewal and audit.

PlatformsOpenText, SharePoint, DocuSign CLM, EzeScanFour platforms worked in depth rather than a logo wall. OpenText and contract lifecycle are covered in detail below. SharePoint and OpenText information architecture, plus migrations that preserve history, permissions, and metadata.

OpenText

Content Server is where the record actually lives.

Most of the estates we are called into have OpenText somewhere near the middle of them. Content Server, eDOCS, Documentum alongside it, twenty years of accumulated structure, and a business that has changed shape several times since any of it was designed. The platform is rarely the problem. The problem is that the classification, the retention and the permissions stopped matching how the organisation actually works, and nobody has been able to say so out loud.

ArchitectureClassification that survives a reorganisationCategories, attributes and the classification tree designed against obligations rather than the current org chart. When departments merge or a function moves, the records model does not need rebuilding, because it was never wired to the structure in the first place.

RecordsRetention and defensible dispositionRecords Management configured so retention applies itself by content type and disposition actually happens. An estate where nothing is ever destroyed is not a cautious estate. It is an expensive one, and it is a discovery liability every time litigation lands.

MigrationOnto OpenText, off it, or between versionsContent Server upgrades, consolidation of multiple instances after an acquisition, and moves to and from SharePoint. Metadata, version history, audit trail and permissions are carried across, because a migration that drops them has not moved the record, only the file.

HonestySometimes the answer is to keep itPlenty of consultancies arrive determined to move you off OpenText because that is what they sell. If Content Server is doing work that SharePoint cannot, we will tell you to keep it and fix what is actually broken. We have no licence resale interest in that decision either way.

Where OpenText work usually starts

Four situations we get called into.

The audit

Nobody can prove what the retention rule isPolicy says one thing, the system does another, and the gap only surfaces when a regulator asks. We reconcile the written schedule against what is actually configured, then close the distance between them.

The acquisition

Two instances, two taxonomies, one companyBoth estates are internally consistent and mutually incompatible. We design the target model, decide what merges and what stays separate, and move it without a year of committee.

The sprawl

Content Server, file shares, and SharePoint all holding recordsThree places that each believe they are the system of record. We establish which one is, and give the others a defined job that is not record keeping.

The exit

A platform decision has already been made above youSometimes the migration is not up for debate. In that case the work is making sure the record survives the move intact, and that the obligations that lived in the old system are carried into the new one rather than quietly dropped.

DocuSign and contract lifecycle

The agreement is signed. The obligations are not tracked.

Signature is the part everyone can see, so it is the part that gets solved first. What survives the signature is the harder problem. Renewal dates, auto-renew clauses, notice periods, indemnity caps, service credits and the obligations your own organisation took on. Those live in the document, and a document nobody has read since execution is not a control.

IntakeRequests arrive somewhere other than an inboxStructured intake that captures counterparty, value, term and risk category before legal opens anything. The routing decision gets made on data rather than on whoever happened to read the email first.

LifecycleClause libraries, playbooks and approval pathsStandard positions and pre-approved fallbacks configured in DocuSign CLM so routine agreements move without counsel touching every one, and the ones that genuinely need review are the ones that reach a lawyer.

ObligationsThe dates that cost money when missedRenewals, notice windows and milestones extracted at execution and surfaced before they matter. An auto renew nobody noticed is one of the most expensive administrative failures in an organisation, and it is entirely preventable.

DiscoveryLegal hold and eDiscovery that hold upHolds that apply and release cleanly, with collection, processing and review scoped so ESI volumes are handled by classification rather than by document by document review.

IntegrationAgreements connected to the systems around themCLM joined to the records estate and to finance, so a signed agreement updates the obligation register and the contract file at the same time instead of being rekeyed into both.

SpecialistsNamed DocuSign expertise on the engagementContract lifecycle work is brought in with a dedicated DocuSign specialist rather than handled generically. Configuration depth on the platform matters more here than general ECM experience does.

Bring us a hard information problem.

Governance, compliance, or an architecture that has outgrown itself. We will tell you plainly what it takes to make it defensible.

Request a briefing