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

SD-01 through SD-11,listed with every G item marked.

UFGS sections gather their submittals under SD headings, item by item, with a G after anything the Government must approve. Spec Register Builder turns each item into a row, types it from its SD number, and carries G or Info into the Action/Info column.

Each UFGS item under an SD heading becomes a typed row, with G marked for Government approval and its paragraph and page cited.

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

The SD list is long, and the G marks are easy to lose.

Under UFGS, each section names what must be submitted beneath numbered SD titles, from SD-01 Preconstruction to SD-11 Closeout, and every entry ends with a classification after a semicolon: G when the Government must approve it, blank when it is for information only. A full federal book holds hundreds of these entries, and each needs its SD number, its section, and its G status in the register.

Where tooling usually breaks

A dropped G turns an approval item into an information item.

When the entries are retyped, the semicolon and the G after it are the first things to go. Something that needed Government approval then goes in as information only, and the gap surfaces at a coordination meeting or a pay request. Entries that wrap mid-sentence, and reviewer office codes after the G, slow the retyping down further.

Where Spec Register Builder lands

Every SD item becomes a row, with its type and its G.

Spec Register Builder recognizes the SD-nn titles, rejoins entries that wrap mid-sentence, and numbers each one beneath its title, such as 1.3 SD-03.2. The type follows the SD number, so SD-02 entries are Shop Drawings and SD-07 entries are Certificates. Entries marked G show G under Action/Info, the rest show Info, and the PDF page is cited for each.

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 contractor on a federal project

A general contractor awarded a federal facilities project has the full UFGS spec book as one PDF and must propose a submittal register at the coordination meeting.

Picking the PDF lists every SD item in the book with its section, paragraph, and page. Export XLSX, sort the Action/Info column, and the G items needing Government approval sit together, ready for reviewer assignments and dates.

Items that wrap onto a second line

A long item, such as a concrete mix design description with admixtures, wraps onto a second line before its semicolon and its G classification.

The two lines join into one item, the G is read from the end, and the requirement text appears without the classification code, so the Requirement Text column reads the way the specification does.

Preconstruction items first

Before mobilization, the contracting officer expects the SD-01 preconstruction submittals, such as schedules and plans, from every section in the book.

Sorting by Type in the app brings the Preconstruction rows together across all sections, each cited to its paragraph and page, so the SD-01 package can be assembled from one list.

Deep dive

How UFGS SD headings, items, and G codes become register rows

SD headings. Unified Facilities Guide Specifications, the guide specifications used for military and federal facilities work, list submittals under numbered headings in each section’s Submittals paragraph. Spec Register Builder maps each heading to a submittal type: SD-01 Preconstruction, SD-02 Shop Drawings, SD-03 Product Data, SD-04 Samples, SD-05 Design Data, SD-06 Test Reports, SD-07 Certificates, SD-08 Manufacturer’s Instructions, SD-09 Manufacturer’s Field Reports, SD-10 Operation and Maintenance Data, and SD-11 Closeout.

One row per item. Every line under an SD heading is an item until the outline resumes. Each item becomes its own row and gets an ordinal under its heading, so the Paragraph column reads 1.3 SD-03.1, 1.3 SD-03.2, and so on. An item that wraps onto a second line is joined back into one before it is read.

The classification. A UFGS item ends with its classification after a semicolon, such as ; G or ; G, RO. Items whose classification starts with G show G in the Action/Info column, for Government approval; items without one show Info, for information only. The code is taken off the end of the text, so the Requirement Text column holds the item as the specification names it.

UFGS numbering and pages. Part headings without a dash, such as PART 1 GENERAL, and decimal paragraphs such as 1.3.1 and 1.3.1.1 are read alongside the SD lists. Printed pages come from UFGS footers such as SECTION 01 33 00 Page 2, and the PDF page is recorded as well.

A strong signal. An item under an SD heading is an explicit request by its format, so UFGS rows carry a high confidence hint. Paragraphs elsewhere in the section that ask for something to be submitted are listed too, typed by their wording.

Review and export. Select a row and its page renders beside the table. Sort by Section to walk the book in order, or by Type to group SD numbers across sections. Export XLSX or Export CSV writes the register with fourteen columns, including Type and Action/Info, and the workbook’s Manifest sheet records the source file’s SHA-256, so the register names the exact issue of the spec book it came from.

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.

FAQ

Straight answers—no glossary dump

What do the UFGS SD numbers mean?

They group submittals by kind: SD-01 Preconstruction, SD-02 Shop Drawings, SD-03 Product Data, SD-04 Samples, SD-05 Design Data, SD-06 Test Reports, SD-07 Certificates, SD-08 Manufacturer’s Instructions, SD-09 Manufacturer’s Field Reports, SD-10 Operation and Maintenance Data, and SD-11 Closeout Submittals. Spec Register Builder types each item from its SD number, so the Type column matches the heading it was listed under.

How does it mark items that need Government approval?

Each UFGS item ends with its classification after a semicolon. When the classification starts with G, such as ; G or ; G, RO, the row shows G in the Action/Info column; items without a classification show Info. The code is removed from the requirement text, so that column reads like the specification, and sorting Action/Info in Excel groups the approval items together.

Does it read UFGS paragraph numbering and page footers?

Yes. Part headings such as PART 1 GENERAL, decimal paragraphs such as 1.3.1, and SD headings such as SD-03 Product Data are all read, and each item gets a paragraph reference such as 1.3 SD-03.1. Printed pages come from footers such as SECTION 01 33 00 Page 2, and the PDF page is recorded on every row as well.

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

A submittal register from the specs, with every page cited. Pull the submittals out of the spec book, paragraph by paragraph. A submittal list in MasterFormat order, read straight from the book.

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