> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to collect client documents and consent in advance
- URL: https://blog.jestor.com/collect-client-documents-and-consent/
- Published: 2026-09-16T18:55:02.000Z
- Updated: 2026-09-16T18:55:02.000Z
- Author: Bruno Bannach

To **collect documents and consent** before a scheduled appointment, the request has to be easy enough that people complete it on a phone. In **Jestor**, an update link writes to the existing record without requiring an account, and permissions restrict who can see what was submitted.

## Why paperwork happens at the counter

Documents are collected on arrival because that is when the person is captive. The cost is a queue, a rushed process and forms completed carelessly.

It also means a missing document is discovered at the worst moment, when the appointment is about to start.

What advance collection improves:

- Queues caused by paperwork rather than service
- Missing documents discovered on arrival
- Forms completed in a hurry at a counter
- Consent recorded on paper that has to be filed
- No way to know in advance who is unprepared

## What to request in advance

| Item                     | Why in advance                          |
| ------------------------ | --------------------------------------- |
| Identification           | Verified before arrival                 |
| Registration details     | Typed by the person who knows them      |
| Required documents       | Missing items chased with time to spare |
| Consent                  | Read properly rather than skimmed       |
| Preparation instructions | Confirmed as received                   |

## Step by step to structure it

1. **Create the record** when the appointment is scheduled.
2. **Send an update link**, which writes to that record rather than creating a new one.
3. **Keep the form short**, using conditional fields so each person sees only what applies.
4. **Accept photos of documents**, since that is what people have to hand.
5. **Use OCR to extract details**, with a person validating.
6. **Show a readiness status** per appointment, so gaps are visible in advance.
7. **Restrict access** to the submitted data by role and field.

## Why the update link matters for privacy as well as tidiness

A public form that creates records invites duplicates and, worse, leaves you matching submissions to people. A link tied to a specific record writes only to that record, which keeps the data organized and limits what any single link exposes.

## Why choose Jestor

In **Jestor**, update links write to an existing record without requiring an account, forms support conditional fields so they stay short, **OCR** extracts details from photographed documents, permissions apply per role, field and action, and a readiness status can be calculated from what has been received.

## Frequently Asked Questions

### Does the person need an account to submit?

No. An update link works without a login. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### How do I know who is unprepared before they arrive?

Through a readiness status calculated from the documents received.

### Can access to submitted data be restricted?

Yes, per role, field and action.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.