Revising Technical Document
Revising Technical Document
(OP)
I am adding to a specification that has already been through the approval proccess and we are nearing the end of the project. What is the best way to add to this so people realize what has changed? I dont think clouding is appropriate for a document situation. Bold lettering maybe?





RE: Revising Technical Document
My current place doesn't really do anything except populate a small revision reason field which doesn't cover all but the simplest changes.
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Revising Technical Document
Good on ya,
Goober Dave
RE: Revising Technical Document
I think Word can do this automatically with track changes or something but it's been a while.
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Revising Technical Document
David
RE: Revising Technical Document
However a vertical line and rev triangle in the margin is the best for the hard copy.
(IMHO)
RE: Revising Technical Document
Bars on the side of the margin are only good for the latest revision.
RE: Revising Technical Document
RE: Revising Technical Document
This really only works if you have relatively few, simple changes, which is what the addendum process should be, but there are always exceptions. What i can't remember is if this is possible in Word, Pages (MAC) or Acrobat because I work for a firm that uses a mixed platform and I work on both PC and MAC at my desk.
"Gorgeous hair is the best revenge." Ivana Trump
RE: Revising Technical Document
Vertical lines sounds golden.
rmw
RE: Revising Technical Document
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Revising Technical Document
Lately I've been reviewing a lot of contracts and doing the negotiation for provisions, modifications and changes. The date/initial/color method made it easy to spot who was requesting the change. Each party reviewing the contract had their initials and a color that was specific to them, so you could glance through and see what that particular individual wanted without having to scrutinize each comment. This was especially useful as the negotiations wound down to a couple of people so it was just a battle between, in my case, blue and purple. Green, orange, red, and teal had dropped out or backed down and it was between me (purple) and the Owner's attorney's boss (dark blue). As far as I know, none us were using black and white monitors, nor color blind. Nothing was printed until the very end when the negotiations were at an end and the parties that were to sign the contract had their final stamp of approval.
Using the commentary method also made it easier to check an agreed-to change if someone tried to make the same change after a certain provision had been agreed to by all parties. It stopped the "didn't we already decide on this?" stuff because the comments were right there for everyone to see.
"Gorgeous hair is the best revenge." Ivana Trump
RE: Revising Technical Document
First used it on a TERD back in 99.
(Training Equipment Requirement Document)
However, I don't think it works well for the final release/revision.
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?
RE: Revising Technical Document
rmw