Split the tracking from the signing

Before building anything, decide which job Notion will do. It works well as a tracker for who received a slip, who signed, and what is still missing, but it can't collect a guardian signature you could rely on later.

You can keep paper slips, use the signing feature in your school's parent communication platform, or request signatures online with a tool like Loio, and then record the result in Notion or even leave links to the document's location for quick access.

Build two databases

Most teachers start with a single table of students and a checkbox. That can work well for one trip and fall apart by the third, because every new event means another column or another copy of the table.

Use two databases instead. Events, that has one row per trip or activity, with the date, location, cost, and slip deadline. And Consents, that holds one row for each student per event, connected to Events through a relation property. If you already keep a class roster in Notion, link Consents to it too, so names and guardian contacts stay consistent across the year.

Next, add a rollup to Events that shows the percentage of linked consents marked as signed. Each event now carries its own readiness score.

Separate "returned" from "ready"

A checkbox tells you whether something came back but it can't tell you whether the form is usable. Replace the checkbox with a Status property and these options:

• Not sent

• Sent

• Signed

• Incomplete, for forms missing a field, a date, or the right signature

• Declined

• Needs re-sign, for slips signed before the event details changed

Declined deserves its own option because a family saying no calls for a different action than a missing form does. That student needs supervision or an alternative activity on the day, and it's better to arrange that early than to keep chasing a signature that won't come.

Make sure the right person signs

Send requests to the contact on file

Always send signing requests to the guardian email or phone number the school already has. A student who is asked for a parent's address can just as easily type in their own, and that is the simplest way a forged approval gets through. In the US, guidance under FERPA and IDEA accepts electronic consent when the method identifies the signer and shows their approval.

Rules vary by country and district, so confirm what applies to your school.

Plan for more than one guardian

Some activities, especially overnight trips, need signatures from both guardians. Set a signing order so the second guardian receives the form after the first one signs, and use the Notes property to record which adults are allowed to sign. Keep that note short and factual.

Leave room for paper

Some families rarely check email, and others simply prefer paper. Set Method to Paper for those rows so they appear in the same views as everyone else and nobody falls outside the system.

Add views that answer real questions

Each view should answer one question you actually ask before an event.

1. Missing this week. Filter Consents to rows that are neither Signed nor Declined, then sort by working deadline.

2. Board by status. Group Consents by Status to see where forms stall.

3. Trip-day list. Filter to one event and Signed, then export it as a PDF for chaperones. A museum basement or a bus on the highway may have no signal, so an offline copy

Keep sensitive details out of the dashboard

Your tracker needs to know that a medical form is on file, not what the form says. Add a checkbox such as "Medical form received" and keep allergies, medications, and health conditions in the signed document or your school's official system.

Re-sign when the event changes

A signed slip covers the event described on it. If the date, venue, transport, or cost changes after families have signed, they agreed to a different trip. Mark the affected rows as Needs re-sign, send an updated form, and add a short change note to the event row so a colleague or substitute can see what changed and when.

Use your history to fix the route

After a term or two, your Consents database holds something paper never gave you, which is a record of how each family responds. Add a formula property that counts the days between Sent on and Signed on, then sort by it. The same few names will sit at the top, often alongside repeated Incomplete statuses.

Those families usually aren't careless, and in most cases the route simply doesn't suit them. A parent who signs paper on the same day but ignores email for a week should get paper. A family that returns half-filled forms may need a translated version or a two-minute phone call before the request goes out. Set Method and language preferences on the roster before the next event, and duplicate the previous event row as your starting template.