Tygart Media

Category: Agency Playbook

How we build, scale, and run a digital marketing agency. Behind the scenes, systems, processes.

  • Introducing the Restoration Carbon Protocol: An Industry Self-Standard for Scope 3 Reporting

    There is no industry standard for how a restoration contractor should calculate, document, and report the carbon emissions from their work. Not from IICRC. Not from RIA. Not from any trade association or certifying body in the restoration industry.

    That absence is becoming a problem. Commercial property managers are facing mandatory Scope 3 emissions disclosures — and restoration contractor activity is squarely in their value chain. Insurance carriers are building ESG criteria into preferred vendor programs. FEMA and federal contracting bodies are increasingly asking about emissions documentation for large-scale disaster response contracts.

    When your clients need Scope 3 data from you and there’s no standard for what that data should include or how it should be calculated, everyone loses. The property manager files an inaccurate disclosure. The contractor gets treated as a data gap. The auditor flags the methodology. Nobody benefits.

    The Restoration Carbon Protocol exists to fix that.

    What the Restoration Carbon Protocol Is

    The Restoration Carbon Protocol (RCP) is an industry self-standard for Scope 3 emissions calculation, documentation, and reporting specific to property restoration work. It is built on the GHG Protocol Corporate Value Chain Standard — the globally accepted framework for Scope 3 accounting — and adapted to the specific job types, material categories, waste streams, and operational patterns of the restoration industry.

    RCP v1.0 will cover five core restoration job types: water damage mitigation, fire and smoke restoration, mold remediation, asbestos and hazmat abatement, and biohazard cleanup. For each job type, the protocol defines:

    • Which GHG Protocol Scope 3 categories are relevant
    • What data points need to be captured per job
    • What calculation methodology to use for each emissions source
    • What emission factors apply, sourced from EPA, DEFRA, and ecoinvent databases
    • What the output format looks like for client delivery

    The output is a per-job carbon report — a standardized one-page document any restoration contractor can complete and provide to their commercial clients for their GRESB, CDP, or SB 253 disclosure.

    Why a Self-Standard and Not a Trade Association Standard

    Trade association standards take years to develop through committee processes. The 2027 deadline doesn’t allow for that timeline. Commercial property managers need something workable now — in 2025 and 2026, as they build their data collection infrastructure ahead of the first required filings.

    A published, rigorous, publicly available self-standard that is built on GHG Protocol methodology and uses credible emission factors is more useful to the market right now than a committee process that might produce something better in 2028. The goal of RCP is not to be the final word — it’s to be the first rigorous word, and to create the foundation that a trade association standard can build on when the bandwidth exists.

    Self-published standards have established category leadership in other industries. The GHG Protocol itself started as a self-published standard by the World Resources Institute and the World Business Council for Sustainable Development before becoming the global norm. The precedent for rigorous self-published standards setting the terms of an industry conversation is well-established.

    The 30-Day Build

    RCP v1.0 is being built over 30 days through a structured series of knowledge nodes — each one establishing a piece of the technical framework, validated against GHG Protocol methodology, and published here on Tygart Media as it’s completed.

    The publication sequence runs from foundation (what Scope 3 is and why it matters for restoration) through technical framework (job-type-specific calculation methodologies) to commercial application (how to use the framework with clients and in RFP responses) to the full framework document publication.

    The Restoration Golf League network of independent restoration contractors will serve as the pilot cohort — providing feedback on the calculation methodology, testing the per-job carbon report format against their actual job data, and validating that the framework is workable for contractors who are running businesses, not sustainability departments.

    How to Get Involved

    If you are a restoration contractor who wants to be involved in the RCP pilot, a commercial property manager looking for Scope 3 data from your restoration vendor network, an ESG consultant working with commercial real estate clients, or an insurance carrier building ESG criteria into your preferred vendor program — this standard is being built with your needs in mind.

    The RCP framework will be published open-access. The knowledge nodes building toward it are published here as they’re completed. Follow along, contribute feedback, and contact Tygart Media if you want to be part of the pilot cohort that validates the framework before v1.0 publication.

    What is the Restoration Carbon Protocol?

    An industry self-standard for calculating, documenting, and reporting Scope 3 emissions from property restoration work. Built on GHG Protocol methodology, covering five core restoration job types, producing a standardized per-job carbon report that contractors can provide to commercial clients for their ESG disclosures.

    Who is building the Restoration Carbon Protocol?

    Tygart Media, in collaboration with the Restoration Golf League contractor network. The framework is being developed through a 30-day structured publication process with input from restoration contractors, commercial property managers, and ESG practitioners.

    Why isn’t a trade association building this standard?

    Trade association standards take years through committee processes. The 2027 deadline requires something workable now. A rigorous self-published standard built on GHG Protocol methodology creates the foundation that a formal trade association process can build on.

    Will the RCP be free to use?

    Yes. The framework will be published open-access. The goal is adoption, not monetization of the standard itself. Value accrues to contractors who adopt it early and build it into their commercial service offering.

  • The 2027 Deadline: What California SB 253 Means for Your Restoration Business

    California Senate Bill 253 — the Climate Corporate Data Accountability Act — is the most significant climate disclosure law in US history. It applies to public and private companies with over $1 billion in annual revenue that do business in California. It requires them to disclose Scope 1 and 2 emissions starting in 2026 and Scope 3 emissions starting in 2027. More than 5,000 companies fall within its scope.

    Those companies include most of the institutional property owners, REITs, hospital systems, hotel chains, university systems, and commercial real estate operators that hire restoration contractors for their facilities. When they disclose their Scope 3 emissions in 2027, your work will be part of what they’re accounting for.

    What SB 253 Actually Requires

    SB 253 requires covered companies to publish annual GHG emissions reports, verified by an independent third party, using the GHG Protocol Corporate Standard methodology. The Scope 3 reporting requirement — which takes effect for the 2027 reporting year — means companies must inventory and disclose emissions across all relevant value chain categories, including emissions from their contractors and suppliers.

    The California Air Resources Board (CARB) is developing implementing regulations that will specify the exact requirements. What’s already clear from the statute is that companies cannot simply exclude contractor emissions because data is hard to collect — they must make good-faith efforts to obtain primary data from their supply chain, and where primary data isn’t available, they must use approved estimation methodologies.

    The third-party verification requirement is significant. Unlike voluntary ESG reporting where companies self-certify their numbers, SB 253 disclosures will be reviewed by independent auditors. That means the quality of the underlying data — including contractor-provided emissions data — will be scrutinized in a way it hasn’t been before.

    The Timeline That Matters for Contractors

    The 2027 reporting year means companies will begin collecting 2027 emissions data in early 2027 and filing reports by the deadline established in CARB regulations. To provide verified, primary-data emissions figures from their restoration contractors, property managers need to have data collection processes in place before the jobs happen — not after.

    That means the real action window for restoration contractors is now. Property managers who are serious about their SB 253 compliance are already building vendor data collection systems and ESG questionnaires. Contractors who can respond to those questionnaires with actual per-job emissions data will be in a materially different position than contractors who can’t.

    The companies that are largest in terms of SB 253 coverage — large REITs, national property management companies, institutional operators — are the ones most likely to make ESG data capability a formal criterion in vendor selection. They’re also the clients where losing a preferred vendor designation costs the most.

    What SB 253 Means Beyond California

    California’s disclosure laws have historically set national standards. SB 253 applies to companies “doing business in California” — which includes companies headquartered elsewhere that have California operations or customers. Many of the large commercial real estate operators that SB 253 covers operate nationally, which means their vendor data requirements will apply nationally even if the law itself is California-specific.

    The EU’s Corporate Sustainability Reporting Directive (CSRD) is already in effect and is pulling US companies with European operations into Scope 3 reporting as well. The direction of travel is global and accelerating regardless of what happens with US federal climate policy.

    For restoration contractors that do any commercial work with institutional property owners, the 2027 deadline should be on their planning horizon now — not in 2026 when their largest clients are scrambling to collect data before the filing deadline.

    What is California SB 253?

    The Climate Corporate Data Accountability Act, signed in 2023. It requires companies with over $1 billion in annual revenue doing business in California to report Scope 1 and 2 emissions starting 2026 and Scope 3 emissions starting 2027, verified by an independent third party using the GHG Protocol methodology.

    How many companies does SB 253 affect?

    More than 5,000 companies. Critically, the law applies to companies “doing business in California” regardless of where they are headquartered — capturing national and multinational companies with California operations or customers.

    Does SB 253 directly require restoration contractors to report emissions?

    Not directly — the law applies to companies with over $1 billion in revenue. But those companies must collect Scope 3 emissions data from their supply chain, which includes restoration contractors. The obligation on the contractor is indirect but practically significant for commercial work.

    What happens if a restoration contractor can’t provide emissions data to their commercial clients?

    The property manager will use spend-based estimates instead, which are less accurate and more difficult to defend in a third-party audit. Over time, inability to provide primary emissions data is likely to become a disadvantage in commercial vendor selection processes.

  • The GHG Protocol’s 15 Scope 3 Categories: Which Ones Apply to Restoration Work

    The GHG Protocol Corporate Value Chain Standard — the framework that governs Scope 3 emissions accounting globally — defines 15 categories of indirect emissions across the upstream and downstream value chain. Understanding which of these categories apply to restoration work is the first step in building a calculation methodology that ESG auditors will accept.

    Restoration work is unusual in that it touches multiple categories simultaneously. A single significant job can generate measurable emissions across four or more categories — which is exactly why restoration needs its own calculation framework rather than a generic contractor template.

    The Four Primary Categories for Restoration Work

    Category 1 — Purchased Goods and Services

    This category covers the emissions associated with producing the goods and services a company purchases. For a commercial property manager hiring a restoration contractor, this means the emissions embedded in everything the contractor uses on the job: antimicrobial treatments, drying agents, HEPA filters, packaging materials, replacement drywall, subflooring materials.

    In practice, Category 1 is the hardest to calculate precisely because it requires knowing the embodied carbon of specific materials. The Restoration Carbon Protocol approach uses established emission factor databases (EPA, ecoinvent) to assign representative values to the most common restoration material categories, allowing contractors to calculate Category 1 contributions from their materials list without commissioning a lifecycle assessment.

    Category 4 — Upstream Transportation and Distribution

    This category covers transportation emissions upstream of the reporting company — meaning the emissions from moving goods and equipment to the job site. For restoration contractors, this primarily means vehicle fleet emissions: the fuel burned driving trucks, vans, and equipment trailers to the loss site and back.

    Category 4 is typically the easiest restoration emissions category to calculate. Vehicle emissions can be calculated from fuel consumption records or from mileage multiplied by vehicle-type emission factors. Most fleet management systems already capture this data.

    Category 5 — Waste Generated in Operations

    This category covers emissions from waste generated during the contractor’s service delivery — the debris, damaged materials, contaminated water, and hazardous materials that restoration work produces and that are disposed of on behalf of the property owner.

    Category 5 is highly variable by job type. A Category 3 water loss with sewage contamination generates different waste streams than a Category 1 clean water extraction. A fire loss generates smoke-contaminated debris with different disposal requirements than mold remediation waste. The Restoration Carbon Protocol maps waste types by job category to appropriate disposal emission factors from EPA and industry waste management data.

    Category 12 — End-of-Life Treatment of Sold Products

    This category applies when restoration work involves removing and disposing of building components — flooring, drywall, insulation, ceiling tiles, cabinetry — that are treated as end-of-life materials. The emissions from disposing of these materials are counted here rather than in Category 5 when the materials originated as “sold products” rather than process waste.

    For large reconstruction-phase restoration projects, Category 12 can be a significant emissions source. The distinction between Category 5 and Category 12 matters for accurate reporting; the Restoration Carbon Protocol provides decision criteria for classifying demolition debris correctly.

    Two Secondary Categories That Apply in Specific Situations

    Category 2 — Capital Goods

    Relevant when restoration work involves the purchase and installation of new equipment on behalf of the property — replacement HVAC components, new water heaters, emergency generators. The embodied carbon of newly installed capital equipment counts under this category for the property manager’s disclosure.

    Category 13 — Downstream Leased Assets

    Relevant for property management companies that own the buildings being restored. When restoration work affects leased spaces and the property manager is accounting for emissions from tenant operations, the restoration work’s contribution to improving (or temporarily worsening) building energy performance can affect Category 13 calculations.

    The Practical Implication for Contractors

    The four primary categories — 1, 4, 5, and 12 — are present in virtually every significant restoration job. A contractor who can calculate and report emissions in these four categories for each job has 85 to 90 percent of what most commercial property managers need for their Scope 3 disclosure.

    The Restoration Carbon Protocol v1.0 focuses exclusively on these four categories, with secondary categories addressed in supplemental guidance. The goal is a framework that produces defensible, auditor-acceptable numbers from data that restoration contractors already capture in their job management systems.

    How many GHG Protocol Scope 3 categories apply to restoration work?

    At minimum four primary categories on most significant jobs: Category 1 (purchased goods and services), Category 4 (upstream transportation), Category 5 (waste generated in operations), and Category 12 (end-of-life treatment of materials). Two additional categories apply in specific situations.

    Which Scope 3 category covers the emissions from driving to job sites?

    Category 4 — Upstream Transportation and Distribution. Vehicle emissions from driving to and from job sites are typically the easiest restoration emissions to calculate and are often the largest single category for smaller jobs.

    How are waste disposal emissions classified?

    Process waste from restoration operations falls under Category 5 (Waste Generated in Operations). Building materials removed and disposed of during reconstruction may fall under Category 12 (End-of-Life Treatment of Sold Products). The Restoration Carbon Protocol provides decision criteria for classifying demolition debris correctly.

    What is the Restoration Carbon Protocol’s approach to Category 1 materials emissions?

    Rather than requiring lifecycle assessments, the RCP uses established emission factor databases (EPA EEIO, ecoinvent) to assign representative carbon intensities to common restoration material categories, allowing calculation from a standard materials list.

  • How Commercial Property Managers Are Counting Your Emissions (Whether You Know It or Not)

    When a commercial property manager reports their Scope 3 emissions to GRESB, CDP, or their California SB 253 auditor, they need to account for the emissions from every significant supplier and contractor in their value chain. That includes their restoration contractors.

    The problem: most restoration contractors don’t track or report their emissions. So property managers are using a fallback method that produces high-uncertainty estimates — and that method systematically misrepresents what restoration work actually emits.

    The Spend-Based Estimation Method

    When primary data — actual measured emissions from a specific supplier — isn’t available, the GHG Protocol allows companies to use a spend-based estimation method. The formula is simple: multiply what you paid a supplier by an industry-average emissions intensity factor (measured in kilograms of CO2 equivalent per dollar spent in that industry), and that becomes your estimate of that supplier’s contribution to your Scope 3.

    For example: a property manager paid a restoration contractor $85,000 for a water damage remediation. Using the EPA’s industry-average emissions factor for “services to buildings and dwellings,” they estimate the Scope 3 emissions from that engagement as approximately 8.5 metric tons of CO2 equivalent.

    That number may be wildly inaccurate. It might be double the actual emissions. It might be half. The spend-based method doesn’t account for job type, geographic location, crew size, equipment used, materials consumed, or waste generated. It treats a $85,000 carpet cleaning the same as an $85,000 Category 3 sewage backup remediation with hazmat disposal — because both cost $85,000.

    Why Property Managers Are Stuck With This Method

    The GHG Protocol is explicit that primary data — actual emissions data provided by the supplier — is preferred over spend-based estimates. Primary data produces more accurate disclosures, reduces auditor scrutiny, and demonstrates genuine supply chain engagement to investors and regulators.

    But primary data requires the contractor to track and report their emissions per job. Almost no restoration contractors do this. So property managers default to spend-based estimates not because they prefer them, but because they have no alternative.

    This creates a specific problem for restoration contractors who want to compete for commercial work: the property manager’s ESG team sees your company as an uncontrolled data gap in their Scope 3 inventory. That’s not a comfortable position to occupy when they’re selecting preferred vendors for their next contract cycle.

    What Happens When You Provide Primary Data

    When a restoration contractor provides actual emissions data per job — even a simple calculation using documented emission factors for their equipment, vehicles, and materials — several things change for the property manager:

    Their Scope 3 disclosure becomes more accurate and more defensible to auditors. Their ESG report can distinguish between a high-emissions fire restoration project and a low-emissions water extraction job, rather than treating them identically based on invoice amount. They can demonstrate to investors and regulators that they have active supply chain engagement on emissions — one of the specific data quality improvements that frameworks like GRESB reward.

    From the contractor’s perspective, providing primary data changes the relationship. You’re no longer a vendor they’re estimating around — you’re a supply chain partner who is actively contributing to the accuracy of their ESG disclosure. That’s a different conversation in a contract renewal discussion.

    The Standard That Doesn’t Exist Yet

    The missing piece is a standardized methodology for calculating restoration-specific emissions per job — one that is rigorous enough for ESG auditors to accept, simple enough for restoration contractors to actually use, and consistent enough that a property manager with multiple restoration vendors can aggregate data from all of them in a compatible format.

    The Restoration Carbon Protocol is being built to be that standard. The goal is a per-job carbon report that any restoration contractor can complete using data they already capture in their job management systems — and that any commercial property manager can plug directly into their GRESB or CDP disclosure without additional processing.

    How do commercial property managers currently estimate restoration contractor emissions?

    Most use a spend-based estimation method — multiplying contractor invoices by industry-average emissions intensity factors from sources like the EPA or EXIOBASE. This produces high-uncertainty estimates that don’t account for job type, equipment, materials, or waste streams specific to restoration work.

    Is spend-based estimation accurate for restoration work?

    No. It treats all restoration spending as equivalent regardless of job type, scope, or actual emissions profile. A $50,000 water extraction and a $50,000 fire debris removal generate very different emissions, but spend-based estimation produces the same number for both.

    Why can’t property managers just ask their restoration contractors for emissions data?

    Most restoration contractors don’t track per-job emissions data and there is no industry standard for what that data should include or how it should be calculated. The Restoration Carbon Protocol is being developed to create that standard.

    What is primary data in Scope 3 reporting?

    Primary data is actual emissions data provided by a supplier, based on measured or calculated emissions from their specific activities. The GHG Protocol prefers primary data over spend-based estimates because it produces more accurate disclosures and is more defensible in audits.

  • What Is Scope 3 and Why Restoration Contractors Need to Care

    If you run a restoration company and nobody has mentioned Scope 3 emissions to you yet, that’s about to change. Commercial property managers, REITs, hospital systems, and institutional facility directors are all facing mandatory ESG reporting deadlines — and the emissions from the contractors they hire count toward their numbers.

    Your restoration work is in their Scope 3. Whether you know it or not, whether you track it or not, your clients are being asked to account for it.

    The Three Scopes of Greenhouse Gas Emissions

    The Greenhouse Gas Protocol — the internationally accepted standard for carbon accounting — divides emissions into three categories based on where they originate in relation to the reporting organization.

    Scope 1 covers direct emissions from sources the company owns or controls. A property management company’s Scope 1 would include fuel burned in company-owned boilers, generators, and vehicles.

    Scope 2 covers indirect emissions from purchased energy — electricity, steam, heat, and cooling consumed by the organization’s buildings and operations.

    Scope 3 covers everything else: all the indirect emissions that occur in the organization’s value chain, both upstream and downstream. For a commercial real estate company, Scope 3 includes the emissions from construction and renovation work, from tenant operations in leased space, from the materials used in building maintenance — and from the restoration contractors called in when water, fire, or mold damage occurs.

    Scope 3 is where the numbers get large. For commercial real estate, Scope 3 emissions typically account for 85 to 95 percent of total reported emissions. It’s also where the data is hardest to collect — because it requires getting information from dozens or hundreds of vendors, suppliers, and contractors who may not track their own emissions at all.

    Where Restoration Contractors Appear in Scope 3

    The GHG Protocol defines 15 categories of Scope 3 emissions. Restoration work touches several of them simultaneously:

    • Category 1 — Purchased goods and services: The materials your crews use on a job — drying equipment consumables, remediation chemicals, replacement materials — generate upstream emissions that get counted in your client’s Category 1.
    • Category 4 — Upstream transportation and distribution: The emissions from driving your trucks to the job site, hauling equipment, and transporting waste to disposal facilities.
    • Category 5 — Waste generated in operations: The debris, contaminated materials, and hazardous waste generated during restoration work that gets disposed of on behalf of the property owner.
    • Category 12 — End-of-life treatment of sold products: Applies when restoration involves removing and disposing of building materials — flooring, drywall, insulation — on behalf of the property.

    A single significant water loss job touches all four of these categories. A large fire restoration project may touch additional categories depending on the scope of reconstruction work involved.

    Why This Is a 2027 Problem for Your Business

    California Senate Bill 253 — the Climate Corporate Data Accountability Act — requires companies with more than $1 billion in annual revenue doing business in California to report Scope 1 and 2 emissions starting in 2026 and Scope 3 emissions starting in 2027. More than 5,000 companies are within scope of this law.

    The EU Corporate Sustainability Reporting Directive (CSRD) is already in effect, with Scope 3 reporting requirements phasing in through 2027 for large European companies — many of which own commercial real estate and operate facilities in the United States.

    What this means practically: the commercial property managers, REITs, hospital systems, and institutional facility directors who hire restoration contractors are right now trying to figure out how to collect Scope 3 emissions data from their vendor base. They need that data to file required disclosures. If you can provide it — in a structured, consistent, usable format — you become a preferred vendor. If you can’t provide it, you become a data gap they need to work around.

    The Gap the Restoration Industry Has Not Addressed

    No major restoration trade association — not IICRC, not RIA, not RCAT — has published a Scope 3 reporting standard for restoration contractors. There is no industry-agreed methodology for calculating the emissions contribution of a water damage job, a fire restoration project, or a mold remediation. There is no standard job carbon report format that a contractor can provide to a property manager for their ESG disclosure.

    This is the void the Restoration Carbon Protocol is designed to fill. In the absence of an industry standard, each commercial property manager is either making up their own methodology, using generic spend-based estimates with high uncertainty, or simply leaving restoration contractor emissions out of their disclosure and hoping their auditors accept it.

    None of those options serve the property manager. None of them serve the contractor. And none of them serve the goal of accurate climate disclosure.

    The restoration industry has an opportunity to lead here — to define the standard before regulators or clients define it for them, and to make that standard one that is actually workable for contractors who are focused on doing restoration work, not filing emissions reports.

    What are Scope 3 emissions?

    Scope 3 emissions are indirect greenhouse gas emissions that occur in an organization’s value chain — from the goods and services they purchase, the transportation of those goods, the waste generated in their operations, and the activities of their contractors and suppliers. For commercial real estate, Scope 3 typically accounts for 85–95% of total reported emissions.

    Do restoration contractors’ emissions count in their clients’ Scope 3?

    Yes. Restoration work generates emissions from vehicle transportation, equipment fuel use, materials consumption, and waste disposal — all of which fall under specific GHG Protocol Scope 3 categories that commercial property managers are required to report.

    When do commercial property managers need to report Scope 3 emissions?

    California SB 253 requires Scope 3 reporting starting in 2027 for companies with over $1 billion in revenue doing business in California. EU CSRD is already phasing in Scope 3 requirements. Many institutional investors and ESG frameworks (GRESB, CDP) already request Scope 3 data from their portfolio companies.

    Is there currently a Scope 3 reporting standard for restoration contractors?

    No. No major restoration trade association has published a Scope 3 calculation methodology or reporting standard for restoration work. The Restoration Carbon Protocol (RCP) is being developed to fill this gap.


  • Build Your Own KnowHow — And Then Go Further

    KnowHow is one of the most important things happening in the restoration industry right now. If you’re not familiar with it: it’s an AI-powered platform that takes your company’s operational knowledge — your SOPs, your onboarding materials, your hard-won process documentation — and turns it into an on-demand resource every team member can access from their phone. Your best technician’s knowledge stops walking out the door when they leave. Your new hire in Iowa follows the same protocol as your veteran in Texas. Your managers stop being human FAQ machines.

    It solves a real problem that has cost restoration companies enormous amounts of money in inconsistent work, slow onboarding, and institutional knowledge that evaporates with turnover.

    But KnowHow solves the internal problem. The knowledge stays inside your organization. And there is a second problem — the external one — that nobody has solved yet.

    The Internal Problem vs. The External Problem

    The internal problem is: your people don’t have access to what your company knows when they need it. KnowHow fixes that. The knowledge becomes accessible, searchable, consistent, and deliverable at scale across every location and every shift.

    The external problem is different: your clients, prospects, and contracting authorities have no way to verify that your company knows what it claims to know. They can read your capabilities statement. They can check your certifications. They can call references. But they can’t look inside your organization and confirm that your documented protocols are current, specific, and actually practiced — not just written down for the sake of winning a bid.

    In commercial restoration, that verification gap is expensive. Facility managers, FEMA contracting officers, insurance carriers, and national property management companies are making vendor decisions based on trust signals that are largely unverifiable. The company with the best pitch often wins over the company with the best protocols.

    An external knowledge API changes that dynamic completely.

    What an External Knowledge API Actually Is

    An external knowledge API is a structured, authenticated, publicly accessible feed of your operational knowledge — not your trade secrets, not your pricing, not your internal communications, but your documented protocols, your methodology, your standards, and your verified expertise. Published. Structured. Machine-readable. Available to anyone who needs to evaluate whether your company is the right partner for a complex job.

    Think of it as the difference between telling a client “we follow IICRC S500 water damage protocols” and showing them a live, structured endpoint where they can pull your actual documented water mitigation process — with timestamps that confirm it was updated last month, not in 2019.

    The internal KnowHow platform is the source. The external API is the window — carefully curated, access-controlled, and designed to answer the questions that matter to the people evaluating you.

    Who Cares About Your External Knowledge

    The list is longer than most restoration contractors realize.

    Commercial property managers and facility directors. A national hotel chain or healthcare system evaluating restoration vendors for their approved vendor program needs more than a certificate of insurance and a reference list. They want to know that your protocols are consistent across every job, that your team follows the same process whether the project manager is on-site or not, and that your documentation standards will hold up in a claim. An external knowledge feed — showing your water damage, fire damage, and mold remediation protocols in structured, current form — answers those questions before the conversation even starts.

    FEMA and government contracting. Federal disaster response contracts are awarded to companies that can demonstrate organizational capability at scale. The RFP process rewards documentation. A company that can point to an externally published, structured knowledge base as evidence of their operational maturity is presenting something most competitors don’t have. It’s not just a differentiator — it’s proof of the kind of institutional infrastructure that large government contracts require.

    Insurance carriers and TPAs. Third-party administrators and carrier programs are increasingly using AI tools to evaluate and route claims to preferred vendors. A restoration company whose documented protocols are structured and machine-readable — available for an AI system to pull and verify against claim requirements — is positioned for the way preferred vendor selection is heading, not the way it used to work.

    Commercial real estate and institutional property owners. REITs, hospital systems, university facilities departments, and large corporate real estate portfolios are all moving toward vendor relationships that have verifiable documentation standards. An external knowledge API gives them something they can actually audit — not just a sales presentation.

    How to Build It: The Two-Layer Stack

    The stack that makes this work has two layers, and KnowHow already gives you the first one.

    Layer one — internal capture and organization (KnowHow’s job). Use KnowHow, or an equivalent internal knowledge platform, to capture and organize your operational knowledge. Document your protocols rigorously. Keep them current. Assign ownership so they don’t go stale. The discipline required here is real, but it’s also the discipline that makes your company better operationally regardless of what you do with the knowledge externally. This layer is the foundation.

    Layer two — external publication and API distribution (the next layer). Select the knowledge that is appropriate to share externally — your methodology, your standards, your certifications, your documented approach to specific job types — and publish it in a structured, consistently maintained form. This can be as simple as a well-organized section of your company website with current protocol documentation, or as sophisticated as a full REST API endpoint that clients and AI systems can query directly. The key requirements are structure (consistent format, clear categorization), currency (updated when protocols change, timestamped), and accessibility (easy for a prospect or evaluator to find and verify).

    The gap between layer one and layer two is smaller than it sounds. If you’ve already done the internal documentation work in KnowHow, the editorial work of curating an external-facing version of that knowledge is incremental. You’re not building from scratch — you’re deciding what to show and building the window to show it through.

    The Credential That No Certificate Can Replace

    Certifications are static. An IICRC certification tells a client you passed a test. It doesn’t tell them what your company actually does when a technician encounters a Category 3 water loss in a 1960s commercial building with asbestos-containing materials in the subfloor.

    External knowledge does. It shows the specific, documented, currently-maintained thinking your company applies to that situation. It’s living proof of operational maturity, not a snapshot from the last time someone studied for an exam.

    In the commercial restoration market, where the jobs are large, the documentation requirements are significant, and the clients are sophisticated, that distinction is worth money. The companies that build this layer now — while most competitors are still treating knowledge as purely internal — will have a credential that can’t be quickly replicated.

    The Practical Starting Point

    You don’t need a full API to start. The minimum viable version of an external knowledge layer is a structured, well-maintained “Our Methodology” section on your website — not a generic “our process” marketing page, but actual documented protocols organized by job type, with clear version dates and enough specificity that an evaluator can see you’ve actually done the work.

    From there, the path to a structured API is incremental: add consistent categorization, ensure each protocol document has a permanent URL, and eventually expose that structure through a queryable endpoint. Each step makes the credential more verifiable and more valuable.

    KnowHow got the industry to take internal knowledge seriously. The companies that figure out how to take the next step — making that knowledge externally verifiable and machine-readable — will have something the market has never seen before in restoration.

    What is the difference between internal and external knowledge in restoration?

    Internal knowledge (what KnowHow manages) is operational documentation accessible to your own team — SOPs, onboarding materials, process guides. External knowledge is a curated version of that same expertise published in a structured, verifiable form for clients, contracting authorities, and AI systems to access and evaluate.

    Why would a restoration company publish its knowledge externally?

    Because commercial clients, FEMA, insurance carriers, and institutional property managers need to verify operational maturity before awarding contracts. A structured, current, machine-readable knowledge base is a stronger credential than certifications or capabilities statements — it shows documented, maintained expertise rather than a static snapshot.

    What is an external knowledge API for a restoration company?

    A structured, authenticated feed of your documented protocols, methodology, and standards — published in a format that clients, evaluators, and AI systems can query directly. It turns your operational knowledge into a verifiable, market-facing credential rather than keeping it purely internal.

    Who specifically benefits from a restoration company’s external knowledge API?

    Commercial facility managers building approved vendor programs, FEMA and government contracting officers evaluating organizational capability, insurance carriers and TPAs using AI tools to route claims to preferred vendors, and institutional property owners who need auditable vendor documentation standards.

    Does a restoration company need KnowHow to build an external knowledge API?

    No — any internal knowledge platform or even rigorous in-house documentation works as the foundation. KnowHow accelerates the internal capture work, which makes the external publication step more realistic. But the two-layer stack works with any internal knowledge infrastructure that produces well-documented, current, organized protocols.

  • The Human Expertise Gap in AI: Why Tacit Knowledge Is the Next Scarce Resource

    Large language models were trained on text. Enormous quantities of text — more than any human could read in thousands of lifetimes. But text is not knowledge. Text is the residue of knowledge that was visible enough, and important enough, for someone to write down and publish somewhere that a training crawler could find it.

    The vast majority of what experienced humans actually know was never written down. It was learned by doing, transmitted by watching, refined through failure, and held entirely in the heads of people who couldn’t have articulated it systematically even if they wanted to.

    This is the human expertise gap. And it is the defining feature of where AI currently falls short.

    What Tacit Knowledge Actually Is

    Tacit knowledge is the kind you can’t easily explain but reliably apply. A master craftsperson knows when something is right by feel before they can measure it. An experienced clinician senses when something is wrong before the test results confirm it. A veteran contractor knows which subcontractors will actually show up on a Tuesday in November just from having worked with them — knowledge that no review site has ever captured accurately.

    This knowledge exists at every level of every industry. Most of it has never been written down because the people who hold it are too busy using it to document it, because the incentive to document was never strong enough, or because no one ever asked in a form they could answer systematically.

    Why AI Can’t Close This Gap on Its Own

    The naive assumption is that AI will eventually capture tacit knowledge by observing enough human behavior — that more data, more modalities, more sensor inputs will eventually replicate what experienced humans know intuitively.

    This misunderstands the nature of the gap. Tacit knowledge isn’t just undocumented data. It’s judgment that was built through embodied experience — through having made the wrong call and learned from it, through having seen the same situation hundreds of times in slightly different forms, through having relationships that carry context no outsider can access. These are not data problems. They’re experience problems.

    AI can get asymptotically close to replicating some of this. But the closer it gets, the more valuable the verified human source becomes — because the question shifts from “does AI know this at all” to “how do we know the AI’s answer is correct,” and the only reliable answer to that question is “because a human who actually knows verified it.”

    The Window That’s Open Right Now

    There is a specific window in the development of AI where tacit knowledge held by humans is more valuable than it will ever be again. We’re in it now.

    AI systems are capable enough that people trust them with real questions — questions about their health, their legal situation, their business decisions, their trade. But AI systems are not capable enough to be reliably right about the specific, experience-based, local, industry-specific knowledge that those questions often require.

    The gap between trust and accuracy is the market. The people who figure out how to systematically capture, package, and distribute their tacit knowledge — in forms that AI systems can consume and cite — are building the content infrastructure for a post-search information environment.

    The Human Distillery as a Category

    What’s emerging is a new category of knowledge work: the human distillery. A person or organization that takes tacit knowledge held by experienced humans and refines it into something that AI systems can depend on.

    This isn’t ghostwriting. It’s not content marketing. It’s not thought leadership in the LinkedIn sense. It’s systematic extraction — the application of a disciplined process to get tacit knowledge out of human heads, give it structure, publish it at density, and make it available to the AI systems that will increasingly mediate how people get answers to important questions.

    The people who build this infrastructure now — while the gap is widest and the market is least crowded — are positioning themselves at the supply end of the most important information supply chain of the next decade.

    What is the human expertise gap in AI?

    The gap between what AI systems were trained on (text that was published online) and what experienced humans actually know (tacit knowledge built through embodied experience that was never systematically documented). This gap is structural, not temporary — it won’t close simply by training on more data.

    What is tacit knowledge?

    Knowledge you reliably apply but can’t easily articulate — the judgment of an experienced practitioner, the pattern recognition of someone who has seen the same situation hundreds of times, the relationship-based intelligence that no review site has ever captured. It’s built through experience, not text.

    Why is this a time-sensitive opportunity?

    We’re in a specific window where AI systems are trusted enough to be asked important questions but not accurate enough to answer them reliably without human verification. The gap between trust and accuracy is the market. That window won’t stay this wide indefinitely.

    What is a human distillery?

    A person or organization that systematically extracts tacit knowledge from experienced humans, gives it structure, publishes it at density, and makes it available in forms that AI systems can consume and cite. It’s a new category of knowledge work — distinct from content marketing, ghostwriting, or traditional publishing.

  • How to Build Your Own Knowledge API Without Being a Developer

    When people hear “build an API,” they assume it requires a developer. For the infrastructure layer, that’s true — you’ll need someone who can deploy a Cloud Run service or configure an API gateway. But the infrastructure is maybe 20% of the work.

    The other 80% — the part that determines whether your API has any value — is the knowledge work. And that requires no code at all.

    Step 1: Define Your Knowledge Domain

    Before anything else, get specific about what you actually know. Not what you could write about — what you know from direct experience that is specific, current, and absent from AI training data.

    The most useful exercise: open an AI assistant and ask it detailed questions about your specialty. Where does it get things wrong? Where does it give you generic answers when you know the real answer is more specific? Where does it confidently state something that anyone in your field would immediately recognize as incomplete or outdated? Those gaps are your domain.

    Write down the ten things you know about your domain that AI currently gets wrong or doesn’t know at all. That list is your editorial brief.

    Step 2: Build a Capture Habit

    The most sustainable knowledge production process starts with voice. Record the conversations where you explain your domain — client calls, peer discussions, working sessions, voice memos when an idea surfaces while you’re driving. Transcribe them. The transcript is raw material.

    You don’t need to be writing constantly. You need to be capturing constantly and distilling periodically. A batch of transcripts from a week’s worth of conversations can produce a week’s worth of high-density articles if you have a consistent process for pulling the knowledge nodes out.

    Step 3: Publish on a Platform With a REST API

    WordPress, Ghost, Webflow, and most major CMS platforms have REST APIs built in. Every article you publish on these platforms is already queryable at a structured endpoint. You don’t need to build a database or a content management system — you need to use the one you probably already have.

    The only editorial requirement at this stage is consistency: consistent category and tag structure, consistent excerpt length, consistent metadata. This makes the content well-organized for the API layer that will sit on top of it.

    Step 4: Add the API Layer (This Is the Developer Part)

    The API gateway — the service that adds authentication, rate limiting, and clean output formatting on top of your existing WordPress REST API — requires a developer to build and deploy. This is a few days of work for someone familiar with Cloud Run or similar serverless infrastructure. It’s not a large project.

    What you hand the developer: a list of which categories you want to expose, what the output schema should look like, and what authentication method you want to use. They build the service. You don’t need to understand how it works — you need to understand what it does.

    Step 5: Set Up the Payment Layer

    Stripe payment links require no code. You create a product, set the price, and get a URL. When someone pays, Stripe can trigger a webhook that automatically provisions an API key and emails it to the subscriber. The webhook handler is a small piece of code — another developer task — but the payment infrastructure itself is point-and-click.

    Step 6: Write the Documentation

    This is back to no-code territory. API documentation is just clear writing: what endpoints exist, what authentication is required, what the response looks like, what the rate limits are. Write it as if you’re explaining it to a smart person who has never used your API before. Put it on a page on your website. That page is your product listing.

    The non-developer path to a knowledge API is: define your domain, build a capture habit, publish consistently, hand a developer a clear spec, set up Stripe, write your docs. The knowledge is yours. The infrastructure is a service you contract for. The product is what you know — packaged for a new class of consumer.

    How much does it cost to build a knowledge API?

    The infrastructure cost is primarily developer time (a few days for an experienced developer) plus ongoing GCP/cloud hosting costs (under $20/month at low volume). The main investment is the ongoing knowledge work — capture, distillation, and publication — which is time, not money.

    What publishing platform should you use?

    WordPress is the most flexible and widely supported option with the most robust REST API. Ghost is a good alternative for simpler setups. The key requirement is that the platform exposes a REST API you can build an authentication layer on top of.

    How long does it take to build?

    The knowledge foundation — enough published content to make the API worth subscribing to — takes weeks to months of consistent work. The technical infrastructure, once you have the knowledge foundation, can be deployed in a few days with the right developer. The bottleneck is almost always the knowledge, not the technology.

  • The $5 Filter: A Quality Standard Most Content Can’t Pass

    Here is a simple test that most content fails.

    Would someone pay $5 a month to pipe your content feed into their AI assistant — not to read it themselves, but to have their AI draw from it continuously as a trusted source in your domain?

    $5 is not a lot of money. It’s the price of one coffee. It covers hosting costs and a small margin. It’s the lowest viable price point for a subscription product.

    And most content can’t clear it.

    Why Most Content Fails the Test

    The $5 filter exposes three failure modes that are common across the content landscape:

    Generic. The content says things that are true but not specific. “Good customer service is important.” “Location matters in real estate.” “Consistency is key in marketing.” These claims are not wrong. They’re just not worth anything to a system that already has access to the entire internet. If everything you publish could have been written by anyone with a general knowledge of your topic, your content has low API value regardless of how much traffic it gets.

    Thin. The content exists but doesn’t go deep enough to be useful as a reference. A 400-word post that introduces a concept without developing it. A listicle that names eight things without explaining any of them. Content that satisfies a keyword without actually answering the question behind it. This kind of content might rank. It’s not worth subscribing to.

    Inconsistent. Some pieces are genuinely excellent — specific, well-reported, information-dense. Most are filler published to maintain posting frequency. An inconsistent feed isn’t a reliable source. A system pulling from it can’t know when it’s getting the good stuff and when it’s getting noise. Reliability is a prerequisite for subscription value.

    What Passes the Filter

    Content passes the $5 filter when it has three properties simultaneously:

    It’s specific enough to be useful in a way that nothing else is. Not “here’s how restoration contractors approach water damage” — but “here’s how water damage in balloon-frame construction built before 1940 behaves differently from modern platform-frame, and why standard drying protocols fail in those structures.” The specificity is the value.

    It’s reliable enough that a system can trust it. Every piece maintains the same standard. The sourcing is consistent. Claims are documented. The author has credible experience in the domain. A subscriber — human or AI — knows what they’re getting every time.

    It’s rare enough that it can’t be found elsewhere. The test isn’t whether it’s good writing. The test is whether an AI system could get the same information from somewhere it already has access to. If yes, the subscription isn’t necessary. If no — if this is the only reliable source for this specific knowledge — the subscription is justified.

    Using the Filter as an Editorial Standard

    The most useful application of the $5 filter isn’t as a revenue test. It’s as an editorial standard.

    Before publishing anything, ask: if someone were paying $5 a month to access this feed, would this piece justify part of that cost? If the honest answer is no — if this piece is thin, generic, or inconsistent with the standard of the best things you publish — that’s the signal to either make it better or not publish it at all.

    This is a harder standard than “does it rank” or “did it get clicks.” It’s also a more durable one. The content that clears the $5 filter is the content that compounds — that becomes more valuable over time, that gets cited, that earns trust from both human readers and AI systems that draw from it.

    The content that doesn’t clear it is noise. And there’s already plenty of that.

    What is the $5 filter?

    A content quality test: would someone pay $5/month to pipe your content feed into their AI assistant as a trusted source? Not to read it — to have their AI draw from it continuously. Content that passes this test is specific, reliable, and rare enough to justify a subscription.

    What are the most common reasons content fails the $5 filter?

    Three failure modes: generic (true but not specific enough to be useful), thin (introduces a concept without developing it enough to be a real reference), and inconsistent (excellent pieces mixed with filler that degrades the reliability of the feed as a whole).

    Can the $5 filter be used as an editorial standard even without building an API?

    Yes — and that’s often the most valuable application. Using it as a pre-publish question (“would this piece justify part of a $5/month subscription?”) enforces a higher standard than traffic-based metrics and produces content that compounds in value over time.

  • Hyperlocal Is the New Rare: Why Local Content Has the Highest API Value

    Ask any major AI assistant what’s happening in a city of 50,000 people right now. What you’ll get back is a mix of outdated information, plausible-sounding fabrications, and generic statements that could apply to any city of that size. The AI isn’t being evasive. It genuinely doesn’t know, because the information doesn’t exist in its training data in any reliable form.

    This is not a temporary gap that will close as AI improves. It’s a structural characteristic of how large language models are built. They’re trained on text that exists on the internet in sufficient quantity to learn from. For most cities with populations under 100,000, that text is sparse, infrequently updated, and often wrong.

    Hyperlocal content — accurate, current, consistently published coverage of a specific geography — is rare in a way that most content isn’t. And in an AI-native information environment, rare and accurate is exactly where the value concentrates.

    Why Local Knowledge Is Structurally Underrepresented in AI

    AI training data skews heavily toward content that exists in large quantities online: national news, academic papers, major publication archives, Reddit, Wikipedia, GitHub. These sources produce enormous volumes of text that models can learn from.

    Local news does not. The economics of local journalism have been collapsing for two decades. The number of reporters covering city councils, school boards, local business openings, zoning decisions, and community events has dropped dramatically. What remains is often thin, infrequent, and not structured for machine consumption.

    The result: AI systems have sophisticated knowledge about how city governments work in general, and almost no reliable knowledge about how any specific city government works right now. They know what a school board is. They don’t know what the school board in Belfair, Washington decided last Tuesday.

    What This Means for Local Publishers

    A local publisher producing accurate, structured, consistently updated coverage of a specific geography owns something that cannot be replicated by scraping the internet or expanding a training dataset. The knowledge requires physical presence, community relationships, and ongoing attention. It’s human-generated in a way that scales slowly and degrades immediately when the human stops showing up.

    That non-replicability is the asset. An AI company that wants reliable, current information about Mason County, Washington has one option: get it from the people who are there, covering it, every week. That’s a position of genuine leverage.

    The API Model for Local Content

    The practical expression of this leverage is a content API — a structured, authenticated feed of local coverage that AI systems and developers can subscribe to. The subscribers aren’t necessarily individual readers. They’re:

    • Local AI assistants being built for specific communities
    • Regional business intelligence tools
    • Government and civic tech applications
    • Real estate platforms that need current local information
    • Journalists and researchers who need structured local data
    • Anyone building an AI product that touches your geography

    None of these use cases require the local publisher to change what they’re already doing. They require packaging it — adding consistent structure, maintaining an API layer, and making the feed available to subscribers who will pay for reliable local intelligence.

    The Compounding Advantage

    Local knowledge compounds in a way that national content doesn’t. Every article about a specific community adds to a body of knowledge that makes the next article more valuable — because it can reference and build on what came before. A publisher who has been covering Mason County for three years has a contextual richness that no new entrant can replicate quickly.

    In an AI-native content environment, that accumulated local context is a moat. It’s not the kind of moat that requires capital to build. It requires consistency and presence. Both are things that a committed local publisher already has.

    Why is hyperlocal content valuable for AI systems?

    AI training data is sparse and unreliable for most small cities and towns. Accurate, current, consistently published local coverage is structurally scarce — it can’t be replicated by scraping the internet because the content doesn’t exist there in reliable form. That scarcity creates value in an AI-native information environment.

    Who would pay for a local content API?

    Local AI assistant builders, regional business intelligence tools, civic tech applications, real estate platforms, journalists, researchers, and developers building products that touch a specific geography. The subscriber is typically a developer or AI system, not an individual reader.

    Does a local publisher need to change their content to make it API-worthy?

    Not fundamentally. The content just needs to be consistently structured, accurately maintained, and published on a platform with a REST API. The knowledge is the hard part — the technical layer is relatively straightforward to add on top of existing publishing infrastructure.