Documentation Index
Fetch the complete documentation index at: https://docs.mangrovesystems.com/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll learn in this lesson:
- Understand the partitioning cadence options available in Mangrove
- Choose between per-event, daily, weekly, and monthly partitioning
- Configure batch types for your chosen strategy
- Evaluate trade-offs between granularity and management overhead
Partitioning cadence options
Mangrove supports two fundamental approaches to partitioning, as described in the Guide to Production Accounting :- ID-based (per-event)
- Time-based (periodic)
Each event with a unique tracking ID becomes its own batch. Best for projects with discrete, countable production units.When to use:
- Each physical event is a natural reporting unit (e.g., a delivery, a shipment)
- The methodology requires per-event traceability
- Events are relatively infrequent (daily or less)
Choosing the right strategy
Your partitioning strategy is driven by three factors:Methodology requirements
Some standards specify the partitioning granularity. For example, a methodology might require per-delivery tracking for chain-of-custody compliance, or monthly aggregation for periodic monitoring.
Operational patterns
Match the batch cadence to how the project actually operates. If deliveries happen 3-4 times per week, per-delivery batches make sense. If a facility runs continuously, daily or monthly batches are more practical.
Trade-offs: granularity vs. overhead
| Factor | More Granular (per-event) | Less Granular (monthly) |
|---|---|---|
| Traceability | Each batch maps to one physical event | Batch aggregates many events |
| Verification | More batches to review, but each is simple | Fewer batches, but each requires drilling into aggregated data |
| Credit issuance | Faster — credits can be issued per batch | Slower — must wait for period to close |
| Management | More batches to track and manage | Fewer batches, simpler workflow |
| Reporting | High granularity, flexible aggregation | Natural aggregation, less flexibility |
Feedstock-based partitioning
Some projects need to partition batches by feedstock type as well. If a biochar facility processes both agricultural waste and forestry residues, batches should be separated by feedstock because the methodology may apply different factors to each. In Mangrove, you can associate events with feedstocks and configure batch types to generate separate batches per feedstock within each accounting period.Feedstock partitioning can be combined with time-based or ID-based partitioning. For example: monthly batches, split by feedstock type. This is configured in the batch type settings.
Configuring batch partitioning in Mangrove
Batch partitioning is configured through the batch type settings in your project. When you generate batches , Mangrove applies the partition rules to create the appropriate number of batches from the events in the selected period.Check your understanding
What are the two fundamental partitioning approaches in Mangrove?
What are the two fundamental partitioning approaches in Mangrove?
ID-based (per-event) partitioning creates one batch per unique tracking ID. Time-based (periodic) partitioning aggregates all events within a time window (daily, weekly, monthly) into one batch. The choice depends on methodology requirements, operational patterns, and verification needs.
When would you choose per-delivery over monthly partitioning?
When would you choose per-delivery over monthly partitioning?
Choose per-delivery when: (1) each delivery is a natural production unit, (2) the methodology requires per-event traceability, (3) deliveries are infrequent enough to manage individually, and (4) faster credit issuance per batch is valuable. Monthly is better for high-frequency continuous production where individual events are too small to report separately.
Next, learn how to account for the emissions produced during your project’s operations in Lesson 3.3: Life Cycle Assessment & Emissions.