Project planning and management tool

Make time for
every handoff.

See who’s building, reviewing, and testing across projects. Put each contribution on an hourly timeline and catch clashes before they hold someone up.

Folded pastel paper ribbons bridge parallel lanes on a planning grid.
BuildReviewTestRelease

Interactive example

One day, two views.

A project can look on track while its reviewer is booked twice. Switch views or select a block to follow the work.

Wednesday

Sample team 9 am – 5 pm
Group by

Scroll across the timeline to see the full day.

Project / task
9 am10 am11 amNoon1 pm2 pm3 pm4 pm
Lumen appAPP-14 · Refund flow
Orbit APIAPI-08 · Auth update
Atlas webWEB-22 · Checkout
Each block shows planned hours

Ren is booked twice at noon.

Lumen’s review and Orbit’s release both need Ren from noon to 2 pm.

Weekly workload

Where did the review time go?

Ren spent six hours reviewing against four planned in this sample week. Seeing that difference helps the team reserve enough time for next week’s handoffs.

Ren Park Review hours · Sample week
Planned4h
Logged6h

Work across tickets

Can Maya spare two hours?

Maya owns the saved filters ticket. Ren needs her for code review, and Alex needs her for testing. Switch views before booking her for a release.

How this compares with Linear

A Linear issue can have one assignee at a time. Here, Ren owns the search endpoint and Maya’s two review hours count toward her own workload. Read Linear’s assignment guide.

Maya Chen

Sample Thursday · 8-hour day

7h booked1h free
  • Search endpointAPI-38 · Owned by Ren Park
    Review2h from 9 am to 11 am
  • Saved filtersWEB-41 · Owned by Maya Chen
    Build3h from 11 am to 2 pm
  • Export reportOPS-12 · Owned by Alex Lane
    Test2h from 2 pm to 4 pm

Two-hour release requestOnly one hour fits on Maya’s Thursday.

7 hours visible. 1 hour free.

Dependencies between phases

What unlocks the next team?

Maya signs off on the search API at 11 am. The platform team monitors it until 4 pm. Which milestone should unlock the mobile team’s one-hour compatibility test?

Start mobile QA after
Thursday
Search endpointAPI-38 · Platform team
Search filtersMOB-21 · Mobile team
11 amQA start

QA finishes by noon while the API team keeps monitoring. That’s a 5-hour head start on the same test.

How this compares with GitHub

GitHub links a blocking issue to a blocked issue. This example ties the mobile test to one phase of the API ticket, so the two teams can work in parallel after sign-off. Read GitHub’s dependency guide.

Share a handoff from your team

Phase checklists

When is a handoff ready?

A software review and a design approval have different finish lines. The idea is to let each team name its phases and choose the checks that unlock completion.

Try a template and complete its review.

Sample template
BuildReviewTestRelease
Refund flow

Code review

1 / 2
Required checks
1 required check left

One-time import

Bring the tickets
you already have.

The proposed one-time import accepts CSV exports from Jira and Linear, and TSV exports from GitHub Projects. Keep the source reference, apply a phase template, and manage the project here from then on.