As far as listing process goes, I know the reviewers want to see each stage (even if there's no container there) listed as a waypoint, with a description of what goes on at that stage. Leave a nice, clear note for the reviewer in the logs, explaining anything that's even slightly unusual. Pretend you didn't write the listing, read over the note for the reviewer, and make sure it makes complete sense.
As far as the reviewing process goes, the previous answers have good advice. Patience is a virtue, especially when waiting for a cache to be reviewed. GC guideleines say to drop your reviewer an email if nothing's happened after 72 hours. That's an okay idea, but just remember that the 72 hour thing is a guideline. Some reviewers have ample free time to get multi or complicated caches reviewed and make a reply to the hider inside 72 hours. Other reviewers have full work loads or family obligations, and assessing a multi or complicated cache may just take longer. In any case, remember that the reviewer is not going to reach an opinion about the cache and not share it with you. Just be patient. The answer will come...
I would suggest if the listing involves code, or some complex method of deriving coordinates, give all that info to your reviewer.
I think the biggest time-consumer in reviewing these caches is trying to decipher what the hider has actually done, and ANYTHING you can tell the reviewer (via a note in the logs) to make it easier to understand and visualize on a map will help them process the listing more quickly.
Also remember that your reviewer is probably reviewing numerous other caches at the same time, and that makes things difficult on his or her end, as well.
Again, just be patient. One really polite email after four or five days is probably all it takes to get a reading on what's going on.
Good luck on your hide, it's a lot of fun to see that FTF log on a new cache.
Happy trails............
WebChimp
That's sage advice, coming from a geocacher who's only been in the game for 14 months, according to his profile.