I would love to see what people can provide in the way of advice, as well.  I recently had to come up with a way to allow orders to be submitted and then be altered along the way at three stages!  

• An applicant submits an order;
• Staff reviews the order, decides it's okay, submits (which sends to SQL lookup table);
• Or, staff reviews the order and knows something isn't available and they need to make a change.
• Or, applicant calls and requests a change, or we discover an item is not available after the order details were send to the db.  What can be done?

I had to build in a Stage.  We needed the record of the original order/request, as well as a record of what was approved.  So, Stage 2 has the table of "original order" (read-only) with a table below mirroring the order but changeable.  Staff would make changes if needed, then Submit to send the data to the db.

But what if a change happens after staff hit submit at Stage 2 and the order details have already gone to the db?  So, now I'm considering building in another stage where another change could be made and still be a part of the record within the paperless process.  Haven't done this yet.  (What I did do, this week, in order to help keep the db record accurate is, I built another form for our staff to use if they have to alter the db order lines for any given applicant, but this form will not be kept as a part of the applicants' records, unless we manually transfer that record into the final entry that gets saved into the repository.) 

I'm kind of hoping that someone will know a better way.