Skip to content

Document collection before a deadline

Synthesized from the base patterns professional-services pack

Asks every client for their documents each week until a deadline, with a link where they upload photos or PDFs. Anyone who hasn't uploaded when the final week starts goes on a call list for your team. Your team marks a client's documents complete once reviewed.

  • Accountants, tax advisers, immigration consultants or bookkeepers who need the same set of documents from many clients by a date.
  • Clients send things late, by WhatsApp photo or email attachment, and you spend days chasing.
  • You want one upload page, and a clear list of who is still missing.
HowWhat
A CSV uploadYour client list as a CSV: phone, email, first name, and a documents_status column set to pending. Imported once for each round of collection.
A Google Sheet or Excel file, syncedOr the client list as a synced sheet. If you sync, update the sheet's documents_status when clients upload, because every sync writes the sheet's value over the profile.
A form people fill inThe Upload your documents form this playbook creates, with a file question for each document you need. Clients open it from a link in the reminders.
A form your staff fill inA Documents reviewed form your team fills when a client's documents are checked, matched by phone.
KindNameWhat it doesLands
TeamAccountsCalls clients who are still missing documents in the final week.Empty
FormUpload your documentsThe upload form, with a file question for each document. A hidden field marks the client as having sent documents.Draft, not published
FormDocuments reviewedStaff form to mark a client's documents as checked and complete. Matched by phone.Draft, not published
SegmentDocuments pendingClients who owe documents (status pending).Ready
TemplateDocuments reminder (email)Weekly reminder email with the upload link.Ready
TemplateDocuments reminder (SMS)Weekly reminder SMS with the upload link.Ready
Follow-upDocuments: weekly reminderWeekly email and SMS to clients whose documents are pending, from the first reminder date.Off
Follow-upDocuments: final-week callsOne run at the start of the final week; a call task for each client still pending.Off
#QuestionDefaultFills in
1What should messages call your firm?none, must answerorg_name
2Which documents do you need? (one upload question each on the form)
One per line. A short id (letters, no spaces) and the name clients will see.
Valid ID, Bank statements, Income recordsdocuments
3What is the deadline? (as you'd say it in a message)none, must answerdeadline_label
4When should the first weekly reminder go out?
A date and time like 2026-11-16T09:00 in your time zone. Reminders then repeat every week.
none, must answerfirst_reminder_at
5When should the call list be created for clients who still haven't uploaded? (the start of the final week)
A date and time like 2026-12-28T09:00 in your time zone.
none, must answerfinal_call_at
6Which team calls clients who are still missing documents? (it can be just you)Accountsaccountant_team

These have defaults. Change any that don’t fit.

SettingDefaultKey
Number of weekly reminders6reminder_weeks
What the documents are for, as messages say ityour filingwhat_for
Sender address‹workspace default_sender›email_from
Hours to make each call48call_due_hours
Time zone for the schedules‹workspace timezone›timezone
Default phone country on the forms‹workspace country›default_country
Greeting when a first name is missingtheregreeting_fallback
  • Weekly reminders by email and SMS, starting ‹First reminder (date and time)› (‹workspace timezone›), 6 of them, to every client whose documents_status is still pending.
  • Clients who upload stop being reminded straight away (the upload form changes their status). Clients whose documents your team marks complete stop too.
  • On ‹Final-week call list (date and time)› a call task is created for each client still pending, due in 48 hours.
ChannelNeeded forBefore it can send
emailThe weekly reminderA verified sending domain for ‹workspace default_sender›.
smsThe weekly reminder, shorterAn SMS provider, or Origamy managed SMS after business verification (KYC).
  1. Import your client list as a CSV with phone, email, first name and documents_status = pending, for the clients who owe documents. Only clients with pending are reminded. If you sync a sheet instead, remember the sync overwrites documents_status.
  2. Add people to the Accounts team. A task assigned to an empty team reaches nobody.
  3. Publish the Upload your documents form (check each document question, and the file types and size limit) and the Documents reviewed form. Bookmark the review form for your team.
  4. Check the dates: the first reminder, how many weeks to repeat, and the final-week call list. They are one-off settings, so for next year's deadline run the playbook again with new dates.
  5. Verify the sending domain, connect an SMS provider or finish business verification, then switch the follow-ups on. Test with your own phone and a test client set to pending.
  6. Tell clients where their files go and who can see them, and follow your local data protection rules for identity documents.
  • Clients already send documents as WhatsApp photos. Keep doing that if it suits them, but ask them to use the upload page when they can: it puts every file in one place under their name, and it is what stops the reminders.
  • Phone photos are large. The form accepts PDF, JPG and PNG up to 10 MB each; raise the limit in the form builder if your clients send scans.
  • Identity documents and financial records are sensitive. Say on the form who sees the files and how long you keep them, and give workspace access only to the people who need to see the answers.
  • For a long deadline, start the reminders about six weeks out. Most clients answer the first or second reminder, so the call list in the final week is usually short.

This playbook is synthesized: no customer has run it with us yet. If you build it, tell us what you changed, and we’ll replace it with the real version.

The request used to test the copilot on this playbook (a live eval):

We're accountants and we need clients to send us their documents by 15 January. Make an upload page with places for their ID, bank statements and income records. Email and text everyone who hasn't uploaded every week, starting on Monday 16 November at 9am. On 28 December, give our team a task to call anyone who still hasn't sent them. Our clients are in the documents_status trait as pending.

It passes when every piece is a valid draft and everything lands off, with at least: form, segment, workflow, message_template. It must never use: discount, tax owed.