Employee Benefit Statements: Static vs variable text

Requirements Define Communication Goals Delivery Methods Styling and Images Content Source documents Data Reports Employee Feedback Updateable Cross Project Integration Access Control Collaborate - or DIY Possible Project Types Other Vendors DIY Tutorial 1 DIY Tutorial 2 DIY Tutorial 3 DIY Tutorial 4 DIY Tutorial 5 DIY Tutorial 6 DIY Tutorial 7 DIY Tutorial 8 DIY Tutorial 9 DIY Tutorial 10 - - A Website - - Website Page 1 Website Page 2 Website Page 3 Website Page 4 Website Page 5 Website Page 6 Website Page 7 Website Page 8 Sample Employee Benefit Statements Sample 1 Sample 2 Sample 3 Sample 4 Sample 5 Sample 6 A | | very | | brief | | slide show Website Page 9

Employee Benefit Statements are available as full service, collaborative or software. You always have the power to choose.

Eliminate the Great Divide

InformEducatePersonalize

HR Communications: Bringing personalized content to those with the greatest need.

Total Compensation Big, Cool but mostly Hidden

Home HR Communications Employee Benefit Statements Employee Retention Recruiting HR Communications The Human Resources Collaborative Suite Productivity for HR HR Communications Group Communications Employee Communications Plan Communications

DIY Tutorial 4: Employee Benefit Statements Getting Started (Static vs variable text)

Continue through all items and develop your Preliminary Employee Benefit Statement Task list. The next Step is pulling together all of your collateral source documents and vendor provided materials which will be used to help you write your static & variable text (link "Content Source Documents").If you are using a Vendor, they may do it all. If it is DIY, you will need to fulfill this task.
Assuming DIY, then:(1) identify 'static' text that will not be personalized. An example would be a brief description of each health plan. Refer directly to your source docs & when possible, use text that mimics those materials. Rewriting text that is already acceptable can be time consuming. Remember:
(2) your source docs may have considerable detail but an employee benefit statement should be brief. 'Simplification' of content is a craft & effective writing skills are quite important. 'Think' like an employee with minimal knowledge, not as the Director of Benefits and Compensation.
(3) Avoid technical benefit terminolgy or acronyms unless they are critical to your message. If you do, make sure you also define the item in laymen's terms.

(4) Keep an eye on your available 'space'. The tendency for most is to provide too much detail. If you are not alert, you will find that (example) your Health Care section has eaten all of the visual space allocated for Disability + Life Insurance.
(5) After every block of static text has been suitably written - stop - place it in your Visual space. If you do not do this as you go, you may have a big redo later.
(6) Do leave room for Variable text & #'s! It's a personalized employee benefit statement. Personalization ---> Knowledge.
Do not decide to:(1) Reduce fonts to a smaller point size.This vs that, which is a difficult read. You want your employees to read their Employee Benefit Statement without increasing Vision Plan claims.
(2) Eliminate 'whitespace' by tightening line height too much. Leave some air.

This would generally be considered to be readable employee benefit statement line height.

This would generally be considered to be undesirable employee benefit statement line height.