Submittal log generation

Submittal Log scans the project's specification sections and builds a working list of required submissions. Each item includes its number, specification reference, source, and type. Review this draft before adding the items to the project's Submittals list.

Start a log

1. Publish the specifications you want to use and check their precedence.
2. Open the project's Chat, type /, and choose Submittal Log.
3. Explain the scope and any packaging instructions. You can request the whole project or name particular divisions and sections.
4. Open the generated log from the conversation. Rows appear as sections finish; a full project can take several minutes.

For example: “Build the mechanical submittal log from Divisions 21–23. Keep product data and shop drawings separate. Follow the project's per-section numbering and include paragraph references.”

The agent uses the project's numbering settings and existing submittals as context. For defaults, see Submittal settings. If Submittal Log is missing from the picker, ask your administrator to confirm that the agent is available for the project.

Use an existing register

If Specset detects a submittal register in the specification package, the agent extracts it first, then checks the sections for additional requirements.

To supply a separate register, open the generated log and click Open chat. Attach the register in that conversation and ask the agent to use it as the starting point. Attachments in the project chat that launched the log are not passed into the log's own conversation.

Tell the agent which register to use and which details must stay, such as owner-assigned numbers or package names. Ask it to identify requirements found in the specifications that are missing from the register.

The Source column distinguishes Register entries from Specification entries. Existing submittals already saved in the project are a separate set of records; the generated log is a draft to review before creating more.

Review the draft

Search the table, open its source references, and check:

• Coverage: Required product data, shop drawings, samples, certificates, and closeout submissions are represented.
• Packaging and numbering: Related items are grouped as your team expects, with no duplicate packages or numbers.
• Specification and paragraph: Each requirement points to the appropriate section and supporting language.
• Type and description: The recipient can tell what needs to be submitted.

Edit the table's editable fields or return to the log's own chat for broader changes, such as splitting a package or removing an item. Check the completion summary for sections that could not be processed before treating the log as complete.

Export or create submittals

• Export: Download the working log as an Excel file. Select rows first to export a subset.
• Create: Add the selected rows to the project's Submittals list. With no rows selected, the action uses the full log. Review the count in the confirmation before proceeding.

After creation, assign responsible parties, set due dates, and manage responses through the submittal workflow. For connected projects, publishing to Procore or Autodesk Build follows the project's integration settings.

Return to the log through Chat → History or Artifacts. When new specifications arrive, identify the new scope and ask for additions rather than assuming a previous log has updated itself.