Quick Start

"Think of this like Google Docs with superpowers for official company policies. Instead of everyone editing the same document and losing track of changes, we have a system where:

1. Writers propose changes in a controlled environment
2. You see exactly what changed with old text crossed out and new text highlighted
3. You approve or request changes with comments
4. Once approved, the policy automatically updates everywhere"

Workflow

Progress:

• Receive notification - Email alert when policy needs your approval
• Click preview link - Opens clean webpage showing the policy as it will appear
• Review changes - Deleted text shows with strikethrough, new text appears highlighted
• Add comments - Click anywhere to leave feedback (like commenting in Word)
• Approve or request changes - Single button click to approve or send back for revisions
• Track progress - See where the approval stands in the workflow chain

1. Writer creates proposal - Policy team drafts changes in the system
2. Multi-level approval - Goes through department head → legal → executive (configurable)
3. Preview generation - System automatically creates readable webpage
4. Collaborative review - All stakeholders can comment and discuss
5. Publication - Approved changes go live instantly across all platforms
6. Archive management - Full history of who changed what and when

Examples

Example 1: Remote Work Policy Update Input: HR wants to change "2 days remote maximum" to "3 days remote maximum" Output: You see the policy webpage with "2 days remote maximum" crossed out and "3 days remote maximum" highlighted in green, with a comment bubble explaining the business justification

Example 2: Approval Workflow Input: New expense policy requiring three approvals (Finance Director, Legal, CFO) Output: System automatically routes to Finance Director first, then Legal after approval, finally CFO. Each person sees their place in the chain and who approved before them.

Best Practices

• Focus on the preview - This is your main workspace, not the technical editing area
• Use comments liberally - Ask questions directly on specific sections
• Check context - Click "Show History" to see why changes were made
• Approve promptly - System tracks approval times and sends gentle reminders
• Review formatting - Ensure policies look professional in the preview before approving

• Like track changes in Word - but everyone sees a clean, professional version
• Like email approval chains - but with full context and history visible
• Like website publishing - but with built-in quality control and legal review

Common Pitfalls

• Don't edit the raw markup - Always work in the preview environment
• Don't approve without reviewing formatting - Check headers, bullets, and links work properly
• Don't skip the comment step - Even simple approvals benefit from "Looks good" confirmation
• Don't ignore the workflow order - System prevents out-of-sequence approvals for good reason
• Don't assume others see your comments - Use @mentions to notify specific people

• Can't see changes clearly? - Use the "Show diff" toggle to highlight modifications
• Preview looks broken? - Refresh the page; if still broken, comment "Preview issue" and tag IT
• Lost in the workflow? - Click "Approval Status" to see the complete chain and your position