Change Management dilemma (Install Guide v. Software Updates)

[Jill Mohan]

I am hoping to find a guru to lead me to my answer.

I have written an Installation Guide for the system we delivered to the
government. We keep releasing updates to the system software...

   - some of these updates are Manufacturer updates (such as Oracle
   patches, Java patches, etc.),
   - some are updated scripts to enhance functionality which take us from
   one baseline version to the next baseline version, and
   - still others are just data dumps that are fed into the system.

I'm thinking I may have my answer... only those updates which enhance
functionality are captured in the Build Guide update for that respective
baseline version, correct?

IMHO, the Govt is preoccupied with this end-of-the-world business.  So they
worry that if civilization were wiped out, would my Build Guide bring them
up and running to the baseline version on record? Which is a tricky
question, because if I only include our enhanced functionality upgrades,
then...i guess i need to put a pointer to check this other document for any
other updates that apply to the system?
Am I on the right track?

Thanks for answering my musings.
Jill