Requirements Traceability

When i manage requirements documents and i get that change that's been accepted, i up date the requirement. I also trac changes within it. So once i've created a new version, what i do then is communicate that out to all the people that are working on the project. It's a good way to em a, aversion control, but b, communicate that out. If we do our jobs where we're just up dating our document, but we're not communicating to everyone else who's impacted, guess what's going to happen at the end of the project? You're not goin to get delivered.