> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/employee-data/dataset.md).

# Employee Data Flat Files

Explore Coresignal employee datasets available as flat files, including data coverage, delivery schedules, and supported formats.

Flat files are one of the two ways Coresignal delivers Employee Data. Rather than querying records manually, you receive the dataset or periodic updates in a downloadable file that can be loaded directly into your data warehouse or pipeline. This page explains how flat-file delivery works for Employee Data, including the available formats and delivery frequencies.

## Delivery frequency and formats <a href="#delivery-frequency-and-formats" id="delivery-frequency-and-formats"></a>

Employee Data is available in:

* **Parquet** for efficient storage and analytics.
* **JSONL** is ideal for streaming and processing data line by line.

Files are delivered daily, weekly, monthly, and quarterly. Historical fields let you track changes in employee metrics over time, including job moves, skill history, and follower counts.

| Dataset       | Delivery frequency                | Delivery format | Update frequency |
| ------------- | --------------------------------- | --------------- | ---------------- |
| Employee Data | Daily, weekly, monthly, quarterly | JSONL, Parquet  | Ongoing          |

{% hint style="info" %}
Use a consistent employee identifier to join files across deliveries. This helps maintain employee history even when names or URLs change.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Explore full employee record sample</td><td><a href="/employee-data/record-sample.md">Employee Record Sample</a></td></tr><tr><td>More information about flat files deliveries</td><td><a href="/introduction/delivery-formats.md">Delivery Formats</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/employee-data/dataset.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.