Consistent language
Help staff classify observations using a shared category rather than scattered labels.
Bring structure to your school’s observations.
Create categories such as Achievement, choose who can use them and design the details staff need to record.
Give observations a shared category.
Separate adding, editing and visibility.
Choose the details each form needs.
Create a category such as Achievement so staff know where an observation belongs. Choose who it relates to and add a short introduction for the entry form.
Staff start with the same category and the same context.
Academics / StudentRecord the student’s achievement and the details that help explain it.
Not everyone needs the same access. Set adding and editing permissions separately, then decide how observations can be shared with parents.
Clear responsibilities for entering, changing and sharing observations.
Academics / StudentA category tells staff what an observation is about. Its form tells them what details to include. Define the fields and review how they will appear before saving the form.
Staff know which details to include, instead of guessing what to write.
Academics / StudentMake this detail required when an observation is entered.
Record the student’s achievement and its context.
See your categories in one list, with their type and form status alongside them. Filter the list, reuse an existing category and form, or archive a category when it is no longer needed.
Reuse useful setups without building every category and form again.
Academics / StudentReuse a category and its form together.
Help staff classify observations using a shared category rather than scattered labels.
Keep adding, editing and parent visibility separate and intentional.
Define the information needed to understand an observation, not just its category name.
Explore how category settings fit your school’s observation process with our team.
A category groups observations under a shared purpose. For example, Achievement can identify student observations and have its own header, permissions and entry form.
Adding permissions determine who can create an observation in the category. The supplied setup defaults to all users when nobody is selected. Editing defaults to the administrator and the user who added the observation.
No. Parent visibility is a separate setting. The supplied option allows visibility to be decided while adding an observation.
The supplied designer includes a field name, field type, mandatory setting and form preview, helping your school define category-specific information.
The category list includes copying a category and its form, editing, deleting, creating a form and archiving. Confirm how these actions affect existing records during your demo.
This page explains category configuration. Confirm employee observation authoring, reporting availability and record-handling rules with the Schogle team during a demo.
Discover category setup, permissions and forms in a guided Schogle demo.