Kind of Lost
·OR Tools
·Project Scheduler
·MS Project leveling
·Support
Microsoft Project makes it easy to allocate resources to tasks and to see who is over-allocated. Resolving the over-allocation is the hard part. Project’s leveling command (Level All) delays tasks one at a time according to a priority order: quick and usually reasonable, but nothing tells you how far the result sits from the shortest schedule your people could manage. This free tool reads your plan as XML, levels it with the Google OR-Tools CP-SAT solver, and gives you back your own file with the levelled dates written in.
Level an MS Project planFree, no signup. Save the plan as XML first; up to 60 tasks.
That last step is a heuristic: it works through the conflicts in that order rather than searching for the best arrangement overall. Scheduling a project around limited people is the resource-constrained project scheduling problem, and a priority rule is a fast approximation to it, not a solution.
Your original file, patched — not a new plan rebuilt from a simplified copy. Your task hierarchy, summary tasks, milestones, resource assignments and custom field values all stay untouched. Each task’s start and finish are updated, summary rows and assignments are rolled up to agree with them, and every task the crew limit pushed later carries a Start No Earlier Than constraint on its new date. That constraint is what stops Project dragging the task straight back when the file opens. Remove those constraints in Project and the levelling is undone, much like Clear Leveling.
Edit the plan in Project and upload it again, and the scheduler respects those same constraints, so the two programs agree. To re-level from scratch instead, tick the box above the results that ignores them.
Read directly: all four link types with their lag; durations, converted to working days using the file’s own hours per day; work resources, with Max Units rounded to a number of people; assignment units as people per day; Must Start On, which becomes a pinned task; and Start No Earlier Than, honoured as a date the task may not start before.
Folded or approximated, with a note each time: summary rows are dropped and links from them now come from the tasks underneath; zero-duration milestones are spliced out so their successors wait on what the milestone waited on; a task with several resources keeps only its largest; part-time units are rounded to whole people; lag measured in elapsed time is converted to working days; material resources are skipped. The calendar is read as a five-day or a seven-day week, and holidays and other non-working exceptions are not modelled — the import says how many there were, because each one moves later dates a working day earlier than Project would show them.
Not applied: As Late As Possible, Must Finish On, Start No Later Than, Finish No Earlier Than and Finish No Later Than. The affected tasks are named at import. On export, their dates still move, but the constraint itself is left exactly as you set it; the tool will not overwrite a rule it could not read. Check those rows after opening, because Project settles any disagreement its own way.
Limits: 60 tasks once summary rows and milestones are folded away — for a larger programme, import one phase or sub-project. Primavera .xer files are not supported.
Does it replace Project? No. It does one job — deciding when each task starts so no resource is over its Max Units — and hands the plan back. Costs, baselines and tracking stay in Project.
Will the dates match what Project shows? On a plain five- or seven-day calendar the round trip is stable: export, re-import, and the same plan comes back with the same dates. Holidays are the usual cause of a one-day gap, and the import notes count them, along with every other approximation listed above.
What if I have no Project plan yet? Use the Gantt chart template for Excel instead; the same solver reads it. For construction work see construction planning and scheduling, and for site meetings the 3-week look-ahead template. The critical path and project crashing pages cover the other two questions the scheduler answers.