Replacements (Blue Badge only)
The 'Replacements' workflow is created automatically if a request for a replacement has been received either through the DfT for a Blue Badge, or manually if a paper application is received.
If a badge number has been supplied by the applicant, the system will attempt to link this ‘Replacement’ workflow with the correct badge holder in the CMS.
So we try our best to link the correct replacement request with the correct citizen in the CMS. To achieve this, we perform further validation, by checking the following:
If there IS a badge number entered:
if the date of birth and last name match with a case in the CMS that has the same badge number as was entered by the applicant, we link the two
OTHERWISE
we create a different case
If there IS NO badge number entered:
if the NINO and date of birth match with anyone in the CMS, we link the two,
OR IF NOT
if the date of birth, last name and postcode match with anyone in the CMS we link the two,
OTHERWISE
we create a different case.
The Replacement workflow commences with the stage 'Replacement Request'.
The 'Work Items' Tab, when opened, will show all new 'Replacement' applications received. It will also show to which stage existing workflows have been progressed.
The 'Replacement' application is progressed depending upon the decision that is made at a specific stage. For example at the 'Replacement Request' stage, there are a number of 'outcomes' depending upon reviewing the submitted Replacement application:
Subsequent stages are dependent upon the choice of outcome from the option above. In our example I have selected 'Badge is Stolen'. When selected, further questions are asked which can be mandatory or not. In this case any Notes relating to the theft and a Crime Reference Number are mandatory before this workflow can be progressed:
Last updated
Was this helpful?
