Employee onboarding
Before
Four manual emails, a checklist, and folder setup repeated by an administrator.
Delivered state
Four validated and logged menu actions create the documents, access, filing, and notices.
- Professional Services
- Global
- 1 service
Confidential client / Financial services operations
Seven HR workflows. One controlled Workspace system.
An anonymized Google Workspace automation suite for a regulated financial services operation: seven HR processes, scheduled dispatch, controlled access, audit status, and client-owned documentation.
Client identity, employee data, emails, folder IDs, and salary-band logic are withheld. This page uses a reconstructed system map, not client screenshots.
Delivered system pattern
No client data01
Validated form
02
Tracking record
03
Document generated
04
Delivered securely
05
Filed with access set
06
Stakeholders notified
Delivered system evidence
- people processes automated end to end
- 7
- daily review-form dispatch runs unattended
- 09:00
- plain-English user manuals delivered
- 3
- manual reference field remains in one promotion flow
- 1
Scope delivered
One engine, seven people processes.
The repeated pattern was not email or document generation on its own. It was the complete handoff from a validated request to a delivered, access-controlled, filed, and traceable outcome.
Employee onboarding
Probation reviews
Promotions
Role changes
Transfers
Secondments
Partner changes
Run the engine
Pick a process and watch the same six stages carry it.
This is the delivered pattern, not a client recording. Where the case study documents something specific about a process, it appears against the stage it belongs to; where it documents nothing, the exhibit says so rather than filling the gap.
Pick a process
Documented for this process
Four validated and logged menu actions
Dry run is documented for the transfer and secondment variants. The case study does not state it either way for this process, so the exhibit does not offer it.
6 stages
DocumentedShared pattern
Employee onboarding: 6 stages.
01Validated form
The request is captured through a validated form rather than an email.
02Tracking record
The request is written to a tracking record with a status and timestamp.
03Document generated
The document is generated from a template rather than assembled by hand.
Creates the onboarding documents.
04Delivered securely
The document is delivered to its named recipient.
05Filed with access set
The file is placed in the correct folder with access limited by the workflow.
Access and folder setup that an administrator used to repeat by hand.
06Stakeholders notified
The stakeholders who need to act are notified.
Before and after
The administrative work moved into a controlled sequence.
Probation review
Before
Letters, salary lookups, email, filing, and review tracking assembled across separate steps.
Delivered state
Seven controlled actions cover intake, band lookup, generation, delivery, filing, and the scheduled review form.
Promotion and role change
Before
Managers, folders, placeholders, permissions, and follow-up coordinated manually.
Delivered state
One form drives the letter, folder creation, private employee access, and stakeholder checklist in a single pass.
Transfers and secondments
Before
The same document-and-access pattern rebuilt for each people process.
Delivered state
Four process variants use the same engine and can be dry-run before any message is sent.
Control model
Privacy and ownership were part of the workflow, not a handover note.
Client-owned environment
The workflows run in the client's Google Workspace rather than an agency account.
Private employee access
Generated files are placed in the correct folder with access limited by the workflow.
Auditable actions
Workflow actions write a status and timestamp so the team can trace what happened.
Dry-run before delivery
Sensitive process variants can be checked without sending documents or notifications.
Measurement disclosure
The delivered system and manuals verify process coverage, scheduled execution, audit fields, and the remaining manual step. They do not contain a defensible hours-saved baseline, so this case study makes no time-saving or ROI claim. The next measurement step is a before-and-after sample of handling time and exception rate for each process.
Start bounded
Bring one repetitive process and its exceptions.
We will map the trigger, finish line, data, approvals, failure cases, ownership, and proof standard before recommending a platform or quoting the build.
Questions
About this
project.
What the work covered, and what this case study does and does not claim.
Brief us on similar workWhat did the HR operations automation include?
It covered employee onboarding, probation reviews, promotions, role changes, transfers, secondments, and partner changes from validated intake through document generation, secure delivery, filing, notification, and audit status.
Which platform was used for the automation?
The workflows run inside the client-owned Google Workspace account. No separate automation platform was introduced for this system.
Does this case study claim hours saved?
No. The source material verifies the delivered process coverage and controls but does not include a defensible before-and-after handling-time baseline.
Why is the client anonymous?
The engagement involves confidential financial-services operations and employee data. The case publishes the system pattern and verified delivery evidence while withholding identity, emails, folder IDs, and salary logic.
More work
Other work you can check.
Hospitality / Global
Aradhana Restaurant and Bar
Brand identity, print collateral and a bilingual reservation site for a Nepali and Indian restaurant in Lisbon. Two complete languages, a lunch menu that rotates daily on Lisbon time, and a heat selector that carries into the booking.
Hospitality / Nepal
Nepal Holiday Makers
A WordPress site rebuilt on Next.js and Sanity for a Kathmandu tour operator trading since 1999. 230 crawled URLs reduced to 93 clean ones, 26 broken pages fixed, and the only llms.txt in a 13-operator field.