Document Request

A checklist that counts approved, never uploaded.

PROGet Document Request and 168 other Pro components with pro lifetime — Get Pro

Category
Documents
Access
Pro
Source
1,114 lines · one file

The decision inside it

Progress counts approvals

Someone who uploaded all six files and had two rejected is not finished. A bar that reads 6 of 6 tells them a lie they discover a week later, when the deal is late.

When to use it

Use Document Request to ask someone for files: grouped items with hints and accepted types, upload progress, review, approve or reject with a reason, and a due date. The same component serves the requester and the person uploading (role).

Installation

How you get it

Paste this into Claude Code, Cursor, Codex or any coding agent. It installs the file and uses it as it is, instead of writing a new one.

Use Liro's Document Request for this.
Install it: npx shadcn@latest add @liro/document-request
(the @liro registry is set up in components.json, with LIRO_KEY in .env.local)
Import it from @/components/ui/document-request.
Do not rewrite or restyle it. Pass my data through its props
and keep its built-in states.

For the full brief with every prop and the mistakes assistants usually make, use Copy prompt above. Pro components install through the @liro registry with your CLI token: see the Namespaced tab.

Usage

components/kyc-request.tsx
import { DocumentRequest, type RequestPhase } from "@/components/ui/document-request";

const phases: RequestPhase[] = [
  {
    id: "company",
    label: "Company documents",
    items: [
      { id: "reg", label: "Certificate of incorporation", status: "approved" },
      { id: "tax", label: "Tax ID letter", status: "waiting", accept: [".pdf"] },
    ],
  },
];

export function KycRequest() {
  return <DocumentRequest title="Onboarding documents" counterparty={{ name: "Ada Moss", email: "ada@vertically.dev" }} phases={phases} role="requester" />;
}

API reference

“Copy prompt” above puts a full brief on your clipboard, install command, dependencies, props, and the mistakes an assistant usually makes with this component.

Props

Read from the component’s own TypeScript interface when the site is built, so this table cannot drift from the file you install.

TypeNotes
titlestring No–
counterparty{ name?: string; email: string; avatar?: string } NoWho is being asked, or who is asking — depends on `role`.
phasesRequestPhase[] No–
resourcesRequestResource[] NoRead-only material: signed contracts, guides, anything they may need but are not being asked to produce. Never mixed into the checklist.
dueAtDate | string | number No–
role"requester" | "responder" NoWhich side is looking. The responder uploads; the requester reviews. A responder must never land on a list containing the requester's own work.
sentboolean NoBefore sending, the list is editable. After, it is fixed.
onAddItem(phaseId: string, label: string) => void No–
onRemoveItem(item: RequestItem) => void No–
onApprove(item: RequestItem) => void No–
onReject(item: RequestItem, reason: string) => void No–
onUpload(item: RequestItem, file: File) => void | Promise<void> No–
onSend() => void | Promise<void> No–
onClose() => void No–
lookLook NoLayered sets the request in a tray, the heading above the card and its standing in the strip below. Flat is one card.

Dependencies

npm packages

clsxframer-motionlucide-reacttailwind-merge

Liro foundations, installed alongside it

liro-themeavatartooltip

Accessibility

  • Keyboard reachable throughout, in visual order
  • Focus trapped in overlays, Escape closes them
  • Focus returns to whatever opened it
  • Live regions announce what changed, not that something did
  • Honours prefers-reduced-motion

Responsive behavior

  • Sizes to its container, not the viewport
  • Usable from 320px up
  • Pointer-based interaction, so trackpad and touch both work
  • No hover-only affordances