Change Management Editing and Proofreading Services

The heat map shows Finance in yellow and Operations in red, and it is the only document in the pack that describes impact. It tells the program office where the pain will be. It tells nobody in Finance what Tuesday looks like after go-live. That is the question the person in the affected role is asking, and most of what a program later handles as resistance is the absence of an answer to it.

The documents we edit for Change Management

Change impact assessments and role-level impact documents are the core of what we edit here. Stakeholder analysis and engagement planning documents come with them, along with communication plans, message frameworks, and business readiness checklists. We also work on training needs analysis and role-based training plans, process and role documentation for the future state, change network and champion material, feedback logging documentation, and benefits realization plans. Go-live and hypercare communications, manager toolkits, and the review documentation written once the system is live come to us as well. Our editors work on the document written from the affected person's chair.

What the editing involves

Role-level impact reads best as one page per role, written in the vocabulary that role uses at work, and each page answers the same fixed set of questions. What you do today and will stop doing, what is new, and what stays the same come first. Then come week one, month three, the training and its dates, and the name of the person who answers questions. A color on a grid answers none of those. One page per affected role across 40 roles is 40 pages, which is more work than a grid of 12 functions on one slide, and that is why the grid usually wins. The client supplies the content under every heading, because what the role becomes is not something we decide.

One entry is almost always missing, which is what happens to a person if the new way is slower for the first month. That fear is real, it is rarely written down, and leaving it out is what makes the rest of the pack read as promotional copy. The honest entries belong in the same document: the role where the change removes the part of the job the person liked, and the team whose workload rises for two quarters before it falls. A line reading "this role keeps the reporting and loses the client contact" is what makes the rest of the page believable. Programs resist writing those down because it makes the losses visible. The losses are already visible to the people carrying them.

Confidentiality and the limits of our role

Everything you send us is treated in confidence, including program material, restructuring plans, and information about identifiable people. We are editors, not change, HR, or employment advisors, and we offer no view on program design, notification obligations, or any decision affecting employment. What we can do is make the pack answer the question the affected person is asking.