In many, not to say all, projects we are dealing with an explosive growth of the number of email messages. Managing project email has become a big challenge, but is crucial to properly control the exchange of information in your project.
Unstructured and unmanaged email (which project email, with or without attachments, is sent to whom and which project email has been received?) can cause serious problems in case of any legal issue with external parties. Especially when the external party knows exactly which email has been sent from your organization.
Email is indispensable in exchanging information between internal and external project members. Project email often includes important information like agreements, confirmations, tasks, contracts, project documents, etc. This requires that project email is managed properly. But how to manage and control project email properly? Where to save and store project email, so it is centrally available and accessible to all project members next to the other project information. How to deal with saving and storing email that is send to multiple recipients, whether as carbon copy or not? And how to prevent that the same email is saved and stored multiple times?
Use the link below to download this case study: