runbookify
← All plans
Logistics & Transportation / Delivery Scheduling & Proof of Delivery

White-Glove Delivery Checklist

Run a per-product white-glove checklist on every premium delivery - assembly, placement, debris removal, photos, condition notes - capture the customer's sign-off, and make ops review and approve before a job is marked complete and billable, so disputes end.

IntermediateA weekendBuilds onNext.js (App Router) on VercelSupabase (Postgres, Storage, Auth + RLS)Resend (email notifications)
What you'll build

An internal tool that opens a delivery job, runs the right per-product checklist (assembly, placement, debris removal, photos, condition notes), captures the customer's on-site sign-off, routes the completed job to ops for review, and only after approval marks it complete/billable and produces a clean proof-of-delivery report and CSV.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A list of delivery jobs you can export to CSV or keep in a Google Sheet (with a job/order ID, customer, address, and the product(s) being delivered)
  • Your white-glove checklist steps - even a paper or PDF version is enough to start
  • Free Vercel, Supabase, and Resend accounts (the plan walks you through each)
  • A weekend and a phone or tablet for the crew to capture photos - no coding experience needed

The problem this kills

A premium delivery isn't dropping a box on the porch. Your crew is supposed to carry it in, assemble it, place it where the customer wants, take away the packaging, and leave the room spotless - and the customer is paying for exactly that. Then, three days later, the call comes in: "There was a scratch on the table." "They never took the boxes." "Nobody assembled the bed frame." Now it's their word against a crew that's already on the other side of town, you have no photos, no signed acknowledgment, and no record of what was actually done. You eat the chargeback, the redelivery, or the refund - and you can't even prove the crew was at fault, or that they weren't.

The usual "system" is a paper checklist that gets lost, a few blurry photos buried in a tech's phone, and a signature scrawled on a clipboard nobody can find later. It doesn't tie to the job, it doesn't capture damage at the door, and it gives you nothing to push back on a dispute with.

What you'll build

A small, private web app for your white-glove crews and ops team that:

  • Opens a delivery job (from a CSV export or a Google Sheet) - job/order ID, customer, address, and the product(s) on it.
  • Loads the right checklist for each product - your own templates for "assembly," "placement," "debris removal," "photo set," and any per-product steps - so a sectional sofa and a treadmill get the steps each actually needs.
  • Lets the crew work the checklist on a phone: tick each step, snap the required photos straight into the job, and log any damage or exception with notes before anyone signs.
  • Captures the customer's sign-off on the device, on site, with their name and the timestamp - their acknowledgment that the work was done and the condition was noted.
  • Sends the completed job to ops for review, and only after a human approves does it mark the job complete and billable and produce a clean proof-of-delivery report plus a CSV you can hand back to your system.

What's inside the Implementation Plan

  • It starts by interviewing you about your business. Before building anything, the plan has the AI agent ask you about your real delivery process, your product types and their checklist steps, your job/order ID format, which photos are mandatory, how customers sign today, your typical and peak daily job volume, and your messy edge cases - then it tailors the data model, the checklists, and the rules to you. No generic template that assumes products and steps you don't deliver.
  • A copy-paste prompt for every step, in order, so you never have to know what to type.
  • A clean data model for jobs, per-product checklist templates, checklist runs, photos, damage/exceptions, sign-offs, and the approval log.
  • The full ops approval gate, audit trail, login, and per-org data isolation wired in from the start.
  • Duplicate protection so the same job/order can't be processed or billed twice.
  • A guaranteed "No API yet?" fallback - run the whole thing off a sheet and export CSV, today, with zero integrations.

The governance it includes (this is the point)

This isn't a throwaway script. The plan builds in the controls that make a tool safe to actually run your premium deliveries - and your disputes - on:

  • Login so only your team can open it.
  • Row-level security so each organization only ever sees its own jobs, photos, and customer data.
  • A complete audit trail - who ran which checklist, what photos were taken, who signed, who approved, and exactly when.
  • A hard human-in-the-loop gate - the crew and customer document the delivery, but nothing is marked complete or billable until ops reviews the checklist, the photos, and the sign-off and approves it.
  • Duplicate guards keyed on the job/order ID so re-importing or re-scanning the same job never double-bills.

Who it's for

White-glove and final-mile delivery teams, installation crews, and the ops managers who own them - anyone whose "delivery" includes assembly, placement, and cleanup, and who is tired of losing disputes because there's no proof of what the crew actually did. If you can export your delivery jobs to a spreadsheet and your crew has a phone, you can build this.

You've got this - paste the first prompt and let the agent interview you.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.