> ## Documentation Index
> Fetch the complete documentation index at: https://docs.puddin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Generating and Sharing Verification Reports in Puddin

> Generate, download, and share verification records for student submissions, and understand what each report contains for academic integrity use.

A verification report is Puddin's formal summary of the writing process evidence captured for a submission. It documents the authorship record in a structured, shareable format — useful for your own records, for academic integrity reviews, for appeals processes, or wherever a portable record of the writing process is needed.

## What a verification report contains

Every report generated from a Puddin submission includes the following sections:

<CardGroup cols={2}>
  <Card title="Submission Details" icon="file-lines">
    Student name, assignment title, course, submission timestamp, and total document word count.
  </Card>

  <Card title="Writing Session Log" icon="clock">
    A table of all writing sessions with start time, end time, duration, and word count at session close.
  </Card>

  <Card title="Process Summary" icon="chart-bar">
    Total active writing time, average writing speed, revision count, paste event count, and total pasted characters as a proportion of the final document.
  </Card>

  <Card title="Paste Event Record" icon="clipboard">
    A full log of every paste event, including the pasted content, document position, and timestamp.
  </Card>

  <Card title="Revision Overview" icon="pen-to-square">
    A summary of revision activity, including total deletion count and a log of significant revision sequences.
  </Card>

  <Card title="Timeline Snapshot" icon="timeline">
    A visual representation of the document's development over time, showing word count growth and key events.
  </Card>
</CardGroup>

<Info>
  Verification reports capture the writing process evidence exactly as recorded. They are a factual record of how the document was created. Interpretive conclusions — whether a submission meets the requirements of your academic integrity policy — remain a matter for your institution.
</Info>

## Generate a report

<Steps>
  <Step title="Open the submission">
    Navigate to **Assignments**, select the assignment, and click the student's name to open their submission.
  </Step>

  <Step title="Open the Reports panel">
    Click the **Reports** tab in the submission view toolbar, or select **Generate Report** from the action menu (the **⋯** button at the top right of the submission page).
  </Step>

  <Step title="Choose the report scope">
    Select what to include in the report:

    * **Full report** — includes all evidence types: sessions, paste events, revisions, writing speed, timeline, and process summary.
    * **Summary report** — a condensed one-page version with the Process Summary and Session Log only, suitable for quick reference.
    * **Custom report** — select the specific sections to include. Useful when sharing a report in a context where only certain evidence types are relevant.
  </Step>

  <Step title="Generate and preview">
    Click **Generate Report**. Puddin compiles the report and opens a preview in the browser. Review the contents before downloading or sharing.
  </Step>
</Steps>

## Download or share a report

From the report preview, you have three options:

<CardGroup cols={3}>
  <Card title="Download as PDF" icon="file-pdf">
    Export the report as a formatted PDF document. Suitable for attaching to correspondence, submitting to an integrity committee, or storing in institutional records.
  </Card>

  <Card title="Shareable link" icon="link">
    Generate a secure, read-only link to the report. The recipient can view the full report in a browser without needing a Puddin account. Links expire after 30 days by default; adjust the expiry in the sharing settings.
  </Card>

  <Card title="Export as JSON" icon="code">
    Download the raw report data as a structured JSON file. Use this for integration with institutional data systems or when you need to process the data programmatically.
  </Card>
</CardGroup>

<Warning>
  Reports contain student writing data and personal information. Share them only with people who have a legitimate need to review them under your institution's data handling policies.
</Warning>

## Understand the report structure

When reviewing a generated report, here is how to navigate the key sections:

### Process summary banner

The banner at the top of the report surfaces the four most relevant signals from the evidence record at a glance: total writing time, paste proportion, revision count, and session count. These figures provide an immediate orientation before you read the detail.

### Session log table

Each row represents one writing session. The **Δ Words** column shows how many words were added or removed during that session. A session with a large positive delta and high paste volume in the same time window is worth examining in the Paste Events section.

### Paste events log

Each paste event entry includes the pasted text in full. Long entries are collapsed by default in the PDF — look for **\[Show full content]** markers in the browser preview or the JSON export for complete text.

### Timeline snapshot

The timeline image shows the document's word count plotted over absolute time. Steep upward steps indicate rapid word count growth; flat periods indicate pauses or sessions with net-zero changes. Downward steps indicate sessions where more text was deleted than added.

## Access historical reports

All reports you generate are stored in the submission's **Reports** tab. To find previously generated reports:

1. Open the submission from the **Assignments** panel.
2. Select the **Reports** tab.
3. All prior reports are listed with the date they were generated, the report scope, and the generating teacher's name.

Click **View** to reopen any historical report in the browser, or **Download** to export it again as a PDF.

<Tip>
  If you generate multiple reports for the same submission over time (for example, as part of an ongoing review process), Puddin keeps all versions. Each report is a snapshot of the evidence at generation time — the underlying process record never changes once a submission is sealed.
</Tip>