Views and folder structures

There are at least 2 ways to split up your documents:
1) Create separate classes for each type of documents
2) Add one or more properties in common classes to add information on which department, court type etc. the documents are related to. For instance you can have a select property for Court and select from a Value List with your different courts. And you can have a property for Department and select from a Value List with your departments. Once you have that in place, you can easily create Views to show only documents related to e.g. Family Court or even to a combination of Family Court and Client Files.
Apparently you didn't have one of these solutions in place when you imported your templates, so you will have to run through them and add the necessary properties to each template.
You can add the court type to the naming function but you should only do that to help users read and identify documents from the lists. This is not well suited for grouping or filtering in order to show different types of documents in separate Views.
Karl

Thanks Karl that was a great help!! Am back on track...luckily I have not got too far so back-tracking is easy right now.

Also does this mean that once the card is populated for the type of court document chosen that these properties will only need to be input once and it will populate all the documents. For example, if I have one card for Applicant and six associated court documents then they should all populate based on the info from the class card Applicant??? and same with Respondent etc.

:)

Not quite sure that I understand exactly what you are asking.
You can fill selected properties on your templates with default values that will then have that default value in every new document created from the template.
With M-Files 2015.1 you can also configure the metadata card to have default values based on different rules. This is very flexible so you can decide that if one property has a certain value then another property by default should have a specific value, or the other property should be hidden or made mandatory or whatever you need.
Users can always overwrite default values, so they are really just a help to speed up work in cases where default values are appropriate.
You cannot populate properties in existing documents automatically unless you write a script that will lookup the documents and fill the properties for you. Only if you use Automatic Values in certain properties, then you can recalculate the values of that property in existing documents.
Karl