Documenting for Future Employee Communications UpdatesThe key to making sure that a Project can be easily modified and/or updated is to Document as we go.  As with other Phases of the Project, this must be Collaborative.
Documenting with notes is not difficult.  Just need a bit of discipline.  We provide a common area where both of us can add documentation as we work
If you look to the far left of this page, you'll see a link for Watch - Collaborate - or DIY.  If DIY becomes your future choice, then documentation will be critical.
DynamicDynamic data is data that changes on-the-fly as a result of UPDATES, DELETES or INSERTS. A dynamic project (such as Benefit Enrollment) requires a greater level of documentation detail and may require additional levels of GUI programming.  
Make sure we understand your Employee Communications goals and get ready to take notes. :-)
 Employee Benefit Statements: One time use or Updateable?
Reinventing the Wheel for every Employee Communications Project can become tiresome and waste your most valuable commodity; time.
Regardless of the Project, we do our best to save the underlying 'design', to include a complete history of employee communications source document edits & alterations.
An ExampleWe work together on an employee communications Project and everyone is satisified.  Well, almost everyone. You take the 'ready to publish' Project to the CEO, who says: "I don't like the colors & move this from here to there and add this and delete that. Rewrite this section. Other than that, I like it."
Ughhh.... but:1) We Save the version that non-CEO's liked.2) Clone- and then make revisions.
The original is saved as XML & since it may only be 300k, keep it.  
Never throw away ideas.  Even the 'bad' ones have value.
 Employee Benefit Statements: Cross Project Integration?