Access Removal Request — shared by the community

Who this template is for

Access Removal Request is built for engineering, IT and product teams who need to route technical requests with the context needed to triage them.

• Engineering, IT and product teams working in technology, saas & dev.
• Teams who need to route technical requests with the context needed to triage them without writing code or paying for a custom build.
• Anyone replacing vague reports that can't be reproduced or prioritised with one structured record per enquiry.
• Respondents are users, testers and internal stakeholders — the form asks them 24 questions across 2 screens.

Why this form is useful

It removes the cost of vague reports that can't be reproduced or prioritised and turns each submission into a record your team can act on immediately.

• 17 questions are required, so submissions arrive complete instead of needing a follow-up email.
• It records a signature you can keep as proof of agreement.
• It pins the request to a specific date.
• Conditional logic hides 4 questions until they are relevant — shorter forms convert better than long ones.
• Splitting the form across 2 pages keeps each screen short and shows respondents how much is left.
• Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

1. 1Press “Use this template” — a fresh copy of Access Removal Request lands in your workspace, ready to edit.
2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
4. 4Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
5. 5Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 4 conditional rules ship with it.

• Features conditional validation: if “Is this an immediate departure?” is Yes, “Who to contact before anything is removed” becomes mandatory before the form can be sent.
• Features conditional validation: if “Does their email need forwarding?” is Yes, “Who receives their email, and for how long” becomes mandatory before the form can be sent.
• Features conditional validation: if “Do they hold keys, cards or building access?” is Yes, “What needs recovering, and from where” becomes mandatory before the form can be sent.
• Features conditional validation: if “Were they an approver in any system?” is Yes, “Which approvals, and who takes them over” becomes mandatory before the form can be sent.
• All 4 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.