Schedule

Schedule

The Schedule module is the contractual baseline timeline. It tracks every milestone, deadline, task and meeting defined in your contract, and feeds directly into the risk and liquidated damages modules.

Event types

Type Description
Milestone A contractually binding completion point — mechanical completion, provisional acceptance, handover. Can be linked to a liquidated damages rule.
Hard deadline A strict date with contractual consequences if missed — submission of a document, expiry of a notice period.
Task An activity with a duration — engineering phases, procurement windows, construction activities.
Meeting A contractually required meeting — progress reviews, FAT, site inspections.

Event fields

Field Description
Title Required. The event name as it appears in the contract or programme.
Description Optional. Additional context or the exact contractual wording.
Type Milestone, Task, Hard deadline or Meeting.
Start date The contractual start date for the event or activity.
End date Optional. The completion or due date. Used to compute status (passed / open) and to draw the Gantt chart.
Source clause Optional link to the contract clause from which the event was extracted, for full traceability.

Adding events

Events can enter the schedule in two ways:

Manually

Click New event on the Schedule page. A two-step modal collects the event definition (title, description, type) then the dates (start, end). Manual events are immediately active and appear in the timeline.

Via AI extraction

When you validate a contract, Belfort's AI scans the uploaded documents for temporal references — dates, durations, contractual deadlines. Each detected event is created with a pending status and appears for review on the contract page. Click Validate on each event to promote it to active, or delete it if it is irrelevant.

Always review AI-extracted events

The AI may extract relative dates ("within 30 days of notice") without resolving them to an absolute date. These will appear without a start date — add the date manually once you know the reference point.

Dashboard KPIs

The schedule page shows a live summary strip across all active events:

  • Total events — count broken down by type (milestones / deadlines / tasks).
  • Next milestone — date and name of the nearest upcoming milestone.
  • Days to next event — colour-coded: red (< 14 days), orange (< 60 days), green (on schedule).
  • Contract horizon — total months from the contract effective date to the last scheduled event.

Gantt chart

The interactive timeline plots all milestones on a horizontal axis. Past milestones appear in grey; upcoming ones are colour-coded by type. A vertical line marks today's date.

  • Click a milestone dot to scroll directly to its row in the events table below.
  • Zoom toggle switches between month and quarter granularity.

Link to risks and liquidated damages

Schedule milestones are the connective tissue between the risk register and the financial module:

  • A liquidated damages rule can be attached to a milestone in the Financials module. This encodes the penalty that applies if that milestone is missed.
  • A risk can reference an impacted milestone. Belfort then resolves the associated LD rule and computes the financial exposure automatically from the estimated delay.

The recommended setup order

Create milestones first → attach LD rules to them → link risks to milestones. This way, any new risk automatically inherits the correct penalty rule without manual configuration.