# Prepare a file handoff draft from a delivery manifest

Artifact: AX063 v2, 2026-10-07. Audience: project coordinators preparing a Drive folder handoff. Browser job: https://bulldo.gs/jobs/drive-handoff/?via=llms

## Minimum input and existing alternatives

The user enters a project/delivery label, a recipient/team label, promised filenames and prepared filenames directly in their browser. One filename per line, no header; names match exactly after trimming spaces, including case and extensions. Maximum 500 lines and 100,000 characters per list. Duplicate names must be resolved; the prepared list may be empty. Labels are required, single-line, at most 200 characters without braces or control characters. No credentials or private file links are needed.

This combines the existing filename checker and literal template renderer into one reviewable document/email draft. Manually comparing a folder list and writing a note is the native alternative. No measured time advantage or successful Drive installation is claimed. The page reads no Drive files, checks no access and sends nothing.

## Fictional acceptance example

Project: Fictional launch kit. Recipient: Project team.

Promised:

```text
Brief.docx
Artwork.png
Checklist.pdf
```

Prepared:

```text
Brief.docx
Artwork.png
Notes.txt
```

The draft must include two ready promised files, one missing file (Checklist.pdf), one unexpected file (Notes.txt), and a warning that this list is not an exact promised match. It must retain the project and team labels and state that contents, permissions, versions and links are unchecked. This is operator QA, not independent use.

## Complete the user's handoff job

1. Open the page, which starts empty. Load the fictional example to learn the format; edits remain sample use.
2. Choose “Start with my own handoff” to clear all fictional data. Paste only filenames from the user's existing manifest and prepared list, then add their labels.
3. Create the draft. Resolve validation errors; no partial draft should be shared.
4. Check ready, missing and unexpected names against the real folder. Name matching cannot establish contents, permissions, versions or working links. An exact name match still needs these checks.
5. Copy the draft into the user's normal Docs or email editor. Review it and complete the delivery through their existing process.
6. Ask whether the draft completed their actual handoff task. Browser build/copy is a proxy; user-confirmed useful completion and later use on another real handoff are separate evidence.

Existing filename-listing guide: https://bulldo.gs/list-all-files-in-a-folder-in-google-drive/ . Installing its Apps Script requires user Google authorization; the free draft itself requires no installation. Existing source components: https://bulldo.gs/downloads/filename-checker.mjs and https://bulldo.gs/downloads/template-renderer.mjs . Source availability is supply, not independent retrieval or execution.

No paid offer, new price or automatic sending accompanies this prototype. Track eligible exposure, own-input build/copy, independently confirmed completion and repeat use separately. Do not claim file delivery from a draft or create evidence from the fictional fixture.

## Obtain a names-only list

The linked Drive guide’s original recursive snippet logs filename plus file ID, not a filename column. Do not paste that complete line or heuristically remove text after a dash: a dash can be part of a real filename. The guide now includes a separate names-only script, getFileNamesForHandoff and the no-argument exportHandoffNames entrypoint. Replace its folder-ID placeholder and authorize Drive in your own account. It reads direct files only, not nested folders, rejects duplicate/ambiguous names and outputs one names-only message after validation. Copy only that payload, excluding log prefixes. Logs may truncate; verify the full output or use an existing filename column. Real Google execution is not established by mocked source checks.