Yup, I've seen and used it both ways.

Dates and responsibilities and all that crap.

In one document? Here (by which I mean my team/division) the people doing the grunt work are handed a requirements document and they generate a design document which will be crosschecked against it. Once that's done, they may or may not do an even more techie document for their own consumption and reference.

But the document written only by the people who need the service is what will be used by the quality assurance people to validate that the service was provided properly.

Slightly relatedly, my training material gave me the words "A tool is a tangible item, such as a software program," all in that order and stuff. Thanks guys. Way to inspire confidence in your mastery of the written word.

eta:

For my project management class, we used the PMBOK -- is that what you're looking at?

This is PMBOK-related. The first class I took was PMBOK and UCLA extension but taught by our guys. So the language matched up. The previous gig knew not of the PMBOK. I'm startled to realise that there are people here using that language, as well as people here who've never encountered it before.

Erf - I've already said more than I ever care to about how our documents work around here. Configuration Management, in the strictest sense, is all a big convoluted blur to me.

I do not envy the people who are trying to make one project management methodology span 15 or so divisions and a gazillion people here. I had no idea we were on so many pages.

That alarm clock is the most evil thing ever.

Finally getting that third eye added to your forehead?

I think it'll go well with the tattoos and the large-caliber weapon, and hey, I can wear an eye-patch over it!

We do a satatement of services with each client - I (the PM) am not involved with it, it is a contract and business people deal with it. It states things we will do, as well as things the client will do. My documents are ever-changing, but basically consist of a schedule with dates when things are do and will happen (both us to them and them to us), a checklist of guidelines on how we need info/items, and an internal checklist we use for delivering our content to our development division.

We do a satatement of services with each client

What input do you use for it?

Also, have you taken any PM classes? Do you use any PM references? I put down PMP as a goal for 2006. I took a UCLA PMBOK-related course in 2004, and have been managing projects for ten years now, but it's all making my head twisty suddenly.

Finally getting that third eye added to your forehead?

I think it'll go well with the tattoos and the large-caliber weapon, and hey, I can wear an eye-patch over it!

Yarr.

I'm sure I took a project management course in grad school but that was over 10 years ago. I know no PM references.

The SOS sets things like price of product, profit-sharing (wrong term) structure on the deal, any minimum product guarantees, life of the product, what we will report to them and how often, what marketing they will agree to for our product, whether the relationship is exclusive, Taht's all I can think of.