Rivalry2

HTML Diff

0 added 0 removed

Original 2026-01-01

Modified 2026-02-28

1 <h2>This style guide was made to help Checkr’s writers create on-brand messages that sound clear and consistent across all teams and channels.</h2>

2 <h2>We encourage anyone communicating for Checkr to reference the elements in this guide, where we’ll cover writing for the Checkr brand, our preferred grammar and style, and our 4 key audiences.</h2>

3 <p>The content of our guide was adapted from the<a>Mailchimp Content Style Guide</a>, which they have generously provided as an open source reference under the<a>Creative Commons Attribution-NonCommercial 4.0 International License</a>. For those outside of Checkr, we also invite you to use and adapt this style guide as you see fit, with the only requirement being crediting Mailchimp and Checkr.</p>

4 <p>Our brand is a strategic framework that helps us connect emotionally with our audience. It guides how we want to sound to people, and how we want them to feel about us in return.</p>

5 <p>We invite you to reference these brand tools when writing for Checkr.</p>

6 <p>We build a fairer future by designing technology to create opportunities.</p>

7 <h2>Clear</h2>

8 <p>It’s a single idea that serves as the foundation of all creative content for our brand.</p>

9 <p>As an adjective it means simple, transparent, unclouded. As a verb it means removing unwanted objects.</p>

10 <p>Everything we do is accessible, transparent, and open.</p>

11 <p>Our approach is to unlock potential and remove unwanted obstacles.</p>

12 <p>To us, it’s more than a word-it’s a philosophy-one that informs every decision we make, from how we look to how we speak and how we act.</p>

13 <h2>We modernize</h2>

14 <h2>We invent what's next</h2>

15 <p>Our industry needs rethinking. Background checks have traditionally been inefficient, biased, and overpriced for both u;'sers and candidates. We’re here to fix that.</p>

16 <h2>We unlock</h2>

17 <h2>We lean into work</h2>

18 <p>We remove obstacles and unlock potential. Our products help customers be more productive, and create new opportunities for people who’ve been unfairly or unjustly kept out of the workforce.</p>

19 <h2>We advance</h2>

20 <h2>We’re about solutions, not problems</h2>

21 <p>Our platform provides customers with the competitive advantage of knowing they’ll make fairer decisions, faster, and with more clarity.</p>

22 <p>Different situations call for different approaches to communication.</p>

23 <p>We use this spectrum to help us figure out who we’re talking to, where and when we’re talking to them, and what we’re talking about.</p>

24 <h2>Expressive</h2>

25 <p>When our goal is to engage with people’s emotions, we are more expressive-our style of communication is warmer and personal. It can even be inspiring and witty.</p>

26 <h2>Functional</h2>

27 <p>When our goal is to inform people or help them accomplish a task, we're more functional-our style of communication is clear, simple and direct.</p>

28 <h2>Fair</h2>

29 <p>We strongly believe in the principle of fairness, and we act accordingly. We believe we can contribute to making the world a fairer place.</p>

30 <h2>Intelligent</h2>

31 <p>We are built on intelligence. It powers our products, streamlines our customer’s work processes, gets them better results, allows them to make more informed hiring decisions, and guides us to acquire the knowledge necessary to create a fairer future of work.</p>

32 <h2>Transparent</h2>

33 <p>We seek clarity in everything we do. We’re transparent about why we exist, what we value, and what our goals are. The benefits of our products are clear and we are honest when we communicate.</p>

34 <h2>Approachable</h2>

35 <p>We are easy to talk to. Behind the innovative technology and software are the efforts of real people dedicated to disrupting and bringing a sense of humanity to an industry that is often impersonal.</p>

36 <p>What’s the difference between voice and tone?</p>

37 <p>When we speak, we always use the same voice. That’s who we are.</p>

38 <p>But our voice doesn’t always sound exactly the same: our tone changes depending on the situation.</p>

39 <p>For example, we might use a different tone of voice when chatting with a close friend than we would in a professional setting. We take people’s needs into account and adjust our tone to fit. When we speak with someone who’s happy we’ll likely use a different tone than if they were upset.</p>

40 <p>Our voice doesn’t change much, but our tone is always adapting to ensure our message is clear.</p>

41 <p>We speak with one voice. Everywhere we interact with people, at all touchpoints, our voice remains consistent.</p>

42 <p>It’s an integral part of our brand, and an accurate reflection of our brand values. Not just in how we speak, but what we speak about.</p>

43 <p>Checkr’s voice springs from our brand attributes. When we speak, these four foundational brand attributes should always be present-<i>fair, intelligent, transparent, approachable.</i></p>

44 <h2>We are:</h2>

45 <h2>The visionary leader</h2>

46 <ul><li>We set new industry standards, aspiring to be thought leaders in our field.</li>

47 <li>This voice has a genuine and optimistic tone.</li>

48 <li>Motivated by innovation, in the quest for order.</li>

49 </ul><p>“This is who we are. This is what the future of work can be.”</p>

50 <p>Content buckets are how we organize the subjects that we talk about. Each bucket is an overarching idea, inspired by our attributes (how we want people to perceive us). We use these buckets to help us come up with ideas for content.</p>

51 <p>Keeping our attributes in mind-fair, intelligent, transparent, approachable - here are some examples of content buckets for Checkr:</p>

52 <ul><li>Building Work Culture</li>

53 <li>The Future of Work</li>

54 <li>Hiring Best Practices</li>

55 <li>Equity in the Workplace</li>

56 <li>Justice Reform and Second Chances</li>

57 </ul><h2>Building work culture</h2>

58 <p>We want to seem: Approachable</p>

59 <p>Examples</p>

60 <ul><li>Webinar: How to design and unify blended teams</li>

61 <li>Blog: 5 ways to show loyalty to your employees and job candidates</li>

62 <li>Webinar: Giving consistent feedback to remote employees</li>

63 </ul><h2>The future of work</h2>

64 <p>We want to seem: Intelligent</p>

65 <p>Examples</p>

66 <ul><li>Blog: Enduring lessons from remote and hybrid work</li>

67 <li>Webinar: Recruiting and onboarding strategies in a remote world</li>

68 <li>Webinar: Expanding your talent pool for the future of work</li>

69 </ul><h2>Hiring best practices</h2>

70 <p>We want to seem: Intelligent, Transparent</p>

71 <p>Examples</p>

72 <ul><li>Webinar: Adopting candidate-centric hiring practices</li>

73 <li>Guide: How small businesses can hire smarter in the great resignation</li>

74 <li>Webinar: Recruiting and appealing to Gen Z</li>

75 </ul><h2>Equity in the workplace</h2>

76 <p>We want to seem: Fair, Transparent</p>

77 <p>Examples</p>

78 <ul><li>Blog: The employer’s guide to medical marijuana and background checks</li>

79 <li>Webinar: The mark of inclusive leaders</li>

80 <li>Webinar: 10 steps to reduce bias and increase fairness</li>

81 </ul><h2>Justice reform and second chances</h2>

82 <p>We want to seem: Fair, Approachable</p>

83 <p>Examples</p>

84 <ul><li>Ebook: The diversity group you’re overlooking: How to be a fair chance employer</li>

85 <li>Blog: The state of post-incarceration employment</li>

86 <li>Webinar: Using individualized assessments in background checks to widen the candidate pool</li>

87 </ul><p>We write and build products with a person-first perspective. Being aware of the impact of your language will help make Checkr a better place to work and a better steward of our values to the world.</p>

88 <ul><li>We write in first and second person voice, addressing the reader directly with "you / your", and addressing ourselves as "we / us"."</li>

89 <li>Don’t reference age or disability unless it’s relevant to what you’re writing.</li>

90 <li>Avoid gendered language and use the singular “they.”</li>

91 <li>When writing about a person, use their preferred pronouns; if you don’t know those, just use their name.</li>

92 </ul><p>Whether you’re writing for an internal or external audience, it's important to write for and about other people in a way that’s compassionate, inclusive, and respectful.</p>

93 <h2>As part of an audience</h2>

94 <ul><li>Don’t capitalize “audience” unless grammatically necessary</li>

95 <li>Don’t refer to an audience as “it.” Audiences are made up of real people, so always use “they.”</li>

96 </ul><h2>Age</h2>

97 <ul><li>Don’t reference someone’s age unless it’s relevant to what you’re writing. If it<i>is</i>relevant, include their specific age. (ex: The candidate, 16, just got her driver’s license.)</li>

98 <li>Don’t refer to people using age-related descriptors like “young,” “old,” or “elderly.”</li>

99 </ul><h2>Disability</h2>

100 <ul><li>Don’t refer to a person’s disability unless it’s relevant to what you’re writing.</li>

101 <li>Avoid disability-related idioms like “lame” or “falling on deaf ears.”</li>

102 <li>If you need to mention it, ask whether your subject prefers person-first language (“they have a disability”) or identity-first language (“they are disabled”).</li>

103 <li>When writing about a person with disabilities, don’t use the words “suffer,” “victim,” or “handicapped.”</li>

104 </ul><h2>Gender and sexuality</h2>

105 <ul><li>When writing about a person, use their personal pronouns. When in doubt, just ask or use their name.</li>

106 <li>It’s OK to use “they” as a singular pronoun.</li>

107 <li>Avoid gendered terms in favor of neutral alternatives. Ex: “server” over “waitress”, or “businessperson” over “businessman.”</li>

108 <li>Don’t call groups of people “guys.” Don’t call women “girls.”</li>

109 <li>Don’t use “same-sex” marriage, unless the distinction is relevant to what you’re writing.</li>

110 <li>Use the following words as modifiers, but never as nouns:<ul><li>lesbian</li>

111 <li>gay</li>

112 <li>bisexual</li>

113 <li>transgender (never "transgendered")</li>

114 <li>trans</li>

115 <li>queer</li>

116 <li>LGBTQ+</li>

117 </ul></li>

118 <li>Don’t use these words in reference to LGBTQ+ people or communities:<ul><li>homosexual</li>

119 <li>lifestyle</li>

120 <li>preference</li>

121 </ul></li>

122 </ul><h2>Hearing</h2>

123 <ul><li>Use “deaf” as an adjective to describe a person with significant hearing loss. You can also use “partially deaf” or “hard of hearing.”</li>

124 </ul><h2>Heritage and nationality</h2>

125 <ul><li>Don't use hyphens when referring to someone with dual heritage or nationality. For example, use "Asian American" instead of "Asian-American."</li>

126 </ul><h2>Medical conditions</h2>

127 <ul><li>Don’t refer to a person’s medical condition unless it’s relevant to what you’re writing.</li>

128 <li>If a reference to a person’s medical condition is warranted, use the same rules as writing about people with physical disabilities and emphasize the person first.</li>

129 <li>Don’t call a person with a medical condition a “victim.”</li>

130 </ul><h2>Mental and cognitive conditions</h2>

131 <ul><li>Don’t refer to a person’s mental or cognitive condition unless it’s relevant to what you’re writing.</li>

132 <li>Never assume that someone has a medical, mental, or cognitive condition.</li>

133 <li>Don’t describe a person as “mentally ill.” If you need to mention a person's mental or cognitive condition, use the same rules as writing about people with physical disabilities or medical conditions. Emphasize the person first.</li>

134 </ul><h2>Race</h2>

135 <ul><li>When we write about a culture or ethnicity, we capitalize the name. For example, we capitalize Black as it refers to Americans in the African diaspora while we keep white lowercase since white refers to the color of a person’s skin and not a group of people.</li>

136 </ul><h2>Vision</h2>

137 <ul><li>Use the adjective “blind” to describe a person who is unable to see. Use “low vision” to describe a person with limited vision.</li>

138 </ul><p>Adhering to certain rules of grammar and mechanics helps us keep our writing clear and consistent.</p>

139 <ul><li>Checkr is one word, no apostrophe. Although our logo is all lowercase, we write our name with a capital C.</li>

140 <li>Some people will read every word you write. Others will just scan. Help everyone by grouping related ideas together and using descriptive headers and subheaders.</li>

141 <li>Focus your message, and create a hierarchy of information. Lead with the main point or the most important content.</li>

142 <li>A sentence should cover only one idea.</li>

143 <li>Use active voice and positive language.</li>

144 <li>Use short words and sentences.</li>

145 <li>Avoid unnecessary modifiers.</li>

146 <li>Use specific examples.</li>

147 <li>Avoid vague language.</li>

148 <li>Be consistent. Adhere to the copy patterns and style points outlined in this guide.</li>

149 <li>Feel free to use contractions.</li>

150 <li>Use the serial comma. Otherwise, use common sense.</li>

151 <li>When in doubt, read your writing out loud.</li>

152 </ul><h2>Abbreviations and acronyms</h2>

153 <ul><li>If your reader won’t recognize an abbreviation or acronym, spell it out the first time you mention it. Then use the short version for all other references.<ul><li>First use: motor vehicle reports</li>

154 <li>Second use: MVR</li>

155 </ul></li>

156 <li>If it’s a well- known abbreviation or acronym like API or HTML, you don’t need to spell it out.</li>

157 </ul><h2>Active voice</h2>

158 <ul><li>Use active voice. Avoid passive voice. In active voice, the subject of the sentence does the action. In passive voice, the subject of the sentence has the action done to it.<ul><li>Yes: Marti logged in to the account.</li>

159 <li>No: The account was logged in to by Marti.</li>

160 </ul></li>

161 <li>One exception is when you want to specifically emphasize the action over the subject. In some cases, this is fine.<ul><li>Your request was completed by our support team.</li>

162 </ul></li>

163 </ul><h2>Capitalization</h2>

164 <p>We use a few different forms of capitalization.</p>

165 <ul><li>All caps capitalizes the entire word. This treatment is reserved for qualifiers or tags.</li>

166 <li>Title case capitalizes the first letter of every word except articles, prepositions, and conjunctions.</li>

167 <li>Sentence case capitalizes the first letter of the first word.</li>

168 <li>When writing out an email address or website URL, use all lowercase.<ul><li><a>samplename@checkr.com</a></li>

169 <li>checkr.com</li>

170 </ul></li>

171 </ul><p>Here are some words we never capitalize in a sentence:</p>

172 <ul><li>website</li>

173 <li>internet</li>

174 <li>online</li>

175 <li>email</li>

176 </ul><h2>Contractions</h2>

177 <p>They’re great! They give your writing an informal, friendly tone.</p>

178 <h2>Emoji</h2>

179 <p>A fun way to add humor and visual interest to your writing.</p>

180 <p>Consider the use case, tone, and audience. Emoji may be an appropriate addition to a social media post but never use them in more functional mediums like blog or website content. Use emoji only in our most expressive tone. Use them sparingly and deliberately to support the copy, not replace it.</p>

181 <p>Spell out a number when it begins a sentence. Otherwise, use the numeral. This includes ordinals.</p>

182 <p>When starting a sentence with a percentage, temperature, time, year, or address, you don’t need to spell out the number. This same exception applies to content titles and headlines where starting the sentence with a numeral makes more sense.</p>

183 <ul><li>Ten new employees started on Monday, and 12 start next week.</li>

184 <li>Two weeks ago we hosted our 8th annual team offsite.</li>

185 <li>Checkr powers 95% of the gig economy.</li>

186 <li>85% of background checks get completed within 24 hours.</li>

187 <li>2021 saw the rise of remote work and hybrid work.</li>

188 <li>5 ways to make hiring more inclusive.</li>

189 </ul><p>Sometimes it feels weird to use the numeral. If it's an expression that typically uses spelled-out numbers, leave them that way.</p>

190 <ul><li>Make a good first impression and build trust with your candidate.</li>

191 <li>We use third-party integrations.</li>

192 <li>We provide all-in-one background screening solutions.</li>

193 </ul><p>Numbers over 3 digits get commas and are written in full. Abbreviate them if there are space restraints, as in a tweet or a chart:</p>

194 <ul><li>999</li>

195 <li>1,000</li>

196 <li>150,000</li>

197 <li>1k</li>

198 <li>150k</li>

199 </ul><h2>Dates</h2>

200 <p>Generally, spell out the day of the week and the month. Abbreviate only if space is an issue.</p>

201 <ul><li>Saturday, January 24</li>

202 <li>Sat., Jan. 24</li>

203 </ul><p>When a date appears after a month, don't add st, nd, rd, th. Only use add-ons when they precede the month (the event is on the 12th of August.)</p>

204 <ul><li>Yes: The event is September 12, 2022</li>

205 <li>No: September 12th, 2022</li>

206 </ul><h2>Fractions</h2>

207 <p>Spell out fractions.</p>

208 <ul><li>Yes: two-thirds</li>

209 <li>No: ⅔</li>

210 </ul><h2>Percentages</h2>

211 <p>Use the % symbol instead of spelling out "percent."</p>

212 <h2>Ranges and spans</h2>

213 <p>Use a hyphen (-) to indicate a range or span of numbers.</p>

214 <ul><li>It takes 20-30 days</li>

215 <li>The event is April 4-5, 2022</li>

216 </ul><h2>Money</h2>

217 <p>When writing about currency, use the symbol before the amount. Include a decimal and number of cents if more than 0.</p>

218 <ul><li>$20</li>

219 <li>$19.25</li>

220 <li>¥1</li>

221 <li>€1</li>

222 </ul><h2>Telephone numbers</h2>

223 <p>Use hyphens without spaces between numbers. Use a country code if your reader is in another country. Don't use the obsolete style with parentheses (555) 123-4567.</p>

224 <ul><li>555-123-4567</li>

225 <li>+1-555-123-4567</li>

226 </ul><h2>Temperature</h2>

227 <p>Use the degree symbol and the capital F abbreviation for Fahrenheit, or the capital C abbreviation for Celsius.</p>

228 <ul><li>98°F</li>

229 <li>23°C</li>

230 </ul><h2>Time</h2>

231 <p>Use numerals and am or pm, with a space in between.</p>

232 <ul><li>7:00 am</li>

233 <li>7:30 pm</li>

234 </ul><p>Use a hyphen between times to indicate a time period.</p>

235 <ul><li>7:00 am-10:30 pm</li>

236 </ul><p>Specify time zones when writing something people would need to schedule.</p>

237 <p>Abbreviate time zones within the continental United States as follows:</p>

238 <ul><li>Eastern time: ET</li>

239 <li>Central time: CT</li>

240 <li>Mountain time: MT</li>

241 <li>Pacific time: PT</li>

242 </ul><p>Abbreviate decades when referring to those within the past 100 years. Use a lowercase s, and don’t use a comma.</p>

243 <ul><li>the 00s</li>

244 <li>the 90s</li>

245 </ul><p>When referring to decades more than 100 years ago, be more specific.</p>

246 <ul><li>the 1900s</li>

247 <li>the 1890s</li>

248 </ul><h2>Apostrophe</h2>

249 <p>The apostrophe’s most common use is making a word possessive. If the word already ends in an s and it’s singular, you also add an ’s. If the word ends in an s and is plural, just add an apostrophe.</p>

250 <ul><li>The employer’s guide to background checks.</li>

251 <li>Chris’s background check was completed.</li>

252 <li>All the team managers’ candidates were screened.</li>

253 </ul><h2>Colons</h2>

254 <p>Use a colon (rather than an ellipsis, em dash, or comma) to offset a list.</p>

255 <ul><li>We’ve narrowed it down to 3 candidates: Jerry, Nellie, and Barney.</li>

256 </ul><p>You can also use a colon to join 2 related phrases. If a complete sentence follows the colon, capitalize the 1st word.</p>

257 <ul><li>Fair chance hiring: your guide to getting started</li>

258 </ul><h2>Commas</h2>

259 <p>When writing a list, use the serial comma (also known as the Oxford comma).</p>

260 <ul><li>Yes: Access to safety, community, and employment are essential.</li>

261 <li>No: Access to safety, community and employment are essential.</li>

262 </ul><p>Otherwise, use common sense. If you’re unsure, read the sentence out loud. Where you find yourself taking a breath, use a comma.</p>

263 <h2>Dashes and hyphens</h2>

264 <p>Use a hyphen (-) without spaces on either side to link words into a single phrase, or to indicate a span or range.</p>

265 <ul><li>End-to-end services</li>

266 <li>Monday-Friday</li>

267 </ul><p>Use an em dash (-) without spaces on either side to offset an aside.</p>

268 <p>Use a true em dash, not hyphens (- or --).</p>

269 <ul><li>No matter the stage of your fair chance journey-novice, expert, or somewhere in between-we have tools to help.</li>

270 <li>Austin thought no one would hire him, but he was wrong-fair chance hiring helped him succeed.</li>

271 </ul><h2>Ellipses</h2>

272 <p>Ellipses (...) can be used to indicate that you’re trailing off before the end of a thought. Use them sparingly. Don’t use them for emphasis or drama, and don’t use them in titles or headers.</p>

273 <ul><li>“Have we reviewed all the candidates?” Amalia asked. Jared said, “I’m not sure…”</li>

274 </ul><p>Ellipses, in brackets, can also be used to show that you're omitting words in a quote.</p>

275 <ul><li>Original: “Do not go where the path may lead; go instead where there is no path and leave a trail”</li>

276 <li>Using ellipses: “...go…where there is no path and leave a trail.”</li>

277 </ul><p>Periods and exclamation marks go inside quotation marks. Question marks go inside quotation marks if they’re part of the quote.</p>

278 <p>All 3 go outside parentheses when the parenthetical is part of a larger sentence, and inside parentheses when the parenthetical stands alone.</p>

279 <ul><li>Kevin said, “I finished my report!”</li>

280 <li>I finished my report (and I started a screening, too).</li>

281 <li>I finished my report and a screening. (I think the report was for Joshua?)</li>

282 </ul><p>Leave a single space between sentences.</p>

283 <p>Use exclamation points sparingly, and never more than one at a time. Never use exclamation points in failure messages or alerts. When in doubt, avoid!</p>

284 <h2>Quotation marks</h2>

285 <p>Use quotes to refer to words and letters, titles of short works (like articles and poems), and direct quotations.</p>

286 <p>Periods and commas go within quotation marks. Question marks within quotes follow logic-if the question mark is part of the quotation, it goes within. If you’re asking a question that ends with a quote, it goes outside the quote.</p>

287 <p>Use single quotation marks for quotes within quotes.</p>

288 <ul><li>Who was it that said, “Once you choose hope, anything’s possible”?</li>

289 <li>Layla said, “I saw a post that read, ‘Once you choose hope, anything’s possible.’”</li>

290 </ul><h2>Semicolons</h2>

291 <p>Go easy on semicolons. They usually support long, complicated sentences that could easily be simplified. Try an em dash (-) instead, or simply start a new sentence.</p>

292 <h2>Ampersands</h2>

293 <p>Don't use ampersands as a substitute for "and." Use an ampersand only when it’s part of a company or product name, or when connecting two words that are always paired together and are meant to be read as one thing.</p>

294 <ul><li>Ben and Dan</li>

295 <li>Ben & Jerry’s</li>

296 <li>Research and design</li>

297 <li>Research & Development</li>

298 </ul><h2>File extensions</h2>

299 <p>When referring generally to a file extension type, use all uppercase without a period. Add a lowercase s to make it plural.</p>

300 <ul><li>GIF</li>

301 <li>PDF</li>

302 <li>HTML</li>

303 <li>JPGs</li>

304 </ul><p>When referring to a specific file, the filename should be lowercase:</p>

305 <ul><li>approved.gif</li>

306 <li>guide-cx-blueprint.pdf</li>

307 <li>checkr-linkedin-profile.jpg</li>

308 </ul><h2>Names and titles</h2>

309 <p>The first time you mention a person in writing, refer to them by their first and last names. On all other mentions, refer to them by their first name.</p>

310 <p>Capitalize the names of departments and teams (but not the word "team" or "department").</p>

311 <ul><li>Volunteer team</li>

312 <li>Support department</li>

313 </ul><p>Capitalize individual job titles when referring to a specific role. Don't capitalize when referring to the role in general terms.</p>

314 <ul><li>Our new Marketing Manager starts today.</li>

315 <li>All the managers are offsite today.</li>

316 </ul><h2>States, cities, and countries</h2>

317 <p>Spell out all city and state names. Don’t abbreviate city names. On first mention, write out United States. On subsequent mentions, US is fine. The same rule applies to any other country or federation with a common abbreviation (European Union, EU; United Kingdom, UK).</p>

318 <h2>URLs and websites</h2>

319 <p>Capitalize the names of websites and web publications. Don’t italicize.</p>

320 <p>Avoid spelling out URLs, but when you need to, leave off the<a>http://www</a>.</p>

321 <h2>Writing about other companies</h2>

322 <p>Honor companies’ own names for themselves. Go by what’s used on their official website. Refer to a company or product as “it” (not “they”).</p>

323 <ul><li>iPad</li>

324 <li>YouTube</li>

325 <li>Yahoo!</li>

326 </ul><h2>Slang and jargon</h2>

327 <p>Write in plain English so your message is clear. If you need to use a technical term, briefly define it so everyone can understand.</p>

328 <ul><li>What are expungements? An expungement removes or “seals” prior criminal records from public access. Individuals with expunged records have low subsequent crime rates and huge increases in wage and employment trajectories.</li>

329 </ul><h2>Text formatting</h2>

330 <p>Use italics to indicate the title of a long work (like a book, movie, or album) or to emphasize a word.</p>

331 <ul><li><i>The Lord of the Rings</i></li>

332 <li>Emanuel is<i>really</i>excited about his new job.</li>

333 </ul><p>Use italics when citing an example of an in-product Checkr element, or referencing button and navigation labels in step-by-step instructions:</p>

334 <ul><li>When you're all done, click<i>Send</i>.</li>

335 <li>The familiar screening criteria-<i>MVR Checks, Drug and health screenings</i>, and<i>Criminal background checks</i>-are all found under our<i>Products</i>tab.</li>

336 </ul><p>Don’t use underline formatting, and don’t use any combination of italic, bold, caps, and underline.</p>

337 <h2>Write positively</h2>

338 <p>Use positive language rather than negative language. One way to detect negative language is to look for words like “can’t,” “don’t,” etc.</p>

339 <ul><li>Yes: To start your background check, you’ll need the right documents.</li>

340 <li>No: You won’t be able to start your background check without the right documents.</li>

341 </ul><p>Every piece of content we publish has multiple supporting pieces. This section lays out our style for these web elements.</p>

342 <ul><li>Organize your page around one topic.</li>

343 <li>Use clear, descriptive terms that relate to the topic in titles and headings.</li>

344 <li>Give every image descriptive alt text.</li>

345 <li><b>CTAs (buttons)</b>should always contain actions. The language should be clear and concise. Use sentence case.</li>

346 <li>Use sentence case for<b>checkboxes</b>and<b>radio buttons</b>.</li>

347 <li>Use title case for<b>drop-down menu names</b>and sentence case for<b>menu items</b>.</li>

348 <li>Use title case for<b>form titles</b>and sentence case for<b>form fields</b>. Only request information that we need and intend to use. Don’t ask for irrelevant personal information, like gender.</li>

349 <li>Use title case for<b>main navigation</b>. Use sentence case for<b>subnavigation</b>.</li>

350 <li>Use title case for<b>headings</b>and sentence case for<b>subheadings</b>.</li>

351 <li>Organize headings and subheadings in a hierarchy, with heading first, followed by subheadings in order. For example, don't skip from heading 2 to heading 4 with no heading 3.</li>

352 <li>Include the most relevant keywords in your headings and subheadings.</li>

353 <li>Provide a link whenever you’re referring to a website, relevant content, and trusted external resources.</li>

354 <li>Avoid saying things like “Click here!” or “Click for more information” or “Read this.” Instead, link relevant keywords.</li>

355 <li>Use lists to present steps, groups, or sets of info. Set up your list with a brief introduction. Number lists when the order of information is important.</li>

356 </ul><h2>Alt text</h2>

357 <p>Alt text is a way to label images, and it's especially important for people who can’t see the images on our site. Alt text should describe the image in a brief sentence or two.</p>

358 <h2>CTAs</h2>

359 <p>CTA (button) copy should always include verbs. Keep things clear and concise, and use sentence case. Brevity is important.</p>

360 <p>Standard website buttons include:</p>

361 <ul><li>Log in</li>

362 <li>Get started</li>

363 <li>Contact sales</li>

364 </ul><h2>Checkboxes</h2>

365 <p>Use sentence case for checkboxes.</p>

366 <h2>Drop-down menus</h2>

367 <p>Use title case for menu names and sentence case for menu items. Use all caps sparingly for qualifiers or tags where applicable.</p>

368 <h2>Forms</h2>

369 <ul><li>Form titles should clearly and quickly explain the purpose of the form.</li>

370 <li>Use title case for form titles and sentence case for form fields.</li>

371 <li>Keep forms as short as possible.</li>

372 <li>Only request information that we need and intend to use.</li>

373 <li>Don’t ask for information that could be considered private or personal, including gender. If you need to ask for gender, provide a field the user can fill in on their own, not a drop-down menu.</li>

374 </ul><h2>Heading and subheading</h2>

375 <p>Headings and subheadings organize content for readers. They should include the most relevant keywords and cover/highlight the main point(s) of the page.</p>

376 <ul><li>Headings and subheadings are written in sentence case.</li>

377 <li>Avoid using end punctuation except for question marks or when a heading is two or more sentences.</li>

378 <li>Organize headings and subheadings hierarchically, with headings first, followed by subheadings in order. (An H2 will nestle under H1, an H3 under H2, and on down.)</li>

379 <li>Headings (H1) give people a taste of what they’re about to read. Use them for page and blog titles, limited to only one per page.</li>

380 <li>Subheadings (H2, H3, etc.) break articles into smaller, more specific sections. They give readers avenues into your content and make it more scannable.</li>

381 </ul><h2>Links</h2>

382 <p>Provide a link whenever you’re referring to something on an external website. Use links to point users to relevant content and trusted external resources.</p>

383 <p>Don’t include preceding articles (a, an, the, our) when you link text. For example:</p>

384 <ul><li>Yes: Read the<a>blog post</a>for details.</li>

385 <li>No: Read<a>the blog post</a>for details.</li>

386 </ul><p>If a link comes at the end of a sentence or before a comma, don’t link the punctuation mark.</p>

387 <p>Don’t say things like “Click here!” or “Click for more information” or “Read this.” Write the sentence as you normally would, and link relevant keywords.</p>

388 <p>Links should look different than regular copy, strong text, or emphasis text. They should have a hover state that communicates they’re interactive, and should have a distinct active and visited state. When setting the hover state of links, be sure to include focus state as well, to help readers using assistive technologies and touch devices.</p>

389 <h2>Lists</h2>

390 <p>Use lists to present steps, groups, or sets of information. Give context for the list with a brief introduction. Number lists when the order is important, like when you’re describing steps of a process. Don’t use numbers when the list’s order doesn’t matter.</p>

391 <p>If one of the list items is a complete sentence, use proper punctuation and capitalization on all of the items. If list items are not complete sentences, don’t use punctuation, but do capitalize the first word of each item.</p>

392 <h2>Navigation</h2>

393 <p>Use title case for main or global navigation. Use sentence case for subnavigation. Navigation links should be clear and concise.</p>

394 <h2>Titles</h2>

395 <p>Titles organize pages and guide readers. A title appears at the beginning of a page or section and briefly describes the content that follows. Titles also tell search engines what a page is about, and show up in search results.</p>

396 <p>Titles are written in title case. Don’t use end punctuation in a title unless it is a question, or it consists of two or more sentences.</p>

397 <p>We’re always working to make our content more accessible and usable to the widest possible audience.</p>

398 <ul><li>Create a hierarchy, with the most important information first.</li>

399 <li>Avoid directional instructions or language that requires the reader to see the layout or design of the page.</li>

400 <li>Place similar topics in the same paragraph, and clearly separate different topics with headings.</li>

401 <li>Use plain language. Write short sentences and familiar words.</li>

402 <li>Links should provide information on the associated action or destination. Avoid saying “click here” or “learn more.”</li>

403 <li>Avoid using images when descriptive text will do.</li>

404 <li>Label inputs on forms with clear names and use appropriate tags. Think carefully about what fields are necessary, and especially which ones you mark as required.</li>

405 </ul><p>Writing for accessibility goes way beyond making everything on the page available as text. It also affects the way you organize content and guide readers through a page. Accessibility includes users of all mental and physical capacities, whether situational (broken glasses!) or more permanent.</p>

406 <h2>Basics</h2>

407 <p>We write for a diverse audience of readers who all interact with our content in different ways. We aim to make our content accessible to anyone using a screen reader, keyboard navigation, or Braille interface, and to users of all cognitive capabilities.</p>

408 <p>As you write, consider the following:</p>

409 <ul><li>Would this language make sense to someone who doesn’t work here?</li>

410 <li>Could someone quickly scan this document and understand the material?</li>

411 <li>If someone can’t see the colors, images or video, is the message still clear?</li>

412 <li>Mobile devices with accessibility features are increasingly becoming core communication tools, does this work well on them?</li>

413 </ul><p>Many of the best practices for writing for accessibility echo those for<a>writing educational content</a>, with the added complexity of markup, syntax, and structure.</p>

414 <h2>Guidelines</h2>

415 <h2>Avoid directional language</h2>

416 <p>Avoid directional instructions and any language that requires the reader to see the layout or design of the page. This is helpful for many reasons, including layout changes on mobile.</p>

417 <ul><li>Yes: “Select from these options,” (with the steps listed after the title)</li>

418 <li>No: “Select from the options in the right sidebar.”</li>

419 </ul><h2>Use headers</h2>

420 <p>Headers should always be nested and consecutive. To help group sections, be sure the page title is H1, top-level sections are H2s, and subsequent inside those are H3 and beyond. Avoid excessive nesting.</p>

421 <h2>Employ a hierarchy</h2>

422 <p>Put the most important information first. Place similar topics in the same paragraph, and clearly separate different topics with headings.</p>

423 <p>Starting with a simple outline that includes key messages can help you create a hierarchy and organize your ideas in a logical way. This improves scannability and encourages better understanding.</p>

424 <p>Make true lists instead of using a paragraph or line breaks.</p>

425 <h2>Label forms</h2>

426 <p>Label inputs with clear names, and use appropriate tags. Think carefully about what fields are necessary, and especially which ones you mark as required. Label required fields clearly. The shorter the form, the better.</p>

427 <h2>Use descriptive links</h2>

428 <p>Links should provide information on the associated action or destination. Try to avoid “click here” or “learn more.”</p>

429 <h2>Use plain language</h2>

430 <p>Write short sentences and use familiar words. Avoid jargon and slang. If you need to use an abbreviation or acronym that people may not understand, explain what it means on first reference.</p>

431 <h2>Use alt text</h2>

432 <p>The alt tag is the most basic form of image description, and it should be included on all images. The language will depend on the purpose of the image:</p>

433 <ul><li>If it’s a creative photo or supports a story, describe the image in detail in a brief caption.</li>

434 <li>If the image is serving a specific function, describe what’s inside the image in detail. People who don’t see the image should come away with the same information as if they had.</li>

435 <li>If you’re sharing a chart or graph, include the data in the alt text so people have all the important information.</li>

436 </ul><p>Each browser handles alt tags differently. Supplement images with standard captions when possible.</p>

437 <h2>Make sure closed captioning is available</h2>

438 <p>Closed captioning or transcripts should be available for all videos. The information presented in videos should also be available in other formats.</p>

439 <h2>Be mindful of visual elements</h2>

440 <p>Aim for high contrast between your font and background colors.</p>

441 <p>Images should not be the only method of communication, because images may not load or may not be seen. Avoid using images when the same information could be communicated in writing.</p>

442 <p>You’ll find the following terminology, abbreviations, and acronyms used often in our language. To make sure they’re used consistently, we’ve included our definitions and usage guidelines.</p>

443 <p>This section is organized into groups:</p>

444 <ul><li>Checkr products</li>

445 <li>Checkr screenings</li>

446 <li>Checkr foundation</li>

447 <li>Candidate experience features</li>

448 <li>Industry abbreviations and acronyms</li>

449 </ul><p>Below are the list of abbreviations and acronyms that are used within the background check industry. Except where noted, in most cases, we should spell out upon first use with abbreviation in parentheses, and then can use abbreviation or acronym in subsequent uses. If first use is in a headline and the abbreviation or acronym is well known (i.e. HR), we can use the shortened version).</p>

450 <ul><li>AI: artificial intelligence</li>

451 <li>API: application programming interface*</li>

452 <li>ATS: applicant tracking system</li>

453 <li>EEOC: Equal Employment Opportunity Commission</li>

454 <li>FCRA: Fair Credit Reporting Act</li>

455 <li>HR: human resources</li>

456 <li>PII: personally identifiable information</li>

457 </ul><p>*Always use acronym**For a full list of HR acronyms and definitions that might be used, please refer to<a>https://www.liveabout.com/human-resources-acronyms-1918214</a>.</p>

458 <p>We’ve provided a ton of detail in our “How to Write for Checkr” section, but we understand not everyone needs all that, so we’ve combined the summaries from each section here.</p>

459 <p>We realize not everyone needs the level of detail we’ve included in our “Using Brand for Writing” section, and some may even find it a bit confusing. So here are the most important things you need to know about using brand for writing for Checkr:</p>

460 <h2>Be clear</h2>

461 <p>Above all else, we are clear. Everything we say and do should be accessible, transparent, and open.</p>

462 <p><i>This is our core creative concept.</i></p>

463 <h2>We aim to project qualities to our users that are:</h2>

464 <ul><li>Fair</li>

465 <li>Intelligent</li>

466 <li>Transparent</li>

467 <li>Approachable</li>

468 </ul><p><i>These are our brand attributes.</i></p>

469 <h2>When we talk, we should sound:</h2>

470 <ul><li>Genuine</li>

471 <li>Optimistic</li>

472 <li>Compassionate</li>

473 <li>Decisive</li>

474 </ul><p><i>This is our tone.</i></p>

475 <h2>The person we want to be for people is:</h2>

476 <ul><li>The visionary leader - setting new industry standards, aspiring to be thought leaders in our field</li>

477 </ul><p><i>This is our brand voice.</i></p>

478 <h2>And the core reason we exist is:</h2>

479 <ul><li>To build a fairer future by designing technology to create opportunities.</li>

480 </ul><p><i>This is our brand purpose.</i></p>

481 <p>Rules for writing inclusively about people:</p>

482 <ul><li>Don’t reference age or disability unless it’s relevant to what you’re writing.</li>

483 <li>Avoid gendered language and use the singular “they.”</li>

484 <li>When writing about a person, use their preferred pronouns; if you don’t know those, just use their name.</li>

485 </ul><p>Rules for language and style. Our writing do’s and don'ts:</p>

486 <ul><li>Checkr is one word, no apostrophe. Although our logo is all lowercase, we write our name with a capital C.</li>

487 <li>Some people will read every word you write. Others will just scan. Help everyone by grouping related ideas together and using descriptive headers and subheaders.</li>

488 <li>Focus your message, and create a hierarchy of information. Lead with the main point or the most important content.</li>

489 <li>Use active voice and positive language.</li>

490 <li>Use short words and sentences.</li>

491 <li>Avoid unnecessary modifiers.</li>

492 <li>Use specific examples.</li>

493 <li>Avoid vague language.</li>

494 <li>Be consistent. Adhere to the copy patterns and style points outlined in this guide.</li>

495 <li>Feel free to use contractions.</li>

496 <li>Use the serial comma. Otherwise, use common sense.</li>

497 <li>When in doubt, read your writing out loud.</li>

498 </ul><p>Rules for writing digital content:</p>

499 <ul><li>Organize your page around one topic.</li>

500 <li>Use clear, descriptive terms that relate to the topic in titles and headings.</li>

501 <li>Give every image descriptive alt text.</li>

502 <li><b>CTAs (buttons)</b>should always contain actions. The language should be clear and concise. Use sentence case.</li>

503 <li>Use sentence case for<b>checkboxes</b>and<b>radio buttons</b>.</li>

504 <li>Use title case for<b>drop-down menu names</b>and sentence case for<b>menu items</b>.</li>

505 <li>Use title case for<b>form titles</b>and sentence case for<b>form fields</b>. Only request information that we need and intend to use. Don’t ask for irrelevant personal information, like gender.</li>

506 <li>Use title case for<b>main navigation</b>. Use sentence case for<b>subnavigation</b>.</li>

507 <li>Use title case for<b>headings</b>and sentence case for<b>subheadings</b>.</li>

508 <li>Organize headings and subheadings in a hierarchy, with heading first, followed by subheadings in order.</li>

509 <li>Include the most relevant keywords in your headings and subheadings.</li>

510 <li>Provide a link whenever you’re referring to a website, relevant content, and trusted external resources.</li>

511 <li>Avoid saying things like “Click here!” or “Click for more information” or “Read this.” Instead, link relevant keywords.</li>

512 <li>Use lists to present steps, groups, or sets of information. Set up your list with a brief introduction. Number lists when the order of information is important.</li>

513 </ul><p>Rules for writing inclusively for and about accessibility:</p>

514 <ul><li>Create a hierarchy, with the most important information first.</li>

515 <li>Avoid directional instructions or language that requires the reader to see the layout or design of the page.</li>

516 <li>Place similar topics in the same paragraph, and clearly separate different topics with headings.</li>

517 <li>Use plain language. Write short sentences and familiar words.</li>

518 <li>Links should provide information on the associated action or destination. Avoid saying “click here” or “learn more.”</li>

519 <li>Avoid using images when descriptive text will do.</li>

520 <li>Label inputs on forms with clear names and use appropriate tags. Think carefully about what fields are necessary, and especially which ones you mark as required.</li>

521 </ul><p>When writing for the Checkr brand, there are 4 audience groups your work could fall into. Each group has its own intended audience, tone, and messaging hierarchy.</p>

522 <h2>Messaging for brand</h2>

523 <ul><li>Who uses this messaging: copywriters, marketers</li>

524 <li>What’s their main goal: introduce the brand and inspire people</li>

525 <li>Tone leads with: optimistic, genuine</li>

526 <li>Most expressive</li>

527 </ul><h2>Messaging for sales and marketing</h2>

528 <ul><li>Who uses this messaging: copy writers, marketers, sales team</li>

529 <li>What’s their main goal: inform people and convert them to customers</li>

530 <li>Tone leads with: compassionate, optimistic</li>

531 <li>Expressive, with some functionality</li>

532 </ul><h2>Messaging for help and support</h2>

533 <ul><li>Who uses this messaging: customer support</li>

534 <li>What’s their main goal: empower and guide users</li>

535 <li>Tone leads with: decisive, compassionate</li>

536 <li>Functional, with some expressiveness</li>

537 </ul><h2>Messaging for product</h2>

538 <ul><li>Who uses this messaging: product team, development</li>

539 <li>What’s their main goal: innovate the product and instruct users</li>

540 <li>Tone leads with: decisive, compassionate</li>

541 <li>Most functional</li>

542 </ul><p>Messaging for brand could include writing for the hero headline on our website, or a billboard. These are attention catching messages that deliver emotion, introduce us to potential new customers, and strengthen our relationship with present ones.</p>

543 <h2>Messaging for product</h2>

544 <p>Who is writing?</p>

545 <ul><li>Copywriters</li>

546 <li>Marketers</li>

547 </ul><h2>Audience overview</h2>

548 <p>Who is being written to?</p>

549 <ul><li>Prospects</li>

550 <li>Candidates</li>

551 </ul><p>This audience is at the<b>awareness</b>stage of the brand journey.</p>

552 <h2>Brand tone</h2>

553 <p>How we should sound:</p>

554 <ul><li>The goal is to introduce the brand and inspire people</li>

555 <li>Our tone of voice is optimistic and genuine</li>

556 <li>Focus on the dignity of work and building a fairer world</li>

557 <li>This voice is our most expressive</li>

558 </ul><h2>Typical use cases</h2>

559 <ul><li>Billboard</li>

560 <li>Hero headline of website</li>

561 <li>Trade show booth</li>

562 </ul><p>Messaging for sales and marketing could be the general content on our website, one-pagers, or promotional posts. These are pieces of content that inspire as well as inform. This audience is primed to buy our service, and needs practical information and reassurance before converting.</p>

563 <h2>Who uses this messaging?</h2>

564 <p>Who is writing?</p>

565 <ul><li>Copywriters</li>

566 <li>Content writers</li>

567 <li>Marketers</li>

568 <li>Sales team</li>

569 </ul><h2>Audience overview</h2>

570 <p>Who is being written to?</p>

571 <ul><li>Customers - companies looking to hire</li>

572 <li>Candidates - people who want to be hired</li>

573 </ul><p>This audience is at the<b>consideration</b>and<b>conversion</b>stages of the brand journey.</p>

574 <h2>Sales and marketing tone</h2>

575 <p>How we should sound:</p>

576 <ul><li>The goal is to inform people about the brand and convert them to customers</li>

577 <li>Our tone of voice is compassionate, and optimistic</li>

578 <li>Focus on user benefits, features, technology, pricing, and social proof</li>

579 <li>This voice is expressive, as well as functional</li>

580 </ul><h2>Typical use cases</h2>

581 <ul><li>One pager</li>

582 <li>General website content</li>

583 <li>eBook</li>

584 <li>Social media</li>

585 <li>Email newsletter</li>

586 </ul><p>Messaging for help and support is to guide users through solving problems. It uses compassionate language, and can be found mostly in the<a>help center</a>, or<a>learning center</a>.</p>

587 <h2>Who uses this messaging?</h2>

588 <p>Who is writing?</p>

589 <ul><li>Customer support</li>

590 <li>Product team</li>

591 </ul><h2>Audience overview</h2>

592 <p>Who is being written to?</p>

593 <ul><li>Checkr users - companies and candidates already in the Checkr ecosystem</li>

594 <li>Developers</li>

595 </ul><p>This audience is at the<b>nurturing</b>stage of the brand journey.</p>

596 <h2>Help and support tone</h2>

597 <p>How we should sound:</p>

598 <ul><li>The goal is to empower and guide users</li>

599 <li>Our tone of voice is decisive and compassionate</li>

600 <li>Focus on guiding users, solving their problems, and getting out of their way</li>

601 <li>This voice is mostly functional, with minimal expressiveness</li>

602 <li>Being clear is very important</li>

603 </ul><h2>Typical use cases</h2>

604 <ul><li>Help center</li>

605 <li>Learning center</li>

606 <li>Technical documentation (engineering release notes)</li>

607 </ul><p>Messaging for product is how we communicate with people who’re already using our services. This includes content like in-product notifications, instructions, and transactional emails.</p>

608 <h2>Who uses this messaging?</h2>

609 <p>Who is writing?</p>

610 <ul><li>Product designers</li>

611 <li>Content strategists and designers</li>

612 <li>In-product marketers</li>

613 <li>Developers</li>

614 </ul><h2>Audience overview</h2>

615 <p>Who is being written to?</p>

616 <ul><li>Checkr users - companies and candidates already in the Checkr ecosystem</li>

617 </ul><p>This audience is at the<b>nurturing</b>stage of the brand journey.</p>

618 <h2>Product tone</h2>

619 <p>How we should sound:</p>

620 <ul><li>The goal is to innovate the product and instruct users</li>

621 <li>Our tone of voice is decisive and compassionate</li>

622 <li>This voice is the most functional</li>

623 <li>Being clear is most important</li>

624 </ul><h2>Typical use cases</h2>

625 <p>Customer-facing, in-product writing:</p>

626 <ul><li>CTAs</li>

627 <li>Explanatory copy</li>

628 <li>Navigational menus</li>

629 <li>Help menus</li>

630 <li>Product deployed emails</li>

631 <li>Candidate onboarding emails</li>

632 </ul><p>Our content guide was adapted from the<a>Mailchimp Content Style Guide</a>, which they have generously provided as an open source reference under the<a>Creative Commons Attribution-NonCommercial 4.0 International License</a>.</p>

633 <p>We’d also like to acknowledge the resources Mailchimp found helpful when writing their own guide.</p>

634 <p><a>18F Content Guide</a></p>

635 <p><a>Buzzfeed Style Guide</a></p>

636 <p><a>A List Apart Style Guide</a></p>

637 <p><a>Accessibility Cheatsheet</a></p>

638 <p><a>18F Accessibility Guide</a></p>

639 <p><a>Designing for Screen Reader Compatibility</a></p>

640 <p><a>Accessible Color Combinations</a></p>

641 <p><a>WAVE Web Accessibility Evaluation Tool</a></p>

642 <p><a>The Conscious Style Guide</a></p>

643 <p><a>GLAAD Media Reference Guide</a></p>