TINDY_WORKS

STUDIO

SPACES

OFFICEGARDENRECEPTION

BUSINESS OPERATIONS // DATA, PROCESS, AUTOMATION & STAFF ENABLEMENT

Guardianship Business Operations Automation

I helped rebuild the day-to-day operations of an education guardianship business, starting with the data behind them. After reconciling student records across the existing systems, I redesigned the process, connected the website, monday.com and Google Workspace, and automated work from registration and invoicing through to renewals and ongoing student admin. I also wrote SOPs and trained staff to use the new workflows and AI tools, with approvals, financial values and exceptions still under human control.

  • Data & Operations
  • Process & Automation
  • Systems Integration
  • Staff Enablement

01 // The Business Problem

Student information had built up across monday.com, spreadsheets, Drive and email, and it didn't always match from one place to the next. Staff relied on manual hand-offs, repeated checks and their own knowledge of what came next. Before automating anything, I cross-checked the existing records and worked out how each part of the business actually ran, which gave me a reliable base for redesigning the workflows.

FIG 1. BEFORE → CONNECTED OPERATIONS → AFTER

BEFORE

  • Student information spread across several systems
  • Repeated data entry and manual cross-checking
  • Processes depended on staff remembering the next step
  • Invoices, documents and folders created separately

CONNECTED OPERATIONS

  • Website + registration
  • monday.com
  • Google Apps Script
  • Google Workspace

Shared data rules + SOPs + human approval gates

AFTER

  • More consistent student records
  • Clearer, repeatable workflows
  • Prepared documents, invoices and reminders
  • Staff working from shared procedures and checkpoints

The work started with getting the records and process into a state the team could trust, then connecting the systems around them.

02 // What I Built

S.01

Data reconciliation & operations

Cross-checked student information across the existing systems, resolved inconsistencies and set up a more reliable operational record before rebuilding the workflows.

S.02

Process redesign & SOPs

Mapped the existing way of working, redesigned it around clearer responsibilities and automation, then wrote SOPs so staff had a consistent way to follow it.

S.03

Website, registration & onboarding

Connected the public website and registration journey to monday.com, then built separate Boarding and University workflows for review, validation and student setup.

S.04

Invoicing, documents & expenses

Automated invoices, PDFs, document preparation, expense workbook setup and filing, with financial values and exceptions kept under staff control.

S.05

Renewals & recurring admin

Scheduled checks spot documents approaching or past expiry and send or prepare the parent reminder, depending on how the workflow is configured, cutting down admin that used to be done by hand.

S.06

Staff training & AI-assisted work

Trained staff on the new workflows and on using approved AI tools for routine admin like drafting and organising follow-up, with staff still reviewing the output and making the decisions.

The SOPs set out which steps were automated, where staff needed to review something and what to do when a case didn't fit the normal path. The aim was to leave the business with a process people could actually use, not just a script running in the background.

03 // How the Operation Works

Each stage shows what happens, who is responsible and, under the hood, how the Apps Script workflow handles it.

FIG 2. STUDENT OPERATIONS JOURNEYSelect a stage

01–04 · Before payment

05–07 · After payment

STEP 01 — Website & Registration · Family submits · automation stages

Families start on the company website and continue to the registration form. Their information arrives in monday.com and is staged for review rather than written straight into live records.

Under the hood

Required fields are checked first, and Boarding and University registrations are routed through separate workflows.

04 // Built for Real Business Operations

P.01DATA INTEGRITY

Get the data right first

Before automating the workflows, I reconciled student information across the working systems and made it clear which system owned which records. Nothing was forced into one platform.

P.02PROCESS DESIGN

Fix the workflow before automating it

I mapped how the work was actually being done, simplified the hand-offs and documented the new process in SOPs before building automation around it.

P.03HUMAN + AI SUPPORT

Use tools to support people

Automation and AI tools handle suitable repetitive work, while staff stay responsible for approvals, sensitive communication, financial values and unusual cases.

P.04PRODUCTION SAFETY

Protect live operations

Existing records are checked before anything is created, test and live processes are kept apart, duplicates are avoided and exceptions are surfaced for review.

OPERATING PRINCIPLE

Automate the predictable.Escalate the ambiguous.

05 // Outcomes

01

Trusted operations data

Reconciled information across the existing systems and gave the team a more dependable operational view.

02

Clearer, repeatable workflows

Rebuilt key student-lifecycle processes, documented them in SOPs and connected them to automation, so staff had a clearer way of working.

03

Less recurring admin

Reduced repeated setup, cross-checking, document preparation, filing and renewal follow-up, and gave staff AI-assisted ways to handle routine admin.

06 // Could This Approach Help Your Business?

This happened to be a guardianship business, but the underlying problem is common in small companies: enquiries arrive in one place, customer information lives somewhere else, documents are created by hand, and the next step depends on someone remembering to do it.

E.01

CUSTOMER & CASE OPERATIONS

  1. Website enquiry
  2. Customer record
  3. Review
  4. Documents
  5. Ongoing status
E.02

PROCESS & STAFF WORKFLOWS

  1. Existing process
  2. Map it
  3. Simplify it
  4. SOP
  5. Automate repeatable steps
  6. Train staff
E.03

RECURRING ADMIN & RENEWALS

  1. Date / status check
  2. Identify action
  3. Prepare reminder
  4. Follow-up
  5. Update record

Many small businesses don't need another platform. They need cleaner data, clearer processes and the systems they already use to work together more reliably.

I can help untangle the existing records, map the process, document a better way of working, automate the repetitive parts and train the team to use the tools confidently.

Discuss Your Operations