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

# Document Classification

> Classify and validate document types for quality control before extraction or downstream review workflows.

### Overview

Document Classification is a workflow that classifies and validates document types for quality control so teams can confirm the right documents were submitted, are readable, and meet basic requirements before downstream processing.

It supports a fast QC step — document type identification, validation, confidence scoring, and issue flagging — in one streamlined workflow.

**What you get:** a structured table of document classifications and validation results you can review, edit, and export.

<Tip>
  To set up the workflow (creating sessions, uploading documents, running a workflow, and exporting), see [Setting Up a Workflow](/workflows/setting-up-a-workflow) for a comprehensive guide.

  This page focuses on what's specific to **Document Classification**.
</Tip>

### When to use Document Classification

Use this workflow when you need to:

* Confirm submitted documents match required types (e.g., ID, bank statement, payslip, utility bill)
* Detect missing or incorrect document types early
* Flag low-quality scans (blurred, cut off, unreadable pages)
* Standardise document intake before extraction or review workflows

### Step-by-step usage

<Steps>
  <Step title="Select the template">
    Navigate to **Workflows** > **Template gallery** and select **Document Classification**.
  </Step>

  <Step title="Upload documents">
    Upload the documents to classify (PDF recommended; other formats supported depending on your setup).
  </Step>

  <Step title="Run the workflow">
    Click **Run** to begin classification and validation.
  </Step>

  <Step title="Review results">
    Review the document types and validation results.
  </Step>

  <Step title="Export results">
    Export results (CSV or Excel) for reporting or downstream processing.
  </Step>
</Steps>

### Inputs

* **Required:** access to [alk.wamiri.com](http://alk.wamiri.com)
* **Required:** stable internet connection
* **Required documents:** documents to classify (PDF recommended)

### What's specific to Document Classification

1. **Confidence helps prioritise review.**
   Use the confidence score to quickly spot classifications that need manual confirmation.
2. **Validation is for QC, not content correctness.**
   Validation should focus on whether the document appears to be the expected type and is usable (readable/complete), not whether the information inside is accurate.
3. **Issues should be actionable.**
   Use clear, specific remarks (e.g., "blurry image", "missing page 2", "document type mismatch").

### Standard fields (default columns)

| Field                 | Description                                                                                                           | Field Type  | Task Type      |
| --------------------- | --------------------------------------------------------------------------------------------------------------------- | ----------- | -------------- |
| **Document Type**     | Predicted document type (e.g., ID, bank statement, payslip, utility bill, contract, invoice).                         | Select/Text | Classification |
| **Validation Status** | QC outcome for the document type and usability (e.g., Valid, Needs Review, Invalid) with a brief reason if needed.    | Select/Text | Validation     |
| **Confidence**        | Confidence score for the predicted document type (0–100 or Low/Medium/High depending on your setup).                  | Number/Text | Classification |
| **Issues / Remarks**  | Notes on problems affecting usability or correctness (e.g., unreadable, cut off, duplicate, missing pages, mismatch). | Text        | QC Notes       |

### Customising Document Classification columns

You can tailor columns to match your intake standards.

* Add columns for required-by-process checks (e.g., "Required? (Y/N)", "Meets minimum pages?", "Contains signature?", "Has stamp/seal?").
* Add columns for routing (e.g., "Next step", "Re-upload required", "Assigned reviewer").
* Keep column names clear and unambiguous to improve classification consistency.

### Important Notes

* Always manually review low-confidence classifications.
* If validation issues are frequent, tighten document submission instructions (format, scan quality, page completeness).
* If a field is consistently wrong, simplify the column name or add a short instruction to the column prompt.

## Related articles

* [Setting Up a Workflow](/workflows/setting-up-a-workflow)
* [How To Add Custom Columns](/workflows/setting-up-a-workflow#how-to-add-custom-columns)

## Need help?

If you run into issues, contact the Wamiri support team at [support@wamiri.com](mailto:support@wamiri.com). Include:

* What you were trying to do
* What happened instead
* Any error messages
* Steps to reproduce
* Screenshots or recordings (if available)