Whether you are establishing categories for a new database, or reviewing the options in an existing one, it is easy to underthink one topic and overcomplicate another. Work categories is a major area. Too many people want their choices in one dropdown data field and don't realize if they combine two dropdown data fields, they have more reporting power to include or exclude categories. The biggest culprits may be found as MaintenanceDirect "Crafts" and ITDirect "Problem Types" along with both applications' "Purpose" category.
First, the definition: "Crafts" or "Problem Types" are your categories of work. "Purpose" is the reason or the "why" behind performing that work.
Now, let's review a few examples. In facilities, custodians typically perform a huge amount of event setups...yet so can electricians, carpenters and other personnel. Same example in tech departments: event setups can include audio-visual, projectors, cables, wireless access, etc.
What some school operational departments to try to do is have a dropdown box to say "Carpentry: Event Setup" or "Carpentry: Installation" or "Carpentry: Removal" and before you know it, the list grows and has to be replicated for each job type. In reality, all that is needed is to have a Craft in MaintenanceDirect for "Carpentry" and then have generic Purposes of "Event Setup", "Installation", "Removal", "Refinishing", etc. Electricians, Glaziers, HVAC and other job types often have the same reasons of performing many of their jobs as well, so there's no need to complicate the list. Simply pick a job type and pick a reason or purpose in a work order. Categories can always be added as needed, so start out small and look for the trends that you need to trend.
Same for IT. It is easy to turn on every category of Problem Type in ITDirect, but that list becomes cumbersome. Who wants to pick from a list of 170 work categories?!? In addition to making your head swim, this can cause user abandonment! Instead of using "Server" and "Server Operating System" and "Server Repair" and "Server Updates", consider just using "Server" and then have Purpose codes relating to OS, repair, updates, installations, etc. as those categories can easily be applied for other Problem Types such as laptops, desktops, mobile devices, network equipment, etc.
When you use two categories in conjunction with one another, it allows you to break down reports and graphs into much simpler context. When you generate reports in MaintenanceDirect or ITDirect, you can pick a work type from a much simpler list and decide what to include/exclude from the purpose or reason of those jobs that is also a simpler list. Plus, it makes any graphs more legible vs. a jumbled mess, all while keeping it simple for your end users in your buildings. As a side note, it doesn't complicate any automatic routing of work, it can actually make it simpler as routing can include work type and/or reason.
If you really need to get into nitty-gritty details about exactly what components or systems what you worked on, that is why Group/Classification/Type and/or Equipment (asset inventories) are available as options. You see those categories, your end users do not. Again, it still keeps it simple for them, but allows you searching and reporting power.
RELATED TIP: Ever wonder what your "requesters" see? You may see a link on your home page's left side for "MySchoolBuilding" to experience what they experience.