Request for Services Budget Overview

The following scenarios describe each type of budget change that can happen in Request.  More than one scenario can be combined in a single request.  However, each is independent and unique to its circumstances.  Consequently, the worker should carefully consider which scenario best fits the circumstances of their request.  For example, if the Request involves both an ongoing rate and unit increase for the same service, then the worker should pursue the "Ongoing Rate and Unit Increase" path instead of trying to load two independent pathways for an "Ongoing Rate Increase" and an "Ongoing Unit Increase" for the same service code in the same Request.

Ongoing Money Scenarios

One-Time Money Scenarios

The budget portion of the Request for Services documents how much a new service or an increase for an existing service increase will cost.  These two types of changes must funnel through the criteria section of the request before their respective services can appear on the budget.  Conversely, a decrease to or elimination of an existing service in the Active PCSP does not have to go through the criteria section of the Request.  Instead, the decrease or elimination can be added directly to the budget outside of the criteria process.

The table above presents the fifteen combinations that can occur to a service code.  Each one represents a distinct scenario the service on the budget must fall within.  That is, the service cannot have more one scenario.  Each scenario has its own data and process requirements.  Consequently, the worker must ensure they are selecting the correct scenario for each service code before proceeding with loading its date(s), rate and units.