Grammar, Clarity & Tone Rewrites
Context-aware rewrites for HR text: fix grammar and spelling, enhance clarity, remove redundancy, active voice; six tones from professional to diplomatic; four styles from formal to storytelling.
Smarter, Faster, More Accurate HR Content with AI
HR and benefits teams create hundreds of messages every month — policy updates, open enrollment notices, FAQs, and employee emails.
IntelliEdit is the writing assistant inside the editor those messages are already written in. Highlight a paragraph, pick a named rewrite — shorter, friendlier, plain language, employee-friendly benefits wording — and read the result with its readability and tone scores before you insert it or replace the box. Numbers, dates and regulatory wording stay as you wrote them.
27 named rewrites + customNumbers, dates, legal wording keptScores in an instantOn every writing screen
Redefining HR Content Creation with AI
"A general-purpose writing tool lives in another tab. You copy the paragraph out, ask for a rewrite, paste it back, and hope the deadline and the legal sentence survived the round trip. IntelliEdit is the assistant inside the box you are already typing in — on the template, the ticket reply, the note, the content block — with rewrites written for benefits communication and a frame that keeps the numbers, dates and regulatory wording exactly where you put them."
HighlightA sentence, a paragraph, or the boxChoose a Rewrite27 named operations, or your own wordsRead the ScoresReadability, clarity, tone — instantlyInsert or ReplaceYou decide; the form savesTemplates & ConfigShared snippets, one editor setup
27named rewrites in six groups — rewrite, tone, clarity, style, benefits language, enhancement — plus custom instructions in your own words
0model calls for the scores: readability, clarity, tone and engagement are computed from the text itself, instantly
30–40%less drafting time — the live estimate — when the rewrite happens inside the form instead of in another tab
1editor shared by every writing screen, so a snippet saved once and a configuration set once serve templates, tickets, notes and content blocks alike
Working flow
Who Clicks What, in Order
The editor and its assistant as they run today — who does what, in order, and the rule the platform enforces at each step.
| # | Who | What they do | What the platform enforces |
|---|---|---|---|
| 1 | Administrator | Maintains named editor configurations in the configuration console — toolbar, insert buttons, fonts, colors, height — and marks one as the default. | Marking a configuration default clears the flag on every other; explicit settings a screen passes win over the default. |
| 2 | Author | Writes in the editor on a template, a ticket, a case, a note or a content block. | The editor loads the default configuration once; the screen it sits on owns the save. |
| 3 | Author | Highlights the text to rewrite — or nothing, to work on the whole box — and clicks BR IntelliEditor on the toolbar. | The selection is saved before the assistant opens so the highlight is not lost; the assistant is available only where the screen has enabled it. |
| 4 | Assistant | Opens with the text, loads the rewrite catalog and scores the text — counts, reading time, readability, clarity, tone, engagement — with suggestion chips. | Scores are arithmetic on the text; no model is called until the author picks an operation. |
| 5 | Author | Picks a named rewrite — or a suggestion chip, or types custom instructions. | An unknown operation fails before any model call; custom instructions apply only to the custom operation. |
| 6 | Model | Rewrites the HTML it was given inside the standard frame: keep the meaning, numbers, dates and regulatory wording unless the operation asks otherwise; self-check meaning, tone, tags and named plans; return an HTML fragment only. | The result is cleaned of stray formatting and scored again; the token budget scales with the source length, larger for expansion operations. |
| 7 | Author | Steps Back and Forward through this session's rewrites, compares scores, and decides. | History is kept only for the open assistant; closing it discards the rewrites. |
| 8 | Author | Chooses Replace (the whole box) or Insert (at the saved cursor). | Only the editor contents change; the host screen is notified and saves when the author saves it. |
| 9 | Administrator | Optionally saves the result as a shared template — title, description, HTML — or retires one. | Templates are shared snippets; a normal delete deactivates rather than removes. |
One Paragraph, Five Steps
Follow an Open Enrollment reminder from a dense first draft to a plain-language paragraph the author inserts — and the snippet an administrator keeps for next year.
The assistant is on the toolbar of the box you are already in
The benefits manager is editing the Open Enrollment reminder template in Communication Hub. The editor is the same one used on ticket replies, case notes and Employee Home content blocks, so its toolbar — styles, fonts, lists, tables, links, images, full screen — is familiar. She highlights the two dense paragraphs about renewal and clicks BR IntelliEditor. The editor saves her selection first, because the toolbar sits outside the writing area and would otherwise drop the highlight, then opens the assistant with that text. Had she selected nothing, the whole box would be the text.
What the step does
- Selection or whole box — the author decides the scope before the assistant opens
- Available where the screen has turned it on for the signed-in person
- The personalization button next to it inserts merge attributes — a picker, not an AI step
- Nothing leaves the form; the host screen still owns the save
Why it matters
No copy-out, no paste-back, no lost legal sentence.
The same assistant on every writing screen means one habit to learn.
Twenty-seven named rewrites — or say it in your own words
The assistant lists the catalog in six groups. Rewrite: improve, shorten, lengthen, simplify, paraphrase. Tone: professional, friendly, confident, casual, diplomatic, engaging. Clarity: fix grammar and spelling, enhance clarity, remove redundancy, active voice. Style: formal, conversational, persuasive, storytelling. Benefits: employee-friendly, compliance-ready, ACA-compliant wording, plain language, highlight benefits. Enhancement: add examples, add data points, boost engagement. And Custom, where the author's own instructions become the operation. She picks Plain language. Every operation runs inside the same frame: keep the meaning, the numbers, the dates and the regulatory wording unless the operation asks for that change; check meaning, tone, tags and named plans; return only an HTML fragment.
What the step does
- Benefits-language operations written for HR — employee-friendly, plain language, compliance-ready wording
- Suggestion chips from the scores can run an operation in one click
- Expansion operations get a larger writing budget; every operation keeps existing structure and links
- "Add data points" inserts marked placeholders — [X%], [number] — for the author to fill from the source
Why it matters
A rewrite never quietly changes a deadline or a legal sentence.
Compliance-ready and ACA-compliant are wording rewrites — they make regulatory text readable; your review still decides.
Scores in an instant — before and after every rewrite
When the assistant opens, and again after each rewrite, it measures the text without calling a model: words, characters, sentences, paragraphs and reading time; a reading-level estimate turned into a readability score, where an easier grade scores higher; clarity, which starts at 100 and loses points for long sentences, long words and passive voice; a professional-tone score that rises for formal words and falls for contractions and slang; and an engagement score. The dense original scores 65 on clarity; the plain-language rewrite scores 90. The same measures produce the suggestion chips — Shorten, Shorter sentences, Active voice, Employee-friendly, Plain language, Grammar — each one an operation the author can run in a click.
What the step does
- Nine measures from the text itself — no waiting, no model cost
- Chips appear when a threshold is crossed: under 50 words, over 500, average sentence over 25 words, passive voice over 20%
- Benefits words with a low readability score suggest Employee-friendly; jargon suggests Plain language
- Re-scored as the author steps through the session history, so versions can be compared
Why it matters
"Is this easier to read?" gets a number, not an opinion.
Scores are arithmetic and word lists, shown as guidance — the author still reads the paragraph.
Insert or replace — the author decides, the form saves
She reads the rewrite beside the scores, steps Back once to compare it with the Shorten result she tried first, and returns. Replace writes the active result over the whole box; Insert writes it at the cursor the editor saved when the assistant opened. She chooses Insert to put the plain-language paragraph where the selection was, and the assistant closes. The template screen is told its text changed and saves when she saves it — IntelliEdit never saves the communication, the ticket or the note itself.
What the step does
- Back and Forward move through this session's rewrites; closing the assistant discards them
- Replace = the whole box; Insert = at the saved cursor — the author chooses
- With nothing generated yet, Replace and Insert use the original text — no surprise edits
- Export and share use the generated HTML when it exists, otherwise the original
Why it matters
Full editorial authority — every accepted word passed through a person.
The host screen's own save, review and send steps are unchanged.
Shared snippets and one editor configuration
An administrator working in the assistant can save a good result as a template — a title, a short description and the HTML, placeholders included — and every author on the platform can search the library, load a template as the working text, rewrite it, and insert it. Separately, the configuration console holds named editor configurations: which insert buttons show (link, image, video, rule), fonts, sizes, colors, height, and which configuration is the default that every editor loads. A screen can still pass its own settings, which win.
What the step does
- Template library: search by title or description; apply into the assistant; rewrite before inserting
- Administrators create, update and retire templates; a normal delete deactivates rather than removes
- Editor configurations: toolbar, insert buttons, fonts, colors, size, custom toolbar layout; one default
- Generate from a brief: a second path that writes new HTML from a requirement, with the same frame and the larger budget
Why it matters
One snippet, one setup, every writing screen.
Templates are shared rows for the whole organisation — write them as the house voice.
Ground rules
Rules of the Assistant
What an author can rely on and what a reviewer can check — from the editor as it runs, not from a brochure.
| Rule | How it behaves | Why it matters |
|---|---|---|
| It rewrites what it is given | The assistant transforms the text in the box; it does not read plans, employees, filings or the configuration. | A rewrite is a writing step, never a lookup — verifying a figure is your review, and Athena for Admins can look it up. |
| Meaning, numbers, dates and legal wording stay | Every operation runs inside the same frame: do not change intent, figures, dates or regulatory wording unless the operation asks; self-check before answering. | The deadline and the notice sentence survive every rewrite. |
| Placeholders, not statistics | "Add data points" inserts marked placeholders such as [X%] or [number]. | A number in a draft is always one a person typed. |
| Compliance-ready is wording | Employee-friendly, compliance-ready, ACA-compliant wording and plain language are rewrite instructions. | They make regulatory text readable; they do not certify it. |
| Scores are arithmetic | Readability, clarity, tone and engagement come from counts and word lists, instantly, with no model call — and are recomputed after each rewrite. | Guidance you can trust to be consistent, shown as numbers, read by a person. |
| Nothing changes until you say so | Replace writes the whole box; Insert writes at the saved cursor; with nothing generated, both use the original. | Full editorial authority, every time. |
| The form saves, not the editor | The screen the editor sits on — template, ticket, case, note, content block — owns save, review and send. | IntelliEdit never sends a message or closes a ticket. |
| History lives in the session | Back and Forward move through the rewrites of the open assistant; closing it discards them. | No hidden archive of drafts. |
| Templates are shared | Administrators save snippets for everyone; a normal delete deactivates rather than removes. | Write them as the house voice. |
Core Capabilities That Power BR IntelliEdit
Six pieces — the catalog, the benefits operations, the scores, the brief, the library and the configuration — that make one editor serve every writing screen.
Benefits-Language Operations
Employee-friendly, compliance-ready, ACA-compliant wording, plain language and highlight benefits — rewrites written for benefits communication, inside a frame that keeps numbers, dates and regulatory wording intact.
Scores & Suggestion Chips
Words, sentences, paragraphs, reading time, readability, clarity, professional tone and engagement — computed from the text in an instant, with one-click chips for the operation that would help most.
Generate from a Brief
A second path that writes new HTML from a requirement rather than transforming existing text — same frame, larger writing budget — for the blank-page moment.
Shared Template Library
Administrators save good results as snippets — title, description, HTML with placeholders — that every author can search, load as working text, rewrite and insert.
Embedded, Configured Once
One editor on Communication Hub templates and personalization, BR Resolve tickets and cases, notes, Employee Home content blocks and the employee case form — with named configurations and one default maintained in the configuration console.
A General Writing Assistant vs. IntelliEdit
Benefits teams already have access to AI that writes well. What they lack is AI that sits inside the form, speaks benefits, and leaves the deadline alone.
| The task | General-purpose AI writing tool | BR IntelliEdit |
|---|---|---|
| Where you work | Another tab; copy out, paste back. | The editor you are typing in — template, ticket, note, content block. |
| Choosing a rewrite | Write a prompt each time. | 27 named operations in six groups, plus custom instructions. |
| Benefits wording | Generic "make it professional". | Employee-friendly, plain language, compliance-ready wording — written for HR text. |
| The deadline and the legal sentence | Often "improved". | Kept. Every operation runs inside a frame that leaves numbers, dates and regulatory wording alone. |
| "Is it easier to read?" | Ask, and get an opinion. | Scores before and after — readability, clarity, tone — from the text itself, instantly. |
| Reusing a good paragraph | A personal notes file. | A shared template library every author can search and load. |
| Accepting | Paste over and hope the formatting held. | Insert at the cursor or replace the box , structure and links kept; the form saves. |
IntelliEdit and the rest of BR Intelligence
The Rewrite Is One Step — the Facts Come From Elsewhere
IntelliEdit changes how a paragraph reads. Whether the paragraph is right is a different question, and the platform answers it in other places: Athena for Admins looks up the deadline or the rate from the screen you are configuring; AutoResponse drafts a ticket reply from the employee's record before IntelliEdit polishes it; Athena for Employees explains the sent message to the person who received it.
- Before you write: ask Athena for Admins "when does OE close this year?" — the answer comes from the plan-year setup, with the screen linked
- While you write: IntelliEdit rewrites for tone, clarity and plain language and keeps the date you typed
- On a ticket: AutoResponse drafts from the employee's record in BR Resolve; the agent polishes with IntelliEdit and sends
- After you send: Athena for Employees quotes the message back to the employee who asks what it means for them
- Across the platform: one editor, one template library, one configuration — the same assistant on every form
When does Open Enrollment close this year, and what happens to people who don't act?
Athena · from the screen help and setupThe 2027 Open Enrollment window closes on November 14 in the plan-year setup. Employees who take no action keep their current elections — the default-enrollment rule on the enrollment period screen renews the existing plan at the new plan-year rate.
Open enrollment periodsOpen default enrollment
Thanks — I'll write the reminder now.
AthenaWhen you're in the template, highlight the renewal paragraph and pick Plain language in BR IntelliEditor — it will keep "November 14" and the rate merge field exactly as you type them. I don't write the template myself; the editor does that with you.
Ask about this screen…
Why HR Teams Choose BR IntelliEdit
Speed and Efficiency
Cuts content turnaround time by 30–40% — the live estimate — because the rewrite, the scores and the snippet library are on the toolbar, not in another tab.
Compliance Confidence
Regulatory wording, dates and figures survive every rewrite by design; compliance-ready and ACA-compliant wording make notices readable without touching what they must say.
Brand Consistency
Maintains tone uniformly across departments — the same named tones, the same shared templates, the same editor configuration on every writing screen.
Readability You Can Measure
Readability, clarity and tone scores before and after, computed in an instant — so "easier to read" is a number the team can agree on.
Improved Employee Clarity
Produces clearer, easier-to-understand messages — plain language and employee-friendly rewrites for the notices, replies and job aids employees actually read.
Platform-Native Scalability
Integrates within Benefits Reimagined and SAP SuccessFactors — and every other synced HRIS — so one assistant serves a shared-services center writing for many employer clients.
Work Smarter with AI-Enhanced HR Editing
IntelliEdit has no screen of its own for authors. It is the box — and the assistant on its toolbar — on every place a person writes in the platform. Administrators have two screens: the editor configuration page in the configuration console, and the template library inside the assistant. Each host screen keeps its own save, review and send.
- Communication Hub — template bodies and personalization text; the Hub sends, tracks and evidences the message
- BR Resolve — ticket and case text, notes, and the reply an agent polishes before sending
- Content Management — text components for Employee Home screens and organisation updates
- Employee case form — the description an employee writes when opening a case
- Configuration console — named editor configurations, one default; the template library for shared snippets
Four Stories, End to End
Four moments from one week of benefits writing, each traced through the flow above.
The dense renewal paragraph
The benefits manager highlights two paragraphs of an OE reminder template, opens the assistant, tries Shorten, steps Back, and picks Plain language. Clarity moves from 65 to 90; "November 14" and the rate merge field are untouched. She inserts it at the cursor and saves the template in Communication Hub.
The ticket reply at 4:55
An agent in BR Resolve has a correct but blunt explanation of a doubled deduction. Friendly tone, then Employee-friendly; the amounts and pay date stay exactly as typed. Replace, then the agent reads it once more and sends from the ticket — the editor never sent anything.
The blank content block
A new Employee Home block needs an intro nobody has written. Generate from a brief produces a first draft from one sentence of requirements; the author runs Shorter sentences from the chip, inserts, and publishes the block from Content Management.
The snippet that outlived its author
An administrator saves the plain-language renewal paragraph as a template with a title and description. Next year's author searches "renew", applies it as working text, changes the date, and inserts — the house voice, kept in the library, not in someone's mailbox.
Bring the Paragraph You Rewrite Every Year
An Open Enrollment launch, a COBRA notice, a plan-change FAQ — bring the dense version. We'll open it in the editor, run Plain language and Employee-friendly in front of you, show the scores move, and save the result as a template for next year.
Numbers, dates, legal wording keptScores without a model callYou insert or replaceNothing stored by the assistant
BR IntelliEdit FAQs
It's an AI-powered HR content editor that improves grammar, tone, and compliance-ready wording in employee communications. It is the rich-text box every writing screen in Benefits Reimagined shares, with a writing assistant on the toolbar: highlight text, pick a named rewrite — shorten, friendlier tone, plain language, employee-friendly benefits wording — and insert the result or replace the box.
Wherever a person writes in the platform: Communication Hub templates and personalization, ticket and case text in BR Resolve, notes, content components for Employee Home, and the employee case form. Each of those screens owns the save; IntelliEdit changes only the text in the box.
Every rewrite runs inside the same frame: the assistant is told not to change the meaning, the numbers, the dates or the regulatory wording unless the operation you chose asks for exactly that, and to check meaning, tone, tags and named plans before it answers. The benefits operations — employee-friendly, compliance-ready, ACA-compliant wording, plain language — are wording rewrites; they make regulatory text readable, they do not replace a compliance review.
No. IntelliEdit rewrites the text it is given; it does not read plans, employees or filings. "Add data points" inserts clearly marked placeholders such as [X%] for you to fill from the source, never live statistics. Verifying a deadline or a rate against configuration is your review step — and Athena for Admins can look the figure up for you.
From arithmetic on the text, not from the model: word, sentence and paragraph counts, reading time, a grade-level estimate turned into a readability score, and clarity, professional-tone and engagement scores from sentence length, long words, passive voice and word lists. They run when the assistant opens, after each rewrite, and as you step through the session history — instantly, with no model call.
No — it's embedded within the platform and ready to use from day one. Administrators can maintain named editor configurations (toolbar, insert buttons, fonts, colors, size) and choose the default; the rewrite catalog is the same for everyone.
Yes — users can accept, reject, or modify AI edits to maintain full editorial authority. Nothing changes until you choose Insert or Replace; Back and Forward move through the rewrites of this session; closing the assistant discards them; the host form is saved only when you save it.
Reusable snippets an administrator saves from the assistant — a title, a description and the HTML — shared with everyone who writes on the platform. Applying a template loads it into the assistant as the working text, where it can be rewritten and then inserted.
Every Rewrite Read, Every Number Kept
HR content that is clearer on the page, consistent in the voice, unchanged where the law requires, and written inside the form that sends it.