Browse articles

Large projects

Break a large, multi-building programme into a deep dated hierarchy, and use the row chevrons to move between a one-line overview and full detail.

What you'll achieve

Break a large, multi-building programme into a deep dated hierarchy, and use the row chevrons to move between a one-line overview and full construction detail.

You'll end up with: A five-level dated hierarchy, Marina Quarter down to Concept Design, that collapses to a single overview bar and expands back to full detail with the row chevrons.

This is an optional step of Plan the work. Model the work programme covers the shape most projects need: a project bar and a lane of stages underneath it, two levels, and done. That's still the right default for a single-building commission like Riverside Apartments. This article is for the projects that outgrow it: a big enough programme that two levels stop being enough to plan or report against, and you need real structure underneath the stages themselves.

We'll build one for Marina Quarter, a multi-building residential development at Northlight Architects, five levels deep: the project, its towers, a level within a tower, the areas on that level, and the design stage inside one of those areas.

When a deep tree earns its keep

Two levels are enough as long as a stage is the smallest thing you plan or report on. A large programme changes that. Marina Quarter has two towers, each tower has dozens of levels, and each level has areas that get designed, documented, and delivered on their own timetables. Flattening all of that into a single lane of stages would work for a week and then become unreadable: dozens of same-named bars with no way to tell which building or level they belong to.

Going deeper buys you something two levels can't: a stable planning and reporting layer at every size of thing you actually manage. Expand to the tower level and you see each building's overall span. Expand further and you see a single level's programme, then a single area's, then the actual design stage. Collapse back up and everything folds away into the number above it. The depth is there because the programme itself has that many meaningful layers, not because deeper is inherently better.

Build the hierarchy, level by level

Each level is drawn the same way you drew the project and stages in build the work programme: expand the row above it, then drag a dated bar in the lane that appears. The only difference here is doing that four more times, once per layer, each nested inside the one before it.

  1. 1

    On the schedule, click New project. Give it the code MQ and the name Marina Quarter, set Status to Secured, and click Create project.

  2. 2

    Point at Schedules and choose Project schedule. Switch to Monthly and click the arrow beside Marina Quarter.

  3. 3

    Drag across Marina Quarter's row to set its dates, August to next June.

  4. 4

    Draw two bars underneath it and name them Tower A and Tower B in the New task window.

  5. 5

    Open Tower A and draw Level 30 beneath it, from October to next April.

  6. 6

    Open Level 30 and draw two areas: Penthouse from October to February, and Lobby from November to March.

  7. 7

    Open Penthouse and draw Concept Design from October to December, the fifth level down.

    Step 7
  8. 8

    Click Save. Every level is kept.

Notice what didn't change: every one of those five levels is a task, drawn and dated the same way. Monument doesn't have a separate concept for "building" or "area", it's tasks nested inside tasks, as deep as the programme needs.

Move between overview and detail with the row arrows

A five-level tree is only useful if you can also not look at it. The arrow on each row opens or closes the level beneath it: close Marina Quarter and only the project bar shows, open it to add the towers, and so on down to level five, where Concept Design itself appears.

  1. 1

    Click the arrow on Marina Quarter's row to close it. Only Marina Quarter's overall bar shows; everything underneath folds away.

  2. 2

    Open the rows again one level at a time with their arrows: Tower A and Tower B appear, then Level 30, then Penthouse and Lobby, then Concept Design at level five.

A one-line overview for a client update and a fully expanded construction programme are the same data at two different depths, not two different views to keep in sync.

Reshape the tree without losing the work already on it

A tree drawn once doesn't have to stay exactly as drawn. A task's ⋯ menu, from the panel or the project page, carries three moves that restructure it while every hour already logged against it stays attached to the same task.

Move to… relocates a task, and everything beneath it, under a different project or a different task. Pick the destination from the picker, review what's about to move (tasks, time, allocations), and confirm. The task keeps its identity: past time entries, allocations and reports still point at it, they just now read against its new parent.

Make this its own project promotes a child task straight into a project of its own, admin or client, keeping its name and every hour already logged against it. It's the move for a stage that's outgrown being a stage, Tower A becoming a standalone commission, for instance, without starting its history over from zero.

Make this a leave type turns a task into a leave type, filed under the organisation's system Leave project (see request leave). Choose a brand new leave type, or fold the task's hours into one that already exists. Folding into an existing type deletes the now-empty original task once its time has moved across, the merge is a real move of every hour, not a copy.

Troubleshooting

  • Deep names get squeezed. Each level indents further into the task list, and the panel doesn't grow to compensate. Marina Quarter, Tower A, Level 30, Penthouse, and Concept Design all read cleanly at five levels because they're short; a name like "Level 30 Residential Fit-Out and Services Coordination" won't.
  • A dependency is refused. Dependencies can link any two rows in the same project: Concept Design to the next stage inside Penthouse, a task in Tower A to one in Tower B, or one stage to another. Two links are refused, and the row you point at says why: a row can't link to a stage that contains it (or to a row inside itself), and a link that would make a loop isn't allowed. Links between projects aren't possible.

Where this fits next

You'll know it worked when every level opens under the one above it. Most projects should stay at the two-level shape in Model the work programme. Next: staff the project.

Search Monument help

Search help articles and open a result.