Putting it in writing: 4 situations during a project when it should be done
You have finally been awarded the project and are eager to get to work. While the focus will be the successful delivery of the stipulated outputs, which may include preparing one or more reports, surprisingly, many Consultants and Vendors are reluctant to communicate with their clients in writing. Phone calls, text messages, especially WhatsApp, are increasingly becoming the norm. However, there are several instances during the life of a project when it would be prudent to properly document what is occurring – in the form of a letter, but at the very least an email – to ensure that there is a suitable paper trail that can be referred to as and when needed. Here we outline four situations, which may occur more than once during a project, and for which we strongly recommend be documented.
1. To confirm the project scope and to document changes made
Although the scope of the project, key tasks and deliverables would be known to all parties, based on the terms of reference included in initial tender documents and in the project agreement, during the life of the project certain issues and nuances that could have an impact on project implementation may emerge after the contract has been signed. While these issues can occur at any time, they frequently become known during the initial client meetings, when you may be engaging for the first time the actual team that should benefit from your work, as opposed to the procurement team.
You may thus receive first-hand insights into the situation and challenges they are experiencing, all of which may have an impact on the approach you had hoped to implement, or what might be possible based on the circumstances now more clearly understood. For matters that are likely to have an impact on the scope, approach, deliverables and/or time lines, it is crucial to ensure they are documented and formally communicated to the client, even though the client’s designated contact person may agree with the changes that should be made,
2. To confirm decisions made
At various points during a project, the client may be required to make decisions or agree to a particular approach or course of action. Once again, it is important to document those occurrences, especially when you are being specifically asked to pursue a certain course of action. You never know when you might need to remind a client of a decision that he/she took, which is now affecting how the project is being implemented, or the outputs that can be realised.
3. To document objections or concerns
Depending on the project and the client, it may not happen very often, but when it does, it is recommended that you formally communicate to the client any concerns or objections that you might have on matters pertaining to the project and/or its implementation. To a considerable degree, the client is relying on you – regardless of whether you are a Consultant or Vendor, and more specifically, your expertise.
For example, if in your expert opinion you have concerns about a certain product or an approach that has been stipulated, say something – in writing. The client may have presented its requirements based on its limited understanding of its situation, and could welcome a more considered or suitable option. On the other hand, if the client still requires you to proceed as instructed (which you should ensure is also in writing!), you may get a better understanding of the circumstances and why that decision is being maintained. Alternatively, you can take solace in the fact that you gave the client the benefit of your expertise, which they chose not to pursue.
4. To track time-sensitive matters
Finally, most project tend to have a time frame in which they must be completed. It therefore means that many of the project tasks are time-sensitive, with some of them being critical inputs for subsequent activities. While you, as the Consultant or Vendor, may have some control over how you use your time, and the effort applied to ensure that tasks are completed within the time envisaged. there tend to be instances over which you have very little control, but they can hinder rate of progress. Two situations readily come to mind: securing feedback or approval from the client; and securing information or feedback from third parties, such as the client’s partners, associates, customers, or stakeholders. In both instances, it is recommended that you ensure that your initial communication on the issue is documented, and thereafter, any follow-up made to urge responsiveness.
In summary, regardless of the project, it is important to develop a habit of establishing a paper trail. Although most projects will occur and conclude without incident, that should never be assumed. Further, projects can go awry for a multitude of reasons, and people tend to develop amnesia with respect to their role in the challenging situation being experienced.
It can thus be easy to try to blame you, as the Consultant or the Vendor – even when it is not your fault, However, in having a paper trail, you may be in a better position to refute allegations levelled at you, and (gently) remind all of the parties of the role in the debacle that has occurred.
Image: todabasura (Pixabay)