n-Basecamp Doesn't Have Gantt Charts. Here's What It Has Instead.
Basecamp deliberately skips a traditional Gantt chart view. In its place, it offers Hill Charts, a visual way to show how far along something is without pretending to know exactly when it'll finish, plus a straightforward Schedule for dates and milestones. If your team genuinely needs dependency-based scheduling, that piece has to come from somewhere other than Basecamp itself.
What Basecamp Gives You Instead of a Gantt Chart
Hill Charts ask people to place a task on a hill shape based on how much uncertainty is left, not how many days remain, which is a genuinely different way of thinking about progress than a timeline bar. The Schedule tool handles dates and milestones in a simple calendar view, but it doesn't link tasks together with dependencies the way a Gantt chart does.
This isn't a missing feature so much as a stated position: Basecamp's maker, 37signals, has been public about not wanting to build a Gantt view that implies a precision most project schedules don't actually have.
Where That Becomes a Real Problem
A simple schedule and a progress indicator cover a lot of client work fine. They stop covering it the moment a business genuinely needs to know that slipping task A pushes task B's start date, and task B's slip affects three other things downstream. That logic has to live outside Basecamp entirely, in a spreadsheet, a separate scheduling tool, or data pulled out of Basecamp and fed into something that actually models dependencies.
What We Build Around This Gap
Basecamp dates into a real Gantt view
To-do due dates and schedule milestones get pulled out of Basecamp automatically and fed into a dependency-aware scheduling tool, so the team keeps Basecamp for communication while still getting a real timeline view elsewhere.
Milestone-change alerts
When a Basecamp schedule date changes, the right people get notified automatically through whatever system actually tracks downstream work, instead of someone having to notice the change and pass it along themselves.
Need real scheduling logic without leaving Basecamp?
Tell us what your team currently tracks by hand to make up for the missing dependency view, and we'll scope what it takes to automate that instead.
Outgrowing what Basecamp can show you about your own schedule?
Tell us where the missing dependency view is actually costing you time, a spreadsheet someone maintains, a status meeting that exists just to catch slippage. We'll scope what it takes to automate that piece. Scheduling doesn't have to be the actual problem for this conversation to be worth having.
Let's talk