Current Google Apps Script workflow
Nanny Payroll shows the exact days, hours and kilometres worked. It then creates the invoice and records when payment is sent and received.
Illustrative week · no family data
Week ending
The useful detail
Each card shows the weekly amount, shift count and every worked date with that day's hours and kilometres. Both people can check exactly what the week contains.
One source of truth
Calendar stays the timesheet. The automation handles the arithmetic and paperwork around it.
The nanny adjusts the real start and finish time on the shared Google Calendar event.
Apps Script groups recognised shifts by date and totals that day's hours and approved kilometres.
The parent reviews the weekly card, pays externally, then marks the week paid and sends the PDF invoice.
The nanny uses a signed one-week link to confirm the payment arrived, closing the loop explicitly.
What it handles today
Only recognised Calendar titles enter payroll, keeping unrelated events out.
Multiple shifts on one date are combined into one clear daily row.
Payment creates a polished invoice and sends it with both HTML and plain-text email.
Paid and payment-confirmed remain separate, deliberate states.
Privacy
The workflow uses Google Calendar, Sheets, Apps Script, Drive and Gmail. It does not send payroll content to an external AI model or a separate payroll platform. Portal access uses private links, and this public page contains only fictional demonstration data.
What comes next
Current
Calendar-based hours, per-day mileage, PDF invoices and payment confirmation are live.
Exploratory
Future work may make unusual travel and one-off shift adjustments easier to review.
A Drew's Digest project