RO referrals for pensioners

  • This topic has 4 replies, 1 voice, and was last updated 19 years ago by Anonymous.
Currently, there are 0 users and 1 guest visiting this topic.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #20067

    Just had a discussion regarding RO referrals after 6/10/03, which has left me even more confused than normal and with a number of queries. Any help/thoughts would be gratefully received!

    1 Should an authority be referring the rent to the RO before the old RO decision has expired, so the new decision will be ready and can run continuously, if not:

    2 Should we wait until the previous decision is 52 weeks old, then refer the rent – if so can we pay benefit based on the old decision, which is now over 52 weeks old

    3 If the RO decision changes the max rent, when do changes in benefit occur from (as usually these are linked to date of review claim or date of a relevant change)

    deep breath….

    4 and finally! If the claim is rereferred due to a non dep joining the household, does any change to the RO decision take effect from a) the date the non dep joined the h/hold, b)the date of the RO decision or c) 26 weeks later???

    I told you I was confused!

    Thanks 😕


    You should be able to refer up to 4 weeks before the previous decision expires, in order to prevent this problem occuring.

    I do not know which software supplier you use, but using Academy we are able to set diary dates, which act as reminders as when to re-refer.

    I may have an answer to the non-dep query closer to the time.


    Just want to clarify something in SI 1338 around when re-referrals can be made.

    Current practise (i.e. prior to abolition of benefit periods) allows us to obtain a new RO decision for use from the start of the next benefit period providing that the old RO decision [i:a5f782b0be]had been used on the claim [/i:a5f782b0be]for at least 52 weeks.

    SI 1338 introduces a similar method of “52 week referrals” but makes reference to “52 weeks since the last application for a decision” – this would reflect the date of the RO referral but would not necessarily reflect the date it is used from on the HB claim.

    I’m guessing that the intention is to re-refer every time a decision has been used for 52 weeks on a claim but SI 1138 doesn’t seem to say this. Can anyone shed any light on this or am I just not reading the regs right?


    I agree that an application should be made 52 weeks after an application was previously made under the old provisions.
    This should make things easier as there is no need to wait until the 52 weeks expiry date, put the claim on interim and then refer to the Ro.
    We have requested a report to be run giving claims where the ROD is due to expire in 4 weeks and refer them to the RO at that time.
    The decision should then be received in sufficient time to use on the claim at the 52 week date.


    Thanks for the response.

    Playing Devils Advocate: 😈

    Supposing a claim is received on 3/11/03, processed the same day and paid on account wef 3/11/03. Customer has not provided sufficient information for a RO referral to be done so this is queried further. Full info received on 22/12/03 and referred to RO same day. RO decision received 29/12/03 and used on claim wef 3/11/03 According to SI 1338, we cannot re-refer until 22/12/04 thus meaning the original decision is used for approx 60 weeks.

    Contrast this with another claim made at exactly the same time but this person does provide all details necessary for an RO referral. This claim is processed on the same day, i.e. 3/11/03 and a referral done that day. This claim can then have a re-referral 3/11/04 meaning that the original decision is valid for 52 weeks.

    Surely this can’t be right – wouldn’t it be easier for all RO decisions to be used for 52 weeks. Upon re-referral, this period would be specified to the RO in the same way that we tell them the benefit period dates at the moment.

    Any comments anyone??? ❓

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.