PerfectIt allows editors to focus on the content and meaning of a given text and is especially useful when dealing with longer texts. It runs automated checks on all the inconsistencies that would require hours to eliminate: abbreviations/acronyms and their expansions, (standardised) spelling, table and heading numbering, spacing and much much more. It simplifies navigation and viewing of these elements across long documents. It can be customised to each text's requirements: either by using the existing preloaded styles (EU, UK, etc.) or by modifying these at many levels to accomodate variations.

Allow me answer that question by sharing my first experience with PerfectIt. SETTING: A (pre-COVID) session of the Bay Area Editors’ Forum EVENT: “Introduction to [the marvels of] PerfectIt” SCREENSHOT: A bullet list of text CONTEXT: Daniel Heuman demonstrating how PerfectIt will identify if there are errors or inconsistencies anywhere within a document, including details like inconsistent capitalization and closing punctuation in bullet lists SOUND BITE: The audible gasp as the crowd realizes how much time this would save (and the discomfiture it would prevent) Someone who isn’t an editor or proofreader might not immediately see the benefit of PerfectIt, but let me tell you … just WOW. It catches stuff we should have caught ourselves, and are chagrined to learn we missed. It catches stuff we’re not even embarrassed to have missed, like a stray or absent hyphen in a VERY long proper name that appears multiple times. It catches stuff we’re humbled to realize we never would have caught, like lesser-known tidbits in the Chicago Manual of Style (CMOS)—which are offered with the CMOS* item number and the precise text of the rule for further reference (and memorization). (*Note that the abbreviation was defined before being used alone.) That’s all just what’s in PerfectIt already. But you can also implement into the program the house style of your employer, your main contract client, etc. That feature is a huge bonus if you work with a number of different clients who have different preferences for small details—and so each time you turn to a different gig you need to reacquaint yourself with that client’s preferences (ten vs. 10 | em-dash [—] vs. spaced en-dash [ – ] | ellipsis character […] vs. three unspaced periods […] vs. three periods w/ nonbreaking spaces [.°.°.] | E.°B. White vs. E.B. White vs. Egad White). You can create a style in PerfectIt for each client, and then let PerfectIt remind you what that client prefers. And it should be emphasized: the PerfectIt process isn’t about running the software, grabbing a snack, having it change stuff unbeknownst to us, and then blindly submitting the document. The process involves having inconsistencies identified for us—at which point we make a conscious decision about which option to choose. And of all the things it’s programmed to catch, my favorite is common typos (General Manger | general pubic | Turdish vs. Kurdish vs. Turkish). BTW: I ran PerfectIt on this review before submitting it just to see what it would find; apparently “screenshot” is one word, not two. So, yeah—I love PerfectIt.

I am a big fan of PerfectIt and use it for most of my editing work. The longer the document, the more it comes into its own. It catches inconsistencies and is quick and straightforward to use. I also like the option of setting up personalised style sheets.