Capacity/bandwidth planning?

I have something like this in my main app, a summary report predominantly displayed on the homepage so managers and people on the same team have basic visibility to each other's workload.

First I made a table called "User Details" to store our team member data. Which team they are on, work location, role, capacities, and of course a "User" field where I select the appropriate Quickbase user. (Notes field is also handy, I log why obscure users have access to our app.)

When I make a user drop down in another table (like the Projects table), I make a relationship to the User Details table and use it to select the project member instead of just adding a basic "User" field type. This way I can pull over other data about the project member and can also get fancy, like filtering the list so that the field only shows certain types of users. (I also went and added this to existing tables, used import/export to copy over the username data from the old basic User field.)

Then back at the User Details table I add a summary field that counts their number of active items in each relationship (such as projects.)

You could setup this basic relationship counting projects, then add project levels with a points system to your Projects table and bring it over to the User Details table as an additional summary field. Finally, make a formula field to compare it to capacity and a summary report to display this data.