why document calculations

huangyhg

why document calculations?
why do we have to document all our calculations?
we seem to waste a lot of time form filling, documenting, filing, to produce a mountain of paper that mostly never gets looked at again.
check out our whitepaper library.
for the one time it does get looked at again.
it really helps when doing a peer review, or checking someone else's project.  it even helps when checking your own work.  i have often found myself wondering what i was thinking when i designed a certain thing, and having my calcs answered the question.
i had the opportunity recently to review calculations produced in the late 60s by someone in my company.  it was a four-story concrete building.  two-way slabs, and moment frames done by hand, with moment distribution.  it was really amazing.  very neat and well organized, and everything was written out, describing the steps.  textbook.  none of my calcs ever look that good.
neatness counts.
sdz
because one day you will have to go to court and justify your design.
cheers
greg locock
i work for a consulting firm doing bridge design for state dot’s, and typically part of our deliverables to the dot will be the engineering calculations.  so, there is an obvious reason to document the design calculations.  this must not be the case in other areas of structural engineering.
also, documenting and backchecking design calculations is part of having a proper qa/qc process, as mentioned by rholder98.
documented calculations are also helpful to have for future work that’s similar to what you have done in the past.  for similar designs, old calcs can be used as a starting point for your new designs.  you can kind of build up an archive of design samples with your old calcs.
sdz...greg's right.  that's one of the most significant reasons we document things in engineering.
my practice includes a substantial amount of forensic work.  i have seen cases where good documentation caused the litigation cannon to get pointed elsewhere.  i just recently was involved in a case where poor documentation cost a company about $500,000 us (in cold cash) not to mention the loss of continuing on a multi-million dollar revenue project.
document everything (wish i could always follow my own advice!).  throw away draft reports.  keep only the final version of anything your produce.  be able to reproduce the project many years from now...sometimes you have to do that.
sdz,
in the aerospace industry where the customer often wants to change the use of the product or add more stuff it is often necessary to go back to the original calculations and see what the consequence of these changes would be for, say, fatigue stresses. it is also often a requirement; the customer demands calculations are kept for at least the lifetime of the product in case of in-service issues.
#1 liability
#2 liability
#3 proof that you did things right.
#4  if a modification is done to a structure at a later date it makes it much easier to see the calcs.
youve never been sued egh?
thank you, everyone, for your comments.
also enforcing jurisdictions often require them to conduct an effective and meaningful plan check.