Architect client document checklist: what to collect before design starts

Most project delays at kickoff are not design problems. They are missing paperwork: a survey the owner thinks is “somewhere in a drawer,” a zoning letter the previous owner received years ago, or a set of original drawings that exist only as a roll of prints in a basement. Until those arrive, you can't confirm setbacks, check what is already permitted, or price the work with confidence. This guide lists what to ask clients for, why each item matters, and a simple way to collect it without a long email thread.

The core checklist

Ask for each document by name. “Send us anything you have on the property” tends to produce a few photos and nothing else.

Depending on the project, you may also want HOA or condo board rules, prior inspection or engineering reports, and contact details for anyone else involved (contractor, lender, building manager).

Why kickoff documents are slow to arrive

A simple collection process

  1. Start from a template. Create one request per project with each document as its own item. Separate items make it obvious which ones are still outstanding.
  2. Mark what is optional. Not every project has existing drawings or a zoning letter. Marking those optional, and letting the client mark an item N/A, keeps the request from stalling on documents that don't exist.
  3. Send one link. The client opens it on a phone or computer and uploads each file next to its name. Site photos can be taken with the phone camera straight from the upload page.
  4. Let reminders do the follow-up. Reminders list only the documents still missing and stop once the request is complete.
  5. Download the project file. When everything is in, download one ZIP with a folder for each checklist item, ready to drop into your project directory.

How FilesDue handles this

FilesDue includes an Architect project kickoff template with six items: Property survey / site plan; Existing drawings / as-builts (optional); Zoning / permit documents (optional); Photos of existing conditions; Program / requirements brief; and Budget outline (optional). You can rename, remove, or add items for each project — for example, add “Deed or title report” and “Signed agreement.”

Clients don't create an account. Reminders go out on day 2, 5, and 9 after you create the request, then weekly, and each one lists only what is still missing. Clients can pause reminders from the email, and you can pause them from your dashboard. If an upload isn't what you needed — the wrong survey, or a photo that is too blurry to use — you can send the item back with a short reason, and the client gets an email asking for a new file.

Each file can be up to 100 MB, with up to 500 MB per request. The upload page accepts PDF, images (including iPhone HEIC), Word, Excel, CSV, and ZIP files. For CAD files, ask clients to put them in a ZIP or send a PDF export.

Tips for architects

Frequently asked questions

Do clients need an account? No. They use the link you send. It is a long, unguessable link tied to that one request.

How many projects can I run at once? Solo ($15/mo) includes 25 active requests; Pro ($29/mo) has no limit on active requests. See pricing for details.

Is there a general template I can adapt? Yes. See our client document request template guide.

Start collecting project documents with FilesDue — 14-day trial (card required; cancel before first charge) →

← FilesDue home