{"id":6315,"date":"2013-11-12T09:29:17","date_gmt":"2013-11-11T22:29:17","guid":{"rendered":"http:\/\/wordconstructions.com.au\/blog\/?p=6315"},"modified":"2013-11-01T17:35:21","modified_gmt":"2013-11-01T06:35:21","slug":"writing-annual-reports-and-attachments-as-one","status":"publish","type":"post","link":"https:\/\/wordconstructions.com.au\/blog\/2013\/11\/writing-annual-reports-and-attachments-as-one\/","title":{"rendered":"Writing annual reports and attachments as one"},"content":{"rendered":"

So you have decided to have an annual report and a couple of inclusions<\/a> that will be sent out with the annual report.<\/p>\n

\"Task<\/a>

An annual report and any inclusions all form one annual mailing project.<\/p><\/div>\n

Does this equate to three separate projects, or three parts to one project?<\/strong><\/p>\n

It is a good question, and I can see a temptation to treat them as two or there projects. Maybe you outsource the big project (the annual report)<\/a> but figure you can manage the smaller ones yourself. or maybe you want to outsource to different people so the inclusions don’t distract from the annual report and vice versa.<\/p>\n

However, I consider them to be aspects of one project<\/strong> and like the idea of them being managed as such. I usually mange the inclusions along with annual\u00a0reports for clients, even if it is just a review and feedback on an existing document.<\/p>\n

why consider them as a single project<\/h1>\n

Treating the annual report and any inclusions as one project works because<\/p>\n