At Viya the first schedule for a new house waited for the one planner who could build it by hand. With this workflow, anyone in the planning role attaches the signed agreement and gets a work breakdown, an activity network, the critical path, float and total working days. Activities are scheduled only where the agreement's scope wording supports them, and fixed logic works out every date, not the AI. It produces documents today and writes nothing to ProjectSignal.
[01]What changedViya Constructions
First shipped in August 2026, live, and handed over to Viya's planners and project managers.
From the workflow's own rules and tests, not a Viya project.
In home construction a milestone is also money: each stage the client signs off releases a payment. A first schedule is where those stage dates get worked out. Copy it from another house, or show assumed durations as facts, and every date taken from it inherits the error. So the workflow shows where each activity came from and lists what it assumed.
[02]Why this is hardViya Constructions
Reusing one project's activity list on a new job carried that project's measurements along. A plinth beam size and a tile size written for one house appeared as steps in another's schedule.
Excluding open terrace waterproofing is not excluding waterproofing. Drop the qualifier and a whole trade leaves the schedule. Ignore the exclusion and the schedule plans work that was never sold.
Columns, slab formwork (shuttering), steel, inserts, inspection, pour and curing repeat on every floor. Finishes follow the top slab. Tie them to the first floor and the upper floor shows float it does not have.
Without BOQ quantities, production rates and crew sizes, a duration is a planning assumption. In a pure labor agreement the owner supplies material, and the schedule cannot know those delivery dates.
[03]How it worksViya Constructions
Each step shows who does it. No date is calculated before the planner confirms.
The planner types "/", picks Critical path schedule and attaches the agreement PDF.
Project, owner, agreement date, contract duration, floors. Scope headings word for word, exclusions with their qualifiers. A commencement date only if the agreement states one.
Activities come from a 33-activity reference library for a conventional RCC-framed building, only where the scope wording supports them. The structural cycle repeats per floor, and a work breakdown is built to ISO 21511.
One card, three parts: project details with working days and holidays, the work breakdown, and every activity with its days, predecessors and reason. Predecessors are typed the way planners write them, such as C060 FS+2.
A loop, an unknown predecessor, a missing duration or a duplicate ID stops the run, with the fault named. Loose ends raise a warning.
A forward and a backward pass give early and late dates and total float, then the critical path as one connected chain. With a commencement date, working days become calendar dates that skip holidays. Without one, results stay as working-day counts.
A schedule PDF, a four-tab Excel workbook and a Gantt view in the chat. The summary uses only the calculated values, calls the result provisional and lists what is missing.
On the review card each row carries a "Why it's here" note, usually the agreement heading that brought it in. Excluded work is either not scheduled, or kept with a note to check quantities.
Most library links are finish-to-start, so on library logic nearly every activity is critical. Every link is to be reviewed with the site team before the schedule is treated as a baseline.
[04]Connected to ProjectSignalViya Constructions
This workflow does not read from or write to ProjectSignal today. Here is how milestone dates get in now, and what is designed to join the two.
ProjectSignal holds one project plan per site, owned by the project manager. Each milestone on it has a target date and the collection amount the client pays at that stage. The bulk route in is a separate workflow, milestone plan import, recorded as in use. It previews every row as a dry run and saves only after a person confirms: as the signed-in person, within their permissions, through the platform's own validation.
Nothing joins the two today. No workflow carries a date from the schedule into the milestone plan, which Viya's planning team keeps, and this workflow saves no copy of the schedule in ProjectSignal. ProjectSignal does keep a versioned schedule PDF per project, but a person uploads it.
The designed next step closes that gap: an approved schedule saved to the project plan as baseline 1, through the import's preview and save steps, with later changes kept as revisions with a reason. Until then there is no baseline to measure slippage against. Further out, the same critical-path logic is planned to run on durations worked out from budget quantities and crew sizes, with milestones tied to payment stages. That depends on budgets from the estimator, which is in build.
[05]Who decides whatViya Constructions
The AI is called twice: to read the agreement, and to write the closing summary from the calculated values.
[06]More detailViya Constructions
A test case you can check by hand: A takes 5 days. B (4) and C (3) follow A. D (2) follows both. Finish is day 11, critical path A, B, D, with 1 day of float on C.
It stops depending on one person's week. Every activity shows the heading that brought it in, and excluded work is listed as never scheduled, so work you did not sell is easy to spot.
Your planner starts from a linked network with every assumption flagged, and spends the time on durations and logic.
Every date comes from fixed logic, and the workflow has 40 automated tests across mapping, calculation and documents. The same inputs always give the same schedule.
To start we need a few signed agreements, the activity list and durations your planner works from, and one owner with thirty minutes a week. Your library and rules replace Viya's.
[07]Where this fitsViya Constructions
Send us one signed agreement and the schedule that was built from it. We will show you what a first version would produce from the same document. Start with one workflow. You only pay if it works.