Planner Simple

Getting Planner Simple Working Without Losing Your Mind

I spent about three weeks last year trying to get Planner Simple to actually serve a purpose in our project workflow. It didn't happen cleanly. The interface is clean enough, but the gaps between what it does and what you need it to do are where people fall apart. I'm going to walk through how I ended up using it, the specific thing that broke my first month with it, and how I fixed it. This is not a polished tutorial. It's just what happened. Planner Simple is a lightweight project planning tool designed around the idea of minimal overhead. You define tasks, assign durations, set dependencies, and it gives you a schedule. That's the core. The name says exactly what it does, and it refuses to add features that complicate that. It doesn't have resource leveling built in. It doesn't do Monte Carlo simulations. If you need PERT analysis with risk-adjusted timelines, you're looking at the wrong tool. What it does well is letting small teams map out a sequence of work without spending more time on the planning tool than on the actual work. The scheduling engine uses forward and backward pass calculations to determine earliest start times, latest start times, and total float for each task. That's standard critical path method stuff, same as anything in Microsoft Project or OmniPlan, just exposed without the menu layers.

How I Set It Up

The first thing I did was define the project scope as a single summary task, then broke it into phases. Each phase became a group of child tasks with explicit duration estimates. I entered everything in days. I used workdays only, not calendar hours, because Planner Simple's default calendar is business days from 9 to 5 with weekends off. If your actual work happens outside that window, you either adjust the calendar or accept that the output won't match reality. Dependencies are where most people get tripped up. You can link tasks as finish-to-start, start-to-start, finish-to-finish, or start-to-finish. I stuck with finish-to-start because that's what 90% of our work looks like. The other 10% was overlap work where one person starts another task before the previous one fully completes. For that I used start-to-start with a lag. But I'll get to that problem.

The Problem I Hit

Here's the thing that nearly made me abandon the tool entirely. We had a task called "Content Review" that should have started two days before "Final Production" finished, but not before "Draft Approval" finished. In other words, Content Review and Final Production overlapped, but Content Review couldn't start until Draft Approval was done. This is a start-to-start dependency with a negative lag, and Planner Simple's interface doesn't make it obvious how to enter it. I tried typing minus two in the lag field. Nothing happened. I tried entering it as a separate constraint. It created a completely wrong schedule. What actually worked was setting the dependency type to start-to-start, then going into the dependency details and entering the lag as a negative number in the edit dialog instead of the main dependency grid. The UI shows the lag as a positive number by default, which is misleading. You have to open the detailed dependency view and override the sign manually. I found this by accident after a couple of hours of frustration. That might sound minor, but in a tool this stripped down, missing features like that create friction points that compound. If you're planning a project with any significant parallel work streams, this limitation will bite you.

What People Miss About It

The first counter-intuitive thing I learned: Planner Simple's critical path isn't always the longest path through your task graph. It's the longest path in terms of duration, yes, but it also depends on how you've set your constraints. If you have too many mandatory start-no-earlier-than constraints, the tool treats those as hard barriers and the critical path shifts. I had a project where I expected six tasks to be on the critical path and it showed only three. The other three were blocked by constraints I'd placed during an earlier revision that I forgot about. The fix was to audit every constraint and change anything that wasn't absolutely necessary to a flexible dependency instead. The second thing: total float doesn't mean free float. Total float tells you how much a task can slip before it pushes the project end date. Free float tells you how much it can slip before it pushes the next task's early start. Planner Simple shows both, but they're not labeled clearly in the default view. You have to switch to the detailed schedule table to see the free float column. Without that distinction, you can misread a task as having more flexibility than it actually does, which leads to schedules that look fine on paper but fall apart in practice.

Practical Workarounds for the Gaps

There's no resource leveling, so if two tasks are assigned to the same person and their schedules overlap, Planner Simple won't auto-shift them. I ended up building a simple resource calendar outside the tool and manually rescheduling tasks that conflicted. It took about twenty minutes per project iteration, which is acceptable for small teams. If you have a team larger than ten people or multiple shared resources, this manual approach stops being viable. You'd be better off with something like GanttProject or even a well-configured spreadsheet with conditional formatting. Another gap: there's no export to PDF with a proper Gantt chart layout. The built-in print function outputs a basic table. I got around this by exporting the schedule to CSV, importing it into LibreOffice Calc, building a Gantt chart from the data, and printing that. The whole export-and-format process takes about ten minutes once you've got the template set up.

When Planner Simple Isn't the Right Call

If your project has more than fifteen active tasks with interdependent constraints, or if you need to track budget against earned value, or if you're managing a project with regularly changing scope, Planner Simple will fight you. The interface assumes a static plan. Anything that requires frequent re-baselining or what-if scenario modeling becomes tedious because you have to rebuild the dependency graph from scratch each time rather than cloning a baseline and adjusting variables. For those cases, I'd recommend something like ProjectLibre if you need full CPM features and free software, or ClickUp if you're willing to pay for a tool that handles scope changes and resource conflicts automatically. Planner Simple occupies a narrow lane: small projects, stable requirements, few shared resources, and a team that doesn't want to spend their Tuesday learning software features.

Bottom Line

I still use Planner Simple. I use it for internal projects that have a clear beginning and end, a small team, and deadlines that won't shift three times in a week. It gets me from idea to schedule in about fifteen minutes instead of the hour it would take to configure something more powerful. The trade-off is real and it shows up in the dependency lag issue and the lack of automated resource management, but for the right project it's fast enough that the friction is worth it.