TGH Tech
Case study · Workflow 05 of 20 · Plan the job · Live

A signed agreement goes in. A provisional schedule comes out, with its critical path and what is still missing.

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.

Client
Viya Constructions
Department
Planning
Starts from
A signed construction agreement, as a PDF
Gives you
A provisional schedule as PDF and Excel, a Gantt view, and a list of what is missing
Connected to
Documents only today. A save to ProjectSignal is designed, not built.
Status
Live. Handed over to Viya's planners.

[01]What changedViya Constructions

The first schedule no longer has to wait for one planner. And it says plainly what it does not know yet.

First shipped in August 2026, live, and handed over to Viya's planners and project managers.

Before

Built by hand, from the last job.

  • One planner builds each schedule by hand
  • It starts from the last project's activity list
  • Only that planner knows which task controls the finish date
Now

Built from this agreement, then checked.

  • Anyone in the planning role starts from the signed agreement
  • Activities come from this agreement's scope wording, each with its reason
  • Fixed logic works out critical path, float and working days, and lists what is missing
  • 33
    generic activities in the reference library
  • 8
    network faults that stop the calculation
  • 4
    link types, each with lag: FS, SS, FF, SF
  • 40
    automated tests behind the workflow

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

A schedule is quick to draw and hard to trust. Four places a first schedule goes wrong.

  1. 01

    The last job leaks into this one

    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.

  2. 02

    Exclusions come with qualifiers

    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.

  3. 03

    The frame repeats, the finishes do not

    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.

  4. 04

    A duration is an assumption until measured

    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

Seven steps from the agreement to a schedule you can check.

Each step shows who does it. No date is calculated before the planner confirms.

  1. 01Planner starts

    Start with the signed agreement

    The planner types "/", picks Critical path schedule and attaches the agreement PDF.

  2. 02The workflow

    Read the agreement

    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.

  3. 03Fixed logic

    Map scope to activities

    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.

  4. 04Planner confirms

    Review before calculating

    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.

  5. 05Fixed logic

    Check the network

    A loop, an unknown predecessor, a missing duration or a duplicate ID stops the run, with the fault named. Loose ends raise a warning.

  6. 06Fixed logic

    Calculate

    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.

  7. 07The workflow

    Produce and report

    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.

Every activity says why it is there.

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.

  • Scope with no matching activity is listed as unmapped, not dropped
Review before calculating · Site B
BlockworkIn scope via "Block work"Kept
Internal plasteringIn scope via "Plastering". The agreement excludes "Open terrace plastering"Check quantities
Wet-area waterproofingExcluded by the agreement: "Water proofing"Not scheduled
Illustrative. Site B is made up. Wording follows the review card.
Critical path schedule · Site A
Total duration173 working daysProvisional
Critical38 of 41 activitiesCritical
Near-criticalWaterproofing, flooring, joinery: 1 day of float eachWatch
Finish21 May 2027, from a 2 November 2026 startNo holidays entered
Still missingHoliday calendar. BOQ quantities, production rates, crew sizes. Owner-supplied material dates.
Illustrative. Site A is made up. Figures are the calculation run on the whole reference library for a two-story house, Monday to Saturday. Not Viya figures.

Read a first pass for what it is.

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

Today the schedule is a document. The milestone plan is what goes into ProjectSignal.

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.

  1. Reads

    From ProjectSignal

    • Nothing today. It starts from the agreement PDF alone.
  2. Does

    What happens in between

    • Reads scope, exclusions and dates from the agreement
    • Builds the activity network and waits for the planner's review
    • Calculates, then produces the PDF, workbook and Gantt view
  3. Writes

    To ProjectSignal

    • Nothing today. The schedule stays a document in Bleno.
    • Designed, not built: an approved schedule saved to the project plan as its baseline

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.

  1. Signed agreement
  2. Critical path schedule
  3. Milestone plan (no link yet)
  4. ProjectSignal
  5. Readiness by role

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms.

StepDone by
Reading project details, scope headings, exclusions and floorsThe AI, word for word. What the agreement does not state stays empty.
Choosing activities, repeating the floor cycle, re-linking around removed workFixed logic, from the agreement's wording
Durations, links, working days, holidays, commencement dateThe library proposes durations and links. The planner confirms or changes them on the review card.
Checking for loops, unknown links and missing durationsFixed logic. It will not calculate until they are fixed.
Early and late dates, float, critical path, calendar datesFixed logic. The AI never computes or adjusts them.
Approving the schedule as a baselineA person, outside the workflow. Every output says it is not an approved baseline.

The AI is called twice: to read the agreement, and to write the closing summary from the calculated values.

[06]More detailViya Constructions

The rules it follows

What it schedules, what it refuses, what it flags.

RuleWhat it does
Only the agreement's workAn activity is scheduled only when a scope heading supports it. Six are always included: mobilization, site establishment, setting out, testing and commissioning, snag rectification, final handover.
ExclusionsRecorded as written, qualifier included. If nothing in scope supports the work, it is not scheduled. If scope supports it, it stays, flagged "partly excluded, check quantities".
FloorsThe eight-activity structural cycle repeats per floor, for 1 to 20 floors. At library durations a floor is 30 working days: columns 5, slab formwork 6, steel 5, pre-pour inspection 1, pour 2, curing 7, lintels and sunshades 4. Blockwork onward waits for the top floor.
Removed workActivities after a removed one are linked to what came before it, finish-to-start, and marked provisional with the reason.
Durations and linksLibrary durations are planning assumptions for a small residential unit, flagged as provisional on the card. Every library link starts as Provisional until the planner marks its row Reviewed or Approved. The count still provisional is printed with the missing information.
Scanned agreementFewer than 400 characters of readable text counts as a scan. The whole library is proposed for review, with a warning to prune before calculating.
Faults that stop the runDuplicate ID. No usable duration. Unknown predecessor. A link type other than FS, SS, FF or SF. A lag that is not a number. A loop, named activity by activity. No start. No finish.
Critical and near-criticalCritical is zero total float. Near-critical is 1 or 2 days. The critical path is one connected chain ending at the project finish, not a list of zero-float rows.
Changes afterwardA change asked for in chat edits the confirmed inputs. The schedule is recalculated and issued as a new version. Dates are never edited directly.

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.

What goes in, what comes out

One PDF in. Two documents and a Gantt view out.

ItemFormatWhat it holds
In: signed agreementPDFScope headings, exclusions, floors, contract duration, dates as written
Out: schedulePDFResult, critical path in order, work breakdown, every activity with early and late dates and float, exclusions never scheduled, unmapped scope
Out: workbookExcel, 4 tabsSchedule with critical rows marked, Critical Path, WBS, Inputs
Out: Gantt viewCard in chatCritical and near-critical rows by default, all rows on a toggle, float drawn as a tail on each bar
Out: missing informationIn all threeCommencement date, holidays, BOQ quantities with production rates and crew sizes, links still provisional, owner-supplied material dates, approval, procurement and inspection dependencies
What it means for you

Three readers, three answers.

  1. For owners

    A first schedule that does not wait

    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.

  2. For planning heads

    Review in place of typing

    Your planner starts from a linked network with every assumption flagged, and spends the time on durations and logic.

  3. For your technical person

    Dates you can reproduce

    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.

Is this your problem too?

Four signs, and what we need to start.

  • Only one or two people can build a schedule
  • A new schedule starts as a copy of the last project's
  • Nobody can show, this week, which activities control the finish date
  • The first schedule does not say which durations are assumptions

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.

Who can build the first schedule when your planner is busy?

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.