Course Content
Level 1 Information Manager – Basics

This video shows how to turn defined scope requirements into a delivery timeline with durations, dates, dependencies, and responsibilities. The written guide below explains how to filter by team and milestone, switch to the timeline view, and build a task information delivery plan that teams can coordinate around.

Turn information requirements into a clear delivery timeline

Defining what needs to be delivered is only half the picture. The other half is understanding when teams are likely to deliver it and how those tasks relate to each other over time. The Scope module in Plannerly bridges this gap by letting you move from a structured list of requirements to a visual delivery timeline where every task has a duration, dates, dependencies, and a responsible team member.

The workflow starts with filtering. When you want a specific team to tell you when they can deliver their tasks at a particular milestone, you filter the scope view for that team and that information exchange. This strips away everything else and shows only the tasks that team is responsible for. From there, you switch from the grid view to the timeline view and start assigning durations, moving tasks to their expected start dates, and creating dependencies between them so the sequence of delivery is clear.

The timeline supports the full range of scheduling functionality you would expect. Tasks can be dragged, resized, and linked with dependencies. When you assign team members to tasks, their names appear on the timeline so everyone can see who is responsible for what. A compact view gives you a traditional Gantt chart layout that is familiar to project managers and easy to share in meetings. When you need more detail, unfiltering the view and expanding out of compact mode reveals everything behind each task: the geometry requirements, descriptions, coordination needs, information requirements, and any attached specifications.

This approach directly supports task information delivery planning under ISO 19650. Each task on the timeline is backed by a detailed information container that defines what complete actually looks like. When teams can see not just when something is due, but exactly what needs to happen and what the acceptance criteria are, coordination becomes far more effective. The timeline becomes more than a schedule – it becomes a shared agreement about delivery that can be referenced in contracts and used to hold teams accountable throughout the project.

How to create a delivery timeline from scope requirements

  1. Filter by team – Select the team you want to plan with so only their tasks are visible in the scope view.
  2. Filter by milestone – Choose the specific information exchange or milestone to focus on the tasks due at that point in time.
  3. Switch to timeline view – Click the timeline view to see the filtered tasks displayed as a visual schedule rather than a grid.
  4. Assign durations and dates – Drag tasks to their expected start dates and resize them to set their duration.
  5. Create dependencies – Link tasks together to define the sequence of delivery and show which tasks depend on others being completed first.
  6. Assign team members – Allocate specific people to tasks so responsibilities are visible directly on the timeline.
  7. Switch to compact view – Use the compact Gantt-style layout for a high-level overview suitable for progress meetings and reporting.
  8. Review detailed requirements – Unfilter and expand tasks to confirm that the geometry, information requirements, and specifications behind each scheduled task are complete.

What you’ll learn

  • Scope filtering – How to filter tasks by team and milestone to create focused views for delivery planning conversations.
  • Timeline scheduling – How to assign durations, dates, and dependencies to tasks using a visual drag-and-drop timeline.
  • Compact Gantt view – How to switch to a traditional Gantt chart layout for high-level progress visibility.
  • Requirement traceability – How every scheduled task connects back to its full information container with geometry, descriptions, and specifications.
  • Contract-ready scope – How a detailed timeline backed by clear requirements creates scope that can be put into contracts and used for accountability.

Common questions

Can I filter for multiple teams at once?

Yes. You can adjust the filters to show tasks for one team, several teams, or all teams. Filtering for a single team is most useful during planning meetings where you need that team to commit to delivery dates. Showing all teams gives you the full project timeline for coordination and progress tracking.

How do dependencies work in the timeline?

Dependencies link tasks so that one cannot start until another is completed. This creates a delivery sequence (sometimes called a waterfall) that reflects real-world constraints. When you move a predecessor task, dependent tasks shift accordingly, helping you understand the impact of delays and keep the schedule realistic.

What is the difference between the timeline and the compact view?

The timeline shows tasks with their full detail, including team member assignments and expandable requirement containers. The compact view condenses this into a traditional Gantt chart layout that shows just the task bars and dependencies. Most teams use the compact view for reporting and the full timeline for planning and status reviews.

How does this connect to the MIDP and TIDP?

The timeline is essentially a visual representation of your task information delivery plan (TIDP). When each team has their tasks scheduled with dates, durations, and dependencies, those individual plans combine into the master information delivery plan (MIDP). The scope requirements behind each task provide the detail that ISO 19650 requires for each planned information exchange.

Explore further

0% Complete

Pin It on Pinterest