Custom contact fields: define your own, map them to requests, let crew fill them in

Every venue and planner tracks a few things about their crew that 1pm didn’t have a box for. A rigging supplier’s licence number. The expiry on a public liability cert. Shirt size for the front-of-house team. A radio callsign. Until now those lived in a spreadsheet or a notes field. Now you can define them properly, once, and reuse them across every event.

Define your own fields

Open Custom fields in the sidebar (it was “Contact fields”) and add the fields your operation actually uses. Each one has a type so the data comes in clean:

• Text, single line or multi-line, for names, callsigns, and free notes.
• Choice, a set of options you define, single-select or multi-select, rendered as radios or checkboxes.
• Date, with a native date picker, stored in a canonical format.
• Number, for counts like party size or table count.
• Time, stored as a tidy HH:mm.
• File upload, for a cert, a licence scan, or any signed document.

Drag the handle to reorder the list, and that order flows through everywhere the fields are shown. Fields only appear on a contact once they actually hold a value, so a contact you’ve captured nothing for stays clean rather than sprouting a wall of empty boxes.

Map a field to a request, and the answer lands on the record

This is the part that saves the double entry. When you build a crew request (or an event-wide request that goes to everyone), you can point it at one of your custom fields. The crew member answers it on their live link, and their answer writes straight through onto their contact record. Ask the AV supplier for a licence number once, and it’s on their contact for every future show, not buried in a one-off request thread.

It works for documents too: a request can save the latest uploaded file to a custom upload field, so the most recent public liability cert is always the one on the record.

Crew can correct their own details

There’s a lighter version of the same idea for the details 1pm already holds. A “linked” request lets a crew member self-update their own first name, mobile, website, or social handles straight from their live link, with the current value shown as the placeholder so they’re correcting, not starting from scratch. The contact form badges “Updated by {name} {date}” while the value still matches what they submitted, so you can see at a glance who fixed their own number instead of you chasing it. Email is deliberately left out: it keys the share link.

Totals where they’re useful, privacy where it matters

Number fields roll up per event on the planner page: sum the party sizes or table counts across an event’s contacts and you’ve got your figure without a calculator. Those totals are planner-only and never appear on a crew view.

Fields are safe to clean up, too. You can hard-delete a field only when nothing has been captured into it and no request points at it; otherwise 1pm keeps it and names what’s blocking the delete, and archiving stays the path for a field that’s in use. Nothing you’ve already collected disappears by accident.

Small thing in the same area

Contact links (a website, an Instagram handle, a LinkedIn URL) now resolve to a proper openable link whether you stored a full URL, a bare domain, an @handle, or just the handle. The icon row on the contact form and the inline modal turns each one into a real click-through.