Teralo
Back to Teralo Host

Program & Scheduling

Create and manage construction schedules with Gantt charts, Work Breakdown Structures, task dependencies, baselines, and critical path analysis.

Creating a Program

New Schedule

  1. Go to Project > Program
  2. Click Create Program
  3. Enter program details:
    • Name: Schedule name (e.g., "Master Program", "Fit-out Schedule")
    • Description: Scope of the schedule
  4. The program opens in the Gantt chart view

Multiple Programs

Projects can have multiple programs for different purposes:

  • Master construction program
  • Detailed phase schedules
  • Subcontractor programs
  • Design delivery schedules

Work Breakdown Structure

Creating Tasks

Build your schedule using a hierarchical Work Breakdown Structure (WBS):

  1. Click Add Task in the Gantt view
  2. Enter task details:
    • Name: Task description
    • Start Date: Planned start
    • End Date: Planned finish
    • Duration: Calculated from dates or entered directly
  3. Use indentation to create a hierarchy:
    • Summary tasks (parent)
    • Detail tasks (child)

Task Hierarchy

Organise tasks into logical groups:

  • Phase 1 - Structure
    • Foundations
    • Ground Floor Slab
    • Level 1 Structure
    • Level 2 Structure
  • Phase 2 - Fit-out
    • Mechanical Rough-in
    • Electrical Rough-in
    • Plasterboard
    • Painting

Summary tasks automatically roll up dates and progress from their child tasks.

Dependencies

Linking Tasks

Create relationships between tasks to model the work sequence:

  1. Select a task in the Gantt view
  2. Create a dependency to another task
  3. Choose the dependency type:
    • Finish-to-Start (FS): Task B starts when Task A finishes
    • Start-to-Start (SS): Task B starts when Task A starts
    • Finish-to-Finish (FF): Task B finishes when Task A finishes
    • Start-to-Finish (SF): Task B finishes when Task A starts

Lag and Lead

Add lag (delay) or lead (overlap) to dependencies:

  • Lag: Task B starts 3 days after Task A finishes (FS + 3d)
  • Lead: Task B starts 2 days before Task A finishes (FS - 2d)

Critical Path

Understanding the Critical Path

The critical path is the longest sequence of dependent tasks that determines the project's minimum duration. Any delay on a critical path task delays the project end date.

Critical Path Configuration

  1. Go to Project > Tools > Program
  2. Configure the critical path threshold
  3. Critical tasks are highlighted in the Gantt view
  4. Monitor float (slack) on non-critical tasks

Baselines

Creating a Baseline

Save a snapshot of your schedule to compare against actual progress:

  1. Open the program
  2. Click Save Baseline or save a numbered revision
  3. The baseline captures all task dates and durations at that point in time

Baseline Comparison

Compare current schedule against baselines to:

  • Identify schedule slippage
  • Support Extension of Time (EOT) claims
  • Demonstrate compliance with contractual milestones
  • Track schedule recovery

Revisions and Saving

Manual Save

Programs use a manual save model:

  • Draft: Auto-saved working state
  • Numbered Revisions: Explicit saves create numbered versions (Rev 1, Rev 2, etc.)
  • Each revision is a permanent record of the schedule at that point

Revision History

View the complete history of schedule changes:

  • Compare revisions side by side
  • Track when changes were made
  • Identify who made changes
  • Restore previous revisions if needed

Task Calendars

Working Days

Configure which days are working days:

  1. Go to Tools > Program
  2. Set up calendars defining:
    • Working days (typically Monday - Friday)
    • Non-working days (weekends, holidays)
    • Custom calendars for different resources

Calendar Assignment

Assign calendars to individual tasks:

  • Standard calendar for most tasks
  • 7-day calendar for critical activities
  • Custom calendars for specific trades

Saved Views

Save custom views of your schedule:

  • Filters: Show only specific task groups or phases
  • Column Configuration: Choose which data columns to display
  • Sort Order: Organise tasks by different criteria
  • Save and name views for quick access

Best Practices

  • Start with the WBS: Build a clear hierarchy before adding dates and dependencies
  • Use dependencies: Link tasks rather than using fixed dates where possible
  • Save baselines: Create baselines at key milestones for comparison
  • Monitor the critical path: Focus management attention on critical activities
  • Use numbered revisions: Save explicit revisions at programme submission points
  • Keep calendars accurate: Ensure working day calendars reflect actual site hours
  • Review regularly: Update the program weekly to reflect actual progress