> For the complete documentation index, see [llms.txt](https://kb.bravegen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bravegen.com/carbon/core-concepts/data-collection.md). # Data Collection
**Data Collection** is how activity data gets into BraveGen Carbon and turned into reportable emissions data. Every [Activity Source](/carbon/core-concepts/activity-sources.md) starts out as data collected through this system - whether that's a spreadsheet from a supplier, a utility invoice, or a value you enter yourself. *** #### Processes and Tasks Two objects sit behind every collection: * A [**Process**](/carbon/core-concepts/data-collection/processes.md) determines how a particular type of data is collected - its Process Type, and behaviour like quarantine and collision handling. You set a process up once and it spawns Tasks on an ongoing basis. * A [**Task**](/carbon/core-concepts/data-collection/tasks.md) is a single collection bucket spawned by a process. A task holds the data for one collection period; once it's marked complete, its data is included in reporting. Every process assigns three collection roles - Process Owner, Data Approver, and Data Supplier - which determine who is notified at each stage. See [Processes](/carbon/core-concepts/data-collection/processes.md) for what each role can see and do. {% hint style="info" %} Entities and Activity Sources don't need to be set up ahead of time. In most cases they're created automatically the first time BraveGen sees a new Entity Identifier or Source in collected data, via [Task Review](/carbon/core-concepts/data-collection/tasks/task-reviews.md). {% endhint %} *** #### Getting data in Every process has a **Process Type**, which determines how it collects data: * [**File Upload**](/carbon/core-concepts/data-collection/processes/file-upload.md) - upload or email spreadsheets (`.CSV`, `.XLS`, `.XLSX`) or [Utility Invoices](/carbon/core-concepts/data-collection/processes/file-upload/utility-invoices.md), then map the columns with a [Data Map](/carbon/core-concepts/data-collection/processes/file-upload/data-maps.md). * **Manual Data Entry**, [**Smart Form**](/carbon/core-concepts/data-collection/processes/smart-forms-planned.md), and **Reminder** are additional process types on the roadmap and not yet available. Any process can also create tasks automatically - see [Automation](/carbon/core-concepts/data-collection/processes/automation.md) for repeating and ad-hoc scheduling, and for the automated channels data can arrive through ([Email Attachments](/carbon/core-concepts/data-collection/processes/automation/email-attachments.md) today; [SFTP](/carbon/core-concepts/data-collection/processes/automation/sftp.md), [API](/carbon/core-concepts/data-collection/processes/automation/api.md), and [MCP](/carbon/core-concepts/data-collection/processes/automation/mcp.md) are planned). Outside of a process, [**Manual Adjustments**](/carbon/core-concepts/data-collection/manual-adjustments.md) let you add or correct values directly on a source's activity, for periods where the ingested data is missing, incomplete, or wrong. *** #### Reviewing and approving collected data Before collected data reaches your reporting, it goes through review: * [**Task Reviews**](/carbon/core-concepts/data-collection/tasks/task-reviews.md) - confirm any new entities, activity sources, and inventory items detected in the incoming data. * [**Quarantine**](/carbon/core-concepts/data-collection/tasks/quarantine.md) - an optional hold state, configured per process, that requires a Data Approver to sign off before data is included in emissions reporting. * [**Resolving Collisions**](/carbon/core-concepts/data-collection/tasks/resolving-collisions.md) - handles data that overlaps with an existing task for the same source and period, eg. a file sent twice, or a correction data set. {% hint style="warning" %} Quarantine and collision-handling behaviour are set on the parent process, not on individual tasks. Changing them later only affects tasks created after the change - it won't reprocess tasks already in progress. {% endhint %} If a supplier changes their file format and mapping starts failing, see [Fixing a Data Map](/carbon/core-concepts/data-collection/tasks/fixing-a-data-map.md) to re-pivot the file without setting up the process again. *** #### Summary * A **Process** defines how a type of data is collected; a **Task** is a single collection period spawned by that process. * Data comes in through a process's **File Upload** type today, with **Manual Data Entry**, **Smart Form**, and **Reminder** types planned; any process can also collect automatically via **Automation**. * **Manual Adjustments** let you edit a source's activity directly, without going through a process. * Collected data passes through Task Review and, depending on the process's quarantine setting, sign-off by a Data Approver, before it's included in emissions reporting.