Workflows for Widgets

I work at a University, which has a number of departments, each with their own set of forms and agreements. Most of these documents include a dynamic signer routing structure that flows one way or another based on the sender. For ease of use and availability to senders outside of the organization, we have decided to use Widgets for most of our documents. However, there are some documents that are not been able to create because of their routing structure. Here are a couple sample scenarios:

Scenario 1:

A student applies for access to one of three University services, managed by different people. This access form must be signed by the student's department chairperson and the Dean of his/her Division. The application is then forwarded to one of three service managers, depending on the service chosen, for signature. The final signed document is forwarded to a static processing center (the author of the application). We are willing to create three separate forms, one for each service manager, if necessary. 

Scenario 2:

An applicant wants to apply for a research grant. He/She must complete an application form that requires the signature of his/her department chairperson and the Dean of his/her Division. The application then goes to few static signers.

There are much more scenarios with similar structures. It would be great if workflows worked with Widgets. Since this is not the case, is there some type of work-around that can be done to allow such documents to flow correctly?