Nobody can say who owns a shared site or folder anymore
It was set up years ago, for a project that finished, and it's still being used by habit.
Enterprise engineering
Information governance and privacy controls.
Make sensitive information easier to find, share and protect. Kritical turns your approved privacy and records requirements into usable access, collaboration, retention and handover controls.
On this page
Choose where to start.
Jump to the part that matches the problem or decision in front of you.
Use the arrows or scroll to see every card.
Three situations bring people to this page.
A migration left records harder to find than before
Files moved; the structure and metadata that made them findable didn't come with them.
A retention or records requirement needs to become technical work
Legal or the business has decided what to keep and for how long; nobody's turned that into configuration yet.
What you get: a review that starts with the problem people are experiencing.
Perhaps teams keep several versions of the same document, nobody knows who owns a shared site, or a migration has left important records difficult to find. We map the repositories, business processes, owners and access paths involved. A focused review identifies a practical first improvement without assuming every file or application needs to move.
A structure with a clear owner, not just a tidier folder tree.
Agree how teams organise working documents and records, what information helps people find them and who can approve access. We scope collaboration and records work across Microsoft 365, SharePoint and connected systems, considering shared spaces, external collaboration and staff changes so the structure stays understandable after the initial cleanup.
Why Kritical: we implement retention decisions, we don't make them for you.
Your records, legal and business owners decide what must be kept, for how long and under which exceptions. We map those approved requirements to the relevant systems, configuration and operating procedures.
- Technical delivery, not legal advice We check required platform features and licences before implementation. Technical configuration doesn't replace specialist advice or certify compliance.
- Gaps identified before a wider rollout The work includes reviewing existing settings, identifying gaps and planning a controlled rollout.
- Continuity planned around your account We aim to provide continuity through a consistent lead or delivery group where the agreed scope and service model support it. Your proposal sets out the contact model, cover and handover arrangements that apply.
A migration that preserves what the records mean.
Moving documents also means dealing with metadata, ownership, versions and permissions. We establish what should move, what needs review and how the receiving system represents it, agreeing mapping, representative checks and the handling of exceptions before a wider transfer. Your information owners approve disposal and retention decisions; deletion is never treated as an automatic cleanup step.
How it's priced, and what a first engagement leaves behind.
A scoped engagement is quoted in writing and can deliver a repository and ownership map, proposed information structure, access model, migration plan and a prioritised set of technical changes. Implementation includes the agreed checks and operating instructions. We explain how new sites, users and records enter the process, who reviews exceptions and which work remains outstanding.
- First call We confirm where information is stored, who uses it and what's getting in the way.
- The agreed first phase Start with an assessment or one business area, priced in writing, then decide what to extend.
- Get a quote Send the systems and constraints involved and we quote the work. Learn more
Follow a records-control question into the systems that carry it.
Information governance becomes useful when ownership, access and system behaviour are visible together. Set the delivery boundary, then move to the specialist evidence needed for the real constraint.
Follow a records-control question into the systems that carry it.
- Make ownership and handover explicitUse the responsibility boundary to identify who approves records controls and who operates the resulting systems.
- Investigate the performance of the information pathIf a repository, integration or application is slow after a governance change, follow the evidence into performance engineering.
Explore the relevant technologies.
Use these guides to see which technologies can help with the job in front of you.
Microsoft
Workplace, identity, cloud and business applications, connected to a clear implementation or support requirement.
Questions before you enquire
Can you improve the environment we already have?
Yes. Start with the repositories and the problem your people are experiencing. A review can identify configuration, ownership or process changes before recommending replacement.
Can you help with SharePoint and Microsoft 365?
Yes. We can scope information structure, sharing, permissions, migration and the implementation of approved lifecycle requirements. The exact configuration depends on your environment and licences.
Will this tell us what records we are legally required to keep?
Your qualified advisers and records owners establish those requirements. Kritical scopes the technical work needed to implement and verify the decisions they approve.
What should we bring to the first conversation?
Describe where information is stored, who uses it and what's getting in the way. An example workflow or repository list is useful; confidential documents and credentials can stay out of the initial enquiry.
Can this connect to our identity and access work?
Yes. Sharing and permission structures depend on the same identity foundations covered in our identity and access engineering, and the two are often scoped together.
Related services
Microsoft 365
When licences, accounts, email, shared files and devices are difficult to administer together, Kritical brings them into one coherent environment — configured and checked against agreed requirements, with ongoing administration scoped separately as your business changes.
Identity & access
When access is inconsistent, over-permissioned or difficult to recover, Kritical improves identity across Active Directory, Microsoft Entra ID and connected applications, so people and services get the access they need and nothing more than that.
Business systems
When finance, sales and commerce run on applications that don't talk to each other, someone on your team is manually reconciling numbers that should already match.
Application integration
When records are duplicated, delayed or stuck between systems, Kritical builds integrations around clear ownership and recovery, so the business process completes instead of needing a person to reconcile it by hand every week.
Resources
Use these practical guides to prepare for a renewal, a business-system change or a secure AI project.
Let’s define the next step.
Tell us what you want to achieve, what you have today and when it matters.