After SiftHub autofills your Primary Document with initial responses, teams need to review, refine, and validate the content before final submission. SiftHub's collaboration features transform this complex process into a streamlined workflow, enabling Delivery Managers to efficiently coordinate with team members through content requests and reviews.
Understanding Document Collaboration
The collaboration workflow is built around the Primary Document Outline, where each Section and Question moves through different stages - from 'First Draft' to 'Approved'. Team members can request content from subject matter experts, submit responses for review, change assignees, and track their assignments, ensuring nothing falls through the cracks.
Different Statuses
When a Project is first created, all Sections and Questions start in "First Draft" status and are assigned to the Delivery Manager of the Project.
The content then progresses through the following statuses:
- First Draft: Initial state with autofilled content
- Content Requested: Assigned to a collaborator for input
- Content Updated: New content provided by collaborators
- Pending Review: Submitted for review
- Approved: Content finalized and ready for submission
Core Workflows
The core workflows that guide Questions/Sections through these different statuses are:
Content Request Workflow: Used when responses need input from subject matter experts or team members. This workflow moves content from "First Draft" through "Content Requested" and "Content Updated" statuses.
Review Workflow: Used when responses need validation from solution leaders or experts. This workflow handles the "Pending Review" stage and moves content to either "Approved" status or back to "First Draft" for revisions.
Next Steps
- To learn how to request and manage content updates from team members, see Content Request Workflow.
- For information about submitting content for review and managing approvals, see Content Review Workflow.