同意是一条记录，不是一个勾。
报名时的一个勾，被用来覆盖将要发给院校、家长、分支代理和邮件名单的整份档案。它撑不住。
Visatory · · 阅读 4 分钟
本文尚未翻译。下方正文为英文，上方的标题和摘要则不是。
Ask most offices where a student's consent is held and the answer is a tick on the intake form. Ask what the student consented to and the answer gets vaguer, because the tick was collected once, at the beginning, to cover everything that would happen afterwards. By the time the file is being sent to a third institution, discussed with a parent who is paying, and passed to a sub-agent in another city, that single tick is being asked to carry four different permissions it was never told about.
The fix is not a longer form. It is treating consent as something that happens repeatedly and gets written down each time, in the same way a payment does.
They are separate permissions.
The permissions an agency actually relies on are distinct, and a student may reasonably grant some and refuse others.
- Holding the file at all, and for how long after the case closes.
- Sending the file, or parts of it, to a named institution.
- Discussing the case with a parent, a sponsor or a relative.
- Passing the case to a sub-agent or a partner office.
- Using the student's name, photograph or result in marketing.
- Contacting the student about services after the case has ended.
The last two are the ones that cause trouble, because they are the ones a student did not think they were agreeing to. A testimonial from a student who ticked a box about file handling is a testimonial with a problem in it.
What a usable consent record contains.
Four fields, and the fourth is the one that is usually missing.
- What was agreed to, in the words the student saw rather than a category name.
- When, as a date and time rather than a month.
- How: signed in the office, tapped on a form, replied to in an email, recorded during a call.
- The version of the text they agreed to, so it can be produced later exactly as it stood on that day.
Without the fourth field the record proves that somebody agreed to something. With it, the record proves what. That difference is the whole value, and it only exists if the wording is versioned rather than edited in place.
Withdrawal is part of the design.
A consent that cannot be withdrawn is not consent, and a withdrawal that only exists as an email in somebody's inbox is not withdrawn. The office needs a place to record it, a rule about what stops immediately, and a rule about what continues because a different obligation requires it.
Those two are genuinely different. A student who withdraws marketing permission should stop receiving marketing that day. A student who asks for their file to be deleted while an application is live is asking for something the case cannot survive, and the honest answer says so and explains what can be done instead.
Parents, sponsors and minors.
The person paying is frequently not the person whose data it is, and the two do not automatically share permissions. An adult student is entitled to decide what their parents are told, including when a parent is paying the fees, and an office that discloses by default because the payer asked has made a decision it never recorded making.
Where the student is under eighteen the arrangement is different again and the local rules differ by country. The practical point is the same either way: whatever the arrangement is, it should be written in the file rather than assumed from who signed the invoice.
The test worth running this week.
Pick a student who signed up eighteen months ago. Produce, in under a minute: what they agreed to, the exact wording as it stood that day, the date, and whether any of it has since been withdrawn.
If that takes an afternoon of searching, the problem is not the form. It is that consent was collected as an event and never designed as a record, and the only moment anybody notices is the moment somebody asks.
