How do I find out who is overallocated or overloaded with iDBQuery?
Ask iDBQuery who is overallocated and it compares assigned work or booked hours against capacity across your team, flagging people over 100 percent and those with room. The answer is cited to your project data, so managers can rebalance workload before people burn out or deadlines slip.
Uneven workloads cause burnout on one side of the team and idle capacity on the other, but the data lives in project tools, timesheets and resourcing sheets that nobody reconciles. iDBQuery brings it together and answers plainly.
- It compares assigned hours or bookings against each person capacity
- It flags who is over-allocated and who has spare capacity
- It rolls up utilisation by team, role or project so you see the shape of the load
- Every figure is a cited answer traceable to the underlying assignments
Ask *who is booked over 100 percent of capacity next month, and who is under?* iDBQuery returns both lists so you can rebalance. Follow up with *which projects are driving the overload?* to find where the pressure comes from.
Because iDBQuery joins resourcing, project and time data into one live model with no pipeline, managers get a current view instead of a stale planning sheet. Cited answers make the rebalancing conversation fair, since each person load traces to real assignments. Operations, PMO and services leaders use this to prevent burnout, hit deadlines by moving work to people with capacity, and plan hiring around genuine, evidenced demand rather than a gut feeling that the team is stretched.
Updated 2026-06-22