Skip to main content

How to Use Contents Formatting in Submittals

Learn how Contents Formatting works in Submittals and O&M packages — and when to use Order by Product vs. Order by Document.

Written by Ni Nguyen
Updated yesterday

Contents Formatting controls how documents are grouped and ordered in your Submittal or O&M package — choose the layout that best matches how your customer needs to navigate the final PDF.

1. Order by Product

Documents are grouped by product, following the order listed in your BOM.

  • Each product's associated documents (datasheets, warranties, installation guides) are grouped together in the PDF.

  • In the Table of Contents, sections are separated by document type, but page numbers reflect the product-based grouping.

  • If the same document is used across multiple products (e.g., a shared warranty), it will appear once per product.

2. Order by Document

Documents are grouped by document type — all datasheets together, all warranties together, and so on.

  • In the Table of Contents, sections are separated by document type and page numbers reflect the document-based grouping.

  • Document types are listed together regardless of which product they belong to.

  • Shared or repeating documents (e.g., the same warranty for multiple products) appear only once — with the associated products listed in the document header.

Tip: Use Order by Document when you want to reduce duplicate pages and streamline the package. Use Order by Product when each product needs its documents clearly grouped together for easy reference.

3. Key Differences at a Glance

Feature

Order by Product

Order by Document

Grouping Basis

Product

Document Type

Document Repetition

Repeated for each product

Appears once (if identical)

Product Association

Clear per grouped section

Listed in document header if shared

Table of Contents

Separated by document type

Separated by document type

Page Numbering

Reflects product grouping

Reflects document grouping

Need help? Visit the Parspec Training Academy or use the in-app support chat.

Did this answer your question?