Please advise: This feature is not currently available. The article has been published to provide reference material for an upcoming release.
Important Note: Content Submission is not enabled by default. Admins can turn on this feature and designate Submission and Reviewer user permissions by going to the Feature pages in the Manage Portal.
Overview
The Content Submission workflow allows project team members to nominate content created or modified during a project for inclusion in the firm's standards library. Instead of relying on manual communication or periodic reviews of container files, users can submit content directly from Revit into a managed review process.
The workflow creates a clear path from:
Project Content → Submission Queue → QA/QC Review → Library Publication
This ensures valuable content is captured, reviewed, and curated before becoming part of the firm's reusable standards.
Why Content Submission Matters
As projects evolve, teams frequently create or improve:
- Revit families
- Drafting views
- Details
- Sheets
- Other reusable content
Historically, identifying which content should be added to the library has been a manual process. Valuable content often remains inside project files because there is no formal mechanism for flagging it for review.
The Content Submission workflow addresses this by allowing users to identify reusable content at the moment it is created.
Benefits
- Capture valuable content before it is forgotten
- Reduce dependence on manual library audits
- Create a consistent QA/QC process
- Track who submitted content and where it originated
- Maintain library quality through controlled publishing
How to Submit and Review Content in AVAIL
Step 1: Submit Content from a Project
Users working in Revit can submit content directly from a project.
Examples include:
- A cleaned-up manufacturer family
- A newly developed detail
- An improved drafting view
- Any content that should become part of the firm's standards
When submission privileges are enabled, users can select content, right-click, and choose:
Submit Content to Library
AVAIL then harvests the content and sends it into a review queue.
Step 2: Content Enters the Submission Queue
Submitted content appears in a dedicated Submissions area within the AVAIL Desktop application.
The submission record includes:
- Submitter name
- Submission date
- Source project
- User notes
- Content metadata
For example, a submitter might include a note such as:
"Cleaned up manufacturer content before submission."
This provides important context for reviewers.
Step 3: Review and QA/QC
Designated Reviewers can evaluate each submission before it becomes part of the library.
Reviewers can:
- Open and inspect submitted content
- Verify standards compliance
- Make necessary revisions
- Determine whether the content should be published
The workflow is intentionally flexible so firms can apply their own QA/QC requirements and approval processes. AVAIL provides the tools; firms control the review standards.
Step 4: Approve or Decline
After review, Reviewers can choose to:
Publish
Publish the content directly to an AVAIL channel and add it to the standards library.
Decline
Reject the submission if it does not meet standards or is not appropriate for reuse.
This keeps the library curated and prevents low-quality or duplicate content from being added.
Best Practices
To get the most value from Content Submission:
- Allow project teams to submit content as they create it.
- Require submitters to include meaningful notes.
- Establish a regular review cadence (weekly or biweekly).
- Assign clear ownership for QA/QC reviews.
- Publish only vetted content that aligns with firm standards.
- Use submissions as the primary intake path for new library content.
Still have questions? Contact support@getavail.com to schedule a call and discuss this feature and workflow with our team.