Construction schedule
Construction schedule and Gantt chart, straight from the BoQ
BuildColab is construction project management software, built in Bulgaria, in which the construction schedule (a Gantt chart) is built directly from the bill of quantities. BoQ positions are laid out on a timeline and linked by dependencies counted in working days; the schedule shows the critical path, keeps baselines, and can take its progress from approved payment applications.
Data stored on Google Cloud in the European Union
What is the construction schedule in BuildColab?
The construction schedule is the time plan of a project: when each piece of work is done, in which order and how far it has progressed. In Bulgarian practice it is called a linear schedule (линеен график) or a Gantt chart. In BuildColab the schedule belongs to one version of the bill of quantities: its structure can follow the BoQ sections or be your own (by location, stage or crew) and its tasks hold the BoQ positions you already priced, with their quantities, units and prices.
You arrange the positions into categories, group tasks and milestones, set dates and link them with dependencies. Because the schedule knows quantities and prices, BuildColab turns it into a cash flow and into materials, labour, machinery and services reports by week, month, quarter or year. Progress is reported as a percent per task or taken from approved payment applications and accepted progress reports.
What does the construction schedule in BuildColab include?
Everything between the priced bill of quantities and the dated plan the site works to.
-
A schedule linked to the BoQ
Rows are BoQ positions with their quantity and price. The distribution says how much of a position each row carries; the coverage shows what is still missing from the schedule.
-
Gantt, dependencies and critical path
Four dependency types with a lag in working days. Move a task and its successors move with it; the critical path outlines the tasks with no float.
-
MS Project import and export
Import an .mpp or .xml file with its hierarchy, dates, milestones and dependencies. The schedule exports to MS Project (.xml) and to PDF.
-
Baselines and history
Lock a draft as a Final baseline that never changes again. Any earlier version opens read-only, and BORO compares two versions for you.
-
Progress from payment applications
Enter percent complete per task or pick a source: approved payment applications, accepted progress reports, or the latest application plus the progress reports filed after it.
-
Slices for subcontractors
Publishing the master schedule sends every subcontractor with a signed contract a read-only slice of its own scope, on which it reports progress.
How do you build a construction schedule in BuildColab?
-
Work calendar and BoQ
Check the project’s working week and holidays. Then create the schedule: a copy of the BoQ structure, a new structure, an MS Project import or a carry-over from the previous version.
-
Dates and dependencies
In the Gantt view set start, end and duration in working days and link the tasks with dependencies. Switch on the critical path to see what drives the finish date.
-
Baseline
Lock the plan as a Final version. On a master schedule this is Publish: the version is locked and subcontractors with an active contract receive a slice.
-
Progress and reports
Report percent complete or let the schedule follow approved payment applications and progress reports. The reports show cash flow and resources by period.
How does the schedule map to a linear schedule and a Gantt chart?
The linear schedule (линеен график) Bulgarian contractors know is a Gantt chart: the works are rows and bars show when each starts and ends. The construction schedule in BuildColab is exactly that: a table of categories, tasks and milestones on the left and a timeline of bars on the right, zoomable from day to year.
The difference is that the schedule knows what each bar contains. Task links are Finish → Start, Start → Start, Finish → Finish and Start → Finish, every duration is counted in working days of the project calendar, and the locked Final version is the baseline BORO compares later versions against.
-
Linear schedule (Gantt) with categories, tasks and milestones
-
Task links of all four types, with a lag in working days
-
Critical path: tasks with zero or negative total float
-
Baseline: a locked Final version with a history
-
Work calendar: the project’s working week and non-working days
-
Export to PDF and to MS Project (.xml)
Why is it better than a schedule in Excel?
| Topic | Schedule in Excel | Schedule in BuildColab |
|---|---|---|
| Positions and quantities | Copied from the BoQ by hand | Rows are the BoQ positions with quantities and prices |
| BoQ changes | The schedule is corrected separately | The schedule synchronizes: deleted positions drop out |
| Dependencies | Dates moved one by one | Successors move with the task, in working days |
| Baseline | Copies of the file | Numbered locked versions and a history |
| Progress | Percentages retyped by hand | From approved payment applications or accepted progress reports |
| Money and resources | A separate summary | Cash flow, resources by period and a pricing report |
Frequently asked questions
Can I import a schedule from MS Project?
Yes. The import accepts one .mpp or .xml file up to 32 MB and brings in the hierarchy, dates, milestones and dependencies. The activities arrive unlinked to the BoQ; you link them by hand or let BORO propose the matches.
Which formats does the schedule export to?
Export PDF saves the current Gantt view, and Export to MS Project downloads an MSPDI XML file with the tasks, hierarchy, dates, dependencies and calendar. The Reports screen exports cash flow and resources by period to Excel (.xlsx).
How does BuildColab calculate the critical path?
Switch on Critical path and the tasks with zero or negative total float are outlined: if they slip by one working day, the end of the schedule slips too. The calculation uses the work calendar and all dependencies; category bars are not analysed.
Can progress come from approved payment applications?
Yes. In the progress source menu next to Critical path choose approved payment applications: a position’s percent becomes the approved quantity ÷ the contracted quantity, capped at 100 %. The schedule must sit on your main BoQ with a signed contract.
How does the schedule handle weekends and holidays?
All durations and lags are counted in working days of the project’s work calendar. By default the working days are Monday to Friday; if the site works on Saturdays, change the working week.
Can I keep a baseline and compare versions?
Yes. A locked Final version stays frozen and the next change opens a new draft; progress can still be reported on a final version. BORO compares two versions and lists added and removed tasks, changed dates and changed dependencies.
Do subcontractors see the schedule?
Only their part. When you publish the master schedule, every subcontractor on BuildColab with a signed contract receives a read-only slice with its contracted positions and reports progress on it. Other subcontractors’ work is not in the slice.
See the whole path of a project: BuildColab for construction companies
See a schedule built on your own BoQ
In the demo we walk the whole path: from BoQ to a schedule with dependencies, a baseline and progress from payment applications.
Book a demo