What is the role of a Document Controller in an approval flow?

Purpose:

To help users understand the job of a Document Controller when a Transmittal is sent for approval.

Responsibilities when a Document Controller is used:

• First Gatekeeper: They receive all new Transmittals before they go to the final managers or clients.
  
  
• Reviewing Content: They check the uploaded documents to make sure everything is correct and no files are missing.
  
  
• Routing: They dynamically assign approvers and forward it to.
  
  
• Rejecting Early: If the files are wrong or incomplete, they can return the Transmittal immediately so the sender can fix it quickly.
  
  
• Make the Flow Parallel: By default, all the Approval Flows are Sequential. Before forwarding the Transmittal, the Document Controller can chose to make it Parallel (cannot be changed during Resubmission Flow).

Note on the Document Controller Role:

• The Document Controller is Optional: A project does not always need a Document Controller. Senders can choose to bypass this role and route documents using Approval Flows with only Approvers or Direct Approver instead. 

Tips and Practices:

• Think of the Document Controller as a sorting office. If your project has strict, large-scale document rules, using a DC ensures that managers only spend time reviewing files that are completely ready for final approval. If your project does not need it, you can skip the DC step entirely.