Ubercart

I'm trying to set up event registration. The client's requirements boil down to:

• Volume discount. (more than 4 = cheaper, but only if all from same institution)
• Date-linked discount. (before date y = cheaper)
• Each reservation corresponds with a record that includes contact information. (I.e., not just buying "seats" -- actually registering people.)

I've had an idea about how I wanted to do this, but looking at the solutions in the forums for similar problems -- well, they're much more complex. So I'd like to do a sanity check on my approach.

Would really like to be able to do this in D6/UC2.x.

Here's what I had planned to do:

1. Create a product that has attributes corresponding to all the information I want -- basically, a data-collection instrument.
2. Constrain that product in such a way that you can't increment the units on the order -- e.g., you can't order 2 of 'Mary Rogers', but you can get one 'Mary Rogers' and one 'Mary Smith' (where the names are buyer-provided product attribute values). (I don't actually know how to do this, yet, so if this is difficult or impossible I suppose that's a gap in my plan.)
3. The pricing and discounting rules I think I've got figured out how to manage.

So in principle I'd have orders that included one to x people, with all the information the client would need to be in touch with them (email, phone, company/institution name, etc.). I'm assuming it might be slightly difficult to get the data into a useful form, but nothing someone clever with SQL couldn't dope out. (I know such a person.)

So, is there anything wrong with this idea? Am I missing something? (Other than the fact that I don't yet know how to keep people from buying 6 'Mary Rogers'.)