Resource Allocation Heatmap
Upload your .mpp or MSPDI XML. We compute per-resource weekly utilization and surface every overallocation hotspot, before they turn into missed deadlines.
What you see
Weekly utilization grid
Every resource × every week in one view. Green is healthy, red is trouble. Scan the whole plan in 10 seconds.
Top 10 hotspots
The specific (resource × week) combos where utilization exceeds 100%, sorted by severity, each with the tasks driving the overload.
Honest capacity math
40-hour working weeks × MaxUnits. If your resources run non-standard calendars, read the FAQ, calendar overrides are on the roadmap.
Per-resource timeline (in PDF)
Unlocked PDF includes a dedicated page per overallocated resource with their full weekly timeline. Great for 1:1 workload conversations.
How it works
Upload your file
Drag and drop a .mpp or MSPDI .xml up to 50 MB.
See the heatmap
We parse the file, distribute assigned hours across working days, and render a full resources × weeks grid.
Fix the hotspots
Click a hotspot to scroll to its cell. The unlocked PDF includes per-resource timelines for 1:1 conversations.
What happens to your file?
We parse your file in memory, compute the heatmap, and discard the source bytes. The file is never written to disk. What we keep: the structured heatmap result (resource names, weekly utilization numbers, task names referenced in hotspots), associated with a random analysis ID. If you unlock the PDF, your email is stored (AES-256-GCM encrypted at rest).
We don't share data with third parties or use it for training.
Frequently asked questions
What does the Resource Heatmap show?
A grid of your project's resources (rows) across weeks (columns). Each cell is colour-coded by utilization %: green under 80%, yellow at capacity, orange 101-150%, red over 150%. The top 10 overallocation hotspots list the specific (resource × week) combinations with the tasks driving each overload.
Is this free?
Yes. Upload your .mpp, see the heatmap inline, download the PDF for free. No credit card, no trial. We ask for email only for the PDF delivery + occasional product updates - unsubscribe any time.
How do you compute utilization?
For each assignment, we distribute the total hours uniformly across the working days (Mon-Fri) of the task. Each resource's weekly capacity is 40 × MaxUnits hours (so a half-time resource has 20h/week, a 2.0-FTE team resource has 80h/week). Utilization = assigned hours / capacity × 100.
What if my resource calendars aren't standard Mon-Fri 40h?
Current limitation: the MPXJ parser we use doesn't yet surface per-resource calendar overrides, so every resource gets the standard 5-day 8-hour week. If your team works non-standard calendars, your utilization numbers will be directionally correct but skewed. Resource-calendar support is on the roadmap for the next MPXJ sidecar release.
What file formats are supported?
Native .mpp (Microsoft Project binary) and MSPDI .xml up to 50 MB. Same parser as our Schedule Health Check and Migration Preview freebies. Password-protected or pre-2003 files → export to MSPDI XML first via File → Save As → XML.
What happens to my file?
We parse it in memory, compute the heatmap, and discard the source bytes. We don't store the source file. What we keep: the structured heatmap result (per-week utilization numbers, resource names, task references in hotspots) associated with a random analysis ID. If you unlock the PDF, your email is stored (AES-256-GCM encrypted).
Why is a resource missing from the heatmap?
Three reasons we filter resources: (1) type is MATERIAL or COST (not time-overallocatable); (2) zero assignments in the project; (3) all their assignments had missing/weekend-only dates and got skipped. Check the warnings panel above the heatmap - skipped assignments surface there.
What about split tasks or leveling delays?
Known limitation: MPXJ reports a combined (start, finish) range for split tasks, so we distribute work uniformly across that range even if the actual plan has a gap in the middle. Your utilization may read slightly hotter than reality for split tasks. MPXJ-side split preservation is on the roadmap.
Are there any usage limits?
Yes - to keep these tools free and fast for everyone, we apply reasonable limits: up to 5 uploads per day, and up to 10 email unlocks per email per day. Limits reset on a rolling 24-hour window. If you hit a limit, we'll tell you when you can retry. For higher-volume needs, email support@onplana.com.
Stop guessing who's overloaded.
Onplana auto-detects resource overallocation across your portfolio and suggests leveling moves. Free tier supports the same .mpp import you just used.