# The BEE Suite: where directors do the work

Illustrated navigation tour with synthetic screen examples and Microsoft Zira computer-generated narration. Source-reviewed against origin/main on October 9, 2026. Not a live production recording.

## Welcome to The BEE Suite

**Where:** Your school workspace

Welcome to The BEE Suite. This tour explains what each director section is for and where to go when a task comes up. We will move from the school day to families, billing, staff, records, enrollment, reports, setup and support. This is an illustrated navigation walkthrough with synthetic screen examples, not a demonstration of live changes. After the tour, use the individual task lessons to learn the detailed steps.

## Find your way around

**Where:** School context → workspace → view → record

First check your school and role. The main menu takes you to a workspace, and the tabs within that workspace narrow the task. For example, Families and Communication contains Families, Children, Messages and Media review. Your menu depends on your role, brand and enabled features. On a phone, use the menu or More to reach additional sections. The navigation map in this lesson groups destinations for learning; it is not an exact copy of every account's menu.

## Dashboard

**Where:** Dashboard

Start the day on Dashboard. It is the overview of your school, with the items that need attention and routes into the work behind them. Use it to decide what to investigate next: classroom coverage, attendance, family follow-up or an outstanding exception. A summary is a starting point. Open the relevant workspace and check the actual record before making a change. Return here during the day to review priorities and follow-up.

## School Operations

**Where:** School Operations → choose a view

School Operations is for the school day. Enrollment status shows the roster and exports. Classrooms is for rooms, capacity, ratios and activity. Attendance is for arrival and departure status. Daily reports covers care notes and family updates, while Incidents is for safety records and follow-up. The teacher screen shown here is a synthetic example of the classroom work directors oversee. Check the child, classroom and date before reviewing or correcting a record.

## Families & Communication

**Where:** Families & Communication → Families / Children / Messages / Media review

Families and Communication brings together household records and family conversations. Use Families for guardians, household details and contacts. Use Children for child profiles, care information and permissions. Use Messages for family conversations, and Media review for photo review and sharing decisions. If a parent reports the wrong phone number or needs a sibling added, start with the existing family. If you need to investigate an account balance, move to Billing and Payments for that same family.

## Billing & Payments

**Where:** Billing & Payments → Billing & invoices / Payments

Billing and Payments is the home for tuition, invoices, balances and payment follow-up. Billing and invoices is where you review family accounts and charges. Payments is for transaction review and reconciliation. Keep the questions separate: what tuition is assigned, what invoice exists, and what payment actually happened? A saved payment method, autopay setting and paid invoice are different states. Use the billing task lessons for the exact procedure, and check the result before repeating an uncertain payment action.

## Staff & Access

**Where:** Staff & Access → Teachers / Team permissions

Staff and Access is for the people working at your school. The Teachers view contains staff records and classroom assignments, with the staff management tools used for schedules and time cards. Team permissions is the place to review roles and module access where your account permits it. Review the employee and the relevant date before correcting a time entry. Changing a profile, changing classroom coverage and granting access are separate tasks; use the appropriate procedure for each.

## Records & Compliance

**Where:** Records & Compliance → Forms / Documents / Compliance

Records and Compliance organizes required paperwork. Forms covers templates and submissions. Documents is for files and acknowledgements. Compliance brings together tasks, evidence and readiness information. Start here when you need a required document or need to see what is still missing. Verify the intended family or staff member, the document and its status. A request being created is different from a submission being received and reviewed.

## Enrollment CRM

**Where:** Enrollment CRM → Leads / Pipeline / Tours / Waitlist

Enrollment CRM is for prospective families and the process leading to enrollment. Leads is the inbox and lead record area. Pipeline shows stages and progress. Tours is for scheduling and follow-up. Waitlist helps track demand and openings. Use this workspace before a family becomes an enrolled household. When the process reaches enrollment, verify the actual family and child records and the enrollment status; moving a lead stage alone should not be treated as proof that every onboarding task is complete.

## FTE reports

**Where:** FTE reports → school and reporting week

FTE reports is the dedicated weekly reporting workspace. Select the intended school and reporting week, check the counts and notes, and use the submission or correction process shown there. It is different from simply exporting the current enrollment roster. After an authorized submission, verify the recorded result for that week. Executive review is a separate step. Use the FTE task lesson for the detailed reporting procedure.

## Insights & Reputation

**Where:** Insights & Reputation → Enrollment status / Analytics / Reputation

Insights and Reputation is for reports, trends and family feedback. Enrollment status is another route to the roster and its exports. Analytics helps you review operating metrics and trends. Reputation is for reviews and family sentiment. Check the school, filters and time period before interpreting a result. Reports help you spot a question; return to the underlying family, classroom, enrollment or billing record to investigate the detail.

## Campaigns & Automations

**Where:** Campaigns & Automations → Campaigns / Automations

Campaigns and Automations is for planned outreach and workflow configuration. Use Campaigns to review the audience and campaign content. Use Automations to inspect triggers, conditions and intended follow-up steps. This differs from answering one family's message in Families and Communication. Saving a workflow configuration does not prove that it runs or sends anything. Confirm the supported execution and review process before expecting a real message or other external action.

## AI Command and Mr. Bee

**Where:** AI Command / Mr. Bee entry point

AI Command and the Mr. Bee entry point provide assistance with information, summaries and drafts. Use them to understand a task, organize a follow-up or prepare wording. Review the source record and the proposed result yourself. An AI response is not proof that a school record changed or a message was delivered. For any supported action, check the exact target and confirmation, then verify the result in the workspace that owns that record.

## Settings & Setup

**Where:** Settings & Setup → Settings / Integrations / School setup / Notifications

Settings and Setup holds school preferences and setup work. Settings contains billing and school preferences. Integrations is where connected services are reviewed. School setup is for the school profile, data starting point and readiness steps. Notifications contains alert and delivery preferences. Some options require additional permissions; for example, White-label branding is an executive view. Completing setup, connecting a service and approving school launch are separate decisions. Use the setup checklist and the matching task guide.

## Data readiness, when enabled

**Where:** Data readiness / School setup

When enabled for your school, Data readiness helps organize data review. It belongs with the School setup work, especially when transitioning existing records. Check families, guardian relationships, enrollment, tuition and opening balances against the approved source information. A completed import is not the same as verified records. If the separate Data readiness entry is not visible, use the School setup guidance available to your account and ask support about the intended review process.

## BEES and training resources

**Where:** BEES / Resources → Director training

For Kid City USA management accounts, BEES opens the director and owner resource area. It includes links to leadership resources, school forms, curriculum materials, employee training, menus and manager training. Linked Drive folders enforce their own access permissions. The Resources area also provides the director tutorial library. Use these reference materials alongside the workspaces. Confirm the currently required reporting destination before substituting an external form for an in-suite workflow.

## Asset Hub

**Where:** Asset Hub → search / preview / download

Asset Hub is the library for approved brand, social, training and school resources. Search or filter the library, preview the correct item and download it for the intended use. Director access is primarily about finding and using the available resources; upload and management controls depend on role. Downloading an asset does not publish it anywhere. Use your school's approved process when sharing or publishing the material.

## Notifications and Audit logs

**Where:** Notification bell / Notifications · Audit logs

Notifications brings attention to items that need follow-up. Open the related record and verify its current state. Audit logs, also described as activity history, helps review recorded actions: who acted, what happened and which record was involved. It supports investigation when a change is unclear. An activity entry is evidence of what was recorded; it is not automatically proof of email delivery, bank settlement or a person's acknowledgement.

## Help and support

**Where:** Help → guides and support guidance

Help is the place to look for instructions and troubleshooting. Start with the guide for your task. If you still need support, describe the school, the task, the time, the exact error and the result you expected. Include a safe screenshot when useful. Avoid including passwords, private credentials or unnecessary family information. The goal is to give support enough context to identify the correct record and reproduce the issue.

## Family kiosk, staff clock and portals

**Where:** Approved kiosk / Teacher workspace / Parent portal

The suite also has experiences for families, teachers and kiosk users. The family kiosk supports arrival and pickup, and the staff kiosk supports clock-in and clock-out. Teachers work in their own classroom workspace. Parents use their own linked portal for family information, messages and billing features available to them. Directors oversee these workflows and help troubleshoot, but should not use someone else's credentials. Use the separate kiosk, teacher and parent lessons for the detailed steps.

## Sections that depend on access

**Where:** Only the sections authorized for your account

Some sections are intentionally role-specific. Terminal store appears only when enabled and is separate from taking a family payment. Multi-location, Executive admin, Software invoice and Developer are not standard director destinations. White-label is also restricted. A director should not expect to see every executive or platform control. If a section needed for your assigned work is missing, ask the authorized administrator to review the role and school scope.

## Choose the workspace by the task

**Where:** Dashboard → task workspace → verify → follow up

Here is the route to remember. A new inquiry goes to Enrollment CRM. A contact correction goes to Families and Communication. A balance question goes to Billing and Payments. A missed staff punch goes to Staff and Access. A missing form goes to Records and Compliance. For attendance and daily care, use School Operations. Start the day on Dashboard, work in the section that owns the task, verify the result, and use Help when something remains unclear. You are ready to move into the task tutorials.
