I know this is an old topic but I don't agree entirely with the responses.
Industry practice seems to be to cloud each change and use revision deltas from start to finish. The following revision will turn off the clouds of the previous and leave the deltas on.
What gets clouded depends on the stage of the drawings and the extent of the change. A typo, misaligned or random floating line, scope/viewport clipping change that doesn't show new relevant information; are examples of things that do not get clouded. If the change, in any way, affects what or how something is constructed then that constitutes a revision and therefore a cloud. A typo (miss spelling, not incorrect size) alone should not constitute a revision.
Now, understanding the progression of drawings from schematic, to design development, to construction documents; revisions should start over when you transition from one of these stages to the next due to who is typically involved up to each stage and who may have seen the documents. My office typically combines the design development and construction documents stages with particular clients using % coordination sets leading up to the first time we sign and seal a set of plans which becomes our rev 0. Regardless of submission for permit, our document is dated from the original rev 0 (when we first S&S the document and sent to our client), and subsequent revisions are based off that unless the client tells us otherwise.
It is important that we cloud each revision as we release them so that anyone who may have already seen the documents can quickly note what has changed. Being a structural firm, we do not typically disseminate document changes to anyone other than the architect or contractor unless specifically requested and we are almost never made aware of who has seen what and what revision they have seen. For this reason, it is important for revision deltas to remain in future documents so that you can backtrack when, where, and why a change occurred. I have drafted both engineer of record drawings and shop drawings and I have learned that you don't always receive the latest or a complete set from the architect, contractor, or structural engineer. The best we can do is base our drawings off what we've received. We note the referenced plans and the date on them in our drawings to protect ourselves from dispute, but I've seen plans where no clouds are ever used, where each sheet has it's own revision order/date, where no revisions are ever noted even though I have multiple S&S versions of the same plans with a multitude of changes.
Bottom line, if a change affects how something is going to be built, then yes you should cloud it.
