Article

Track staff leave requests in Google Forms and Sheets

For small teams already using Workspace, collect leave requests, record private manager decisions and handle changes without another subscription.

Editorial illustration for Track staff leave requests in Google Forms and Sheets: a document represents the research briefing. Not documentary evidence.

A small team already using Google Workspace can collect planned leave requests through a restricted Google Form, store the responses in Sheets, and have a manager record decisions and reply privately. Submitting the form does not approve leave. If email and a private spreadsheet already capture requests and decisions reliably, keep that routine.

This guide uses documentation and public USD prices checked on November 22, 2026. The illustrative business is a US design studio with five nontechnical staff, including a deciding manager and an authorized backup, existing Workspace Business Starter accounts, desktop access and US$0 for additional software subscriptions. These are planning assumptions, not a customer case.

The proposed workflow covers planned full-day requests, decisions, changes and cancellations. It does not calculate entitlement, run payroll, prove attendance or collect medical records. No AI subscription, script or paid connector is needed; the manager still does the checking and communication.

Do you need a form, or is email enough?

Choose according to the missing step: consistent dates, repeat submissions, private access, traceable decisions or handling later changes. Also decide who maintains the record and covers the manager’s absence. A new form helps standardize intake; it does not remove that ongoing work.

Option and best fit

Added five-person subscription cost

Meaningful limit

Setup and ongoing work

Existing email plus a private Sheet: a reliable request-and-reply routine.

US$0 with the assumed existing accounts.

Someone must reconcile messages, dates and decisions.

Keep a decision register and private replies; little process change if already working.

Google Forms plus private Sheets: requests often omit necessary fields.

US$0 with the same existing accounts.

The proposed setup does not approve leave, calculate balances or send decision messages automatically.

Configure fields and access; assign IDs, check requests, record decisions and reply manually.

Zoho People Workforce: a need for configured approval routing and policy or balance management.

Conditional five-seat calculation: US$300 annually or US$30 on monthly billing, before tax.

Exceeds the zero-additional-budget baseline; minimum seats and local order eligibility remain unverified.

Configure people, permissions, existing policies and approval rules; check cancellation and export behavior.

The zero-added-cost options are not cost-free operations. At Google’s ordinary Starter list price of US$7 per user per month with a one-year commitment, billed monthly, five seats calculate to US$35 monthly before tax. That is the existing suite bill, not a new leave-tracker charge. Your agreement may differ; promotions, equipment, connectivity and staff time are excluded.

For Zoho, the November 22 USD pricing page shows Workforce at US$5 per user per month-equivalent, billed annually. The edition comparison shows US$6 per user on monthly billing. Assuming five seats can be purchased, 5 × US$5 × 12 = US$300 annually, versus 5 × US$6 = US$30 monthly, before local taxes or optional purchases. The annual equivalent is not a cancellable US$25 monthly subscription, and this bill would not replace Workspace.

The visible Free edition covers three users, not this five-person studio. Workforce includes time-off approvals; the displayed Essential HR and Talent columns do not. Confirm the edition, minimum order and regional quote before buying. These are conditional planning figures, not a five-seat checkout offer.

What should staff enter in the form?

Create an unpublished Form under the responsible work account. Keep it short. For this proposed design, use the following fields, supported by Google’s question types:

  • Name, if the work email alone is not enough to identify the requester.

  • Action: new request, change request or cancellation.

  • Start date and end date, using Date questions with the year included. For a change, enter the proposed replacement dates; for a cancellation, repeat the original dates.

  • Original request ID for changes or cancellations. Leave this blank for a new request; explain that the manager supplies the ID later.

Make the action and dates required. Keep the original-ID field optional so a new requester can submit, but tell staff to supply it for follow-ups. If someone needs a correction before receiving an ID, they should contact the manager with their original dates and submission details. The manager must resolve that link before deciding.

Collect the signed-in work address through Settings → Responses → Collect email addresses → Verified, as described in Google’s response-management guide. This identifies the Google account; it does not establish that its holder is authorized staff. Responder access needs its own restriction. Omit medical explanations, attachments and an open-ended “reason for absence” field from this limited tracker.

Who can submit, and who can see the records?

Staff need responder access, not permission to manage the Form or browse its responses. Before distributing the link, set up manager-only records.

In the Form’s Responses area, select the response destination and create a new spreadsheet. Keep this incoming-response file separate from a second, manager-maintained decision spreadsheet. Google documents the linked-Sheet setup and permissions: existing Form collaborators gain access to a newly created response spreadsheet, but later permission changes do not synchronize. Check both files separately, plus the decision file.

In each record file’s Share menu, use Restricted access and name only the deciding manager and authorized backup. Reserve Form editor access for them too. Check the containing folder: Drive permissions are inherited, so a broadly shared parent can expose a file despite your intended restrictions. Use an appropriately restricted location and check your organization’s sharing rules.

Do not give everyone the workbook and hide other employees’ tabs. Google says protected ranges are not a security measure and hidden sheets can remain accessible, including through copies. Protection can reduce accidental editing; it cannot turn a shared register into private employee accounts. Send each person their own decision instead.

Use these Form settings for this design:

  • Under Responses, leave Limit to 1 response off so staff can make later requests. Leave Allow response editing off; corrections should create linked follow-ups, not rewrite an earlier submission.

  • Under Presentation, leave View results summary off. Google warns that summaries can expose full answers or charts to responders.

  • Use a confirmation message such as: “Request received. Wait for the manager’s decision before treating these dates as approved.”

  • Choose Publish → Manage and add the intended work accounts as Responders. Do not enable Anyone with the link. Check access before publishing and distributing the responder link.

A customer enquiry form has a different audience and access requirement. If that is also on your task list, use the separate guide to choosing a customer-enquiry form; keep its records separate from staff leave.

How does a submission become a manager’s decision?

Treat arrival, decision and notification as three separate events. Forms can send answer copies and manager alerts, but neither is a decision notice. In Responses → More, enable email notifications for new responses. Optional answer copies are configured under Settings → Responses. Google notes that response receipts can be blocked by spam or anti-abuse filtering, so agree a routine for checking the Form and Sheet directly.

In the separate decision spreadsheet, create a Register tab and a History tab. This is a proposed manual record design, not a built-in Google approval template. For every new submission, the manager should add a Register row containing:

  • A stable, manually assigned ID, such as LR-001, and the action requested.

  • The submitted timestamp, verified email and original request details, so the row can be matched to its source without relying only on a spreadsheet row number.

  • The original requested dates and any parent request ID.

  • One current status: Pending, Approved, Declined or Cancelled.

  • The deciding person, decision date and a reference to the private message sent, including when and to whom it was sent.

The manager assigns Pending when entering the record; linking Forms to Sheets does not create this register or its statuses automatically. Reconcile incoming submissions against registered items so an unprocessed response does not disappear from view. Communicate the assigned ID privately. It will not be inserted automatically into a Forms answer receipt in this no-code design.

Select the status cells, choose Insert → Dropdown and enter the four values. Keep multiple selection off and reject entries outside the list. Google’s dropdown documentation supports those controls, but a dropdown does not enforce who may approve, validate a change or send a message.

Before deciding, check the requester, date order, duplicates, overlapping requests and work coverage under the studio’s existing rules. A Date question does not settle those questions. If information is inconsistent, keep the item pending and clarify it privately.

Record the decision and then send an individual message stating the ID, exact dates and outcome. Log the communication separately: an Approved cell does not establish that the employee has been told. Keep a dated History entry for each action, including the person responsible and the previous decision, rather than overwriting the only evidence of what happened.

What happens when dates change or leave is cancelled?

A follow-up should identify the original request and receive its own record and ID. Preserve the original dates and earlier decision. The follow-up starts pending; approval for one set of dates must not silently become approval for another.

For an illustrative example, LR-001 might approve December 7–8, 2026. A request to move the whole absence to December 9–10 becomes LR-002, linked to LR-001. Until the manager decides otherwise, the earlier decision still describes December 7–8; the new dates are not approved.

If the replacement is approved, record LR-002 as Approved and mark the old request Cancelled, with a dated History entry explaining that LR-002 replaces it. Preserve LR-001’s earlier approval in that history. If the change is declined, record that outcome on LR-002 and explicitly confirm whether the original approval remains in place. For a partial change, state the complete resulting dates so the employee and backup do not have to infer them.

Handle cancellation similarly: link the follow-up, record the manager’s action and update the original request only when that action is settled. On a cancellation follow-up, Approved means the requested cancellation was accepted—not that more leave was granted. Keep the original record and send a private confirmation specifying which dates are now cancelled.

Approved planned leave is not proof that it was taken. Keep attendance and payroll outside this tracker. For allocating client work around agreed absences, the guide to tracking a small studio’s client projects addresses task ownership and deadlines; do not share the confidential register as a project board.

How do you keep the routine working and preserve records?

Agree how often the manager checks incoming requests and what happens while they are away. The backup should use their own authorized account, know where pending items are recorded and follow the same decision convention. Tell staff whom to contact when they have no acknowledgment or decision. Review access when responsibilities change.

Keep independent exports in a restricted, approved location. Forms offers a response CSV download; separately use File → Download for the decision spreadsheet, following Google’s download guidance. Choose a format that retains the needed tabs, or export each required tab separately. Retain the necessary private confirmation records under the business’s existing retention policy.

Reopen the exports and check that requests match the register and action history. A raw-response CSV alone cannot preserve decisions maintained elsewhere. Neither a CSV nor a spreadsheet download should be assumed to preserve sharing permissions, Form settings or message history.

When is dedicated leave software worth evaluating?

Consider a paid tool when maintaining balances, routing decisions or handling changes has become a recurring operational problem—not simply because the response Sheet has more rows. Zoho describes policy configuration, balances and manager approval routing. Those capabilities may address a specific gap; they are not evidence of savings or a reason to exceed the budget without one.

Adoption requires setting up the people, permissions and existing policies. Zoho’s approval instructions distinguish configured approvers from automatic actions. Select the intended human decision route and backup. Its leave-request settings separately control cancellation permissions and extensions. Buying seats does not configure these choices for you.

The 30-day trial is temporary access to a selected plan; the advertised move to Free afterward does not provide continuing paid features for five people. Zoho’s general terms provide for automatic renewal and warn about losing trial data or customizations without an applicable purchase or export, subject to service-specific terms. Establish what you need to retain before trial expiry.

Zoho documents exports for specific leave reports, including CSV and spreadsheet formats. That does not establish complete approval-history or account portability. Check that the records you actually need can be exported and understood before moving real staff data.

What should you check before inviting staff?

Run a small dummy-request exercise with the intended access roles. These are proposed checks for your business, not reported test results:

  • An intended staff account can submit twice; an unauthorized account cannot use the restricted form. A responder cannot open manager files, Form management or other staff’s summaries.

  • The manager can find a submission without relying on email, assign an ID and enter Pending. A reversed date range and a duplicate are noticed rather than treated as approved.

  • A changed-date request remains linked to the earlier record and pending until reviewed. A cancellation preserves the earlier decision and has its own manager action and private reply.

  • The backup can find unfinished work using their own account. Exported requests, decisions and history reopen and can be matched.

Start with the smallest change that fixes the problem. Keep dependable email; add Forms for consistent intake; evaluate dedicated software for a defined need for routing or balance management. Whichever you choose, the routine is complete only when the decision is recorded and the employee has been told privately.