You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > Operations > Editorial Support > Proofing Process for Legacy Handbooks
Proofing Process for Legacy Handbooks
print icon
Note:  Generally, handbooks are not full proofed unless specified — only proof tracked changes unless otherwise specified by your designer.  All Cases and Exercises created by a Designer unless otherwise specified should be full proofed by the Editorial Specialist before being pulled into a handbook.  If the handbook is already created, be sure to check that any global changes in the handbook are made to the cases and exercises.

 

(Cases and exercises should be created using the current templates in the system. 

These are either in the program folder in Design SharePoint Library or the Products Library.

The Leader’s Guide page usually contains a section called “With Thanks To:” that is included to give credit to the role play interviewee.  This should be close to the bottom of the page.)

  1. Check out to edit the document from SharePoint.
  2. Turn off or unlock the handbook (depending which round of edits you’re in — for the first round, the book most likely will not be locked.  But, it should be locked for all following rounds.)
  3. Add/update the client logo, if needed.
  4. Proofread the track changes.  (If you come across any formatting issues, you can fix those as you go along.)  Look for:
  • Logic/ambiguity/missing words
  • Does the content follow the appropriate Model?
  • Grammar
  • Consistency
  • Spacing between sentences
  • Spelling
  • Fact check (all proper nouns, names, numbers, technical terms, product names, etc.)
  1. Check/set margins.
  2. Check styles.  (Only make sure that appropriate styles are there.  If they are not, ask another ES to help you.  Do not pull the styles in again from scratch as your first option.)
  3. Simultaneously check formatting on each page (including looking for any pages that might be landscape pages, all styles are correct on the page, section breaks are on and are visible on each page, spacing between bullets and dashes, correct background images being used, text centered in model boxes, picture sizes are correct, gray size and color of word on bumper page is correct, headings sitting on the line correctly, correct copyright year, black bold to intense emphasis, etc.)
  • Insert comments with any questions for Designers.
  1. Check headers to make sure that they are linked/unlinked correctly.
  2. Check footers to make sure that they are linked/unlinked correctly.
  3. Navigation Bar:  If there is a navigation bar present in new materials, remove it.  If it is present in existing materials, confirm with the Designer that it is okay to remove it.
  4. Check pagination (set/adjust, where needed).
  5. Pull standalone material into the document, if they are clean and ready and if they are required (such as role plays, change story poster, etc.).
  6. Do globals.
  7. Spell check, according to the spell check process (see the document for that).
  8. Update or add code to the bottom of the last participant page (including date and version number:  MM.DD.YY/DESIGNER INITIALS/da initials v.___).   Designer initials should be CAPITALIZED. ES initials should be lowercase.Follow spacing and punctuation exactly as is on the above example.
  9. Lock the document by setting the editing restrictions to only allow tracked changes.
  10. Save the document.
  11. Check in the document
  12. Alert the Designer that the document has been proofed, and send along the new link to the document or folder location that the document is located.
  13. Cross-check:  If the document is ready to be cross-checked, PDF (from read only view), print in color, and send out for cross check to another ES.
Feedback
0 out of 0 found this helpful

scroll to top icon