More bids, without stretching your team
Most contractors don't lose work because their pricing is wrong — they lose it because they can't get enough accurate, complete bids out the door. Every tender needs a defensible quantity takeoff, a realistic schedule, and a proposal that proves to the client you can execute — and building all of that takes time your team doesn't have when three tenders land in the same week.
End to end, tender receipt to submission
- Quantity takeoffs
- Client communication on scope gaps and RFIs
- Material and subcontractor quote requests, per project, through your company email — backed by established vendor relationships across the Lower Mainland
- Workplans
- Project schedule, built in MS Project (or Primavera P6, if your company has P6 access)
- Complete, submission-ready proposals
How JYCS fits into your team
JYCS works as a white-labeled member of your estimating team — supplementing your existing team during high-volume tender periods so no bid gets rushed or missed. All communication runs through your company email (e.g. estimating@yourcompany.com), with RFIs and vendor/material quote requests submitted on your company's behalf. No external estimator is visible to clients or vendors — it reads as your team, because for all practical purposes, it is.
Built to win the tender isn't built to run the job
Most CPM schedules are developed at a high level during tender — enough detail to price the work and show a defensible sequence, but rarely broken down past WBS Level 2 or 3. Once the project team tries to progress that same schedule through execution, the logic isn't detailed enough to manage the work: near-critical paths stay hidden inside broad summary activities, and updates become a guessing game instead of a real reflection of progress. JYCS brings the expertise to detail that tender schedule out to WBS Level 5 or 6 — sequencing the actual work with proper logic ties so the critical path, and the paths running close behind it, are visible and defensible from day one of construction.
From baseline through project close-out
- Detailing tender-level schedules down to WBS Level 5/6 for execution
- Logic-tied activity networks that establish true critical and near-critical paths
- Ongoing schedule updates and progress tracking against milestones
- 3-week lookahead reviews with Superintendents and Project Managers
- Subcontractor schedule integration into the overall project timeline
- Risk, opportunity, and forecast reporting to clients and stakeholders
- Schedule basis and what-if scenarios to support delay and claims documentation
How JYCS fits into your team
JYCS works as a white-labeled extension of your project controls team — maintaining the P6 or MS Project schedule, running lookahead meetings, and preparing progress and forecast reports under your company's name. Clients and stakeholders see your team's reporting; the scheduling depth behind it is ours.
Estimating and scheduling support built for heavy civil work
Independent, engagement-based support for contractors who need accurate estimates and reliable schedules without carrying the overhead of a full-time in-house team.
Cost Estimation
Cost estimates developed from conceptual budgets through detailed, competitive tender submissions for pipeline, earthworks, and civil infrastructure work. Estimates are built for accuracy and defensibility under tender deadlines, using TamCost — a proprietary estimating tool — alongside InEight and Kubla for earthworks modeling.
- TamCost
- InEight
- Kubla
CPM Scheduling
Critical path method schedules developed and maintained in Primavera P6 and MS Project, coordinated with project stakeholders to track progress against milestones — from tender-stage schedules through active construction on major infrastructure builds.
- Primavera P6
- MS Project
Project Controls
Ongoing cost and schedule tracking support to keep infrastructure projects aligned to budget and timeline, using CM Builder and MS Project alongside the estimating and scheduling toolset above.
- CM Builder
- MS Project
Sample modeling output
Example model output produced with the tools used on active engagements.
