ContextCleaner: see every entry in the Windows 11 right-click menu, and which app added it — on the Microsoft Store.

Last updated:

Guided workflow variation

A submittal register from the specs,with every page cited.

Pick the project manual PDF. Spec Register Builder reads each section, lists the requirements it finds with part, article, paragraph, and page, and lays them beside the rendered sheet so the whole team can trace any row back to the book.

Pick the spec book, review the rows beside each page, and export a register to Excel or CSV that cites every requirement back to its paragraph.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Full Spec Register Builder overview
One-time purchase No telemetry Local-first

windows · every row cites its page · spec book never written · nothing uploads

If this sounds like your week

Building the log by hand starts with reading every section.

A project manual for a mid-size building runs to hundreds of pages across dozens of sections. Each one buries its own requirements in Part 1, and many add more under Quality Assurance, Warranty, or Field Quality Control. The usual method is a person, a highlighter, and a spreadsheet: read, type the item, type the section and paragraph, and repeat through the last division.

Where tooling usually breaks

A missed item surfaces when the material is already ordered.

Typed logs drift. A transposed paragraph number, a mock-up requirement in an article nobody opened, a closeout warranty that never made the list: each one shows up months later as a held inspection, a returned delivery, or a closeout package that cannot be finished. And a log without page references sends every reviewer back to the binder whenever a question comes up.

Where Spec Register Builder lands

The book builds the register, and every row says where it came from.

Spec Register Builder reads the SECTION title line on each opening page, walks every part and article beneath it, and lists each paragraph that asks for something to be submitted. Each row records the section, part, article, paragraph, PDF page, printed page, type, and a confidence hint. Check it beside the rendered page, then save the register as XLSX or CSV.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Learn more about Spec Register Builder

windows · every row cites its page · spec book never written · nothing uploads

What you get

Feature highlights

Every row cites its page

each requirement carries its spec section and title, part, article, and paragraph, plus the PDF page and the printed page from the section footer, and the rendered page opens beside the table when you select it.

Sections read from the book

numbers and titles come from each SECTION title line, including six-digit, level-four, run-together, five-digit, and dual numbers, so the register follows the project’s own numbering.

Twelve submittal types

Preconstruction, Shop Drawings, Product Data, Samples, Design Data, Test Reports, Certificates, Manufacturer’s Instructions and Field Reports, O&M Data, Closeout, and Sustainability, with Action, Informational, Closeout, or UFGS G and Info.

Filter, sort, and review beside the page

narrow the table by any word or section number, sort by section, paragraph, page, type, or confidence, and check rows with a Review flag first.

Excel and CSV for the log

fourteen columns that line up with common submittal logs, with Submit By, Reviewer, and Notes left blank for your team, and requirement text written as text, never as a formula.

Source hash on record, nothing uploaded

the workbook’s Manifest sheet records the source file’s SHA-256, pages, rows, and export time, the spec book is never written, and the app makes no network connections.

Especially when

  • Build a submittal register from a construction spec book PDF instead of reading every section and typing each requirement into a spreadsheet
  • Cite every submittal requirement to its section, paragraph, and page so the team can check it against the specifications
  • Export the register to Excel or CSV with columns that line up with common submittal logs and a record of the source file
  • Keep the spec book on the PC and unchanged, with no upload, no account, and no network connection

Who benefits

Real-world scenarios

A general contractor at award

The contract is signed, the preconstruction meeting is two weeks out, and the project engineer has a long project manual PDF and an empty submittal log to fill before then.

She picks the PDF, sorts by Section, and works through the register beside the rendered pages, starting with any row that carries a Review flag. Export XLSX gives her the log with Submit By, Reviewer, and Notes columns ready to fill in for the meeting.

A mechanical subcontractor after buyout

The subcontract covers the Division 23 sections, and the subcontractor wants its own list of required submittals before the general contractor sends the master log.

The estimator sorts by Section to bring the Division 23 rows together, reads the Product Data and Shop Drawings rows beside their pages, then exports the register and keeps the Division 23 rows in Excel for the submittal schedule.

An owner’s representative checking a log

The owner’s representative receives the contractor’s proposed submittal log and wants a second list, built from the same specifications, to compare it with.

A register built from the same project manual gives a cited list of every requirement found. Rows that appear in one list and not the other point straight to the paragraphs worth a closer look, each with its page.

Deep dive

What a submittal register built from the specifications should give you

Every requirement, wherever it sits. Submittal requirements are not confined to the article titled Submittals. Spec sections also ask for samples and mock-ups under Quality Assurance, mix designs and test reports under Quality Control, and warranties and extra stock under Closeout. Spec Register Builder reads every article of every section, so those paragraphs land in the register alongside the ones under Action Submittals and Informational Submittals.

A citation on every row. A register is only as useful as its references. Each row carries the spec section and title, the part, the article, and the full paragraph path, such as 1.3.C.1, plus two page numbers: the PDF page, so you can jump to it, and the printed page read from the section footer, such as 03 30 00 - 3, so it matches the paper set.

Types and action codes. Each row is typed as one of twelve submittal types, from Preconstruction and Shop Drawings to Operation and Maintenance Data, Closeout, and Sustainability. The Action/Info column comes from the article the row sits in: Action, Informational, or Closeout, or G and Info on UFGS books.

A way to check before you send. The rendered page sits beside the table. Select a row and its page appears; Previous and Next step through the book. A confidence hint from 0 to 1 weighs how directly the paragraph asks for a submittal, where it sits, whether a type is named, and whether the sentence is complete, and rows at 0.40 or below carry a Review flag so you know where to look first.

A file the team can work in. Export XLSX writes a Register sheet with a frozen header and fourteen columns in the order a log uses, with Submit By, Reviewer, and Notes left blank for your team. Export CSV writes the same columns in UTF-8 with a byte-order mark, so Excel opens it with accents intact. Every row is exported, whatever the filter shows.

The source on record. The workbook adds a Manifest sheet with the source file name, its SHA-256, the page, section, and row counts, the pages read with OCR, the app version, and the export time, so anyone can tell exactly which book a register came from when an addendum arrives.

Try it on a book you know. The Microsoft Store runs a 15-day free trial with every feature. Build a register from a project manual you have already logged and compare the two.

How it is built

Built so every row leads back to the book.

Every row cites its page

Each requirement carries its section, part, article, paragraph, PDF page, and printed page, and the rendered page sits beside the table. Rows with a low confidence hint carry a Review flag.

The spec book is only read

The PDF is opened read-only through the Windows file picker and never written. Exports are new XLSX or CSV files, and the workbook records the source file’s SHA-256.

Nothing uploads

It runs in the Windows app sandbox with no declared capabilities, makes no network connections, and has no account and no telemetry. Scanned pages are read with the OCR built into Windows.

Head-to-head

How Spec Register Builder compares

Feature Spec Register Builder Spreadsheet by hand Online converter Subscription suite
Requirements found Every article of every section is read for submittal language Whatever the reader catches Page text or tables, not submittal rows Varies by platform and plan
Page cited on each row Yes: PDF page and printed page, plus part, article, and paragraph Typed by hand when someone remembers Not part of the output Varies by platform
Review against the book Rendered page beside the table, one click per row A binder or a second window A separate viewer Usually a linked document viewer
Where the spec book goes Stays on this PC. Nothing uploads. Stays on this PC Uploaded to the site Uploaded to the platform
Record of the source file Manifest sheet with the SHA-256 of the PDF, page and row counts, and export time Whatever someone types in Not usually Varies by platform
How it is paid for One-time purchase in the Microsoft Store Staff hours on every project Per use or per plan Often per user or per project, every year

FAQ

Straight answers—no glossary dump

What is a submittal register?

A submittal register, also called a submittal log, is the list of everything the contract documents ask the contractor to submit for review or for the record: shop drawings, product data, samples, test reports, certificates, warranties, and more. Each item is tied to its spec section and paragraph, then tracked with dates, reviewers, and status. Spec Register Builder builds the list part from the spec book and cites the page for each row.

Does it handle a full project manual?

Yes. It reads the whole book in one pass, section by section, from Division 01 to the last division in the file, and it was tested on a generated 2,000-page project manual with 200 sections. The status line counts what it found, such as 24 rows in 3 sections · 6 pages, and the Recent list keeps up to 20 books so you can reopen one later.

How do I check the rows before I send the register?

Select a row and its page renders beside the table, so the requirement text sits next to the paragraph it came from; Previous and Next step through the book. Sort by Conf. to bring rows with a low confidence hint to the top, where rows at 0.40 or below carry a Review flag. Filter rows narrows the table to a word, a submittal type, or a section number while you work.

What happens to the spec book PDF?

It stays exactly as it was. Spec Register Builder opens the PDF for reading only and never writes to it. Each export is a new XLSX or CSV file that you name in the Windows Save dialog, and the suggested name follows the book, such as Project Manual - submittal register.xlsx. Pick the same book again any time to rebuild the register from the untouched original.

Where does the work happen, and how do I get Spec Register Builder?

On your PC. Spec Register Builder makes no network connections, has no account, and collects no telemetry. It runs in the Windows app sandbox with no declared capabilities and reads only the PDF you pick. It is a one-time purchase in the Microsoft Store, and the Store runs a 15-day free trial with every feature, so you can build a register from your own project manual before you buy.

Related pages

Pull the submittals out of the spec book, paragraph by paragraph. A submittal log template that arrives already filled in. A submittal list in MasterFormat order, read straight from the book. SD-01 through SD-11, listed with every G item marked.

A spec book in.
A cited submittal register out.

Spec Register Builder reads every section of the project manual, lists each submittal requirement with its paragraph and page, and exports the register to Excel or CSV with the source file’s SHA-256. The PDF is never written, nothing uploads, and the Microsoft Store runs a 15-day free trial.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Open full product page

MasterFormat is a trademark of The Construction Specifications Institute, Inc. (CSI). Spec Register Builder is not affiliated with or endorsed by CSI.

Technical specifications

Technical specifications for procurement

Spec Implementation
Data Sovereignty Reads only the spec book PDF you pick in the Windows file picker, read-only, and never writes to it; writes only the XLSX or CSV you name in the Save dialog; the Recent list (up to 20 books) stays in the app’s own local storage on this PC
Telemetry Status None; no account, no telemetry, and the app makes no network connections
Core Runtime .NET 10 and WinUI 3 (Windows App SDK 2.5), packaged as MSIX; runs in an AppContainer with no declared capabilities; pages are rendered with the PDF engine built into Windows, and scanned pages are read with Windows OCR
Network Requirements Fully functional offline; no network capability is declared, and the app makes no network connections
Deployment Compatibility Windows 10 version 2004 or later and Windows 11, x64 and ARM64; one-time purchase in the Microsoft Store with a 15-day free trial
Input A construction spec book (project manual) PDF picked in the Windows file picker; password-protected PDFs open with their password; scanned pages read with the installed Windows OCR language; a bundled sample spec book
Sections SECTION title lines with six-digit (03 30 00), level-four (31 62 13.13), run-together (033000), five-digit (03300), and dual (03 30 00 (03300)) numbers; printed pages from CSI, UFGS, and Page n of m footers
Rows Part, article, and paragraph (such as 1.3.C.1 or 1.3 SD-03.2), PDF page, printed page, requirement text, twelve submittal types, Action/Info (Action, Informational, Closeout, or UFGS G and Info), and a 0 to 1 confidence hint
Review Register beside the rendered page; Filter rows; sort by section, paragraph, page, type, or confidence; Review flag at 0.40 or below; light, dark, and high-contrast themes
Exports XLSX with a Register sheet (14 columns, frozen header, text cells never written as formulas) and a Manifest sheet (source file, SHA-256, pages, OCR pages, sections, rows, app version, export time in UTC); CSV in UTF-8 with BOM, RFC 4180
Originals The spec book is opened read-only and never written; every export is a new file named in the Save dialog and holds every row