The spec book fills in your submittal log

Every spec section's PART 1 lists what you owe: "Product Data: for each type of product," "Samples: two 12×12 sections of each color," "Shop Drawings: indicate joint pattern." Until now you re-typed those into the submittal log by hand.

Seed from spec, on the project's Submittals page, reads the manual for you:

• Every lettered requirement from your declared sections' SUBMITTALS articles — the exact words, with its section, article, and page.
• Sorted into the log's own categories: product data, shop drawings, samples, test reports, warranties, O&M. Requirements the parser can't confidently categorize are listed too, just unchecked — procedural boilerplate never floods your log.
• Nothing enters the log unreviewed. You check what's real, confirm, and those become pending log items carrying the verbatim spec language and the page it came from.
• Re-running offers only what's new — items you already seeded stay put.

Same rule as everywhere else in STrOp's document intelligence: the manual is read deterministically, quoted verbatim, and a human confirms before anything becomes an obligation.