![does final draft 11 read final draft 10 documents does final draft 11 read final draft 10 documents](https://i1.rgstatic.net/publication/346312919_Public_transport_users_versus_private_vehicle_users_differences_about_quality_of_service_satisfaction_and_attitudes_toward_public_transport_in_Madrid_Spain/links/5fd7901292851c13fe86f1f0/largepreview.png)
Recently I have been marking up my changes manually, simply by changing the font colour, and thus avoiding such subversive feelings. Sure, you can improve readability by accepting an addition or a deletion here and there, but that somehow feels like you are subverting the tool, trying to trick your audience. The trouble with “track changes” is that it shows each and every change you have made verbatim, and sometimes that can impair readability. Microsoft Word’s “track changes” facility has improved considerably over the years and is a very useful markup tool, although I always feel somewhat politically conservative every time I “reject change”. Marking up changes is a common technique to show your audience what has changed in a document. It’s especially useful if I’m working on several documents at once, and really helps on projects where I am storing work-in-progress on a shared drive. In this way, I can easily spot the difference between a document that’s in progress and one that’s complete. I do this even for draft documents, and even if the document is only stored locally on my computer, where no one else can see it. When I am ready to share/issue the document, I remove the “WIP” suffix (and also add details of the version to the version history section within the document). When I’m working on a version controlled document, I always add a suffix “WIP” onto the file name to show that it is Work In Progress. There seems little point in calling something a draft if it’s never actually going to be approved (or baselined). If I am creating a document that I know I will share with others, but it’s not a document that will be going through any formal approval process, I tend to give it a simple numerical version number (v1, v2, v3 etc.). Don’t Use Drafts Unless the Document Will Be Approved Sometimes it’s as simple as adding the version number to the file name, rather than inserting an explicit document control section within the document, and it takes seconds to do. That doesn’t mean I use a formal template for every document. it’s not just purely for personal use), I will version control it as a matter of course. If I think I am likely to share a document with others (i.e. Oh, hang, on, I have a few extra thoughts. The only downside is that you run into trouble after 26 drafts! Drafts are associated with the final version they are working towards.
![does final draft 11 read final draft 10 documents does final draft 11 read final draft 10 documents](https://image.slidesharecdn.com/ivegotagreatideaforafilm-150507210227-lva1-app6891/95/screen-australia-info-guide-10-638.jpg)
Final/approved versions are clearly labeled as such.Issue 2 Draft A – first draft of a change to Issue 1 Final (working towards Issue 2).Issue 1 Final (or, alternatively, Issue 1 Approved) – signed off/approved version.I discovered it on a project I worked on a few years back and I’ve tried to introduce it everywhere I’ve been since then. But there is an alternative that I do like. So I don’t like this version numbering scheme. So, for example, version 1.3 is supposed to be a draft working towards version 2.0, but to my mind the “1” associates it more with version 1.0 than version 2.0. In order to be sure, I have to open the document and check the version history, and even then, authors are sometimes not rigorous enough to state explicitly whether the document amendment is signed off or not.Īnd even if you have a clearly stated convention that says an approved document must be “something dot zero”, I don’t like the way that the numbers stack up.
#DOES FINAL DRAFT 11 READ FINAL DRAFT 10 DOCUMENTS UPDATE#
But at this point it’s never clear (to me at least) whether version 1.1 is a draft for approval or an approved update to version 1.1. So version 1.0 gets updated to version 1.1, and maybe version 1.2, and so on. But inevitably (and increasingly in an agile world where change is to be encouraged, nay embraced)… things change, and version 1.0 needs to be revised.
![does final draft 11 read final draft 10 documents does final draft 11 read final draft 10 documents](https://img.yumpu.com/6975405/1/500x640/lg251-intermediate-german-i.jpg)
Now that’s all well and good up to that point. Most people tend to use the following version numbering scheme: Document version numbers might seem like a trivial concept – a subject upon which there is little to be said – but they are a real bug bear for me. So here’s a topic that you don’t see discussed very often.