Tag: Developer Reference

The RCP REST API endpoint allows software developers, ESG platforms, and job management systems to programmatically access the full Restoration Carbon Protocol framework — all articles, emission factors, schema documentation, and article relationships — without scraping the site. This endpoint is part of the Tygart Media REST API and is publicly accessible without authentication.

Base URL: https://tygartmedia.com/wp-json/tygart/v1/rcp

Endpoints

GET /wp-json/tygart/v1/rcp

Returns the complete RCP framework index: all published articles with metadata, their relationship type within the framework, and links to full content.

Request:

GET https://tygartmedia.com/wp-json/tygart/v1/rcp
Accept: application/json

Response structure:

{
  "rcp_version": "1.0",
  "schema_version": "RCP-JCR-1.0",
  "last_updated": "2026-04-11",
  "framework_url": "https://tygartmedia.com/rcp/",
  "contact": "rcp@tygartmedia.com",
  "license": "CC BY 4.0",
  "articles": [
    {
      "id": 2481,
      "type": "introduction",
      "title": "Introducing the Restoration Carbon Protocol",
      "url": "https://tygartmedia.com/restoration-carbon-protocol-introduction/",
      "excerpt": "...",
      "tags": ["RCP", "GHG Protocol", "ESG", "Scope 3"]
    },
    ...
  ],
  "article_types": [
    "introduction", "regulatory", "job_type_guide",
    "data_standard", "commercial", "technical", "strategy"
  ]
}

GET /wp-json/tygart/v1/rcp/schema

Returns the full RCP-JCR-1.0 JSON Schema for a Job Carbon Report — the machine-readable data standard for per-job Scope 3 emissions records. This is the canonical schema endpoint for software developers implementing native RCP data capture.

Request:

GET https://tygartmedia.com/wp-json/tygart/v1/rcp/schema
Accept: application/json

Response: Full JSON Schema Draft-07 object as published in the RCP JSON Schema v1.0 article.

GET /wp-json/tygart/v1/rcp/factors

Returns all RCP emission factors as structured JSON — vehicle emission factors, material factors, waste disposal factors, demolished building material factors, and the eGRID subregional table. This allows ESG platforms and carbon calculators to pull the current RCP factor set programmatically rather than hardcoding values.

Request:

GET https://tygartmedia.com/wp-json/tygart/v1/rcp/factors
Accept: application/json

Response structure:

{
  "factor_vintage": "EPA 2025 EF Hub, EPA eGRID 2023, EPA WARM v16, DEFRA 2024",
  "gwp_basis": "IPCC AR6 GWP-100 for refrigerants; IPCC AR5 for other gases",
  "last_updated": "2026-04-11",
  "transportation": {
    "units": "kg_co2e_per_mile",
    "factors": {
      "passenger_car_gasoline": 0.355,
      "light_truck_gasoline": 0.503,
      "light_truck_diesel": 0.523,
      "medium_truck_diesel": 1.084,
      "heavy_truck_unloaded": 1.612,
      "heavy_truck_loaded": 2.25,
      "hazmat_hauler_acm": 3.20,
      "medical_waste_hauler": 2.80
    }
  },
  "electricity": {
    "units": "kg_co2e_per_kwh",
    "national_average": 0.3497,
    "subregions": {
      "NYUP": 0.1101,
      "CAMX": 0.1950,
      "NEWE": 0.2464,
      "ERCT": 0.3341,
      "FRCC": 0.3560,
      "SRSO": 0.3837,
      "NYCW": 0.3927
    }
  },
  "waste_disposal": {
    "units": "tco2e_per_short_ton",
    "factors": {
      "mixed_cd_landfill": 0.16,
      "gypsum_drywall_landfill": 0.16,
      "gypsum_drywall_recycled": 0.02,
      "carpet_pad_landfill": 0.33,
      "carpet_pad_recycled": 0.05,
      "vinyl_lvp_landfill": 0.28,
      "vinyl_lvp_recycled": 0.08,
      "mixed_plastics_landfill": 0.25,
      "biohazard_incineration": 0.97,
      "biohazard_autoclave_landfill": 0.50,
      "acm_inert_transport_only": 0.018
    }
  },
  "materials_kg_co2e_per_unit": {
    "nitrile_glove_each": 0.0277,
    "n95_respirator_each": 0.05,
    "tyvek_suit_each": 0.52,
    "h2o2_antimicrobial_per_kg_active": 1.33,
    "lvp_flooring_per_m2": 5.2,
    "ceramic_tile_per_kg": 0.78,
    "ready_mix_concrete_per_kg": 0.13,
    "ldpe_sheeting_per_kg": 1.793
  },
  "refrigerant_gwp_ar6": {
    "R410A_blend": 2256,
    "R32": 771,
    "R454B_blend": 530,
    "R134a": 1530
  },
  "fuel_combustion": {
    "units": "kg_co2e_per_gallon",
    "gasoline": 8.887,
    "diesel": 10.21
  }
}

GET /wp-json/tygart/v1/rcp/articles/{type}

Returns articles filtered by framework type. Valid type values: job_type_guide, regulatory, data_standard, technical, strategy, introduction, commercial.

Example — get all job type guides:

GET https://tygartmedia.com/wp-json/tygart/v1/rcp/articles/job_type_guide

Response: Array of article objects matching that type, with title, URL, excerpt, and job_types array (e.g., ["water_damage", "category_2", "category_3"]).

Existing WordPress REST API — RCP Queries

While the tygart/v1/rcp endpoints above are planned for v1.1 deployment, the existing WordPress REST API at /wp-json/wp/v2/ already supports filtered RCP queries using tag and category IDs.

Get all RCP articles

GET https://tygartmedia.com/wp-json/wp/v2/posts?tags=409&per_page=50
# Tag 409 = "RCP" — returns all 30 published RCP articles

Get RCP articles by sub-type

# Developer/technical articles only (tag 411 = Developer Reference)
GET https://tygartmedia.com/wp-json/wp/v2/posts?tags=409,411&per_page=20

# Regulatory articles (tag 369 = SB 253)
GET https://tygartmedia.com/wp-json/wp/v2/posts?tags=409,369&per_page=20

Get a specific article with full content

# RCP v1.0 Full Framework Document (post ID 2976)
GET https://tygartmedia.com/wp-json/wp/v2/posts/2976

# Returns: id, title, content.rendered, excerpt.rendered, 
#          link, slug, date, modified, tags, categories

Get the RCP hub page

GET https://tygartmedia.com/wp-json/wp/v2/pages?slug=rcp
# Returns the hub page at /rcp/ with full content and navigation structure

Response fields available per post

RCP Tag ID Reference

Planned v1.1 API Enhancements (Roadmap)

The following endpoints are targeted for deployment in RCP v1.1, pending implementation by the infrastructure team. The spec above defines the intended response format.

• GET /wp-json/tygart/v1/rcp — Framework index with article type classification
• GET /wp-json/tygart/v1/rcp/schema — RCP-JCR-1.0 JSON Schema as a clean API response
• GET /wp-json/tygart/v1/rcp/factors — All emission factors as structured JSON with vintage metadata
• GET /wp-json/tygart/v1/rcp/factors/{category} — Filtered factor sets (transportation, electricity, waste, materials)
• GET /wp-json/tygart/v1/rcp/articles/{type} — Articles filtered by framework type

Software vendors who want to implement the planned endpoints ahead of formal deployment, or who have implementation questions, contact: rcp@tygartmedia.com

Third-party verification of Scope 3 emissions data is no longer theoretical. California SB 253 requires limited assurance for Scope 3 emissions beginning in 2030. CSRD requires limited assurance for all emissions including Scope 3 from the date of initial reporting. GRESB added GHG data assurance as a newly scored metric in 2025. The direction of travel is clear: the per-job carbon data restoration contractors deliver to commercial clients will eventually be subject to external verification — not as a direct requirement on the contractor, but because the client’s verifier will examine the quality and traceability of the supplier data the client used to build their Scope 3 inventory.

This guide explains what verifiers actually look for in Scope 3 contractor data, how the RCP framework satisfies those requirements by design, and what documentation you need to retain to be audit-ready when your clients’ verifiers come asking.

The Two Levels of Assurance and What They Mean for Contractor Data

Understanding assurance levels prevents confusion about what is actually being asked of you.

Limited assurance is a negative assurance — the verifier is confirming they found nothing that makes the report materially wrong. It involves reviewing methodologies, sampling data points, and checking for internal consistency. For Scope 3 data from restoration contractors, a limited assurance engagement will typically review: whether the methodology is documented and consistent with the GHG Protocol, whether proxy values are sourced and labeled, and whether the total reported figure is internally consistent with the underlying calculation inputs.

Reasonable assurance is a positive assurance — the verifier actively confirms the data is accurate. It involves re-performing calculations from source documents, testing internal controls, and in some sectors, site visits. For Scope 3 contractor data under reasonable assurance, verifiers will request the underlying source documents — GPS trip logs, waste manifests, purchase receipts — and verify that the calculation produces the reported number from those inputs.

The practical implication: for limited assurance, methodology documentation and labeling of proxy data are sufficient. For reasonable assurance, you need the source documents. The RCP 12-point data capture standard is designed to collect exactly those source documents at the time of the job, making reasonable assurance retroactively possible without extra effort.

The GHG Protocol’s Five Audit Principles — Applied to RCP Records

The GHG Protocol Corporate Value Chain Standard specifies five principles that a Scope 3 inventory — and by extension, the contractor data that feeds it — must satisfy for assurance purposes. Understanding how RCP records satisfy each principle makes audit preparation straightforward.

1. Relevance

What verifiers check: Whether the emissions sources included reflect the actual emissions generated on behalf of the client, and whether any exclusions are documented and justified.

How RCP satisfies this: The scope boundary section of the RCP Full Framework Document explicitly lists what is included and excluded, with justification for each exclusion. The job_type and damage_category fields in the RCP JSON schema ensure the correct emission domains are applied for each job type. No RCP-compliant record silently excludes a material emission source — exclusions must be documented in the data_quality.notes field.

2. Completeness

What verifiers check: Whether all material Scope 3 categories are covered and whether the reporting boundary is consistently applied across all jobs in the portfolio.

How RCP satisfies this: The RCP portfolio summary covers all jobs at a client’s properties during the reporting period. The four GHG Protocol categories covered (Cat. 1, 4, 5, 12) are documented in the framework as the complete set of material categories for restoration work. A verifier can confirm completeness by checking that every invoiced job appears in the portfolio summary.

3. Consistency

What verifiers check: Whether the same methodology and emission factors are applied across all jobs, and whether year-over-year comparisons are valid.

How RCP satisfies this: The schema_version field (“RCP-JCR-1.0”) ensures every record uses the same schema. The emission factor vintage is documented in the framework (“EPA 2025 EF Hub, EPA eGRID 2023, EPA WARM v16”). When CARB or EPA updates emission factors, the RCP patch version increments, creating a clear record of when methodology changed. Verifiers can request the emission factor table used and verify it matches the published RCP version for that reporting year.

4. Transparency

What verifiers check: Whether methodology is fully disclosed, proxy values are labeled, and the calculation can be reproduced from the disclosed inputs and factors.

How RCP satisfies this: The data_quality section of every RCP Job Carbon Report explicitly lists which data points are primary and which are proxy-estimated. The calculation_method field in each domain section identifies whether primary or proxy methodology was used. The emission factors are published in the RCP Emission Factor Reference Table with source citations. A verifier provided with an RCP JSON record, the proxy value table, and the raw source documents can reproduce the reported number independently.

5. Accuracy

What verifiers check: Whether the quantification is systematic, consistent, and not materially biased toward over- or under-reporting.

How RCP satisfies this: The proxy value hierarchy (primary > derived primary > job-specific proxy > national average proxy) ensures that the calculation uses the most accurate available data for each input. The data_quality section’s primary_data_points list lets verifiers assess what fraction of the total is based on primary data. The systematic use of EPA-sourced emission factors — not custom or proprietary factors — provides a defensible, auditor-recognized basis for every number.

What Source Documents to Retain and for How Long

The following source documents underpin each of the 12 RCP data points. Retain these at the job level, linked to the job ID, for a minimum of seven years. This covers the typical verification lookback period under CSRD (5 years) plus margin.

How RCP Records Are Treated by Verifiers Under Limited vs. Reasonable Assurance

When a property manager’s verifier reviews their Scope 3 inventory under limited assurance, they will typically sample a subset of vendor records — often 10–20% of the total by value — and check for: consistency with stated methodology, that proxy records are labeled as such, and that the calculation produces a plausible number given the stated activity. An RCP JSON record satisfies all three checks without additional preparation, because the schema enforces methodology documentation, proxy labeling is required in the data_quality section, and the calculation is transparent and reproducible.

Under reasonable assurance, the verifier may specifically request source documents for the sampled records. This is where the seven-year document retention requirement becomes material. A contractor who can produce the disposal facility receipt, the GPS trip log, and the Xactimate estimate for a job from 18 months ago has converted a potential audit finding into a zero-question pass.

The most common Scope 3 audit finding for contractor data is: proxy data used without documentation of why primary data was unavailable. The RCP data_quality.notes field is specifically designed to prevent this. Every proxy-based data point should have a note explaining why primary data was unavailable: “Vehicle mileage estimated from dispatch records — GPS fleet system not yet deployed” is a valid and audit-acceptable explanation. Silence is not.

The Chain of Custody for RCP Data

Verifiers are increasingly attentive to the chain of custody for supplier data — how data traveled from the source activity to the reported number in the client’s inventory. For RCP records, the chain of custody is:

1. Source activity: Vehicle trip, equipment run, waste disposal event
2. Source document: GPS log, manifest, purchase receipt
3. Data entry: Job management system (Encircle, PSA, Dash, manual log)
4. RCP calculation: Activity data × emission factor = kg CO₂e per domain
5. RCP Job Carbon Report: JSON record with emissions summary and data quality metadata
6. Client delivery: Email, ESG platform upload, or API transmission
7. Client inventory: Aggregate Scope 3 figure in GRESB/CDP/SB 253 disclosure

Each link in this chain should be documentable. When a verifier asks “how did this number get into the inventory?” you should be able to walk from step 1 to step 7 for any sampled job.

Conducting Your Own Pre-Audit Review

Before your clients face their first verified Scope 3 disclosure cycle, run a pre-audit review of your own RCP records. The GHG Protocol explicitly recommends that inventory preparers treat each verification cycle as a learning process. For restoration contractors, a practical pre-audit review involves:

1. Pull the portfolio summary for your largest commercial client for the most recent year. Count the total jobs and total tCO₂e reported.
2. Sample 5 jobs — pick 2 large, 2 medium, 1 small by affected area. For each, verify you can locate all 12 data point source documents.
3. Check proxy labeling. For every job where a proxy was used, confirm the data_quality section identifies the proxy data points and the notes field explains why.
4. Reproduce one calculation. Take one job record and manually calculate the emissions from the source documents. Verify it matches the reported total within rounding.
5. Check version consistency. Verify all records in the portfolio used schema_version “RCP-JCR-1.0” and the same emission factor vintage. Mixed vintages require disclosure.
6. Document your findings. A one-page internal review memo noting what you checked and what you found creates a quality control record that verifiers view favorably as evidence of internal controls.

The Version Control Requirement

If a Job Carbon Report is corrected after delivery — because a waste manifest weight was updated, a vehicle mileage was corrected, or a proxy value was replaced with primary data — the corrected record must be issued as a new version. The version increment convention for RCP Job Carbon Reports is appending a revision suffix to the job ID: JOB-2026-04847-R1, JOB-2026-04847-R2, etc. The data_quality.notes field must document what changed and why. The original record should be retained alongside the revision — verifiers may ask why a record was corrected.

Assurance Standards Your Clients’ Verifiers Will Use

Different verifiers use different professional standards for GHG assurance. The most common frameworks your clients’ verifiers will reference:

• ISAE 3000: The International Standard on Assurance Engagements (Revised) — the dominant framework for GHG assurance in the EU and used by the Big Four accounting firms globally
• ISO 14064-3: Specification with guidance for the validation and verification of GHG statements — widely used in the US and internationally
• AA1000AS: AccountAbility Assurance Standard — common in voluntary sustainability reporting contexts
• CSAE 3410: Canadian standard, referenced by SB 253 as an acceptable framework

None of these standards create requirements that a contractor must meet directly — they govern how the verifier conducts the engagement. But understanding them helps you know what questions to expect if a client’s verifier contacts you directly about sampled records.

Sources and References

• GHG Protocol. Corporate Value Chain (Scope 3) Accounting and Reporting Standard. ghgprotocol.org/scope-3-standard
• California Air Resources Board. SB 253 Climate Corporate Data Accountability Act. ww2.arb.ca.gov
• Workiva. Emissions Auditing and Verification for Third-Party GHG Assurance. workiva.com
• GSI Environmental. Ensuring a Smooth GHG Verification. gsienv.com
• RCP v1.0 Full Framework Document. tygartmedia.com/rcp-v1-full-framework-document/
• RCP JSON Schema v1.0. tygartmedia.com/rcp-json-schema-v1-machine-readable-standard/

The Restoration Carbon Protocol was designed from the start to be implemented by software, not filled out by hand. The 12 RCP data points map almost entirely to fields that restoration job management platforms already capture — or can capture with minimal configuration. This guide is a direct call to action to the restoration software industry: Encircle, PSA, Dash, Xcelerate, Albiware, Restoration Manager, and any platform serving restoration contractors. Here is exactly what RCP compatibility requires and how to implement it.

The Business Case for Software Vendors

Restoration platforms that implement RCP compatibility give their contractor customers a differentiator that commercial property managers will actively request. As California SB 253 Scope 3 reporting requirements come into effect in 2027 and GRESB, CDP, and CSRD pressure continues to build, commercial clients will increasingly require their restoration vendors to provide per-job carbon data. The contractor that can push a button and produce an RCP-compliant Job Carbon Report wins the commercial renewal. The platform that makes that button possible wins the contractor.

RCP compatibility is also a concrete AI-era feature: it transforms job documentation from a liability tool into a value delivery mechanism. Every well-documented job becomes a carbon asset that the contractor can monetize with commercial clients.

Platform-by-Platform RCP Compatibility Analysis

Encircle

Encircle’s strength is field documentation — photos, moisture readings, drying logs, contents inventories, and report generation. It is the platform closest to capturing the data RCP needs at the source.

RCP JSON export implementation: Encircle’s existing report generation engine can be extended to produce an RCP-JCR-1.0 JSON file as an additional report type at job close-out. The JSON structure maps directly to Encircle’s data model with the additions described above.

PSA (Canam Systems)

PSA is a full job management, CRM, and accounting platform with open API access. It integrates with Xactimate, XactAnalysis, Encircle, and Matterport. PSA’s open API makes it the platform most ready for RCP integration without UI changes.

API integration path: PSA’s open API allows an RCP calculation engine to pull job data at close-out, compute emissions, and POST the resulting RCP-JCR-1.0 JSON to a client-facing endpoint or ESG platform directly. This is the most powerful implementation path and requires no UI changes to PSA itself.

Dash (Next Gear Solutions)

Dash is a full restoration business management platform with Xactimate integration and strong insurance claims workflow support. Its equipment tracking and job financials modules are the primary RCP integration points.

Xcelerate

Xcelerate focuses on operational efficiency and field capture with workflow management and daily checklists. Its customizable daily checklist system is the primary integration point for RCP data capture.

The Xcelerate daily checklist can be configured to include RCP data fields at each technician check-in: vehicle mileage logged, equipment runtime hours, materials consumed. This captures data points 1, 3, 4, 5, and 6 as part of the existing technician workflow with no additional friction. At job close-out, waste and demolished materials fields complete the 12-point record.

The Xactimate Integration Opportunity

Xactimate is the dominant estimating platform across the restoration industry. Its line-item scope database defines what was removed and replaced on virtually every insurance-backed restoration job in the US. This creates a unique RCP integration opportunity: Xactimate line items can be mapped to RCP material types automatically.

A partial Xactimate → RCP material type mapping:

A software vendor that implements this mapping can auto-populate RCP data points 9 and 10 directly from the Xactimate estimate on any job where an estimate exists — which is the majority of commercial losses. This is the single highest-leverage implementation step in the entire RCP software integration roadmap.

The API Call Structure for RCP Data Exchange

For platforms that want to push RCP data to a client-facing endpoint or ESG platform, the standard API pattern is:

POST /api/rcp/v1/job-carbon-reports
Content-Type: application/json
Authorization: Bearer {api_key}

{
  "schema_version": "RCP-JCR-1.0",
  "job_identification": { ... },
  "emissions_summary": { ... },
  "transportation": { ... },
  "materials": { ... },
  "waste": { ... },
  "demolished_materials": { ... },
  "data_quality": { ... }
}

Response 201 Created:
{
  "record_id": "RCP-2026-04847",
  "status": "accepted",
  "validation_warnings": [],
  "client_notification": "sent"
}

For ESG platforms that receive RCP data from multiple contractors (Measurabl, Yardi Elevate, Deepki, Atrius), the recommended intake pattern is a webhook endpoint that accepts POST requests with RCP-JCR-1.0 JSON bodies, validates against the published schema, and maps emissions totals to the platform’s Scope 3 category data model.

RCP Compatibility Certification for Platforms

Software platforms that implement RCP compatibility will be listed on the RCP-compatible platforms registry (forthcoming at tygartmedia.com/rcp). To qualify:

1. Capture all 12 RCP data points (primary or proxy with documentation)
2. Produce valid RCP-JCR-1.0 JSON output that validates against the published schema
3. Label proxy-estimated data points in the data_quality section
4. Notify Tygart Media at rcp@tygartmedia.com with a sample output record

Compatibility certification is free. It is a recognition that the platform meets the RCP standard, not a paid endorsement.

Sources and References

• RCP JSON Schema v1.0 — tygartmedia.com/rcp-json-schema-v1-machine-readable-standard/
• RCP v1.0 Full Framework Document — tygartmedia.com/rcp-v1-full-framework-document/
• PSA (Canam Systems) open API documentation — canamsys.com
• Encircle platform documentation — encircleapp.com
• Next Gear Solutions Dash — nextgearsolutions.com
• Xcelerate Restoration Software — xceleraterestoration.com

The Restoration Carbon Protocol v1.0 JSON Schema is the machine-readable definition of the RCP Job Carbon Report. It specifies every field name, data type, required status, and valid value for a complete RCP emissions record. This is the document software developers, ESG platform integrators, and restoration job management platforms use to implement RCP data capture and exchange.

This schema is released as an open standard. Any platform that produces RCP-compliant JSON output can be described as RCP-compatible. No license is required. Attribution to the Restoration Carbon Protocol is encouraged.

Schema version: RCP-JCR-1.0
Conforms to: JSON Schema Draft-07 (json-schema.org/draft-07)
GHG Protocol alignment: Corporate Value Chain (Scope 3) Standard
Emission factor vintage: EPA 2025, EPA WARM v16, EPA eGRID 2023

Schema Overview

The RCP Job Carbon Report JSON object has seven top-level sections that mirror the paper report format: job identification, emissions summary, transportation data, materials data, waste data, demolished materials, and data quality metadata. All sections except data_quality are required for a complete RCP record. Partial records (missing sections) are valid as draft records but must not be delivered to clients as final RCP disclosures.

Full Schema Definition

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://tygartmedia.com/rcp/schema/v1.0/job-carbon-report.json",
  "title": "RCP Job Carbon Report",
  "description": "Restoration Carbon Protocol v1.0 — Per-Job Scope 3 Emissions Record",
  "version": "1.0.0",
  "type": "object",
  "required": [
    "schema_version",
    "job_identification",
    "emissions_summary",
    "transportation",
    "materials",
    "waste",
    "demolished_materials"
  ],

  "properties": {

    "schema_version": {
      "type": "string",
      "const": "RCP-JCR-1.0",
      "description": "Schema version identifier. Must be 'RCP-JCR-1.0' for v1.0 records."
    },

    "generated_at": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 timestamp of when this record was generated."
    },

    "job_identification": {
      "type": "object",
      "required": [
        "contractor_name",
        "job_id",
        "client_name",
        "property_address",
        "job_type",
        "damage_category",
        "damage_class",
        "affected_area_sqft",
        "job_start_date",
        "job_completion_date",
        "reporting_standard",
        "egrid_subregion"
      ],
      "properties": {
        "contractor_name": {
          "type": "string",
          "description": "Legal name of the restoration contractor performing the work."
        },
        "contractor_rcp_id": {
          "type": "string",
          "description": "Optional. RCP self-certification ID if contractor is RCP-certified."
        },
        "job_id": {
          "type": "string",
          "description": "Contractor's internal job identifier. Used to cross-reference with job management system."
        },
        "client_name": {
          "type": "string",
          "description": "Name of the property owner or manager receiving this report."
        },
        "property_address": {
          "type": "object",
          "required": ["street", "city", "state", "zip"],
          "properties": {
            "street": { "type": "string" },
            "city": { "type": "string" },
            "state": { "type": "string", "pattern": "^[A-Z]{2}$" },
            "zip": { "type": "string", "pattern": "^[0-9]{5}(-[0-9]{4})?$" }
          }
        },
        "job_type": {
          "type": "string",
          "enum": [
            "water_damage",
            "fire_smoke",
            "mold_remediation",
            "asbestos_hazmat",
            "biohazard_trauma",
            "combined"
          ],
          "description": "Primary job type per RCP classification."
        },
        "damage_category": {
          "type": "string",
          "enum": ["1", "2", "3", "N/A"],
          "description": "IICRC S500 water damage category (1=clean, 2=gray, 3=black). Use N/A for non-water jobs."
        },
        "damage_class": {
          "type": "string",
          "enum": ["1", "2", "3", "4", "N/A"],
          "description": "IICRC S500 water damage class (1=minimal to 4=specialty drying). Use N/A for non-water jobs."
        },
        "affected_area_sqft": {
          "type": "number",
          "minimum": 0,
          "description": "Total affected area in square feet."
        },
        "job_start_date": {
          "type": "string",
          "format": "date",
          "description": "ISO 8601 date (YYYY-MM-DD) of job mobilization."
        },
        "job_completion_date": {
          "type": "string",
          "format": "date",
          "description": "ISO 8601 date (YYYY-MM-DD) of job close-out."
        },
        "reporting_standard": {
          "type": "string",
          "const": "Restoration Carbon Protocol v1.0, GHG Protocol Corporate Value Chain Standard",
          "description": "Must match this exact string for RCP v1.0 compliance."
        },
        "egrid_subregion": {
          "type": "string",
          "description": "EPA eGRID subregion code for the job site ZIP code. Use 'US_AVG' if subregion unknown.",
          "examples": ["WECC", "SRVC", "RFCW", "US_AVG"]
        }
      }
    },

    "emissions_summary": {
      "type": "object",
      "required": [
        "total_job_emissions_tco2e",
        "category_1_materials_tco2e",
        "category_4_transportation_tco2e",
        "category_5_waste_tco2e",
        "category_12_demolished_materials_tco2e"
      ],
      "properties": {
        "total_job_emissions_tco2e": {
          "type": "number",
          "minimum": 0,
          "description": "Total job Scope 3 emissions in metric tons CO2 equivalent (tCO2e). Sum of all categories."
        },
        "category_1_materials_tco2e": {
          "type": "number",
          "minimum": 0,
          "description": "GHG Protocol Scope 3 Category 1 — Purchased Goods and Services. Embedded carbon in consumable materials."
        },
        "category_4_transportation_tco2e": {
          "type": "number",
          "minimum": 0,
          "description": "GHG Protocol Scope 3 Category 4 — Upstream Transportation. All vehicle fuel combustion for job-related trips."
        },
        "category_5_waste_tco2e": {
          "type": "number",
          "minimum": 0,
          "description": "GHG Protocol Scope 3 Category 5 — Waste Generated in Operations. Disposal of materials removed from the property."
        },
        "category_12_demolished_materials_tco2e": {
          "type": "number",
          "minimum": 0,
          "description": "GHG Protocol Scope 3 Category 12 — End-of-Life Treatment. Embedded carbon in building materials removed and disposed."
        },
        "equipment_energy_kwh": {
          "type": "number",
          "minimum": 0,
          "description": "Optional. Total kWh consumed by contractor-deployed equipment. Included in Category 1 if equipment operates on building power; Category 4 if generator-powered."
        }
      }
    },

    "transportation": {
      "type": "object",
      "required": ["vehicle_trips", "calculation_method"],
      "properties": {
        "calculation_method": {
          "type": "string",
          "enum": ["primary_fuel_volume", "proxy_mileage"],
          "description": "'primary_fuel_volume' = actual gallons recorded. 'proxy_mileage' = miles x fleet average mpg x emission factor."
        },
        "vehicle_trips": {
          "type": "array",
          "minItems": 1,
          "items": {
            "type": "object",
            "required": ["vehicle_type", "fuel_type", "round_trips", "round_trip_miles"],
            "properties": {
              "vehicle_type": {
                "type": "string",
                "enum": ["light_truck", "service_van", "equipment_trailer", "dump_truck", "heavy_equipment", "other"],
                "description": "Vehicle category."
              },
              "fuel_type": {
                "type": "string",
                "enum": ["diesel", "gasoline", "electric", "hybrid"],
                "description": "Primary fuel type."
              },
              "round_trips": {
                "type": "integer",
                "minimum": 1,
                "description": "Number of complete round trips for this vehicle on this job."
              },
              "round_trip_miles": {
                "type": "number",
                "minimum": 0,
                "description": "Miles per round trip."
              },
              "fuel_consumed_gallons": {
                "type": "number",
                "minimum": 0,
                "description": "Optional. Actual fuel consumed in gallons. Preferred over proxy when available."
              },
              "emissions_kg_co2e": {
                "type": "number",
                "minimum": 0,
                "description": "Calculated emissions for this vehicle entry in kg CO2e."
              },
              "trip_purpose": {
                "type": "string",
                "enum": ["response", "monitoring", "equipment_delivery", "equipment_pickup", "waste_haul", "crew_transport", "other"],
                "description": "Primary purpose of these trips."
              }
            }
          }
        },
        "total_vehicle_miles": {
          "type": "number",
          "minimum": 0,
          "description": "Sum of all vehicle-miles across all entries."
        },
        "total_emissions_kg_co2e": {
          "type": "number",
          "minimum": 0,
          "description": "Total transportation emissions in kg CO2e."
        }
      }
    },

    "materials": {
      "type": "object",
      "required": ["calculation_method"],
      "properties": {
        "calculation_method": {
          "type": "string",
          "enum": ["primary_purchase_records", "proxy_job_type_standard"],
          "description": "'primary_purchase_records' = actual quantities from purchase records. 'proxy_job_type_standard' = RCP standard consumption rates by job type."
        },
        "chemicals": {
          "type": "array",
          "items": {
            "type": "object",
            "required": ["product_type", "quantity_liters"],
            "properties": {
              "product_type": {
                "type": "string",
                "enum": ["antimicrobial", "biocide", "encapsulant", "deodorizer", "wetting_agent", "other"]
              },
              "quantity_liters": { "type": "number", "minimum": 0 },
              "emission_factor_kg_co2e_per_liter": { "type": "number" },
              "emissions_kg_co2e": { "type": "number", "minimum": 0 }
            }
          }
        },
        "ppe_disposable": {
          "type": "object",
          "properties": {
            "tyvek_suits": { "type": "integer", "minimum": 0 },
            "glove_pairs": { "type": "integer", "minimum": 0 },
            "respirators_n95": { "type": "integer", "minimum": 0 },
            "respirators_p100_half_face": { "type": "integer", "minimum": 0 },
            "boot_covers_pairs": { "type": "integer", "minimum": 0 },
            "emissions_kg_co2e": { "type": "number", "minimum": 0 }
          }
        },
        "containment_materials": {
          "type": "object",
          "properties": {
            "poly_sheeting_meters": { "type": "number", "minimum": 0 },
            "zipper_doors_units": { "type": "integer", "minimum": 0 },
            "hepa_filters_replaced": { "type": "integer", "minimum": 0 },
            "emissions_kg_co2e": { "type": "number", "minimum": 0 }
          }
        },
        "replacement_materials": {
          "type": "array",
          "description": "Installed replacement building materials, if reconstruction is within contractor scope.",
          "items": {
            "type": "object",
            "required": ["material_type", "quantity_kg"],
            "properties": {
              "material_type": {
                "type": "string",
                "enum": ["drywall_standard", "drywall_moisture_resistant", "insulation_fiberglass", "insulation_mineral_wool", "lumber_framing", "carpet", "lvp_flooring", "tile_ceramic", "other"]
              },
              "quantity_kg": { "type": "number", "minimum": 0 },
              "emission_factor_kg_co2e_per_kg": { "type": "number" },
              "emissions_kg_co2e": { "type": "number", "minimum": 0 }
            }
          }
        },
        "total_emissions_kg_co2e": {
          "type": "number",
          "minimum": 0,
          "description": "Total materials emissions in kg CO2e. Sum of chemicals, PPE, containment, and replacement materials."
        }
      }
    },

    "waste": {
      "type": "object",
      "required": ["calculation_method", "waste_streams"],
      "properties": {
        "calculation_method": {
          "type": "string",
          "enum": ["primary_manifest_weights", "proxy_volume_conversion"],
          "description": "'primary_manifest_weights' = actual weights from disposal manifests. 'proxy_volume_conversion' = volume estimates converted to weight using RCP standard densities."
        },
        "waste_streams": {
          "type": "array",
          "minItems": 1,
          "items": {
            "type": "object",
            "required": ["waste_type", "disposal_method", "quantity_short_tons"],
            "properties": {
              "waste_type": {
                "type": "string",
                "enum": ["cd_debris_mixed", "drywall_gypsum", "wood_debris", "contaminated_water", "regulated_hazmat", "biohazardous_waste", "ppe_disposable", "other"]
              },
              "disposal_method": {
                "type": "string",
                "enum": ["landfill", "recycling", "hazmat_incineration", "wastewater_municipal", "wastewater_licensed_facility", "other"]
              },
              "disposal_facility": {
                "type": "string",
                "description": "Optional. Name or identifier of disposal facility."
              },
              "quantity_short_tons": {
                "type": "number",
                "minimum": 0,
                "description": "Weight of waste in US short tons."
              },
              "haul_miles_one_way": {
                "type": "number",
                "minimum": 0,
                "description": "Optional. One-way distance to disposal facility in miles. Used to calculate haul transport emissions."
              },
              "emission_factor_tco2e_per_short_ton": { "type": "number" },
              "emissions_kg_co2e": { "type": "number", "minimum": 0 }
            }
          }
        },
        "total_emissions_kg_co2e": {
          "type": "number",
          "minimum": 0,
          "description": "Total waste disposal emissions in kg CO2e."
        }
      }
    },

    "demolished_materials": {
      "type": "object",
      "required": ["calculation_method"],
      "properties": {
        "calculation_method": {
          "type": "string",
          "enum": ["primary_demolition_records", "proxy_affected_area"],
          "description": "'primary_demolition_records' = actual weights from demolition scope. 'proxy_affected_area' = RCP standard weight-per-sqft by material type."
        },
        "materials_removed": {
          "type": "array",
          "items": {
            "type": "object",
            "required": ["material_type", "quantity_kg"],
            "properties": {
              "material_type": {
                "type": "string",
                "enum": ["drywall_standard", "drywall_moisture_resistant", "insulation_fiberglass", "insulation_mineral_wool", "lumber_framing", "carpet", "lvp_flooring", "tile_ceramic", "concrete", "other"]
              },
              "quantity_kg": { "type": "number", "minimum": 0 },
              "emission_factor_kg_co2e_per_kg": { "type": "number" },
              "emissions_kg_co2e": { "type": "number", "minimum": 0 }
            }
          }
        },
        "total_emissions_kg_co2e": {
          "type": "number",
          "minimum": 0,
          "description": "Total demolished materials emissions in kg CO2e."
        }
      }
    },

    "data_quality": {
      "type": "object",
      "description": "Optional but strongly recommended. Documents data sources and proxy usage for audit purposes.",
      "properties": {
        "preparer_name": { "type": "string" },
        "preparer_date": { "type": "string", "format": "date" },
        "primary_data_points": {
          "type": "array",
          "description": "List of data points captured from primary sources.",
          "items": {
            "type": "string",
            "enum": [
              "vehicle_mileage_gps",
              "vehicle_mileage_odometer",
              "fuel_consumed_recorded",
              "equipment_kwh_metered",
              "waste_weight_manifest",
              "materials_purchase_records",
              "demolition_scope_documented"
            ]
          }
        },
        "proxy_data_points": {
          "type": "array",
          "description": "List of data points estimated using RCP proxy values.",
          "items": {
            "type": "string",
            "enum": [
              "vehicle_mileage_estimated",
              "fuel_consumed_proxy_mpg",
              "equipment_kwh_proxy_wattage",
              "waste_weight_estimated",
              "ppe_consumption_standard_rate",
              "materials_proxy_sqft"
            ]
          }
        },
        "notes": {
          "type": "string",
          "description": "Free-text field for data quality notes, exceptions, or unusual circumstances."
        }
      }
    }
  }
}

Minimal Valid Record Example

The following is the smallest valid RCP-JCR-1.0 JSON object — all required fields populated, optional fields omitted. This represents a simple water damage job with proxy-based calculations:

{
  "schema_version": "RCP-JCR-1.0",
  "generated_at": "2026-04-11T09:00:00Z",

  "job_identification": {
    "contractor_name": "Acme Restoration LLC",
    "job_id": "JOB-2026-04847",
    "client_name": "Westfield Properties Inc.",
    "property_address": {
      "street": "1200 Commerce Blvd",
      "city": "Sacramento",
      "state": "CA",
      "zip": "95814"
    },
    "job_type": "water_damage",
    "damage_category": "2",
    "damage_class": "3",
    "affected_area_sqft": 2400,
    "job_start_date": "2026-03-14",
    "job_completion_date": "2026-03-22",
    "reporting_standard": "Restoration Carbon Protocol v1.0, GHG Protocol Corporate Value Chain Standard",
    "egrid_subregion": "WECC"
  },

  "emissions_summary": {
    "total_job_emissions_tco2e": 1.84,
    "category_1_materials_tco2e": 0.09,
    "category_4_transportation_tco2e": 0.89,
    "category_5_waste_tco2e": 0.70,
    "category_12_demolished_materials_tco2e": 0.16
  },

  "transportation": {
    "calculation_method": "proxy_mileage",
    "vehicle_trips": [
      {
        "vehicle_type": "light_truck",
        "fuel_type": "diesel",
        "round_trips": 4,
        "round_trip_miles": 47,
        "emissions_kg_co2e": 189,
        "trip_purpose": "response"
      },
      {
        "vehicle_type": "equipment_trailer",
        "fuel_type": "diesel",
        "round_trips": 2,
        "round_trip_miles": 47,
        "emissions_kg_co2e": 151,
        "trip_purpose": "equipment_delivery"
      },
      {
        "vehicle_type": "dump_truck",
        "fuel_type": "diesel",
        "round_trips": 1,
        "round_trip_miles": 22,
        "emissions_kg_co2e": 50,
        "trip_purpose": "waste_haul"
      }
    ],
    "total_vehicle_miles": 470,
    "total_emissions_kg_co2e": 390
  },

  "materials": {
    "calculation_method": "proxy_job_type_standard",
    "chemicals": [
      {
        "product_type": "antimicrobial",
        "quantity_liters": 12,
        "emission_factor_kg_co2e_per_liter": 2.8,
        "emissions_kg_co2e": 33.6
      }
    ],
    "ppe_disposable": {
      "tyvek_suits": 18,
      "glove_pairs": 36,
      "respirators_n95": 24,
      "emissions_kg_co2e": 45
    },
    "containment_materials": {
      "poly_sheeting_meters": 40,
      "emissions_kg_co2e": 9
    },
    "total_emissions_kg_co2e": 87.6
  },

  "waste": {
    "calculation_method": "primary_manifest_weights",
    "waste_streams": [
      {
        "waste_type": "cd_debris_mixed",
        "disposal_method": "landfill",
        "disposal_facility": "Sacramento County Transfer Station",
        "quantity_short_tons": 1.8,
        "haul_miles_one_way": 11,
        "emission_factor_tco2e_per_short_ton": 0.021,
        "emissions_kg_co2e": 37.8
      }
    ],
    "total_emissions_kg_co2e": 37.8
  },

  "demolished_materials": {
    "calculation_method": "primary_demolition_records",
    "materials_removed": [
      {
        "material_type": "drywall_standard",
        "quantity_kg": 900,
        "emission_factor_kg_co2e_per_kg": 0.12,
        "emissions_kg_co2e": 108
      },
      {
        "material_type": "carpet",
        "quantity_kg": 180,
        "emission_factor_kg_co2e_per_kg": 5.40,
        "emissions_kg_co2e": 972
      }
    ],
    "total_emissions_kg_co2e": 1080
  },

  "data_quality": {
    "preparer_name": "Jane Smith, Operations Manager",
    "preparer_date": "2026-03-22",
    "primary_data_points": ["waste_weight_manifest", "materials_purchase_records"],
    "proxy_data_points": ["vehicle_mileage_estimated", "ppe_consumption_standard_rate"],
    "notes": "Vehicle mileage estimated from dispatch address records. PPE consumption from standard Cat 2, Class 3 rate table."
  }
}

Emission Factors Referenced in This Schema

All emission factors used in RCP-JCR-1.0 calculations are drawn from the RCP Emission Factor Reference Table. The authoritative source for each factor is documented there. The key factors for software implementations:

• Grid electricity (US national average): 0.3499 kg CO₂e/kWh — EPA eGRID 2023
• Diesel fuel (mobile combustion): 10.21 kg CO₂e/gallon — EPA 2025 EF Hub
• Gasoline (mobile combustion): 8.89 kg CO₂e/gallon — EPA 2025 EF Hub
• Mixed C&D waste, landfill: 0.021 tCO₂e/short ton — EPA WARM v16
• Drywall production: 0.12 kg CO₂e/kg — EPA WARM v16
• Carpet (nylon): 5.40 kg CO₂e/kg — DEFRA 2024

Implementation Notes for Software Developers

Several implementation patterns are worth noting for platforms building RCP compatibility:

Field nullability: Optional fields should be omitted entirely when no data is available, not set to null or 0. A missing field is distinguishable from a zero-value field, which matters for audit purposes.

Calculation_method flags: The calculation_method field in each section is required because it tells the receiving system and verifier whether to trust the numbers at primary-data quality or proxy quality. ESG platforms that ingest RCP JSON should surface this distinction to their users.

Unit consistency: All emissions totals in emissions_summary are in metric tons CO₂e (tCO₂e). All emissions in sub-sections are in kilograms CO₂e (kg CO₂e). The conversion is 1 tCO₂e = 1,000 kg CO₂e. Software implementations should validate unit consistency at write time.

eGRID subregion codes: The canonical list of eGRID subregion codes is available from EPA at epa.gov/egrid. The US_AVG code is an RCP extension for cases where the subregion is unknown — it instructs consuming systems to apply the national average factor (0.3499 kg CO₂e/kWh).

Schema validation: Implementations should validate records against this schema before transmission. Invalid records — missing required fields, wrong data types, enum violations — must not be transmitted as final RCP disclosures.

Versioning and Backwards Compatibility

The schema_version field is used by consuming systems to identify which version of the RCP schema a record was produced under. RCP v2.0 will introduce a new schema version string and may add fields not present in v1.0. All v1.0 records remain valid and will be processed by systems that implement backwards compatibility for RCP-JCR-1.0. No fields will be removed between minor versions; only additions are permitted.

The current schema is published at: tygartmedia.com/rcp/schema/v1.0/job-carbon-report.json

Sources and References

• JSON Schema Draft-07 Specification — json-schema.org/draft-07
• GHG Protocol Corporate Value Chain (Scope 3) Standard — ghgprotocol.org/scope-3-standard
• EPA 2025 GHG Emission Factors Hub — epa.gov/climateleadership/ghg-emission-factors-hub
• EPA eGRID 2023 — epa.gov/egrid
• EPA WARM v16 — epa.gov/warm
• ANSI/IICRC S500 5th Edition (2021) — iicrc.org/s500