# Unforged Nib for logistics: proof of delivery from a driver's phone

> Unforged Nib checks the driver's photo of the signature against the recipient's own references, so a disputed delivery comes with reasons.

Source: https://unforged.ai/nib/use-cases/logistics

**The problem:** Proof of delivery is a squiggle on a phone, until it's disputed.

## What you send

- The driver's photo of the signed delivery note or screen
- The recipient's reference signatures
- Your reference, such as the consignment number

## What you get back

- A verdict: one of six, from AUTO APPROVE to NO SIGNATURE
- A probability from 0 to 1, with a band
- Plain-language reasons you can show an auditor
- The policy and version that produced it

## How it fits your process

1. **Enrol regular recipients** (API): Enrol reference signatures for the accounts you deliver to.
2. **Send from the driver app** (API): Your app sends the photo when the driver closes the delivery.
3. **Or batch at the end of the day** (bucket drop): Drop the day's photos and a manifest in your bucket instead.
4. **Answer a dispute** (API): Pull up the check by consignment number, with its verdict and reasons.

## Decisions that matter

- **UNREADABLE**: A blurred photo: ask for a retake. Free.
- **NO SIGNATURE**: Nobody signed. Catch it early. Free.
- **FLAG**: Someone looks before a claim is settled.

## What it reads

Phone photos. Up to 50 MB and 200 pages.

$0.50 per check, pay as you go. [How Unforged Nib works](https://unforged.ai/nib/product).
