Getting started
From scattered announcements to one news centre everyone reads
Chronicle is a solution accelerator. The foundation is already built, so iomer builds your organization’s version, installs it in your tenant and pilots it with you. Most of your effort goes into deciding your topics, templates and approval routes, and who runs the news centre.
Go live in five steps
Five steps, in order
-
Step 1
Plan
Agree your topics, departments, templates, approval routes and archive rules with us, and check department and manager data in Entra ID. We also look at how news goes out today, who writes it and who approves it.
From you: a few recent stories, how approvals work now, and someone from internal communications, IT and records for a workshop.
-
Step 2
Build
We build your news brand, templates, workflows, routing rules and lifecycle rules into your package. It’s one deployment package for your tenant, and we set up your topics, departments and leads when we install it.
From you: your brand colours and fonts, example stories for the templates, and decisions on routes.
-
Step 3
Install
We install Chronicle on your news site, help your admin approve two permissions, run the guided setup and apply the permissions. We create the Chronicle groups, give people their roles and install the two Power Automate flows if you want them. There’s nothing for your IT team to assemble.
From you: a SharePoint administrator for the app catalog and the two approvals, a site owner on your news site, and a service account if you want the flows.
-
Step 4
Pilot
Start with one or two departments’ news, then adjust templates and routes before everyone writes. We review the first stories and approvals with you.
From you: one or two departments to pilot with, and feedback from their authors and approvers.
-
Step 5
Launch
Train authors and approvers, add news web parts to your intranet home and department sites, and go live. As your needs change, we build and install a new version of your package.
From you: a news owner who will run Chronicle day to day.
Everyone on board
Bring your head of internal communications, a department communicator, an approver such as a department lead, someone from IT and someone from records into the conversation before the proposal. Chronicle touches all of them.
Who’s involved
Starting from what you have
Your existing news and how it’s run
Your news categories become topics, the formats you publish most become templates, and the way approvals work today becomes workflows and routing rules. Your existing SharePoint news pages stay where they are: Chronicle doesn’t import them, so we agree with you which to leave, which to take down, and whether any should be rewritten in Chronicle.
We scope this with you, so you can see the effort before you commit.
What sets the size of the job
- How many templates you need, and how much design they need
- How many approval workflows and routing rules, and who approves what
- How much your Entra ID department and manager data needs tidying
- More than one news site, business unit or brand
- Whether you want the flows, Herald and news web parts
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 Chronicle fits, who else should be involved, and how big the job is.
Where does your news go out today, and who writes it?
SharePoint news, all-staff email, Teams posts or a mix. It shows us how many voices there are, and where news gets lost or repeated.
How many departments or locations publish news, and who should approve each?
These become your departments, their leads and the routing rules that send news to them.
Does approval follow the reporting line today, or go to named people?
Routes can go to the author’s manager, a department or topic lead, a campaign owner or a named person.
Which kinds of story do you publish most, and do they need their own look?
Leader messages, quick updates, features, event recaps or change notices. Each can have its own template, and your brand sets the look.
How long should news stay current, and when should it come down?
Your archive and delete periods, by topic or campaign if they differ. Bring in your records staff early.
Do you run campaigns, such as a benefits enrollment or a safety year?
Campaigns group news for a goal and a period.
How reliable is your department and manager data in Entra ID?
Manager approvals, department routing and News for you depend on it. Gaps mean a clean-up task before go-live.
Who will run the news centre day to day?
Chronicle needs an owner, usually the head of internal communications.
Will you use the Power Automate flows for email and scheduling?
They send approval emails, publish scheduled news and archive on time. Without them, Chronicle works on demand.
Which other sites should show the news?
Twelve news web parts put headlines, a ticker or topic tabs on any SharePoint site.
Do you also send email newsletters?
If you use Herald, iomer’s newsletter accelerator, Chronicle can suggest stories to it and share campaigns.
Are you using Hazel, Beacon, Journey or another iomer accelerator?
Your IT team already knows how iomer installs and updates an accelerator, and Chronicle is administered the same way, with the same kind of roles and setup checks.
Why a solution accelerator
The benefits of off-the-shelf and custom, without the trade-offs
No two organizations are the same, but every news centre needs the same foundation. Chronicle gives you that foundation already built, and builds the rest around you.
| Communications software | Custom build | Chronicle solution accelerator | |
|---|---|---|---|
| Fits how you work | You adapt to it | Built around you | Your templates, approval routes, topics and archive rules are built in |
| Designed before you start | Yes | No, designed as it’s built | Yes, the foundation is already built |
| 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 deployment package |
| Where records live | Usually the vendor’s cloud, with its own sign-in | 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
Every Chronicle engagement starts by working through your news with you: the topics, templates and approval routes you need, whether you want the flows, and how much help you want with launch. Then we give you a work estimate and a written proposal for building, installing and piloting, so you can see the effort before you commit.
What the estimate depends on
- How many templates, workflows and routing rules you need
- Whether you want the Power Automate flows, Herald and news web parts
- How many departments, locations or news sites are involved
- How much help you want with training and launch
Chronicle runs on the Microsoft 365 you already have: SharePoint Online for the news site, and a service account with Exchange Online and Power Automate if you want the flows. Already running an iomer accelerator? Chronicle installs the same way.
What happens next
From first call to proposal
Watch the 50-second tour first Download the datasheet (PDF, 2 pages)
- Discovery call
We learn how news goes out today and what matters most.
- Tailored walkthrough
Thirty minutes with Chronicle, set up with topics and routes like yours.
- Scoping workshop
Your topics, templates and routes, your data and your archive rules. It produces your news centre design and a work estimate.
- Proposal
A written proposal with the work estimate and timeline.
See Chronicle with news like yours
Book a 30-minute walkthrough set up with topics and approval routes like yours, or take the evaluation kit away and come back when you’re ready.
