What we do
Tools
Industries
Department
How we workLet's talk →
Home/Basecamp/No Basecamp Gantt Chart

There's No Basecamp Gantt Chart. The Lineup and Hill Charts Cover Part of the Job

A client asked for a Gantt chart, and you went looking in Basecamp for the button. There isn't one. Basecamp has no Gantt view and no task dependencies, and that's by design rather than an oversight. What it does have is the Lineup, a timeline of every project by start and end date, along with Hill Charts for progress, card tables for flow, and to-dos that carry start and due dates.

Basecamp and Gantt charts

No Gantt chart, no dependencies. A to-do can have a start date and a due date, but it can't wait on another to-do, so one slip never moves the next.

Dates across projects: the Lineup draws each project as a bar from start to end date, shows overlaps and who's assigned, and carries account-wide markers for key dates.

Progress inside a project: Hill Charts show whether each piece of work is still being figured out or is on its way to done.

Day-to-day flow: card tables move work through columns, kanban-style, and each project's schedule holds its events and milestones.

The Basecamp Lineup beside a true Gantt chart

Basecamp Lineup

One bar per project

  • Built in, and needs nothing beyond each project's start and end dates.
  • Shows which projects overlap and who's working on what.
  • Markers flag account-wide dates, such as a launch or a holiday.
  • Bars stand for whole projects, not the tasks inside them.
Gantt chart

One bar per task, linked together

  • Tasks are linked, so a late one pushes everything that waits on it.
  • A critical path shows which slips move the finish date.
  • Baselines compare today's plan with the one you agreed.
  • Needs a separate tool, or a layer built beside Basecamp.

If the question is "what's running this month?", the Lineup answers it. If it's "what moves when this slips?", Basecamp can't, and that's the gap worth filling.

Five questions that show whether you need dependencies at all

  • Does one team's late work push back another team's start?

    That one is a dependency. If handoffs rarely wait on each other, the Lineup and a weekly check-in may be all you need.

  • Do clients hold you to a finish date that should move when their feedback is late?

    A dependency model makes the knock-on date plain to see, instead of something argued over on a call.

  • Is someone keeping a spreadsheet next to Basecamp just for dates?

    That sheet is already a Gantt chart kept by hand, and it drifts every time a date changes in one place and not the other.

  • Do you need the chart, or the warning?

    Knowing a milestone moved may matter more than seeing bars. If so, that's a smaller build than a full schedule.

  • Would the team move to a scheduling tool, or stay in Basecamp?

    If they're staying, the dependency logic has to sit beside Basecamp and write its dates back in.

Dependency logic beside Basecamp, with dates written back in

n-frames builds that layer on Basecamp's API. It reads each project's to-dos and schedule entries, holds the links Basecamp doesn't (this to-do waits on that one, with so many days between), and when a due date changes it works out what else has to move and writes the new due dates onto the waiting to-dos. The team keeps working in Basecamp, and the dates stay true to the plan.

Basecamp's API documents what this needs: to-dos carry starts_on and due_on and can be updated, schedule entries can be created and changed, and Lineup markers can be added or moved account-wide. One trap for whoever builds it: a to-do update expects every existing field, so a request that sends only the new due date clears whatever it left out.

If people want to look at bars, the same dates can feed a Gantt view in a separate tool, while Basecamp stays the one place a date gets changed. For the integration side in general, see the Basecamp API page.

Basecamp timeline and scheduling questions

Does Basecamp have a Gantt chart feature?

No. There's no Gantt view in Basecamp and no setting that turns one on. The nearest built-in view is the Lineup, which shows whole projects on a timeline rather than the tasks inside them.

What is a Basecamp Hill Chart?

A progress view for a to-do list. Each piece of work is a dot on a hill: on the uphill side the approach is still being worked out, and on the downhill side it's known and being done. People drag the dots themselves, so it shows judgment rather than dates.

Can I get Gantt-style dependency tracking with Basecamp?

Only from outside it. One route syncs Basecamp dates into a scheduling tool, which leaves two places to keep in step. The other puts a layer on Basecamp's API that holds the dependencies and pushes new due dates back. n-frames builds the second kind, so planning doesn't mean leaving Basecamp.

Does Basecamp support task dependencies at all?

No. To-dos have start and due dates, assignees and subtasks, but none of them can be set to wait for another, and moving one never moves the rest.

What's the difference between the Lineup and a Basecamp project's schedule?

The Lineup is account-wide and shows each project as one bar, with markers for shared dates. A project's schedule lives inside that project and lists its events, milestones and dated to-dos, and it can be subscribed to from Google Calendar, Outlook or HEY Calendar.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.