Search that works. Permissions you can explain.
We design the structure the estate should have had, close the oversharing, and move content into it — without taking the business down while we do.
Assessment, then remediation and migration scoped from it
What we find in an estate that grew.
Someone creates a Team for a project, which creates a site nobody names properly, with a folder structure copied from a file share, shared with the whole company because that was faster. Multiply by four years.
- 01Sites with no owner, and sites whose owner left before the last reorganization.
- 02Inheritance broken to solve a Tuesday problem and never restored.
- 03The same document in four places, with different names and no way to tell which is current.
- 04A term store nobody maintained, and content types nobody applied.
- 05File shares still acting as the real system of record, with SharePoint used as a backup.
- 06Sharing links, guest access and external members that nobody has reviewed.
- 07Storage consumed by content that has not been opened since it was uploaded.
What lands on your desk
An information architecture
Hubs, site patterns, navigation and the boundary between a Team and a document library — designed against how the business is organized.
A taxonomy people will use
A managed metadata term store and content types small enough to survive contact with real users, and enough to make search work.
A permissions remediation plan
Sequenced so access closes in an order the business can absorb, with the high-risk items first.
A migration plan
What comes across, what gets archived, and what stays behind — decided deliberately rather than by whoever runs the tool.
A governance model
Provisioning, ownership, review and archival, so the estate does not re-accumulate within a year.
A search position
The schema, managed properties and promoted results that decide whether anyone believes the search box again.
Designed first, then moved.
- Assess
Sites, ownership, activity, sharing, external access and storage. What is dead, what is duplicated, and what is quietly high risk.
- Design
The architecture and taxonomy, agreed with the people who own content — because a structure imposed on them is a structure they will work around.
- Remediate
Permissions, orphaned sites and stale links, in an order that does not interrupt the business.
- Migrate
Content moved into the design, with what should not survive the move left behind.
- Govern
Provisioning rules, owners, review cadence and the training that keeps the habits.
SharePoint audit for AI readiness — energy services and construction. We reviewed the estate, found a significant number of high-risk issues, and designed the information architecture along with the other remediation the estate needed — recommending the cleanup ahead of any assistant rollout rather than alongside it.
Before you ask
Can we migrate first and fix the structure later?
You can, and most estates that did are the ones we are called about. A migration is the one moment structure can change without asking people to reorganize their own work.
How disruptive is permissions remediation?
Handled in the wrong order, very. We sequence by risk and by blast radius, communicate what changes before it changes, and keep a rollback for the items most likely to catch someone out.
Bring us the estate.
Forty-five minutes on what you are running, what people cannot find, and what it would take to fix it properly.