InfoPath Dev

Hey everybody, i'm working on my first infopath'07 + sharepoint'07 + MOSS deployment. I have a solution in the pipe, but i feel like i'm missing something.

this will be a long post.

i'm not looking for any specific details, just more or less if i'm on the right path. 

*everything will be browser compatible and will not leave the intranet*

 Customer (John) submits form (Widget XYZ) to Sharepoint document library #1

 John's Boss Bobby, then approves the form, which gets submitted into Sharepoint #2

The Team Leader Tom, views the WidgetXYZ request and approves it, which gets sent to Sharepoint #3

The Overall Lead Manager Neil, agrees with Tom that WidgetXYZ is valid and decided to have his number one engineer Chris to work on the Job.

Chris then gets the request for XYZ, and sets to work on it, updates progress, and then finishes it.

Neil takes the finished form for WidgetXZY, and then places it in the Archive Sharepoint #4, where it becomes read-only forever. 

~Fin

Now obviously i know i dont normally need that may sharepoint libraries, but here is my reasoning. 

The #1 SP Lib, will get thousands of entries a week. so based on the mgr approval the documents will get weeded out and only the approved ones that will actually get work done will be seen by the overall lead manager. He then needs to be able to see all the active requests and be able to look at a few rows and columns and determine priority which can change daily.

 another thing, the first link in the chain, the customer and his manager can be anybody in the company (500,000+ people). and 75%+ of the first step customers will NOT have a unique login.

So from what i'm describing, does anybody see any glaring flaws or anyway i can make this easier or any solid tips and tricks?

Let me know if i'm even on the right track.

Thanks, 

Scott

Hi, Scott:

What happens to forms that don't get approved in Step One or Two? Is anything not approved considered rejected? Or does everything eventually get approved? I'm concerned about how the person who approves the form submitted in step one is going to manage his workload -- be able to find the forms he's looking for. You say that more than a thousand will be submitted each week, and the guy who has to cull through them, if he doesn't have a way to make that list manageable, is going to have a hard time finding stuff. Same with step two.

How does the person who initially submitted know if their form has been approved or not? Is there an action step if my form isn't approved?

I realize you were just painting out a broad outline, but those were the details that popped out to me.

Hope that helps!