The diagram below represents the typical workflow for each project.

The dark gray arrows correspond to obligatory workflow chains. The light arrows show optional chains.

  A client posts an order. The support team responds to the order.

  The support team makes sure the order has all required information (descriptions, attachments). Support may ask the client to submit additional information, etc.

  Support passes the order to a project manager.

  The manager investigates the design and requirements. This may result in additional questions.

  The manager prepares the order and passes it to a markup-developer.

  The markup-developer receives the order and studies the requirements. This may result in questions to the manager.

 After the markup is done, the markup-developer passes the result to the QA-team.

  The QA-team tests the markup thoroughly in all of the supported browsers. This may result in fixing requests to the markup-developer.

  Once QA-team approves the mark-up it is passed to the client.

  If the order includes implementation, the markup is passed to the Development Department.

• The Development Manager assigns the implementation task to a developer.
• After the implementation is completed the order is passed to the development QA-team.
• When the implementation is ready, the Development Manager notifies the manager, who delivers the final product to the client.

Client feedback is processed in the same way.