FEZA innovation – Home
← All products

A project shaped around your nursery day

Nursery and Preschool

Nursery and Preschool Software

Keep attendance and collection records linked to each child while sharing daily updates with parents. In the nursery and preschool software we will build, we will select the areas teachers, parents and administrators need together.

  • Meals and sleep summaries
  • Collection by authorised people
  • Sharing permissions per child
Toy blocks, food bowl and blanket beside a tablet with food, sleep and person icons
  1. Discovery
  2. Scope and quote
  3. Development

When nursery updates stay in the classroom, parents keep calling

A parent asks about meals or sleep while the teacher searches for a paper note. Arrival time may be in another register, photographs on a personal phone and the evening collector remembered only by the class teacher. At shift changes, staff ask again which information is current. Fee information can become mixed into the same conversation as daily care notes.

Link short daily entries to each child to prepare a clearer parent summary. Attendance, meals, sleep and activities will be scoped around classroom use. Collection authority and payment information will be considered separately for different responsibilities. A parent's account having access to information will not be treated as permission to collect the child.

Information checked again at shift changes

  • Daily notes and collection details are kept in different places.
  • Photo and notification recipients are selected from messaging groups.

A daily workflow linked to the child

  • Attendance and care summaries will be linked to the relevant child's record.
  • Information sharing, collection authority and payment views will be scoped separately.

From morning arrival to daily summaries and evening collection

Walk us through a class's day using blank records. We will discuss which fields teachers complete with quick choices, when they add a short explanation and what the teacher on duty checks. Tell us how you would like to capture parents' preferences for immediate updates or an end-of-day summary.

  1. 01

    Record arrival and attendance

    Linking arrival times and absences to the child's record will be scoped. Your nursery's workflow will determine when a parent update is prepared and who checks it.

  2. 02

    Use short choices for daily entries

    Meal, sleep, toileting and activity records can be designed for classroom use. Additional teacher notes and photo sharing will be considered with separate permissions.

  3. 03

    Confirm collection and share the summary

    Authorised collector lists and time-stamped collection records will be scoped in the project. Releasing the daily summary to the relevant parent will be a separate sharing step.

From core attendance to photo permissions and nursery fees

Start by choosing what teachers need to enter during the day. We will review your short options rather than turn every daily field into a detailed text entry. Health and special dietary notes will be discussed separately according to need and access purpose. Including them in every parent notification will not be an initial assumption.

  1. Daily records for the first release

    Children, classes and attendance
    Child-parent relationships, class allocation, arrivals, departures, meals, sleep and activities can be selected for the first release.
    Collection list
    Defining authorised collectors, recording collection and showing staff when someone is not listed can be scoped.
  2. Extensions for your nursery

    Sharing and administration
    Photo permissions, announcements, health notes for authorised teachers and fee tracking can be added according to need.
  3. Notification infrastructure dependencies

    Parent messaging channels
    In-app notification needs will be identified. SMS or messaging platform delivery will be reviewed separately if your provider enables technical access.

Choosing between nursery updates during the day and one evening summary

Parents may prefer different ways of receiving information. Some want to see entries during the day; others prefer a combined summary. You can choose a sharing approach without changing teachers' recording habits. Recording an event and notifying parents will be treated as separate actions. Your nursery will identify situations needing separate consideration beyond these preferences.

Sharing time

Updates during the day
Preparing a notification after selected daily entries will be scoped.
End-of-day summary
Combining daily fields in the agreed closing workflow will be designed.

Teacher entries

Updates during the day
Selected short fields for meals, sleep and activities are used.
End-of-day summary
A summary uses the same fields; any additional commentary is chosen separately.

Parent preference

Updates during the day
The relevant parent's explicit preference and recipient details are considered.
End-of-day summary
Summary access is determined through child-parent relationships.

Health notes, class photographs and parent views need separate permissions

A teacher seeing an allergy note needed for daily care is different from a parent reading a class announcement. The software we will build will use classroom responsibilities and child-parent relationships as its basis. Who appears in a photograph and which permissions allow sharing will receive separate consideration in the sharing workflow.

Teachers and duty responsibilities

Access to a teacher's own class and collection details needed on duty will be defined separately. Allergy, medication and dietary notes will be scoped for authorised staff needs.

Information available to parents

Daily summaries, announcements and permitted photographs of the relevant child will be selected. Information access, photo sharing and collection authority will have separate records.

Reviewing sensitive records

KVKK, Turkey's personal data protection law, relevant legislation, child and health data, retention and access logs will be considered in scope. Your nursery is the data controller; parent documentation will be discussed with your authorised adviser.

Can the recipient of a daily nursery update also collect the child?

The parent receiving a summary may differ from the person collecting the child. When a relative's previously recorded authority changes, the teacher on duty needs the current list. For separated parents, information access and collection conditions may also differ. Automatically treating a message recipient as an authorised collector loses this distinction.

The project will scope child-linked accounts, notification recipients and collection authority separately. You will decide who verifies changes and how earlier collection records are retained. If children arrive or leave by nursery transport, discovery can examine which handover points need recording; transport planning will not automatically enter the first release. Handling legal restrictions will only be discussed within scope.

When a contact list becomes an authority list

  • Notification recipients may be assumed to have collection authority.
  • Changed collection details are passed verbally to the teacher on duty.

A collection workflow with separate checks

  • Information recipients and authorised collectors will be scoped separately.
  • Changes in authority will be distinguished from records of completed collections.

Add parent, class and collection relationships to nursery lists

Prepare more than names and telephone numbers for an import. In a sample without personal data, show which account relates to each child, where collection authority is recorded and how photo consent is stored. Whether current relationships can be established from older messaging groups will require separate review.

  1. 01

    Match children with accounts

    One parent's different children and one child's different parent accounts will be treated as separate relationships. Class and teacher allocations will be verified in a sample import.

  2. 02

    Check authority and permissions

    Source fields for information access, photo sharing and collection lists will be identified. Missing consent records will be handled according to your nursery's assessment within scope.

  3. 03

    Try a sample notification

    Recipient and content scenarios will use no real personal details. External messaging connections require provider access; incorrect recipients and delivery failures will be designed separately.

Examples for discussing nursery parent and teacher roles

Explore different parent and teacher views in our existing educational product. Daily care, collection and photo permission requirements will be defined separately for your nursery. Our service page can also help frame a conversation about custom development.

Discuss daily record choices and a blank collection list

Share blank examples of the fields teachers complete during a day and the collection checks they make. We will select parent summaries, photo permissions and administrative payment views as separate needs. This lets us describe both teacher and parent use in the first release.

  • Show your choices for meal, sleep and activity records.
  • Explain collection information needed at duty handovers.
  • Identify priorities for parent accounts and notification channels.

The proposal will follow the selected classroom workflow and sharing areas. Subscription use, support and additional development responsibilities will be discussed in writing.

How we work

We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.

  1. 01

    Discovery

    We listen to how your business works, your team and the tools you use today.

  2. 02

    Scope and quote

    Modules, priorities and price are set out in a written quote.

  3. 03

    Development

    We show working versions at short intervals and move on with your feedback.

  4. 04

    Setup and migration

    We move your existing records across and help your team get started.

  5. 05

    Support

    We run the software on a subscription and keep it up to date and secure.

Frequently asked questions

Won't this add to the staff's workload?

Keeping the workload down is a core design goal. Meals, naps and toileting are recorded by choosing options rather than typing, and the only thing staff write is an optional daily note. The screens are designed to be used on a tablet or phone in the room, without leaving the children.

How is children's privacy protected when photos are shared?

The scope can include sending each photo only to that child's parents and holding back group photos that include a child without sharing consent; parental permissions are stored in the software. Your setting is the data controller for the children's personal data, and we recommend handling privacy notices and parent agreements with your legal adviser.

Do parents have to receive every notification?

No. Letting each parent choose between live notifications and a single end-of-day summary can be included in the scope. Some parents want every detail, others find frequent messages intrusive, and that choice should stay with them.

How is access handled for separated parents?

Each parent gets a separate account, and access to information and permission to collect can be set for each of them independently. Where a court order imposes restrictions, these are entered and staff are alerted at collection. As one of the most sensitive situations a nursery deals with, this scenario is considered separately in the design.

We have several sites. Can we see them all in one place?

A multi-site setup can be included in the scope. Each site manages its own rooms, staff and registers, while the owner sees every site on one screen. Permission boundaries between sites are agreed in the discovery meeting.

Will a parent with photo permission also be authorised to collect a child?

We will scope photo sharing, information access and collection authority as separate relationships. Your nursery will be able to verify each person's authority separately; the design will consider how one permission must not automatically grant another.

Will the teacher on duty see every daily health note?

We will select the fields needed for duty responsibilities together. Collection checks and care responsibilities may require different information. Health note access, child data and relevant legislative requirements will be considered separately in scope.

How is the price set?

After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.

Do we receive the source code?

In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.

Who is responsible for what is done with the software?

We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.

Related products

Let's choose the records for a day at your nursery

Describe teacher, parent and collection responsibilities so we can define your custom development scope.

  • Meals and sleep summaries
  • Collection by authorised people
  • Sharing permissions per child