Keep in mind that each area (#.__) can have ten categories (#.__)
So IF you have more than 10 TODOs, or more than 10 servers, or more than 10 customers, or more than 10 inhouse projects, THEN you will run out of numbers.
I can imagine that especially for your projects. If you do just one project per month then this will work for less than a year.
For each of those categories, consider if it would make sense to divide them into segments or something?
So 31.__ could be general doctors, 32.__ could be dentists, 33.__ could be surgeons, etc.
Then 32.04 could be dentist Smith, 32.05 is dentist Jones, etc.
But then you have no index values for the individual files or notes within “32.04” – do you need that??
Before settling on any given structure, play around with ideas about what sort of data to put at what level. This is very individual, so it’s hard to give a clear answer without knowing more about what sort of stuff you have below the levels you listed.
You can use this excellent little online tool to try out your ideas:
20-29 → 21 TEST → 21.01 → individual file
Does the individual file should get a number or only the folders ?
When i compare it with the screenshot from JD website my file is a “unique thing” and in this example there is an ID number
This feels like you might run out of space eventually? Can you guarantee that you won’t have more than 9 servers?
I don’t think that ‘a particular server’ is a category. Remember, a category is ‘a type of work that you do’. Managing servers is the type of work, and each server is then an item within there: each server is an ID.
It looks like each server might have any number of things associated with it?