Skip to main content

Working with Batches

Batches represent a unit of carbon stored which evidence can be organized against. A monitoring period can have multiple batches, each representing a distinct quantity of carbon removed during that period. Carbon Stored calculations should be performed at the batch level if summing or averaging metrics across the batches can produce inaccurate results. Not all batches produced in a monitoring period may be applied or used within the same period, which may carry forward emissions or sequestration to subsequent periods.

info

Batches are managed at the monitoring period level. When an Evidence Request is configured as type BATCH, evidence submissions is organized by the corresponding batchItemId.

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.

Listing Batches for Evidence Request​

To view batches 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

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.

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.