Toggle Nav
 

Docuflow User Guide

User Guide

Last updated on Apr 24, 2026.

Docuflow is the publishing hub for Revit sheet packages. It helps you build reusable sheet sets, publish them to several output formats, and keep filenames and archive paths consistent across repeated issues.

Use it when a project team needs one controlled workflow for PDF, DWG, DWF, IFC, and optional drawing-list output from the same selection of Revit sheets.

Getting started

Overview

Docuflow opens from the Archi tab in the Publishing panel and reads the printable sheets in the current Revit document. The main workflow starts with building a publish set, choosing an output folder, and enabling the output formats required for the issue.

The current product line has separate branches for Revit 2015-2021, 2022-2024, and 2025+, so the installed build should always match the Revit version in use.

Requirements

  • A supported Revit version with Docuflow installed.
  • A saved Revit project file with printable sheets.
  • Write access to the main output folder and any archive folders used by your workflow.
  • Reports installed and licensed if you want to publish a drawing list together with the sheet package.
  • A PDF workflow that fits the workstation setup, either native Revit PDF export or a supported printer-driven path.

Install and uninstall

Deploying to multiple machines? This section covers standard local installation. For automated deployment by IT administrators or BIM managers, see the Silent Installer Guide.

Install

  1. Close Revit.
  2. Run the Docuflow installer with administrator rights.
  3. Complete the installer steps and any activation that applies to your license.
  4. Start Revit.
  5. Confirm that Docuflow is available on the Archi tab in the Publishing panel.

Uninstall

  1. Close all Revit sessions.
  2. Open the Windows uninstall entry for Docuflow, or run the installed uninstaller.
  3. Confirm removal.
  4. Open Revit again only after the uninstall is complete.

Uninstalling Docuflow removes the add-in registration, but it does not remove project-specific XML settings, archive folders, or previously published files.

Publishing workflow

Open Docuflow

  1. Save the Revit document before you start.
  2. Open Docuflow from Archi > Publishing.
  3. Let the main window load the printable sheets from the current document.
  4. Review the current output folder, enabled formats, and any saved set selections before publishing.
Docuflow main window

Build a sheet set

The Main tab is where you build the current issue package. Move the required sheets into the publish list, reorder them if sequence matters, and save the selection as a named Revit ViewSheetSet when you need to reuse it later.

  1. Review the available printable sheets.
  2. Add the sheets that belong in the issue set.
  3. Reorder them to match the package sequence.
  4. Save the result as a reusable set if this package will be issued again.

Publish to PDF

The PDF tab controls naming, merge behavior, cleanup options, and the selected PDF path. In newer Revit versions, native PDF export is available, but some environments still rely on printer-driven workflows.

  1. Choose the output folder on the Main tab.
  2. Enable PDF.
  3. Open the PDF tab and review the export settings.
  4. Choose whether to merge the issue into one file or keep separate files per sheet.
  5. Start the publish run.

If the workstation is configured for a printer-driven PDF path, printer availability and user permissions can affect the result.

Docuflow PDF tab

Publish multiple formats from one set

Docuflow can publish the same sheet set to several outputs in one run. PDF, DWG, DWF, and IFC each keep their own option surfaces, so review each format tab before issuing.

  1. Load or build the sheet set.
  2. Enable the formats needed for the issue.
  3. Open each relevant format tab and review the settings for that export type.
  4. Publish once all required formats are enabled.

Documents and export options

DWG, DWF, and IFC export

Use the dedicated format tabs when the same package must be delivered as coordination, review, or handoff files in addition to PDF. Each format has its own setup names and export rules, so treat each tab as a separate configuration surface even though the sheet selection is shared.

  • DWG: Use when downstream CAD delivery or consultant exchange is required.
  • DWF or DWFx: Use for review workflows that still depend on Autodesk review formats.
  • IFC: Use when the issue package includes a model handoff beside the sheets.

Drawing list export

Docuflow can publish a drawing list together with the sheet issue when the required Reports installation is present and licensed. This is controlled from the Documents tab and included in the main publish run.

  1. Open the Documents tab.
  2. Select the schedule that should be used for the drawing list.
  3. Choose the required output format, such as Excel or PDF.
  4. Return to the main workflow and enable drawing-list output before publishing.

If these controls are disabled, check the Reports installation and license state first.

Naming and settings

Advanced filename patterns

The Advanced tab is used to build reusable naming patterns from sheet, revision, project, and shared-parameter values. This is the part of Docuflow that keeps repeated issues aligned with office naming standards without manual renaming after export.

  • Use advanced patterns when filenames need revision, discipline, or project metadata.
  • Keep naming rules consistent across PDF, DWG, DWF, and IFC outputs.
  • Review background native PDF jobs carefully, because some background flows support a narrower naming feature set.
Docuflow advanced naming settings

Output and archive paths

Docuflow remembers the last output folder and can also keep archive folders for different export formats. In cloud and shared-folder workflows, project-specific settings can be resolved through a shared Docuflow path instead of being stored only beside the model.

  • Output folder: The main location for the current publish run.
  • Archive folders: Optional secondary destinations for PDF, DWG, or DWF outputs.
  • Shared Docuflow path: Used to keep project settings accessible in cloud or office-shared workflows.

Saved preferences

Docuflow stores output choices, folder paths, format toggles, and several publish preferences between sessions. Project-specific settings are written to Docuflow XML files resolved from the document or shared-folder context, while broader user behavior is stored in the application settings.

Troubleshooting and FAQ

Docuflow does not open

Cause: The current Revit document is unsaved, or Docuflow cannot initialize against the current file state.

Fix: Save the document first, then run Docuflow again.

Docuflow says there are no sheets to publish

Cause: The project does not contain printable sheets, or the available sheets are placeholders.

Fix: Create or enable printable sheets before reopening the workflow.

PDF export fails or stalls

Cause: The selected printer-driven PDF path is unavailable, blocked by workstation permissions, or unsuitable for the current setup.

Fix: Prefer native PDF export where supported, or correct printer access and PDF driver configuration when an older printer-driven path is required.

Drawing list export is disabled

Cause: Reports is missing, unlicensed, or below the required supported version.

Fix: Install or update Reports and confirm that the license is active.

Can I publish several formats from one sheet set?

Yes. That is one of Docuflow's main workflows. Build the sheet set once, enable the required formats, review the settings on each relevant tab, and publish.

Where are project-specific settings stored?

Docuflow stores project-specific XML settings in a Docuflow folder resolved from the document path or shared-folder context. User-scoped preferences are stored separately so the general workflow settings persist between sessions.