onsummit
Menu
← Selected work

Construction planning / Business case

Updated schedules for active construction projects.

Revised plans for different home types were applied to projects already underway, following stakeholder review.

What we delivered
Revised construction templates applied to active schedules.
Key consideration
Carry revised plans into projects already underway.
Contribution
Consulting and client team · schedule-template deliveryDelivered with a wider consulting and client team
Illustrative construction schedule template connected to two active project timelines, with review, application and final checks shown as distinct steps.
Illustrative reconstruction · Sample data

A revised template and updates to active schedules are distinct pieces of work. These sample timelines illustrate applying planning changes and requesting final checks, rather than automatic future propagation.

View full-size illustration (opens in a new tab)

The system at a glance

How it works.

The team revised schedule templates and task dependencies for different construction plans. Stakeholders reviewed the changes before they were applied to active projects. After the updates, the team requested final checks and coordination with project managers.

Architecture / simplifiedCarry an agreed template change into active work
  1. Template variants

    Maintain plans for different construction needs.

    Review the intended changes
  2. Stakeholder review

    Check revised template content and dependencies.

    Apply the revised planning content
  3. Active schedules

    Propagate updates to projects already underway.

    Check the updated schedules
  4. Final checks

    Review the result and coordinate communication to project teams.

A conceptual view of the documented template-update sequence. Propagation to active schedules was reported complete; final checks and wider staff adoption are separate from that technical update.

The problem behind the system.

Construction schedules need to reflect different home tiers and task dependencies. When a planning rule changes, future projects can use a revised template, but projects already underway need a separate update. The business needed to carry template changes into active schedules while giving project stakeholders a chance to review them.

  • Different construction plans need distinct template content and dependencies.
  • Updating a template and updating an existing project schedule are separate operations.
  • Technical propagation does not by itself establish that every project team has reviewed and adopted the revision.

Team contribution

This example comes from a prior consulting engagement delivered with a wider consulting and client team. The delivery team revised TaskRay schedule templates, coordinated stakeholder review and propagated the changes to active construction schedules. This story is limited to that template-update work; newer permit-orchestration services and later client technology-team enhancements are separate contributions.

The decisions that shaped the work.

Keep variation in the planning model.

Different construction tiers cannot always use the same sequence of work or the same template details.

The work maintained and revised multiple TaskRay schedule templates. Template review let stakeholders consider the intended plan before applying changes to existing schedules.

Design consideration. Template variants support real differences in the work, while creating several plans that need coordinated maintenance.

Treat active-project updates as their own delivery step.

A corrected template can help future projects while leaving schedules already in use unchanged.

The delivery explicitly included propagation to schedules in flight, in addition to the template revisions themselves. The team reported that active schedules had been updated.

Design consideration. Updating active work requires attention to the affected schedules. This story does not imply that every future template change propagates automatically.

Separate technical completion from business rollout.

An update reaching the system is not the same as every project manager knowing about it or confirming the result.

Stakeholder review preceded propagation, and the delivery team requested final checks after confirming the updates. Business communication remained a distinct part of the rollout.

Design consideration. The documented result is template propagation. It does not establish universal acceptance or a measured reduction in schedule maintenance.

What the system delivers

  • Revised schedule templates for different construction plans.
  • Template changes applied to schedules already in use.
  • Stakeholder review before the update and final checks requested afterward.

Technical implementation

  • Salesforce
  • TaskRay
  • Schedule templates
  • Salesforce Flow
  • TaskRay provides the template and project-scheduling foundation on Salesforce.
  • The work addressed template content, dependencies and updates to schedules already in use.
  • Separate review and propagation steps connected configuration changes to the project-management process.

More work examples

Homeowner changes, from request to delivery.Keep each request linked to bids and progress.Invoice review against purchase orders.Keep uncertain invoice matches visible for review.

When your standard process changes, what happens to the work already underway?

Start a conversation