Opus Docs are Resource documents you can create and maintain right in Opus.
Unlike traditional training PDFs, Opus Docs let your team members:
š Search for what they need
š Read in their preferred language
š² Easily view Resources on their phone
Opus Docs are great for knowledge-rich materials like:
Step-by-step SOPs (Standard Operating Procedures)
Recipe cards
HR policies like your employee handbook
Table of Contents:
How to Create a New Opus Doc
Go to Training > Resources and click "Opus Doc."
Give your doc a title (like Grilled Chicken Bowl Recipe or Closing Procedures - FOH).
Add your content using text, bullet points, images, or links.
Click Publish when you're done.
Keep it clear and skimmable. Use short steps, plain language, and visuals where they help. For a full walkthrough, see How to Create an Opus Doc.
š§ Link training content, Resources, and Task Lists directly in Opus Docs so your team can quickly find what they need. This is ideal for SOP hubs, employee handbooks, and Manager playbooks.
How to Convert a PDF into an Opus Doc
Go to Training > Resources and click "+ New Resource."
Upload your file and select "Convert into Opus Doc."
Review and clean up the formatting.
Click Save, and assign it like any other training doc.
For more detail, see How to Convert a PDF into an Opus Doc.
š§ PDF conversion gets you about 70-80% of the way there. A quick review helps make sure everything looks right.
Best Practices for Using Opus Docs
Opus Docs are designed to help you create Resources that are clear, text-based, and easy to read, especially on mobile.
ā ļø Opus Docs aren't meant to look like polished printouts or marketing materials.
Here's how to get the most out of them:
Keep it simple and text-focused
Opus Docs work best for SOPs, recipes, and HR policies that rely on clear instructions, not heavy formatting or design.
Avoid relying on layout
When you import a PDF, design elements like columns, colors, or fancy fonts won't carry over. That's by design: Opus Docs prioritize readability, searchability, and language translation.
Write with search in mind
Use clear, consistent language so team members can easily find docs using keywords.
Add visuals where they help
You can still include images or videos for steps that benefit from visual support.


