> For the complete documentation index, see [llms.txt](https://docs.sentinel1.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sentinel1.tech/02-specifications-urs-and-traceability/dscsa_audit_pitch.md).

# DSCSA Audit Pitch

## Why This Matters

Many DSCSA workflows appear to pass locally but fail regulatory integrity checks once data is serialized, transmitted, and re-read downstream.

This quick audit focuses on ALCOA+ integrity, especially:

* Accurate
* Contemporaneous

## What We Audit

* EPCIS event formatting and payload completeness
* GS1-128 scan string consistency
* Transaction Information (TI) field presence
* Transaction Statement (TS) continuity
* Hash-chain continuity in audit logs

## Ghost Data Risk

If a serial event is scanned but TI or TS is malformed or missing, inventory may become non-verifiable during recalls or investigations.

Business impact:

* Product value at risk
* Delayed response during verification events
* Increased compliance exposure

## Visual Example: Format Mismatch

| Signal                   | Scanner UI   | Backend Integrity | Compliance Outcome  |
| ------------------------ | ------------ | ----------------- | ------------------- |
| Scan event accepted      | PASS         | FAIL              | At risk             |
| TI present but malformed | PASS         | FAIL              | At risk             |
| TI missing               | PASS/UNKNOWN | FAIL              | Quarantine required |
| Hash chain valid         | PASS         | PASS              | Defensible          |

## Common Failure Pattern

* Device records scan data
* TI is missing or malformed
* System still marks transaction as complete
* Downstream verification fails

## Offer: Baseline Integrity Report

Fixed price: $500

Deliverables:

* 1,000-line audit of DSCSA serialization logs
* Gap Analysis for vendor remediation
* Priority defects list with compliance impact
* Integrity verification summary

Guarantee: If zero errors are found, the audit fee is waived.

## Positioning Statement

"I am not replacing your system. I am auditing your data integrity so your current vendor can fix defects before DSCSA 2026 enforcement pressure peaks."

## Technical Terms for Credibility

* EPCIS
* GS1-128
* 21 CFR Part 11
* VRS

## Suggested Close

"Would you like a baseline report first, or a deeper vendor escalation package after the baseline run?"


---

# 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 dynamically by asking a question.

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

```
GET https://docs.sentinel1.tech/02-specifications-urs-and-traceability/dscsa_audit_pitch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.