Free Network Build Assessment
Score your buildWho does what in a network build? A practical guide to the roles, reporting lines, and tools each team member needs.
Network build failures are almost always attributed to provider gaps or regulatory problems. The root cause is usually staffing: either the wrong people in the roles, the right people with the wrong tools, or not enough people to run the contracting, credentialing, and compliance tracks simultaneously. A large service area build means coordinating many provider relationships, regulatory filings, and adequacy tracking over many months. That is not a spreadsheet problem. It is a people and process problem.
This guide describes the core roles in a network build, what each person is responsible for, and how they need to work together.
The Network Development Director owns the overall build strategy and is accountable for adequacy submission outcomes. This is a senior role, typically VP or Director-level, with both internal leadership and external credibility. The NDO is the person who signs off on county selection strategy, approves exception filing approaches, and gets on the phone with the Medical Director of a hospital group when a key negotiation stalls.
Responsibilities include: service area strategy and county selection, network build P&L oversight, escalation point for stalled provider negotiations, executive-level reporting to the CMO and COO, and final review of all adequacy filings before submission.
What they need to be effective: a real-time view of adequacy gaps by county and specialty, a pipeline view of active contracting status, and credentialing status by provider. Without these views in a single system, the NDO is managing by exception from email and spreadsheet reports, which means they're always behind.
The Provider Relations Manager (PRM) owns the provider contracting pipeline. How many you need depends on the number of active provider relationships and how hard the market is. The PRM is responsible for the full contracting lifecycle: outreach, LOI, rate negotiation, contract execution, and handoff to credentialing.
Responsibilities include: managing the 6-touch outreach sequence for their assigned provider list, conducting rate negotiations within established parameters, coordinating with the contracting attorney on non-standard contract language, and maintaining accurate pipeline status so the NDO has a current view of contracting progress.
What they need to be effective: a CRM system that tracks provider contact history, pipeline stage, and next action items. It is easy to drop follow-up touches when working from spreadsheets, and a sequenced outreach cadence is hard to manage reliably without reminders and status tracking.
The Credentialing Coordinator manages the credentialing pipeline from application through committee approval and effective date assignment. Too many active files per coordinator and things fall through the cracks. Large builds may need several coordinators, or a delegated credentialing arrangement.
Responsibilities include: sending and tracking credentialing applications, CAQH verification and flagging stale profiles, managing PSV requests to licensing boards, malpractice carriers, and hospitals, scheduling and preparing committee packages, and tracking effective dates against the adequacy model run date.
What they need to be effective: a credentialing tracking system that shows stage, days-in-stage, and adequacy model run date alignment. When this lives in a spreadsheet, committee timing windows are easy to miss, and so are the providers who won't be credentialed in time.
The Data Analyst is the least glamorous and most undervalued role in a network build. They own the adequacy model: the quantitative analysis that maps contracted and credentialed providers to CMS adequacy standards by county and specialty, identifies gaps, and generates the filings. In teams without a dedicated analyst, this work falls on the NDO or the PRMs, who are then pulled away from their core responsibilities during the most critical periods of the build.
Responsibilities include: maintaining the adequacy model on a rolling basis, running gap analyses by county and specialty, preparing exception filing documentation, cross-validating provider data against PECOS, and producing the provider directory for submission.
What they need to be effective: access to current PECOS data, accurate contracting and credentialing status feeds, and a modeling environment that can run county-level time-distance calculations efficiently.
Blueprint gives this team one place to work: a contracting pipeline for each provider, outreach sequences with recorded decline reasons, credentialing status on the provider record, and adequacy scoring by county and specialty against CMS's standards. It doesn't replace any of these roles. Network teams still negotiate, credential, and review what gets filed.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.