What Is an ITP Log and How to Create One

If you've ever been handed a 500-page spec and told to "build the ITP," you know the feeling. It's one of those things nobody teaches you in school — you learn it on your first project by staying late and reading specs until your eyes blur. The Inspection and Test Plan log is the backbone of any QC program, but honestly, most people learn to build one through years of trial and error. This guide covers what an ITP log actually is, why you need one, and how to put one together — whether you do it the old-fashioned way or use software to save yourself a few weekends.

What Does ITP Stand For?

ITP stands for Inspection and Test Plan. It's a document — usually a spreadsheet or database — that lists every inspection, test, and verification required on a construction project. Each line item ties a specific activity (like concrete placement or structural steel erection) to the test standard that governs it (like ASTM C39 for compressive strength of concrete cylinders), the frequency of testing, the acceptance criteria, and who's responsible for witnessing or performing the test.

A typical ITP log entry for a concrete pour might look like this:

Multiply that by every testable activity on the project — soils compaction, asphalt density, fireproofing thickness, structural welding, waterproofing adhesion, and hundreds more — and you start to see the scope of the document.

Why ITP Logs Matter

Regulatory Compliance

On most commercial and public projects, the contract requires a QC plan that includes an ITP. Building codes (IBC), agency standards (USACE, NAVFAC, state DOTs), and project specifications all mandate specific testing. If you miss a required test, you're out of compliance — and inspectors will notice.

Liability Protection

Your ITP log is your audit trail. When a structural issue surfaces three years after substantial completion, the ITP log proves you performed every required test and the results met spec. Without it, your company is exposed. Conversely, if a required test was never logged, that's a gap that attorneys will find.

Project Handoff and Closeout

At project closeout, the owner or construction manager will ask for your completed ITP log as part of the turnover package. A clean, complete log accelerates final payment. A messy or incomplete one delays it — sometimes by months.

The Traditional Manual Process

Here's what building an ITP log looks like without software:

You sit down with the specs, open up a fresh spreadsheet, and start reading. Every section. Every paragraph. You're scanning for the magic words — "testing shall be performed in accordance with," "submit test reports," "independent testing agency shall verify" — basically anything that references ASTM, ACI, AWS, or AASHTO standards.

For a mid-size commercial project with 40-60 spec sections, this takes 40 to 100 hours of focused reading. Larger projects — hospitals, data centers, federal facilities — can push past 150 hours. And that's just the specs. You also need to cross-reference the plans for notes, details, and callouts that add or modify testing requirements.

Most people do this in Excel. You set up your columns — division, section, activity, test standard, frequency, acceptance criteria, responsible party, status — and fill it in line by line as you grind through the specs. It's tedious, it's easy to miss things when you're tired, and the kicker is it all has to be done before anyone breaks ground.

How to Create an ITP Log: Step by Step

1. Gather your documents. Collect the full project specification (all divisions), the drawing set, any addenda, and the contract's general requirements. Pay special attention to Division 01 (General Requirements), which often contains the overarching QC and testing requirements that apply across all trades.
2. Set up your log structure. Create a spreadsheet with columns for: Spec Section, Description, Test Standard, Test Method, Frequency, Acceptance Criteria, Responsible Party (contractor, owner, third-party lab), Hold/Witness/Review point, and Status.
3. Read Division 01 first. Section 01 45 00 (Quality Control) or similar sections establish the project-wide testing framework. Note the general testing frequencies, lab requirements, and reporting procedures. These apply as defaults across all divisions unless a specific section overrides them.
4. Work through each technical division. Starting at Division 02 or 03, read each section and extract every testing requirement. Look for references to ASTM standards, required submittals, mock-up requirements, and field verification procedures. For Division 03 (Concrete), you might find ASTM C31 (making cylinders), C39 (compressive strength), C143 (slump), C138 (unit weight), and C1064 (temperature) — each with specific frequencies and criteria.
5. Cross-reference the plans. Structural drawings often have general notes specifying testing that isn't in the specs, or modifying spec requirements. Geotechnical reports may add soil testing requirements. Don't skip this step.
6. Verify against the code. Compare your extracted requirements against the applicable building code (IBC, local amendments) to make sure nothing is missing. The specs should be at least as stringent as the code, but gaps happen.
7. Get it reviewed. Have your project manager, superintendent, and — if possible — the owner's QC representative review the log before construction begins. Catching a missing test now costs nothing. Catching it during a final inspection costs real money.

How AI Tools Automate ITP Creation

Look — the manual process works. People have been building solid ITP logs by hand for decades, and plenty of great QC managers swear by their Excel templates. But it's slow, and the reality is there aren't enough experienced QC people to go around anymore.

That's the problem SpecFunnel was built to solve. Instead of reading specs page by page, you upload your project specifications as PDFs and SpecFunnel's AI reads every section, identifies testing requirements, extracts ASTM/ACI/AWS standards, and organizes them into a structured ITP log — organized by MasterFormat division, with test frequencies and acceptance criteria already populated.

What used to take 40-100 hours takes minutes. And because the AI reads every line of every section, it catches requirements that humans commonly miss — like a testing requirement buried in a submittal paragraph, or a frequency override in a general note.

The output isn't a black box — you can see exactly which spec section each requirement came from, so you can verify everything and make adjustments. Think of it as a really good first draft that saves you 90% of the grunt work. You still bring the judgment; the software just handles the reading.