BRIXEL — Construction planning and cost tracking interfaces

The planner selects a project, enters the task, owner, allocation and dates, then chooses its predecessor. A start on or before the earlier task’s end keeps the form open with the conflict explained. A dependency chain that loops back to itself is rejected before saving.

The valid task appears in the schedule with its predecessor reference. Recording progress remains blocked until the earlier work is complete. The relationship survives navigation and reload, and once the dependent has started its predecessor cannot regress. Other dates do not shift automatically; reviewing the wider schedule remains an explicit planning decision.

The reviewer records an expense with its description, amount and date. Expenditure and remaining allocation change; the recorded completion percentage does not. Paying for work does not by itself establish that the work is finished.

A correction requires a reason and keeps the old/new amount in the history. Totals are recalculated, and spending above the allocation produces an explicit over-budget amount rather than a silent budget increase. Expenses can be exported for separate review. The interface does not execute a payment or an external accounting entry.

The manager selects a project and reading date. A task becomes overdue when its planned end precedes that date and completion remains below 100%. The alert leads into the schedule, where search, owner and status filters focus the review.

Switching between Gantt and table preserves the selection, and each task opens its dependencies, expenses and history. Export includes exactly the visible rows. Mobile scheduling stacks task names, dates and bars into a readable vertical arrangement for reviews away from a desk.