Keys, access, and room changes

Also called key issue form, building access request, classroom move request

Requested by staff, approved by their supervisor, and issued by whoever handles keys, with a signature for every key and a record of who holds it. We build it to work the way you track keys and access now.

Video coming

Start to finish

From the request to who holds which key.

Here’s how it runs in Flow Forms. The steps marked on its own happen without anyone, and everyone else is notified when it’s their turn.

  1. 1
    The staff member

    Fills it out on any device: a key, building access, or a room change, and why. The form only asks what applies, so a room move skips the questions about badges.

  2. 2
    Their supervisor

    The principal or department head approves it from any device, or sends it back with a note. If they’re out, it goes to their backup.

  3. 3
    Whoever issues keys

    Issues the key, sets up the access, or schedules the move, and records which key or badge went to whom. If it sits, reminders go out.

  4. 4
    The staff member, signing

    Signs for the key or badge when they pick it up, on any device.

  5. ✓
    On fileOn its own

    The record keeps which key or access went to whom, who approved it, when, and when it came back. If anyone edits it later, the edit is logged.

What it handles

The details, built in.

  • Who holds which keyEvery key issued and checked back in, by person, building, or key, whenever you need it.
  • Checked back inWhen a key comes back, it’s marked returned on the same record, so who holds what stays current.
  • A signature for every keySigned when it’s picked up, on any device.
  • Approved before it’s issuedThe supervisor signs off before anything is handed out.
  • When someone leavesWhat they hold is on record, for whoever collects keys when someone leaves.

Yours needs something that isn’t here?

Bring it to the first call. We’ll build it in while you walk us through how it works.

Book a conversation →

Or see what’s included with every process →

How it varies

Every organization tracks keys and access a little differently.

We don’t start from a standard key request. We start from how yours runs today. And when something changes, like a new building or a new level of access, tell us and we change it.

We build it to yours.

  • What can be requestedKeys, badge access, after-hours access, alarm codes, or a room change.
  • Who approvesThe principal, a department head, or a security officer for master keys.
  • Who issuesFacilities, a locksmith, IT for badges, or the building office.
  • Master and restricted keysA second approval, or a different path entirely.
  • Districts and officesA district often routes by building. A city or county often routes by facility or department.

Questions

About keys, access, and room changes.

Can we see who has which key?

Yes. Every key issued and every key checked back in is on record, so you can see who holds what by person, building, or key.

Can staff sign for a key when they pick it up?

Yes. They sign on any device, and the signature is kept with the record.

Can master keys need a second approval?

Yes. Requests route by what’s asked for, so a master key can go to a second approver.

Does this program our badge system?

No. Whoever manages badges sets up the access. The request, the approval, and the record of who has what live here.

Bring us yours.

We’ll build it with you.

Tell us how keys and access get requested now, who approves them, and how you know who has what. Not a demo. A conversation about your process.

Book a conversation