Skip to main content

Working with Batches

What are Batches?​

Batches represent units of carbon stored within a Monitoring Period. A batch is a quantifiable unit of carbon removal, defined by:

  • A unique identifier (batch ID)
  • Specific carbon sequestration metrics
  • Association with a monitoring period

Why Use Batches?​

Carbon Stored calculations are typically performed at the batch level because:

  1. Accuracy - Summing or averaging metrics without associating them with specific quantities produces inaccurate results
  2. Partial application - Not all batches produced in a monitoring period may be applied
  3. Proportional emissions - Total production emissions should be reduced by the percentage of material that remains ineligible
  4. Exclusions - Ineligible batches should be excluded from the carbon stored formula
Batch-Level Calculations

When an Evidence Request is configured as type BATCH, submissions can be organized by batchItemId, allowing the grouping of related Evidence files and Expected Field Values together.

Creating Batches​

To create batches for a monitoring period, use POST /v0/monitoring-periods/{id}/batches:

Create batch
curl -X 'POST' "/v0/monitoring-periods/{id}/batches" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

This creates a batch and returns its ID. The batch is automatically associated with the specified monitoring period.

Shared Batches

All Batch documents in the same monitoring period reference the same batches. Once created, batches are available for use across all batch-type evidence requests in that period.

Listing Batch Items for Evidence Request​

To view batch items available for a specific evidence request, use GET /v0/evidence-requests/{id}/batch-items:

Get batch items for evidence request.
curl -X 'GET' "/v0/evidence-requests/{id}/batch-items" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

Response Schema​

id
required
string
type
required
string
Enum: "BATCH" "GROUP"
label
required
string

Batch Item Types​

Batch items can be:

  • BATCH - Individual batch unit
  • GROUP - Grouping of multiple batches

Deleting Batches​

To delete a batch, use DELETE /v0/batches/{id}:

Delete batch
curl -X 'DELETE' "/v0/batches/{id}" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"
Deletion Impact

Deleting a batch will affect all evidence and field values associated with that batch across all documents in the monitoring period.

How Batches Affect LCA & CORC Reports​

Key Fields Tracked per Batch​

When working with batches in LCA & CORC Reports, two critical fractions are calculated:

1. Fraction of Material Produced and Applied per Batch​

(Date Produced >= Monitoring Period Start) AND
(Date Applied <= Monitoring Period End) AND
(Weight by Batch / sum(Weight by Batch))
  • Can be less than 1 - Not all produced material may be applied
  • Multiplied to emissions related to batch production and material sourcing

2. Fraction of Total Material Applied per Batch​

(Date Applied >= Monitoring Period Start) AND
(Date Applied <= Monitoring Period End) AND
(Weight by Batch / sum(Weight by Batch))
  • Always equals 1 when summed across all batches
  • Multiplied to all other steps in the formula

Carried Forward Emissions​

Emissions that typically carry forward in an LCA are those associated with batches produced during an earlier monitoring period but used during the current monitoring period.

These values are applied proportionally, multiplied by the fraction of material produced in their originating monitoring period that is being used in the current period.

Using Batches in Evidence Submission​

When submitting evidence or field values for a batch-type evidence request, you can specify the batchItemId:

Submitting Evidence with Batch ID​

Evidence files can be associated with specific batches:

Create evidence
curl -X 'POST' "/v0/evidence-requests/{id}/evidence" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER" \
  -d '{ \
    "file": "batch-data.xlsx", \
    "evidenceTemplateId": "template-uuid" \
  }'

Submitting Field Values with Batch ID​

Expected field values can be tied to specific batches:

Create expected field value
curl -X 'POST' "/v0/evidence-requests/{id}/values" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER" \
  -d '{ \
    "type": "NUMERIC", \
    "expectedFieldId": "field-uuid", \
    "value": "1000", \
    "batchItemId": "batch-uuid" \
  }'

Batch References in Models​

When a document configured as a Batch Request is referenced as a source in a model, it creates:

  • Batch Fields - Fields that reference batch-level data
  • Batch Formulas - Formulas that calculate across batches

These enable batch-level calculations in your carbon accounting models.

Best Practices​

  1. Create batches early - Set up all batches for a monitoring period before submitting evidence
  2. Use consistent identifiers - Keep batch labels clear and traceable
  3. Track production vs application - Maintain accurate dates for both production and application
  4. Plan for carry-forward - Consider how batches might be used across monitoring periods
  5. Validate fractions - Ensure your batch fractions sum correctly in calculations

Next Steps​

With batches configured, you can now build out the structure of your models by creating sections and field libraries to organize your calculations.