May I

for a few?
Why not just tell the missed to "climb to vfr pattern altitude, and extend your upwind for departing traffic
on rwy 16, I'll call your crosswind, squawk VFR." Tell the 1st one waiting for rwy 16 to expect departure
without delay, TIPH (if not already on the numbers and not an intersected/shared threshold).
Confirm IFR departure release for and launch the 1st rwy 16 a/c, make the on-the-go call, then give apc a
heads-up

for potential spill out traffic from the class D into class c to the west @ f/w pattern
altitude, will be changing squawk from IFR to 1-2-0-0 momentarily. Once a/c departing 16 crosses
intersection, 28L/R is clear and ready for landing both left base for 28L and (by this time) short final
28R. Make the base follow the short for opposite rwy landing if it looks too tight, as turning a/c will
get eaten up by straight descending a/c 99% of the time, and give all parties wake turb. warnings if
applicable (due to rwy 16 a/c).
After the twins for 28 are passed 16, launch the second, and continue as above, calling dep.
w/ rolling, and setting up for the next 16 dep guy. This works great if all a/c are the same size/weight
class, as they can request to waive for delays (though you cannot solicit the waiver), and if the
pilot isn't aware of this ability, do not bank on them working rapidly on the departure for you.
It's all about keeping it simple, and keeping everybody informed. You can accomplish ANYTHING
with proper coordination and information sharing.
But, then again, what do I know about pushing traffic and driving the bus?