Skip to main content

Logatot

Product work · Home child care

Helping child care providers log their day by voice

Providers can record meals, naps, and attendance while caring for children. I led front-end work on a three-developer team, covering voice interaction, error recovery, and shared components in a paid product.

VOICEBOARD · HANDS-FREE “Nap for Leo” Nap Leo 12:40 pm Logged without a tap
2+ hrs
saved on daily data entryReported by providers
21
reusable ViewComponentsAcross nine namespaces
My role
Lead front end and interaction design
Owned
Provider research, voice interaction, repair flows, shared components
Team
Three developers
Built with
Rails, ViewComponents, Alpine

Project summary

Three providers, interviewed separately, described the same problem. The job leaves no time for paperwork, so they filled it in from memory at night. Inspectors and auditors care most about those records.

The decision
I chose matching speech against a known list, with AI used only ahead of time, because compliance records can't contain guessed entries.
The result
Attendance, meal, and safety records now come from entries logged during the day, so reviewing them takes minutes instead of an evening.

Audience

A home daycare provider is caregiver, cook, and record-keeper through a twelve-hour day, answering to three sets of rules. Logatot moves the record-keeping from 8pm into the moment, hands-free. Providers say what happened and it appears on the Voiceboard, the app’s main screen. Renee, Tanya, and Marisol show how that plays out for different providers.

Three sets of rules

  • CACFP

    Reimburses a meal only if it met the age group’s food requirements, with proof.

  • State licensing

    Signed attendance, fire drill and shelter-in-place logs, and allergy and medication rosters.

  • Tax

    The IRS time-space percentage, which needs business hours and square footage.

Problems with logging from memory

  • Memory isn’t reliable

    A nap logged at 8pm is a guess, and those are the records that matter most legally.

  • Providers leave the work

    Many providers leave the work because of the paperwork.

  • Errors are found too late

    A lunch missing a vegetable is found at month end, when it can’t be fixed.

Research

Requirements gathering

I was hired to bring UX design and research to what was still a prototype. Its design decisions had come from hunches or followed the database, so screens were laid out the way the data was stored.

The team knew the market existed. Its picture of these providers didn’t go much further than what an accounting ledger could show. Everyone agreed that providers were exhausted and overworked. My job was to reduce their workload.

To replace the guesses with evidence, I interviewed three providers separately. I also spoke with food-program administrators and child care influencers.

Changes from the research calls

  • Accents were getting misheard

    Transcription got names wrong before the app could parse them. Each child now has a list of likely mishearings.

  • Providers needed better proof for claims

    Reimbursement processors found gaps in the claim evidence. The reports were reworked to close them.

“I would want to review it. Names can be difficult. A system may misunderstand a child’s name or a Spanish word. It should show me what it heard and let me approve or correct it.”
Yari, on trusting voice entry for official records

Watching customers use voice logging

Some customers complained that voice logging didn’t work, though it worked well for many others. I replied to them by email and watched Hotjar sessions, and we worked through the usual troubleshooting: browser, browser version, operating system, and device.

We found the cause by sitting down and watching them use it. Many of the people having trouble were Spanish speakers who spoke very little English, the group Marisol represents. The system couldn’t understand their accents. Yari’s interview, quoted above, came after we found this.

What people say in questionnaires and conversations doesn’t always match what they do. Watching them work showed where they ran into trouble.

The screens around the voice workflow had drifted: two icon sets, colors picked page by page, and controls that looked alike but did different things. I ran a front-end audit and kept the brand and every route.

Front-end audit findings

0

forms guarded against double submits

Out of about fifty.

0

confirm prompts that worked

“Cancel my account” deleted the account on the first click.

4

different ways to delete

htmx, Rails buttons, Alpine fetch calls, and inline handlers.

14

index pages with hand-built headers

Titles, actions, and spacing differed from page to page.

The audit also found leftover scaffold pages that could show data across accounts. I removed them first, and a test now checks every page for server errors.

Heuristic audit

I scored all 119 pages against Nielsen’s ten heuristics, tying every finding to a file and line. The lowest scores had one cause. Rails confirm prompts and double-submit guards need Turbo, and the app loads htmx, so none of them worked. One shared fix covered every page.

4.9

average score before

across ten heuristics and 119 page captures

3

lowest scores

error prevention and recovering from errors

Score by heuristic

Each heuristic’s score before the fixes and the change made.

  1. Visibility of system status

    5 /10

    Busy states on every form, and failed background saves show a message.

  2. Match with the real world

    6 /10

    “Logged Events” became the Activity log, opening on Needs review instead of “Failed.”

  3. User control and freedom

    5 /10

    Sign-in lands on the Voiceboard, and deleted events can be restored.

  4. Consistency and standards

    6 /10

    One confirm dialog and one page header everywhere.

  5. Error prevention

    3 /10

    “Cancel my account” asks first, and every form blocks double submits.

  6. Recognition over recall

    6 /10

    Reports open with every active child selected, and the calendar’s warning icon has a legend.

  7. Flexibility and efficiency

    4 /10

    Press / to search from any page, CSV export on reports, and bulk actions on documents.

  8. Aesthetic and minimalist

    7 /10

    One raised surface per page, the compact Voiceboard, and recessed filters.

  9. Recovering from errors

    3 /10

    Inline errors announced to screen readers, and a crashing sidebar page fixed.

  10. Help and documentation

    4 /10

    An empty Voiceboard teaches the voice commands. Help moved into the sidebar.

All three providers asked for the same fix: capture entries by voice in the moment and review them later.

Personas

  • Renee Walsh

    The solo provider

    “We choose the children, and then we pay for that choice with our evenings and our sleep.”
    Angie, home-based provider

    About 11 years running a licensed home program, with six children and a few hours of help a week.

    Needs
    • Log a moment without looking away from the children
    • Finish the day’s records before dinner
    • Proof of good faith if a record is questioned
    Frustrations
    • Records rebuilt from memory at night
    • Fear that an honest error will look like fraud
    • Tools built for centers with desks and office staff

    Based on the interview with Angie.

  • Tanya Brooks

    The provider running a business

    “The technology has to fit the work. The work should not have to change to fit the technology.”
    Deborah, home-based provider

    About 14 years in home care, with six children and an assistant three days a week.

    Needs
    • One attendance record for billing, subsidy, meals, and licensing
    • Enter information once
    • A tool that saves more time than it takes
    Frustrations
    • The same details typed into several systems
    • Reimbursement lost to mismatched records
    • Apps that took more managing than they saved

    Based on the interview with Deborah.

  • Marisol Vega

    The Spanish-speaking provider

    “When everything is working, I already know what to do. When there is a problem, the explanation is in English.”
    Yari, home-based provider

    About eight years in home care, with five or six children and occasional help from family.

    Needs
    • Voice entry in Spanish
    • Errors, warnings, and support in plain Spanish
    • A chance to review what the system heard
    Frustrations
    • English on the screens that matter most
    • Tools that translate poorly
    • Systems that can’t share basic information

    Based on the interview with Yari.

Persona names and photos are illustrative, as are quotes without a named source.

Journey map: a provider’s day

  1. Children arrive

    Activity

    The provider greets families and records who is here.

    Problem

    Attendance feeds billing, subsidy, meals, and licensing, but each system wants it entered separately.

    Design response
    A PIN and signature at the kiosk, with attendance calculated from check-in history.
  2. Care through the day

    Activity

    One person supervises the children while meals, naps, and diapers all need recording.

    Problem

    Supervision and paperwork both need full attention, so notes end up on paper scraps and in texts.

    Design response
    Hands-free voice logging, lined up by child on the Voiceboard.
  3. Evening paperwork

    Activity

    After the children leave, the provider rebuilds the day’s records.

    Problem

    Records written from memory are less accurate, and the work takes evenings and weekends.

    Design response
    Entries are already logged, so only misheard ones wait in Needs review.
  4. Month-end claim

    Activity

    The provider claims meal reimbursement from CACFP.

    Problem

    A lunch missing a vegetable is found at month end, when it can’t be fixed.

    Design response
    Menus are checked against CACFP rules while they’re planned.
  5. Inspection or audit

    Activity

    A licensor or auditor asks to see the records.

    Problem

    Mismatched records make providers afraid an honest error will look dishonest.

    Design response
    Reports come from entries logged during the day, and deleted records are kept.

A Voiceboard that shows where every child is

Providers check the Voiceboard most often to see where every child is and whether each has had the basics today. Each child gets one compact tile with a status and an icon chip for each kind of moment logged today.

A missing chip stands out. A child with no nap chip in the afternoon is easy to spot. Compact is the default. Detailed is one tap away and is used to write the end-of-day report.

The Voiceboard for Friday, October 30, signed in as the provider: a sidebar with Voiceboard, Children, Activity log, and Meals, then Modules and Resources groups and a Dark mode switch. The main area has a Ready to listen panel with a microphone and the example “Logatot, Ava woke up,” count pills for 0 here, 12 expected, 11 picked up, and 1 absent, a date control, and a Children heading with a Compact and Detailed switch above a three-column grid of child tiles, each with a photo, the pickup time, and colored moment chips.
Voiceboard, Compact

One compact tile per child, with a chip for each kind of moment.

Child cards on the Logatot Voiceboard. Each card shows a photo, the child’s name, their check-in time, and a list of the day’s events with times, such as a 7:08 am health check, a 12:29 pm wet diaper change, a 12:37 pm nap, lunch at 11:45 am, and outdoor play.
Voiceboard, Detailed

Each child’s day so far, grouped by event type, for writing up the end-of-day report.

A review step for misheard entries

Providers asked to capture by voice in the moment and review later. When the app can’t match an entry to a child or an event, it sends the entry to review.

A failed entry is saved with its words, translation, recording, and whatever the app partly understood. Tapping the word that was the child’s name adds that mishearing to the child’s name variants.

Out loud, the app says “processing unknown event for unrecognized child” instead of announcing a failure to a room of children.

Annotated wireframe of the logged-events review screen: a queue of failed voice captures, each showing the raw utterance as selectable word chips, the partially understood fields, and the retained audio, with callouts explaining the two diagnostic flags and how a correction improves recognition permanently.
Logged events: review and repair

Tapping the right word adds it to that child’s name variants.

The Activity log with the Needs review tab selected, showing 2, beside Logged 819, Processing, and Recently deleted. Two failed entries, each with Name not heard and Event not recognized tags and a time, a large quote such as “Log a diaper change for, um, the little one in the blue shirt,” a hint to tap the word that was the child’s name, and on the right Child and What happened selects, an Edit transcript or time link, a Delete link, and a Save event button.
Activity log: needs review

What Logatot heard on the left, the fields to fix it on the right.

Spanish

Yari said: “A translated button is not enough. We need the instructions, warnings, support, and official documents to be clear too.” All of it ships in English and Spanish.

After researching best practices and prototyping Spanish support, I convinced the team that internationalization was worth the work. Speech turned out to be simpler than we expected: changing lang="en" to lang="es-us" told the browser how to interpret what the customer said.

The wording took more care. Google Translate was an acceptable starting point, but its translations weren’t culturally or contextually accurate. We hired a contractor to make sure the language made sense to Spanish-speaking providers. The work also prepared the app for Russian and Ukrainian, which smaller groups of customers speak.

Every new label, hint, and error was written in English and Spanish together. Layouts were checked in Spanish at phone width.

The Voiceboard in Spanish: a sidebar with Tablero de voz, Niños, Registro de actividades, and Comidas, the panel Lista para escuchar with “Di ‘Logatot’ para registrar un momento” and the example “Logatot, Ava se despertó,” counts reading 0 presentes, 12 esperados, 11 recogidos, and 1 ausentes, the date Viernes, Octubre 30, and the Niños heading with Compacto and Detallado above child tiles reading “Recogido a las 4:55 pm.”
Tablero de voz

The Voiceboard with the provider’s language set to Spanish.

The Needs review screen in Spanish: tabs Por revisar 2, Registrados 819, Procesando, and Eliminados recientemente, entries tagged No se escuchó el nombre and Evento no reconocido, the hint “Toque la palabra que era el nombre del niño,” Niño and Tipo de evento selects, and Eliminar and Guardar evento buttons.
Registro de actividades

Labels are translated. The quote stays as heard.

A kiosk that shows a parent only their own child

Kiosk mode signs the provider out first, so a parent holding the tablet can reach only their own child.

The check-in kiosk on a tablet: a single white card with the Logatot logo, the heading Check In/Out, “Enter your PIN for Little Acorns Home Daycare,” and a large PIN field.
Kiosk: enter a PIN

The PIN field is the only control.

The kiosk after the PIN 0317 is entered: Liam Carter with a Check In checkbox, a signature pad labeled Signature for Megan Carter, and Clear Signature and Continue buttons.
Kiosk: after the PIN

Only this person’s children, then a signature.

Families use the app about a dozen times a year, so they sign in with an email link instead of a password. They see the provider’s events for their own child and have nothing to manage. The family channel adds no work to the provider’s day.

Flow diagram of parent access: a passwordless magic-link request that returns an identical screen for known and unknown addresses, a fifteen-minute single-use token, role resolution at the shared sign-in, and the automatic end-of-day summary email that drives the daily loop.
Parent access

Email-link sign-in and a daily summary email that brings parents back.

Liam Carter’s profile signed in as the provider: the full sidebar, a raised header card with his photo, name, pronoun, birth date, age, an Active badge, Archive child and Edit buttons, and Health tiles for allergies, medications, diapers, and diet restrictions. Below, recessed panels list Legal guardians Megan and Ryan Carter with an Add legal guardian button, a Monday-to-Friday attendance strip, and Billing of $275.00 every two weeks.
Provider: a child’s profile

The whole record, editable.

The family channel signed in as Megan Carter: a top bar with the daycare name and her name, a Family channel heading, a panel greeting her with a choice of child, the provider’s thank-you note, then October 30th activities for Liam Carter as a table of times and activities from Lunch to Check-out, and a Child details panel with tuition, allergies, medications, and Authorized pickups listing Tyler Carter.
Family: the same child

Liam’s day and details, with no editing tools.

Roles and access

Four kinds of people use Logatot. Each signs in differently and sees a different set of screens built from the same components.

  • Logatot staff Sign-in: Password

    Everything a provider sees, plus every account for support, and the blog.

  • Provider and employees Sign-in: Password

    The full app.

  • Families Sign-in: Email link

    Their own children only, in a family channel. Staff pages redirect back to it.

  • Authorized pickups Sign-in: Kiosk PIN

    No account. A PIN shows only the children they may check in or out.

Menus checked against CACFP rules while they’re planned

A lunch missing a vegetable used to be found at month end, when it couldn’t be fixed. Menus are now checked per meal against the age group’s food requirements while they’re planned, and the month-end claim comes from records that already exist.

Flow diagram of the CACFP food program: building a menu validated per meal against the age-group component matrix, duplicating a week, generating a shopping list, serving meals through the shared event pipeline, and reconciling the month-end claim from records that already exist.
Food program

Plan, serve, and claim, with menus checked against the rules while they’re planned.

The menu calendar for November 2026 in month view: My meals, Menu calendar, and Shopping list tabs, Today and month controls, a legend for Breakfast, Snack, Lunch, Dinner, and Missing a required food component, and a calendar grid where each day lists meals such as Toast and Bananas, Apples and Cheese ×2, and Pasta and Meatballs, with warning triangles on some breakfasts and today’s date highlighted.
Menu calendar

Meals missing a required component get a warning.

One set of rules for every screen

To keep the screens consistent, I started with the shared pieces: one 154-icon set, a contrast-checked pastel palette, and shared helpers for buttons, forms, surfaces, tables, and filters. Then I rebuilt screens, most-used first.

Design decisions

  • Pastels that pass contrast

    Each module has a soft hue, generated and checked for WCAG AA in light and dark mode.

  • Buttons, tabs, and filters look different

    Actions are filled pills, navigation is a segmented control, and filters are checkbox chips.

  • One raised surface per page

    The page’s main content sits on a white card. Everything else sits in recessed panels.

  • Never color alone

    Every color-coded category also has an icon or a label.

  • Logo blocks show loading, empty, and error states

    The toy blocks stack while loading, lose the top block when empty, and teeter on error pages.

  • A Voiceboard that fits on one screen

    A compact view took a full day from 3,849 to 1,318 pixels tall.

Accessibility

Everything you can say can also be entered by hand. Focus outlines are visible, status changes are announced to screen readers, and reports print in black on white.

The Children page: Active, Inactive, All, and Archived segments, a search field, and a two-column grid of child cards with photos, Active status, and labeled chips such as Diapers, Meds, and Diet. On the right, a recessed Add a child panel with first name, last name, and date of birth fields, an Add child button, and a Use the full form link.
Children

The roster raised, quick add recessed beside it.

The Expenses page: All expenses, Expense locations, and Expense categories segments, a recessed strip with This month $142.37, This year $600.40, and Receipts 8, a Find expenses panel with a search field and date chips, then a table of expenses with checkboxes, dates, places such as Costco and Target, category badges, amounts, mileage, and edit and delete buttons.
Expenses

Totals and filters recessed, the table raised.

Dark mode

Providers log naps in darkened rooms. Dark mode follows the device until someone flips the sidebar switch, and every token is contrast-checked in both themes. Recessed panels get darker in dark mode, so they stay distinct from raised cards.

The Voiceboard for October 30 in dark mode: a near-black sidebar with the Dark mode switch turned on, a navy Ready to listen panel, dark count pills, and a grid of dark child tiles with photos, pickup times, and colored moment chips.
Voiceboard, dark

Module hues keep their meaning on navy.

Mobile

Every rebuilt screen was checked at 390 pixels wide, in both themes and in Spanish. Layouts are rearranged for small screens. Calendars become lists, tables become cards, and the sidebar becomes a drawer.

  • The Voiceboard on a phone: the Ready to listen panel with the example “Logatot, Ava woke up,” a date control for Friday, October 30 with a Today button, count pills for 0 here, 12 expected, 11 picked up, and 1 absent, then the Children heading with the Compact and Detailed switch, an Add event button, and Ava Johnson’s tile.
    Voiceboard

    Date, counts, and children stack in one column.

  • The provider’s navigation drawer on a phone: Voiceboard highlighted, Children, Activity log, Meals, a Modules group with Calendar, Chat, Documents, and Expenses, and a Resources group with Photo gallery, Reports, Video learning library, and Help.
    Provider menu

    Twelve destinations in three groups.

  • A parent’s navigation drawer on a phone: Little Acorns Home Daycare, then only My children, Chat, Reports, and a Dark mode switch.
    Family menu

    A parent sees three links and the dark mode switch.

  • Liam Carter’s profile on a phone: a large photo, his name, pronoun, birth date and age, an Active badge, Archive child and Edit buttons, then Health tiles for allergies, medications, and diapers.
    Child profile

    Health details become full-width tiles.

  • A failed voice entry on a phone: Name not heard and Event not recognized tags, the time, the quote “Log a diaper change for, um, the little one in the blue shirt,” a hint to tap the word that was the child’s name, and Child and What happened selects.
    Needs review

    The misheard sentence first, then the fields to fix it.

  • The menu calendar on a phone: Month and Week controls, a legend item for a missing required food component, then Sunday the 1st and Monday the 2nd as lists of breakfast, morning snack, lunch, and dinner, with a warning icon on two breakfasts.
    Menu calendar

    The month grid becomes a list by day and meal.

  • The family channel on a phone: a Show filters button, the provider’s thank-you note, and October 30th activities for Liam Carter with a date filter and a timeline starting with Check-out and Activity.
    Family channel

    The provider’s welcome note, then the child’s day.

  • The provider login on a phone: email and password fields, Remember me, a Login button, Register and Forgot your password links, and a “Family member? Family login” button.
    Provider login

    Families get their own link at the bottom.

Public site

The homepage previews are the app’s own components with demo data, so the site can’t fall out of date. The hero plays a voice demo that respects reduced motion and is announced to screen readers.

The full Logatot homepage: a header with an EN/ES switch, the hero “Child Care’s Only Voice-Controlled Assistant” beside a live listening panel and Ava Johnson’s card of the day’s moments, Try it phrase chips, a Why Logatot section with four benefits, a Speak, record, comply section with live Voiceboard tiles, a Ready for anything section with Olivia Bennett’s profile, guardians, and pickups, a Simplified, effective management section with report cards, Pricing at $30 a month or $300 a year, testimonials, and a footer with a contact form.
Full page Logatot homepage

Every preview is a live app component with demo data.

Results

2+ hrs

saved on daily data entry

Reported by providers

For providers like Renee, Tanya, and Marisol

  • Records logged in the moment, hands-free, instead of from memory at 8pm
  • Menus checked against CACFP rules while they’re planned
  • Significantly fewer voice logging complaints after adding Spanish, though we didn’t formally measure it

For families

  • The day’s events for one child, in one place
  • Email-link sign-in instead of a password
  • A daily summary by email

For the business

  • Shipped as a paid product
  • Sold directly and through child care associations

Post-launch feedback

A questionnaire led to a readable menu calendar, clearer pages, and a compact Voiceboard.

Read the follow-up case study

Testimonials

President

CSEA/VOICE Local 100A

It is truly remarkable to be completing a physical task and talking to the voice assistant to record it simultaneously! Now I do not have to do my data entry outside of business hours. Each day I am saving over 2 hours on data entry!!!

Margaret Balko

Home-based provider

I never realized how much time I had to spend filling in paperwork until I didn’t have to. Logatot has given me my evenings back.

Build process

The wake word is detected on the device, so no audio leaves the device to listen for “Logatot.” Providers asked about this first.

Speech is matched against known phrases and the class roster without AI. A live model would be slower and could log a nap that never happened. The rules either match an entry or send it to review.

AI runs only when a child is added. It lists likely mishearings of the name, and corrections in the review queue add to that list. Spanish is translated before matching, so one phrase set covers both languages.

Services

  • Picovoice Porcupine

    Custom wake word, WebAssembly, on-device

  • Web Speech API

    Transcription, silence-timer endpointing

  • OpenAI

    Phonetic name variants, at child creation

  • Pusher

    Per-account channels for live board updates

  • Sidekiq

    29 jobs, 4 scheduled reminder workers

  • Stripe + union API

    Direct billing and association membership

Attendance is calculated from check-in history, so it always matches what happened. A wrong headcount is a licensing problem.

System-level decisions

  • Attendance calculated from check-in history
  • Enrolment status derived from dates
  • Deleted records are hidden and kept
Flow diagram of voice event logging. An on-device wake word opens transcription, which runs through a ladder of phrase matchers and roster name matching, forking into a single-child inline write, a multi-child background job, or a failed parse that lands in the repair queue with its audio attached.
Voice event logging

From speech to a saved event, with the failure path drawn in full.

Limitations

  • We assumed everyone spoke English

    We knew some providers were bilingual, but we had no idea that some homes didn’t speak English at all. We missed Marisol in our initial research and persona development. Conversations with agencies like CACFP focused on what providers had to do and too little on the people doing it. I’d focus more on the users themselves and start with internationalization, which is significantly easier than adding it later.

  • Screen-reader support on the busiest screen

    The Voiceboard’s expand and collapse controls don’t announce their state. It’s the first thing I’d fix.

  • No tablet layout

    The layout has one breakpoint, so tablets, including the kiosk, get a poor fit.

  • No offline mode

    The pieces exist but were never finished. For homes with unreliable WiFi, it’s the most valuable missing feature.

Still open

  • Recurring time zone bugs

    Most recent updates were time zone fixes, and the underlying cause remains.

  • The family channel is behind

    It still uses the old layout, and its welcome note is nearly unreadable in dark mode. It’s the next screen to rebuild.

  • Family menu links loop back

    My children, Chat, and Reports are staff-only, so each redirects a parent to the family channel.

  • Spanish isn’t complete

    Spanish is missing 67 of 2,313 entries, and the home page demo cards stay in English.

  • No re-score yet

    Every heuristic has fixes, but I haven’t re-scored the app. The 4.9 average from before the fixes is the only measured score.

More screens

Annotated wireframes and flows, more screens from the shipped app, and more before-and-after pairs from the feedback round.

See all 34 in the gallery