How to collect 40 passports and consent forms without chasing anyone
Every group departure has the same last two weeks. Thirty-six of forty forms are in. The remaining four belong to families who are not ignoring you — they opened the email on a phone, at a bus stop, meant to do it later, and later never came.
So somebody on your team spends a fortnight on it. That fortnight is the actual cost of document collection, and almost none of it is spent reading documents.
Why it fails, specifically
The ask arrives where nobody can act on it. An email asking for a passport scan requires a laptop, a scanner or a decent camera app, and a moment of calm. It gets read in none of those conditions.
Nobody knows their own status. A parent who sent a passport six weeks ago has no way to check whether the medical form is still outstanding. So they either do nothing, or they email you to ask — which is worse.
The chase is manual. Someone reconciles a folder against a spreadsheet and writes personal reminders. That work scales linearly with the group, which is exactly the wrong shape.
What changes the numbers
Ask in the channel they already use. A message on WhatsApp asking for a photo of a passport gets answered in the queue at the supermarket. The phone that receives the request is the phone with the camera.
Make status visible without asking. One link, always current: received, received, still needed. This kills the "what do you still need from me?" email, which is a surprising share of the volume.
Chase on a schedule, not on a mood. (How the automatic chasing works.) Three automatic reminders — three weeks, ten days, four days out — going only to the people actually missing something. Predictable, unemotional, and nobody on your team has to decide whether today is the day to nag a client.
Let the group leader see their own group. (Setting up groups and leaders.) On a school trip, the teacher will chase harder than you ever will, but only if they can see who is outstanding. Give them a page for their group and the work does itself. This is the single biggest lever, and most agencies never pull it.
Name the documents in your own words
"Voucher" and "document" mean nothing to a parent. "Signed medical form", "Passport photo page", "Ski insurance certificate" mean something. If your system only offers fixed categories, you will spend the whole trip translating between its vocabulary and your travellers'.
The label should be whatever the organiser would say out loud. Add a sentence of description and, where a form has to come back signed, the blank form attached to the request.
Handle minors deliberately
For under-18s the document belongs to the child and the consent belongs to the guardian. That means the request goes to the parent, the file is filed against the child, and the group leader can see the status without seeing the passport itself. Getting this wrong is not a UX problem — it is a data protection problem. See where your data lives, and who can see it.
What "done" should look like
On the morning of departure, the organiser opens one page and sees forty green rows. Not a folder they have to reconcile. Not an inbox they have to search. A list, complete, with the two exceptions flagged and already escalated.
That is an achievable standard, and the last fortnight of a group departure is where you get the time back.
Viaquo collects documents in the traveller's own chat, tracks each requirement per person, chases the stragglers automatically and gives every group leader a live page for their own group.
