Publishing to subcontractors (slices)

Master schedule and slice

• Master schedule. Any schedule created by the company that created the project. Its lock action is labeled Publish (Публикувай) even when no subcontractor has a contract yet.
• Slice (Срез). A read-only schedule in the subcontractor's company, on the BoQ of its contract. It holds the master rows whose BoQ positions match the subcontractor's contracted positions, with their dates and dependencies, under the same categories and group tasks as in the master. Rows outside the contract and other subcontractors' work are not included.

The scope of the slice is never chosen by hand. It comes from the signed contract: each contracted position is matched to the master row of the same BoQ position, through the offer the contract came from or through the link to the client's BoQ line.

Who receives a slice

• A subcontractor company on BuildColab with a signed contract on the project. A contract proposal that is still pending or was declined gives no slice.
• Only the main contract counts; change orders do not create a separate slice.
• Self-contracts and self-managed subcontractors (external companies you manage yourself, without their own BuildColab account) do not receive slices.

How to publish the master schedule

1. Open the master schedule on its current draft.
2. Click Publish (Публикувай) in the toolbar — the same place and icon as Lock.
3. Read the dialog Publish schedule (Публикуване на графика): "This version will be locked and sent as a slice to all contractors with an active contract. Your changes will be saved."
4. Click Publish (Публикувай). Cancel (Отказ) closes without publishing.
5. The version is locked at once. The slices are sent in the background while "Publishing schedule to contractors…" (Публикуване на график към изпълнители…) shows.
6. The result is "Master schedule published — slices sent: {count}" or "Master schedule published — no contractors with an active contract".

If the slices could not be sent, you see "Failed to send slices to contractors. Please try publishing again." The lock has already happened. Make any change, confirm Create draft and publish the new version to send the slices again.

If a schedule without any dates is published, the dialog shows the general lock text "The schedule has no dates set. You can still lock it, but the version will be empty. …" instead of the publishing text; the slices are still sent.

1. The Publish (Публикувай) button, shown instead of Lock on a master schedule.
2. The dialog Publish schedule (Публикуване на графика) with the explanation.
3. Publish locks the version and sends the slices.

When slices are updated

• Every publish sends updated slices to all subcontractors with a signed contract. You never resend by hand.
• A contract signed after the publish (the usual order: the main contractor publishes, then the subcontractor accepts the contract proposal) triggers a slice automatically, from the latest published version — as long as the master schedule's current version is locked. If the main contractor has a newer draft open, the subcontractor receives its slice at the next publish.
• Each slice shows the master version it was taken from.
• Progress the subcontractor already reported is carried into the updated slice.

What the subcontractor sees

1. The subcontractor opens the project's Construction schedule (Строителен график) for the BoQ covered by the contract — in the sidebar the schedule of its budget list, which for a subcontractor is Contract with client (Договор с възложител).
2. Above the Gantt a badge reads "Slice of master schedule — Version {version}" (Срез от майсторски график — Версия {version}).
3. The rows, dates, dependencies and the structure above them come from the master schedule.

1. The badge "Slice of master schedule — Version {version}" (Срез от майсторски график — Версия {version}).
2. The master category with the contracted positions below it.
3. The % Done (Изп. %) column.

What the subcontractor can and cannot do

Seeing what changed in an update

To see what changed between two published versions of a slice — added, removed or moved tasks and changed dependencies — ask BORO to compare the versions of the schedule. See Versions, locking and comparing and What BORO can do.

Common questions

Related

• Versions, locking and comparing
• Reporting progress
• Contracts: signing, details and history
• Gantt view and dependencies