Do you have any experience with Abaqus ? PrePoMax is based mostly on that software due to CalculiX using almost the same syntax as Abaqus. Thus, I would rather suggest following the way it’s handled in Abaqus to not confuse users with similarities to different software. In Abaqus, there are no such checkmarks (only job status: Submitted, Running, Completed, Terminated or Aborted) and you can have multiple models within a single database (they have separate containers in the model tree) but in PrePoMax it wouldn’t work since it uses a different approach with 3 tabs - for geometry, FE model and results. However, what could be implemented is the way Abaqus handles reruns. There you create jobs (like Analysis-1 in PrePoMax) and when you submit them, they use inputs from current settings in GUI. If you change something in the setup, you can still access old results but if you submit the same job again then the analysis will use new inputs. So you can have multiple jobs, with some of them containing results from previous runs with different settings and others containing results based on current settings. Of course, you may also have jobs for different models in the tree.
What’s more, in Abaqus it’s always possible to access the results of the currently running job if some increments were completed and thus output is partially written. You can also access the results if the analysis fails or is killed by a user but manages to complete some increments. In PrePoMax it’s more tricky. From what I’ve noticed, you can’t access the results when the analysis is running or when you kill it but you can open the results when the analysis fails to converge at some point. It doesn’t seem to be a limitation of CalculiX and its results files so it would be great if this behavior could be changed in PrePoMax.