Getting started
From Word files to a working knowledge centre
Hazel is a solution accelerator. The foundation is already built and proven, so iomer builds your organization’s version, installs it in your tenant and brings your content across. Most of your effort goes into your content and approval routes.
Go live in five steps
Five steps, in order
-
Step 1
Plan
We map your content, the content types you need and the approval routes each one follows, and review a sample of the documents you’ll migrate.
From you: the owners of your procedures, a sample of documents, and how approvals work today.
-
Step 2
Build
We build Hazel for your organization as a single installation package: your content types and Word templates, approval workflows, taxonomy, audiences, required reading, search and theme.
From you: decisions on types, routes, review cycles and who sees what.
-
Step 3
Install
We install your package in your tenant and test it there with your Microsoft 365 admin. There’s nothing for your IT team to assemble.
From you: an admin to approve the installation with us, and your Entra ID groups.
-
Step 4
Migrate
We bring your Word procedures across in batches. Each document becomes a structured article with an owner, a category and a review date.
From you: authors to resolve the documents that need a decision, and a willingness to clean up as you go.
-
Step 5
Launch
Training for authors and admins, and a launch plan for staff. As your needs change, we build and install a new version of your package.
From you: a knowledge owner and a group of authors.
Everyone on board
Bring operations, compliance and IT into the conversation early. A knowledge centre touches all three.
Who’s involved
Migration
Word document in, governed article out
Migration is usually the biggest part of any knowledge project, which is why Hazel reads Microsoft Word documents. Authors fill in a template or import an existing document, headings map to sections, and the details table supplies the owner and topic. The same parser runs in bulk, with a dashboard that tracks each batch and lists the documents that need a decision.
We scope migration separately, so you can see the effort before you commit.
What sets the size of a migration
- How many documents you have
- How consistent their structure is
- Whether they carry images or complex tables that need rework
- How much you want to retire or merge on the way
Headings, lists, bold, italic and tables come across from Word. Images and complex layouts need rework.
Before we talk
Questions to think about
You don’t need answers to all of these for a first conversation. They’re what tells us how Hazel fits, who else should be involved, and how big the job is.
Where does your organization’s know-how live today: Word files, shared drives, intranet pages or people’s heads?
The answer sizes the migration and shows what still needs writing down.
When someone on the front line needs an answer, what do they do?
If they ask a colleague, search is where to start.
What do people search for most, and what can’t they find?
Hazel’s insights show top searches and searches with no results, so gaps surface instead of hiding.
How much of your content is out of date, duplicated or without an owner?
This sizes the clean-up, and sets review cycles from the first day.
Who owns each area of knowledge, and who keeps it current?
They become Hazel’s knowledge owners and authors, with a review date on every article.
What knowledge leaves when an expert retires or moves on?
Content types and templates turn what experts know into articles anyone can follow.
How do you organize content now: by product, department, regulation or process?
This shapes the taxonomy and the filters.
Which kinds of content do you need: procedures, job aids, FAQs, product or system guides?
Each becomes a content type with its own template, and existing templates come across.
How do staff find out that something has changed?
Required reading and a short change summary reach the right audience.
Are you rolling out Microsoft 365 Copilot or agents?
They answer from whatever they can find. Hazel gives them one current, approved version to find. AI answers in Hazel are optional.
Is any content restricted to specific teams?
Restricted articles need a permissions design.
Which intranet do you run, and which languages do staff need?
Hazel sits on SharePoint pages in your intranet. Multilingual content is a design item to raise early.
Why a solution accelerator
The benefits of off-the-shelf and custom, without the trade-offs
No two organizations are the same, but every knowledge centre needs the same foundation. Hazel gives you that foundation already built, and builds the rest around you.
| Off-the-shelf software | Custom build | Hazel solution accelerator | |
|---|---|---|---|
| Fits how you work | You adapt to it | Built around you | Your types, routes, audiences and theme are built in |
| Proven before you start | Yes | No, tested as it’s built | Yes, the foundation is already built and tested |
| Time to go live | Fast to start, slow to fit | Slow, everything is built from scratch | Faster, because only your parts are built |
| Who sets it up | Your team | Your developers or a partner | iomer, as one installation package |
| Where it runs | Usually the vendor’s cloud | Wherever it’s built | Your own Microsoft 365 tenant |
| Cost | Per-user subscription | An open-ended project | Scoped with you first, then a work estimate and proposal |
| Changes later | Wait for the vendor’s roadmap | Another project | A new version of your package, built and installed by iomer |
Pricing
Scoped with you first, then a work estimate and proposal
We start by working through your content, content types and approval routes with you. Then we give you a work estimate and a written proposal for building, installing and migrating, so you can see the effort before you commit.
What the estimate depends on
- How many content types and approval routes you need
- How much content you migrate, and its condition
- Restricted content, languages and the number of business units
- Whether you want AI answers
Already running Beacon or Journey? Hazel can share the same SharePoint site design, Entra ID groups and governance set-up.
What happens next
From first call to proposal
Watch the 30-second tour first Download the datasheet (PDF, 2 pages)
- Discovery call
We learn how procedures work today and what matters most.
- Tailored walkthrough
Thirty minutes with Hazel, set up with a procedure like one of yours.
- Scoping workshop
Content types, routes, taxonomy and a sample of the content to migrate.
- Proposal
A written proposal with the work estimate and timeline.
See Hazel with a procedure like one of yours
Book a 30-minute walkthrough set up with a procedure like one of yours, or take the evaluation kit away and come back when you’re ready.