Subcontractors hide timeline risk until it becomes a crisis | Professional Services

What it costs you today

Your subcontractor handles a critical piece of the engagement. In every update they are on track. Then two weeks before the client deadline they surface a problem that has been building for a month. You absorb the hit and have nothing to point to because every check-in looked clean.

How RadRoot is used here

RadRoot runs a mid-engagement pulse with the subcontractor's PM. Five structured questions about their actual confidence level, where they see risk, and what they need to stay on timeline. If they flag a resource constraint, the follow-up asks how severe and what it would take to fix it.

The file you would upload

A Deltek Vantagepoint - Active Subcontracts export. One row is one subcontract engagement. RadRoot reads the whole row, so every question can name something the person already knows is true.

Subcontract ID	Client Name	Engagement Name	Subcontractor Firm	Subcontractor PM Name	Subcontractor PM Email	Subcontractor PM Title
SC-2026-0041	Frontier Health Systems	Provider Network Analytics Platform	DataCraft Solutions	Michael Torres	m.torres@datacraft-solutions.example.com	Senior Project Manager
SC-2026-0052	Clearview Financial	Regulatory Compliance Upgrade	Apex Integration Group	Priya Sharma	priya.sharma@apexintegration.example.com	Delivery Manager
SC-2026-0067	Northpoint Manufacturing	Supply Chain Visibility Tool	Velocity Dev Labs	James Kellerman	j.kellerman@velocitydevlabs.example.org	Technical PM
SC-2026-0073	Redstone Energy	Asset Management Portal	Pinnacle Software	Sarah Lin	sarah.lin@pinnaclesoftware.example.net	Project Lead
SC-2026-0081	Beacon Retail Group	Customer Segmentation Engine	Insight Analytics Co	Derek Martinez	derek.martinez@insightanalytics.example.com	Lead PM

First 5 of 20 rows, first 7 of 14 columns. RadRoot interviewed the project manager on each row, and 7 of 20 answered.

One interview, exactly as it ran

Six options every time, including the ones that reflect badly on whoever sent it. Each question was written after the answer above it landed.

Q1Your Provider Network Analytics Platform delivery for Frontier Health Systems is scheduled for April 30. How confident are you that your team will meet that deadline without requiring an extension?

·Highly confident, we have completed all major milestones early and have buffer time remaining
·Confident, barring any unexpected scope changes or resource losses
✓Moderately confident, but one or two factors could still shift the timeline
·Not particularly confident, several issues are unresolved and the runway is short
·Not confident at all, we are already behind schedule and would need significant help to deliver on time
·Confident only if the client agrees to descope certain features we have not started yet

Q2You mentioned that one or two factors could shift the timeline. What is the biggest risk you see right now that could cause a delay?

·Delays in receiving data or configuration access from the client
·A technical dependency on a third-party API that has not been fully tested yet
·Uncertainty around whether the testing environment will be ready when we need it
✓A key team member is splitting time between this project and another commitment
·Open questions about how certain reporting requirements will be implemented
·The possibility that stakeholder approval cycles could take longer than planned

Q3How severely is that time split affecting your ability to hit milestones on this engagement?

·Not affecting us at all, we have adjusted workflows to accommodate it
·Creating minor delays in handoffs, but nothing that threatens the overall timeline yet
✓It is manageable now but would become a problem if scope expands or priorities shift
·Already causing us to push internal milestones back by several days
·Significantly impacting progress, we are falling behind on key deliverables
·Making it nearly impossible to maintain quality and meet the deadline simultaneously

Q4Speaking of scope, has the client signaled any additions or changes since you started, or has the scope held steady?

·Scope has held completely steady, no discussions of changes at all
·There have been a few questions about potential enhancements, but nothing serious
·The client has asked about adding features but has not pressed the issue
✓Scope has been stable, but there have been informal conversations that could turn into requests
·The client has verbally requested additions but has not submitted them formally yet
·Scope has already expanded once, and there are signs more changes may be coming

Q5If one of those informal conversations did turn into a formal scope request, what would you need from Meridian to keep the April 30 date intact?

·Nothing, we have enough buffer to absorb a small scope addition without impact
·A commitment from the client to defer the new request to a post-launch phase
·Additional budget approval so we can bring in a contractor for two weeks
·Clear prioritization from Meridian on whether we should accommodate or push back
✓A written scope freeze confirmation within the next week
·An immediate timeline extension or agreement to descope something else of equal size

The verdict it produced

Written for whoever ran the campaign. The respondent never sees it.

The subcontractor reports moderate confidence in the April 30 delivery, but a resource conflict is already in play. The lead developer is splitting time with an internal project, and while the PM describes this as manageable, it becomes a problem if scope expands. Informal client conversations have not yet turned into formal requests, but the risk is real. The PM requested a written scope freeze confirmation within one week. This is the first time the resource split or scope risk has been documented. Weekly check-ins showed no blockers.

resource conflict negative high confidence

The lead developer on this engagement is splitting time with another internal project.

scope stability mixed medium confidence

Scope has been stable so far, but informal client conversations pose a risk of future expansion.

timeline confidence mixed medium confidence

The PM reports moderate confidence in the April 30 deadline, contingent on no scope additions.

communication gap negative high confidence

The resource conflict and scope risk were not surfaced in prior weekly check-ins.

mitigation readiness positive high confidence

The PM has identified a clear mitigation step and can articulate the timeline for it.

See this on your own data

Fifteen minutes, screen to screen. We run your real question through RadRoot while you watch, and you leave with the follow-up it wrote and a price.

Book 15 minutes Answer one yourself