Pinch-to-zoom Gantt,
right on your phone.
Build schedules with phases, dependencies, and milestones — no laptop required. Critical path auto-calculates. When change orders add days, the schedule shifts automatically.
Phase-based task management
Organize work by phase — sitework, foundation, framing, finishes — with each task carrying a duration, start/end, dependencies, and progress percentage.
Watch How: Move a Task on the Schedule
- Drag to reschedule, tap to edit duration
- Predecessor / successor dependencies with FS, SS, FF lag
- Percent-complete tracking that rolls up to the phase
- Milestone markers that stand out visually
Critical path, highlighted.
The app computes the critical path every time you edit a task — no plugin, no separate tool. Tasks on the critical path glow red so you always know what's driving your finish date.
- CPM computed automatically from dependencies
- Total float shown per task
- Red highlighting for zero-float tasks
- Change order schedule impact applies instantly
Schedule health, scored against the DCMA assessment.
The federal Defense Contract Management Agency assessment, built in here, with no separate scheduling licence and no add-on fee. Ten of the fourteen DCMA checks run in full on your own schedule, an eleventh runs as a labelled proxy, and three do not run at all. We would rather print which is which than round the number up.
- Running today — #1 Logic (missing predecessors and successors), #2 Leads, #3 Lags, #4 Relationship Types, #5 Hard Constraints, #7 Negative Float, #8 High Duration, #9 Invalid Dates, #10 Resources and #13 CPLI. Each is computed from data the engine already carries — the typed dependency links and their lags, the date anchors, and the total float the critical-path pass returns.
- Running as a proxy, and labelled as one on the screen — #11 Missed Tasks. The real test compares progress against a data date; this engine has no data date, so it measures tasks that should already be running against the schedule’s own span instead. The check says so on itself, not in a footnote.
- Not running — #6 High Float, #12 Critical Path Test and #14 BEI, and the reasons differ. #6 (float above 44 working days on more than 5% of tasks) is a small addition and is not built yet. #12 needs a perturbation run — push a critical activity out 600 days and confirm the finish moves with it — which is a scheduling pass we have not written. #14 BEI is baseline tasks completed divided by baseline tasks due by the data date, and this engine has no data date by deliberate design, so the denominator does not exist. We will not fake it with a slippage number and call it BEI.
- Thresholds are tuned for residential job sizes rather than a federal megaproject — the high-duration limit in particular is well below DCMA’s 44 days, because a 30-day task on a kitchen remodel is already a problem.
- Live overall score 0–100, plain-English failure reasons (not just “DCMA #5 failed”), and tap a check to jump to the offending tasks.
A schedule link your subs can answer
Share a read-only copy of the schedule with a link. A sub opens it on any phone, with no app and no login, sees the critical path, and answers you about the tasks they are on. Each answer comes to you as a ready-to-send email or text. You decide what moves on your Gantt; nothing a sub taps changes it.
- One link per sub, no install and no account
- Confirm a date or ask to reschedule it, with a reason
- Log a daily update on a task: percent done, hours and crew size
- Every reply reaches you as an email or text you can read and act on
Weather-aware reflow — and a forecast that admits when it isn't one.
Pull the forecast for the jobsite, see which outdoor tasks are exposed, and reflow the schedule around them in one tap — with the critical path recomputed, not just the dates nudged. Every shifted task keeps the reason attached, so the owner asking "why is the deck a week late" gets an answer instead of a new date.
The part most software would hide. A weather feature is only as good as the forecast behind it, and today's builds ship without a live weather key, so days come back from a simulator instead of a weather service. We do not quietly pass those off as a forecast. Every simulated day is labelled SIMULATED WEATHER — NOT A FORECAST on the screen it appears on, and the delay log flatly refuses to record a weather delay day that has no live observation behind it — so the log stays empty rather than filling up with invented evidence. A delay record you cannot defend in a claim is worse than no record at all.
- Outdoor-task exposure flags on the Gantt
- One-tap reflow with full CPM recalculation and an undo
- Live days and simulated days are visibly different, always
- Weather delay log writes on live evidence only
Built for the full schedule lifecycle
From initial planning to closeout, every schedule feature you need without the desktop software overhead.
Baseline vs actual
Lock a baseline at kickoff. See variance per task as actuals come in.
Milestones
Foundation complete, dry-in, TCO — shown as diamonds on the Gantt.
Resource assignment
Assign crews or subs to tasks. Flag overallocation across projects.
Weather-aware reflow
Weather-sensitive tasks are flagged against the jobsite forecast and the schedule reflows around them, critical path recomputed. A day we can't get a live forecast for is marked simulated and kept out of the delay log.
CO auto-extension
Approved change orders with schedule impact extend the Gantt automatically.
Client-safe view
Owners see a simplified read-only version in their portal — no editable internals.
Schedule import
Bring in a schedule from Excel or Microsoft Project XML. You check the column mapping and a preview first, and your current schedule is saved as a baseline before anything changes. On Pro.
Last Planner
A three-week lookahead with a constraint log, a weekly plan the crew commits to, and percent plan complete with the reasons that cost you most. On Pro.
Ready to run your schedule from the field?
Start free and set up your first project in minutes.
Start free