Onboarding readiness handoff between the hiring manager and IT

Each manager submission creates one readiness row, posts an actionable IT handoff, and sends the manager a receipt without changing any account or permission.

Starter: When a form response comes in (your manager-to-IT onboarding handoff Form)

1. Capture the handoff in a SheetSheetsUse the Sheets 'Add a row' step to record the new hire, manager, start date, requested systems, equipment status, and any unresolved dependency from the Form response.
2. Notify the IT onboarding spaceChatUse the Chat 'Post in a space' step to post a concise handoff summary to an existing onboarding space, including the start date and the outstanding items that need an owner.
3. Confirm receipt to the managerGmailUse the Gmail 'Send an email' step to confirm that IT received the request and restate the captured start date and named follow-up owner.

• New hire — Name and work email from the onboarding Form. (e.g. Priya Shah)
• Start date — The confirmed first working day. (e.g. 2026-09-01)
• Requested systems — The manager's requested access list. (e.g. Google Workspace, Jira, VPN)
• Outstanding dependency — Anything still blocking readiness. (e.g. Laptop delivery pending)

Paste this draft into Google Workspace Studio's Describe it with AI box, then review and adjust the flow it builds. This is Google's Gemini feature — CertPilot does not run any AI.

• An eligible Google Workspace edition with Workspace Studio and Gemini enabled by your admin.
• Access to Sheets, Chat, and Gmail (subject to your admin's Studio step controls).
• A manager-to-IT onboarding Google Form, an Onboarding Readiness Sheet, and an existing IT onboarding Chat space.

Security notes

• Keep the Form, Sheet, and Chat space limited to staff who need onboarding details; do not collect passwords, private keys, or other secrets.
• Use only the minimum personal data needed for the handoff, and keep external recipients out of the Chat space unless approved.
• Subject to your admin's Studio controls, DLP, and external-user approval policy.

What it does not do

• Does NOT create, configure, suspend, or license a Google Workspace account.
• Records requested access but does NOT grant access to any system or Drive folder.
• Chat cannot create a space — the flow posts to an existing one.
• The Sheet is the readiness record; the flow does not verify that each task was completed.

• Workspace Studio test runs take real actions — this test really writes a Sheet row, posts to Chat, and sends an email.
• Submit a fictional hire using your own email, a test Sheet, and a test Chat space.
• Confirm that the same start date, system list, and outstanding dependency appear correctly in all three outputs.

Primary source

Last verified 26 August 2026

Related recipes

• New-hire welcome pack (welcome email, Drive folder, induction meeting)
• Existing Chat-space onboarding notification and admin follow-up
• Helpdesk request intake (log to a Sheet, notify Chat, acknowledge by email)

← All Workspace Studio recipesBuild your own flow blueprint