2026 Guide to CSI MasterFormat

MasterFormat is the CSI (Construction Specifications Institute) numbering system that organizes the Project Manual on a US construction project. The Project Manual is the bound set of specs that tells every trade what products to use, how to install them, and what quality standards apply. MasterFormat gives every spec requirement a fixed address, so the GC (general contractor), subs, and Owner are all pointing at the same page.

That numbering then carries into your Schedule of Values (SOV), Submittals, RFIs (Requests for Information), Change Orders, and closeout documents. The specs are the primary home. Everything else inherits its codes from there.

Division

A two-digit bucket grouping related work. Division 09 = Finishes. Division 23 = HVAC. There are 50 possible Divisions (00 and 01–49), though most projects use 15–25 of them.

Section

A six-digit code inside a Division identifying one specific work result. 09 29 00 = Gypsum Board. The first two digits are the Division; the middle pair narrows the group; the last pair pinpoints the product or assembly.

Project Manual

The specifications volume for a project. Its table of contents lists every Division and Section that applies to the job. If a Section isn't listed, that scope isn't specified.

Reading a real spec table of contents

Here's a trimmed table of contents from a typical $6M office fit-out Project Manual. Scan it and you'll spot Divisions vs Sections in seconds.

Division rows are the bold two-digit headings. Sections sit underneath, always six digits in three pairs. Your PM says "check Division 07," she means open that shelf. The architect's RFI response says "per Section 07 84 00," they mean one specific firestopping spec and nothing else.

Where MasterFormat shows up beyond the specs

The Project Manual is the source. Margin gets protected when those same codes flow into daily project controls.

• Schedule of Values (SOV): Each line item maps to one or more Sections. Billing disputes drop when retainage (the percentage of each payment the Owner holds back until Substantial Completion), stored materials, and percent-complete all tie to the same spec code the Owner's rep can check.
• Submittals: Tagging a product data sheet to Section 09 29 00 stops drywall data from being reviewed against the wrong requirement.
• RFIs: Pinning a question to a single Section forces the architect to answer against one spec clause, not "the drawings in general."
• Change Orders: A Section code ties the scope change back to the original spec and the SOV line you bill against. Good change order write-ups start with that traceability.
• Closeout: Warranties, O&M manuals, and as-builts are indexed by Section so the Owner can find them years later.

2004 vs 2016 edition: the only part you need to care about

MasterFormat expanded from 16 Divisions to 50 in 2004, then got refinements in 2016. The practical rule is simple: don't mix editions on one job.

How to spot which edition you're looking at in 60 seconds:

• Divisions stop at 16 and you see "Division 15 – Mechanical" and "Division 16 – Electrical" → you're holding a pre-2004 legacy spec.
• You see Divisions 21, 22, 23, 25, 26, 27, or 28 (fire suppression, plumbing, HVAC, integrated automation, electrical, communications, electronic safety) → it's the 2004 edition or later.
• Section numbers run to eight digits (e.g., 09 29 00.13) → that's the 2016 refinement layer.
• Still unsure? Check the cover page or front matter. CSI prints the edition year on the Project Manual's Division 00 (Procurement and Contracting Requirements) boilerplate.

4-step alignment fix before buyout:

1. Lock the Project Manual TOC as the single source. Print the table of contents. Circle every Division and Section. This is the master list of what's specified. Everything else aligns to it.
2. Update your cost code list. Map each cost code to the Divisions and Sections in that TOC. If the specs use 2004+ numbering but your template still has "15 – Mechanical," fix it now, not after your first pay app.
3. Mirror your folder structure. Set up document folders by Division and Section so Submittals, RFIs, and Change Orders land in the right place from day one.
4. Require a MasterFormat tag on every RFI, Submittal, and Change Order. No tag, no log entry. This one discipline keeps specs, costs, and documents connected through closeout.

Take a $2.4M interior fit-out with a 10-line SOV. Firestopping sits in Division 07, Section 07 84 00. If your buyout packages skip it because nobody scanned the spec table of contents past Division 09, it lands as a $25k unplanned sub add. The Owner says "it was in the documents." Matching your SOV lines and subcontract scopes to the Project Manual's Sections at the start catches that gap before it becomes a billing fight. In Archdesk, committed costs from POs and subcontract packages track against the same code structure used in the specs, so a gap between specified scope and bought scope surfaces during buyout rather than at the first application for payment.

You've got your Section list at the right depth. Now assign who carries each Section through every phase, from buyout through closeout. A Section code without a named owner at each handoff is just a filing label. It won't stop scope from falling through the cracks.

Picture our $2.4M, 3,200 sq ft medical office remodel at bid award, heading into buyout. The Project Manual is issued, drawings are permit set, and your first Submittals and RFIs are about to hit.

Step-by-step: build the map in one working session

1. Start with how you'll buy the job. Write your "money packages" first: Demo, Framing and Drywall, Ceilings, Flooring, Painting, Doors and Hardware, Casework, Mechanical, Electrical, Fire Alarm, Plumbing, Fire Protection, and GC General Conditions.
2. Tag at the 6-digit Section level. For a remodel this size, stay at Sections like 095100 Acoustical Ceilings and 265100 Interior Lighting. "Division 09" or "Division 26" is too coarse to be useful.
3. For each Section, write one spec anchor and one drawing anchor. A spec paragraph and a sheet or detail. You'll need both to prove scope fast when pricing a Change Order.
4. Assign four owners, not one. Buyout owner: who installs it. Change Order owner: who prices it. RFI owner: who writes and tracks the RFI. Closeout owner: who delivers O&M manuals, warranties, and as-builts.
5. Let one Section feed more than one package. Think of it like a relay. The baton is the Section code. Name who carries it at each handoff so nothing sits unclaimed between trades.

Filled template: a real slice of the remodel

The map's real value is exposing the hidden gaps, not the obvious scope. These six rows alone carry split ownership worth $315,100, or 13.1% of the contract. That's where "who owns the RFI" and "who prices the Change Order" matters more than "who installs." Skip naming the runner for each baton, and you'll rediscover that orphaned scope on the Punch List (the final deficiency walk before Substantial Completion). By then you're paying for it out of your fee.

Your ownership map exposed $315,100 of split-ownership scope across six rows. Now turn that map into the document the Owner actually pays from: the Schedule of Values. The SOV is the line-by-line breakdown of your contract price that the Owner (or their rep) uses to review and certify each monthly pay application. A good SOV lets an Owner walk the site once and confirm what you've earned. A bad one turns every pay app into a fight.

Same medical office job. Contract sum: $2,400,000, 3,200 sq ft, 16-week schedule under AIA terms. Your estimate has 120 internal cost codes, but the Owner will tolerate about 15 to 20 billing lines. The method below gives you a repeatable crosswalk from MasterFormat divisions (the industry-standard numbering system for specs) to rolled-up SOV lines you can reuse on every job.

The grouping rules: from 50 Divisions to 16 lines

MasterFormat has 50 numbered divisions. Most medical office fit-outs touch 18 to 22 of them. Three rules govern how you group them into billable lines.

1. One subcontract, one line. If a single sub covers Divisions 22, 23, and 25 (plumbing, HVAC, and integrated automation), keep them as separate SOV lines only if the Owner can verify them independently during a walk. If the sub's contract is a single lump sum and the scope overlaps physically, roll them together.
2. Walkable scope beats spec structure. The Owner can see a finished ceiling tile. They can't see the difference between Division 09 21 16 (gypsum board assemblies) and Division 09 29 00 (gypsum board accessories). Group divisions that produce a single visible result into one line.
3. Keep most lines between 3% and 18% of contract value. A line under 3% creates billing noise for pocket change. A line over 18% invites disputes because the percent-complete swing per pay app is too large. If a group lands outside that band, split or merge. Small specialty scopes like fire protection may fall below 3% when the trade simply doesn't carry enough contract value to hit the threshold, and that's fine as long as the Owner can still verify the line in a single walk.

Think of it like a grocery receipt. You don't list every tomato and onion. You list "Produce: $14.20." But you don't lump produce and cleaning supplies together, because the cashier can't verify them in the same aisle. Each SOV line is one aisle the Owner can walk and confirm.

Run every division through these rules in order:

The crosswalk: MasterFormat divisions to 16 SOV lines

Here are all 16 lines for the $2.4M job, with every touched MasterFormat division mapped to its billing home.

Putting it to work on your next job

Copy these three grouping rules onto a one-page template. Before pay app #1, list every MasterFormat division your spec touches. Assign each one to an SOV line using the decision tree above: does it share a subcontract? Can the Owner verify it on a walk? Does the value land inside the 3%–18% band? The whole exercise takes about 90 minutes on a $2M–$5M fit-out.

Two approved Change Orders on this job added $34,430. The SOV stayed at 16 lines. $27,450 went into line 14 (Plumbing) and $6,980 into line 16 (Electrical), so the Owner certifies the added work by looking at fixtures, tests, and functional rooms. No new line items. No billing bloat.

Retainage (the percentage the Owner holds back from each pay app until the work is fully complete) stays predictable. At 10% retainage, that $34,430 holds back $3,443, so the COs bill $30,987 of cash even though $34,430 of work is done. Every line carries 10% retainage until its release trigger fires. In Archdesk, each SOV line maps to its subcontractor valuations and PO commitments underneath, so the 120 internal cost codes roll up automatically. Your project team sees a cost overrun inside Plumbing at the cost-code level. The Owner's pay app shows one clean line with a percent-complete number tied to tested zones.

Catching the curb mismatch and the missing controls scope is a one-time save. The harder problem is making sure every RFI, Submittal, and Change Order that follows lands in the right MasterFormat bucket the first time, without you personally cross-checking every line. That takes governance: three deliverables before any buyout package leaves your office. A coded project structure, a named ownership map, and a weekly QA routine with teeth.

Definitions (60 seconds)

Three terms will come up every Tuesday morning. Learn them now so the QA meeting runs clean.

• Orphan: Any cost line, RFI, Submittal, or Change Order that has no MasterFormat tag at all. It sits in your system with no home, so it can't roll up to a budget line or an SOV line. Orphans hide cost and delay billing.
• Dual-coded: One item legitimately tied to two MasterFormat Sections because of a physical interface. The RTU curb from the previous exercise is a good example: it touches both roofing (07 50 00) and mechanical (23 81 00). Dual coding is real, but rare. Most items belong to one Section only.
• 99 99 99 Misc: A temporary holding code with a strict 7-day time limit. It is not a real budget bucket. It exists so the team can log something immediately when they genuinely don't know the right Section. If Misc entries aren't re-coded within a week, they rot into orphans with a label.

Target: fewer than 2% of your total lines should be dual-coded. Misc should trend to zero after week 4. If either number is climbing, the team needs coaching on the code list, not more Misc capacity.

Step 1: Build the coded project structure

Start with the template below. This medical office remodel uses 6-digit MasterFormat Sections as the primary code, with internal cost-code suffixes for labor, material, and subcontract splits. Every cost code rolls up to one Owner-facing SOV line. No orphans.

The pattern: one MasterFormat Section, one or more cost-code suffixes (L/M/S), one SOV line. Your job may have 80 to 140 cost codes rolling into 12 to 20 SOV lines. The RTU curb that crossed roofing and mechanical gets dual-coded only: 07 50 00-S and 23 81 00-M. Dual coding is the exception, not the default.

Step 2: Assign the ownership map

Every MasterFormat Section gets one named person responsible for RFIs, Submittals, and Change Orders in that scope. Shared-scope items get a lead owner and a secondary reviewer.

Post this map in the project trailer and attach it to every subcontractor kick-off package. If a sub sends an RFI without a MasterFormat tag, typically return it for correction and point them to the map, unless the contract or RFI procedure requires you to log it first. Setting this standard firmly in the first week carries through the next 16 weeks.

Step 3: Run the 30-minute weekly QA routine

Every Tuesday morning, the Lead PE pulls the exception list and resolves every item live. Here is the routine, step by step.

1. Pull orphans (5 min). Filter all PO lines, pay app lines, and RFIs entered in the last 7 days that have no MasterFormat tag or sit in 99 99 99. On a $2.4M remodel, expect 3 to 8 orphans per week in the first month.
2. Pull dual-coded items (3 min). Flag anything coded to two or more Sections. Confirm each one is genuinely cross-scope, like the RTU curb (07 50 00 + 23 81 00). If it isn't, strip the second code.
3. Review the exception list and decide (15 min). For each orphan or coding question, make one of three decisions on the spot. No item leaves the meeting undecided.

4. Clear the Misc bucket (5 min). Any item older than 7 days in 99 99 99 gets re-coded or escalated to the PM. Track who created each Misc entry. If one person generates more than two per week, they need a 10-minute coaching session on the code list, not a reprimand.
5. Update the master list (2 min). If the QA review created a new Section (like 22 66 00 for med gas, which wasn't in the original structure), add it to the master list, assign an owner, and map it to a SOV line. Notify the full team by end of day.

What to learn next

• Change Order workflow and backup, because coded scope is only useful if your pricing and narrative tie back to the exact Section fast enough to get approval.
• Retainage release triggers by SOV line, because clean coding stops "work complete, cash stuck" at Substantial Completion and closeout.
• Closeout indexing by Division, because O&M manuals, warranties, training records, and as-builts filed to the same codes cut the punch list tail and stop rework during Owner inspections.

This routine is the job's chart of accounts. If the team can't code it, you can't prove it, price it, or bill it. In Archdesk, the master code list drives budgets, POs, and subcontractor pay apps in one structure, so when that med gas PO gets re-coded from 99 99 99 to 22 66 00 during Tuesday's QA, the CVR view updates committed cost against forecast on the same screen, and the $6,000 coding gap shows up that week instead of surfacing as a billing misalignment at the month-end SOV reconciliation.