GAD Editorial · Published · · English study · Chinese summary
A submittal register can look complete while obscuring where its entries came from. For an architect reviewing the process, an item explicitly required by a specification and an item suggested by a predictive system deserve different evidence trails. Both may be useful, but they answer different questions.
Autodesk's AutoSpecs help describes uploading a specification to generate a draft submittal log, then viewing entries in their specification context. It also supports named specification versions and comparison between them. Separately, Suggested Submittals uses Construction IQ technology and historical project information to identify possible omissions that a user can accept or ignore. Getting started · Suggested Submittals
These are documented product capabilities, not a hands-on GAD test. The help pages do not establish a publication day; an official feature video is dated 8 October 2024. This article examines an established workflow rather than announcing a new release. Dated feature material
Keep the source document beside each entry
Start with the agreed specification issue and record its revision, date and scope. Confirm that the team is permitted to process the document in the chosen service. Avoid combining superseded and current sections into an apparently authoritative input set.
For each extracted item, retain a retrievable section and paragraph reference. Review whether the entry captures the actual requirement, including any condition or exception. A heading containing a product name may not represent a separate submission, while a requirement embedded within a paragraph may be easy to miss.
Choose a small manual reference sample across several kinds of requirement, including product data, samples and closeout information where present. Check both missed requirements and entries that should not have been created. Counting only successful extractions gives a misleading impression of completeness.
Treat a suggestion as a question for review
Label predictive suggestions separately from entries supported by a cited clause. Ask why the proposed item belongs on this project and who is responsible for deciding. Historical patterns can suggest a useful question, but they should not silently add a requirement to the team's record.
If the suggestion exposes an ambiguity, route it through the project's agreed clarification process. Record the resulting decision and supporting document before changing the working register. Do not infer that accepting a software suggestion changes a contract or authorizes an additional service.
Reconcile the next issue before distributing changes
When a revised specification arrives, compare it against the version actually used for the previous register. Review additions, removals and changed conditions. A renamed entry may describe an existing obligation, while unchanged wording may sit within a newly relevant scope.
Keep the revision comparison and reviewer decision with each affected item. Confirm responsibility and sequencing through the normal project workflow before entries are assigned or circulated.
The useful deliverable is a reviewed register with source-backed requirements, separately resolved suggestions and a visible revision history. Evaluate the time spent correcting omissions and false positives alongside extraction time. The AI step earns its place when another reviewer can explain why each item is present and what evidence supports it.