# Proof of Record

**Proof of Record™** helps you track the origin of your data. For every data point, you can see:

* **Who** extracted it (name or email)
* **When** it was extracted (timestamp)
* **Where** it came from (URL)
* **What** it looked like (screenshot of the page)

Every captured record is accompanied by metadata, including the extractor’s name or email, a timestamp, the source URL, and a screenshot of the page at the moment of extraction.

This feature is especially valuable where **data reliability**, **transparency**, and **auditability** are non-negotiable.

## Why does it matter?

### Transparency and traceability

In an era of AI-generated content and automated scraping, trust in data is everything. With **Proof of Record™**, every piece of information can be **traced back to its origin**. This creates a **source lineage** that empowers you to:

* Validate the authenticity of your datasets
* Ensure data consistency across teams and tools
* Build trust with stakeholders, clients, and auditors

### Trust and accountability

Data errors are inevitable, but ambiguity doesn’t have to be.

Proof of Record™ provides your team with the accountability framework it needs to identify the root cause of inconsistencies or anomalies. Whether it's internal QA, external audits, or cross-functional handoffs, you’ll always know **what happened, when, and by whom**.

### Operational efficiency and troubleshooting

Instead of wasting time verifying the source of a data point or tracking down errors manually, you get everything you need to investigate, validate, and resolve issues at a glance.

No guesswork. No redundant meetings. Just clarity.

***

## What's included with each record

<table><thead><tr><th width="204.2421875">Data Detail</th><th>What You Get</th></tr></thead><tbody><tr><td><strong>Who</strong></td><td>Name or email of the user who performed the data extraction</td></tr><tr><td><strong>When</strong></td><td>Timestamp of when the data was extracted</td></tr><tr><td><strong>Where</strong></td><td>The source URL from where the data was captured</td></tr><tr><td><strong>Screenshot</strong></td><td>Screenshot of the web page as it appeared during the data extraction</td></tr></tbody></table>

## The value it brings

* &#x20;Enhances data governance for regulated industries
* &#x20;Improves confidence in data-driven decisions
* &#x20;Strengthens collaboration across teams through transparency
* &#x20;Accelerates troubleshooting by removing ambiguity

With **Proof of Record™**, you're not just capturing data, you’re capturing **context**. That context becomes your safety net, your audit trail, and your competitive edge.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pline.ai/features/proof-of-record.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.