Author Topic: RFD vs COS  (Read 1255 times)

0 Members and 1 Guest are viewing this topic.

Offline SailorGuy1975

  • Guest
  • *
  • 90
  • Rate Post
  • Posts: 3
RFD vs COS
« on: April 09, 2019, 19:04:47 »
Hello all,

I am being posted to CFLRS and am from ESQ. My COS date is AUg 06. My CM stated that I can change this date 30 days either side if both the losing and gaining unit agree and in turn the CM doesnt get involved.

I have picked July 8th.
But now I am confused as my COC is asking my Co and CFLRS to have my RFD be July 8th.

So here's my question
Is RFD is the date CFLRS expects to see my at work and if so so what is my new COS date? As Brookefield states the COS date is the date we start travelling.
But if my RFD changes to July 8th, obviously we would need to start travelling in June as it takes 10 days and we were hoping to be in new home july 1st, and then take 5 annual and RFD july 8th.

This make sense? Any clarification on this matter would be greatly appreciated.

Sailor Guy

Offline Lumber

  • Donor
  • Army.ca Veteran
  • *
  • 59,794
  • Rate Post
  • Posts: 2,104
Re: RFD vs COS
« Reply #1 on: April 09, 2019, 19:56:06 »
Hello all,

I am being posted to CFLRS and am from ESQ. My COS date is AUg 06. My CM stated that I can change this date 30 days either side if both the losing and gaining unit agree and in turn the CM doesnt get involved.

I have picked July 8th.
But now I am confused as my COC is asking my Co and CFLRS to have my RFD be July 8th.

So here's my question
Is RFD is the date CFLRS expects to see my at work and if so so what is my new COS date? As Brookefield states the COS date is the date we start travelling.
But if my RFD changes to July 8th, obviously we would need to start travelling in June as it takes 10 days and we were hoping to be in new home july 1st, and then take 5 annual and RFD july 8th.

This make sense? Any clarification on this matter would be greatly appreciated.

Sailor Guy

Just to be clear:
COS = Change of Strength Date, i.e.the date you officially stop being a member of one unit and start being a member of another unit. This is all administrative;
RFD = Report for Duty Date, i.e. the day you actually physically show up for work at your new unit.

One you first get your posting message, your COS and RFD are the exact same date. But as we all know, the COS date doesn't always work with everyone's particular situation, which is why we have RFD dates.

Technically, you can request ANY RFD, and whatever the RFD is, it would, I suppose, technically make sense for that to be your COS date. However, it's unreasonable to expect the career managers to release a new posting message with a new COS date every time someone's RFD doesn't line up with their existing COS. Therefore, as rule of thumb (because I haven't seen this written in stone), the Career Managers are happy to stay out of it as long as the RFD is within 30 days either side of your COS. If you are requesting (or need) a COS date that is 31 or more days either side of the RFD, then the career manager WILL cut a new posting message.

So, with respect to Brookfield, they sometimes seem to have trouble understanding the difference between your COS and RFD. Considering how many postings they process a year, this surprises me. Anyways, the bottom line is that Brookfield WILL work with your RFD date, not your COS date. In the past, I've had Brookfield request the email chain that shows both my chains of command approving my change in RFD, and another time when I moved, Brookfield just took my word for it!

TL;DR: Your COS date will not change. Your RFD of July 8th is fine, and Brookfield will process a move that has you in St.Jean on the 6th of July, and at CFLRS by the 8th of July.

If I wasn't clear, or if you have any other questions, please ask.
"Aboard his ship, there is nothing outside a captain's control." - Captain Sir Edward Pellew

“Extremes to the right and to the left of any political dispute are always wrong.”
― Dwight D. Eisenhower

Death before dishonour! Nothing before coffee!

Offline Eye In The Sky

  • Army.ca Fixture
  • *****
  • 225,865
  • Rate Post
  • Posts: 8,912
    • VP INTERNATIONAL
Re: RFD vs COS
« Reply #2 on: April 09, 2019, 20:55:46 »
Therefore, as rule of thumb (because I haven't seen this written in stone), the Career Managers are happy to stay out of it as long as the RFD is within 30 days either side of your COS.

I'd have to check the manual to be sure but...I think it is in CH 7 of MILITARY HUMAN RESOURCES RECORDS PROCEDURES MANUAL.  From my posting msg this year, Para 5(a)(2):

AS PER THE MILITARY HUMAN RESOURCES RECORDS PROCEDURES MANUAL, GAINING AND LOSING CO CAN AUTHORIZE A REPORTING DATE WITHIN 30 DAYS OF THE COS DATE. THERE IS NO NEED TO ADVISE CAREER MANAGER OF THE MUTUALLY AGREED UPON REPORTING DATE

Quote
If you are requesting (or need) a COS date that is 31 or more days either side of the RFD, then the career manager WILL cut a new posting message.

Unless it has changed in the last 6 years, if you request a new COS date you will have to get a new posting msg.  Getting a new posting message will cause Brookfield to close your current file, open a new one and start from scratch.

Your request for change in RFD should be a memo, email, etc...something you can provide to Brookfield to show you are attempting to do the 'door to door' move thing happen.  Important IAW CFIRP, Ch 2, Sect 2.3.
« Last Edit: April 09, 2019, 21:31:09 by Eye In The Sky »
Everything happens for a reason.

Sometimes the reason is you're stupid and make bad decisions.

Offline Eye In The Sky

  • Army.ca Fixture
  • *****
  • 225,865
  • Rate Post
  • Posts: 8,912
    • VP INTERNATIONAL
Re: RFD vs COS
« Reply #3 on: April 09, 2019, 21:10:30 »
and then take 5 annual and RFD july 8th.

Keep in mind, you should be able to request 5 days Special (Relocation) leave on either end of your move IAW the CFLPM, Chap 5, Section 5.10 Special Leave (Relocation).  Worth having a read of.

5.10.10 Relative to a Posting

Special Leave (Relocation) may be granted to a member who is posted when it involves a move to a new geographical area. The authority for granting the leave and the amount of Special Leave (Relocation) that may be approved at each end of a posting, based on the posting situation, are prescribed within Annex B, Table 1.  (3 x days Pers Admin, 2 x days HG & E by each the losing and gaining unit COs).

(* My last move, Brookfield scheduled my Pack/Load on a Thur-Fri which left Sat for my Clean day.  I said nope, and made them move their Pack/Load.  Be watchful of little things like that.)

Special Leave (Relocation) shall not be granted to a member who is posted within their geographical area.

Special Leave (Relocation) may be granted to both members of a service couple who are posted or attached posted. If only one member of a service couple is posted, then annual leave must be taken for the member who is not posted.

The Special Leave (Relocation) granted remains exclusive of and distinct from the travel time authorized for the relocation of members and families between locations.

When a member’s COS date is prior to their move, the CO of the gaining unit may grant the member the leave at both ends of the move.

Special Leave (Relocation) is not intended and shall not be used to compensate for a member having worked weekends or statutory holidays.




« Last Edit: April 09, 2019, 21:19:30 by Eye In The Sky »
Everything happens for a reason.

Sometimes the reason is you're stupid and make bad decisions.

Offline SailorGuy1975

  • Guest
  • *
  • 90
  • Rate Post
  • Posts: 3
Re: RFD vs COS
« Reply #4 on: April 09, 2019, 22:01:28 »
Thank you so much for that incredible clarification..our first meeting with BF is monday...., if any new questions come up after that I will ask

He who authorizes the Relocation leave? My losing unit or gaining unit?

Offline Infanteer

  • Directing Staff
  • Army.ca Myth
  • *
  • 176,830
  • Rate Post
  • Posts: 15,319
  • Honey Badger FTW!
Re: RFD vs COS
« Reply #5 on: April 09, 2019, 22:04:02 »
He who authorizes the Relocation leave? My losing unit or gaining unit?

Depends if the leave is before or after your COS (why that administrative date is important).  If it is before the COS, your losing unit should do it.  If after, your gaining unit.
"Overall it appears that much of the apparent complexity of modern war stems in practice from the self-imposed complexity of modern HQs" LCol J.P. Storr

Offline PuckChaser

  • Directing Staff
  • Army.ca Fixture
  • *
  • 923,065
  • Rate Post
  • Posts: 8,203
    • Peacekeeper's Homepage
Re: RFD vs COS
« Reply #6 on: April 09, 2019, 22:09:20 »
When I moved my RFD (earlier due to the closing date on the home I was selling), all Brookfield needed was a signed copy of the memo that authorized my new RFD. That let them change my pack/load/move days and my travel to line up properly.

Offline Old EO Tech

  • Full Member
  • *****
  • 10,335
  • Rate Post
  • Posts: 430
Re: RFD vs COS
« Reply #7 on: April 09, 2019, 23:43:59 »
When I moved my RFD (earlier due to the closing date on the home I was selling), all Brookfield needed was a signed copy of the memo that authorized my new RFD. That let them change my pack/load/move days and my travel to line up properly.

Emails between losing and gaining units have always worked in my experience, including myself this year :-/

Offline PuckChaser

  • Directing Staff
  • Army.ca Fixture
  • *
  • 923,065
  • Rate Post
  • Posts: 8,203
    • Peacekeeper's Homepage
Re: RFD vs COS
« Reply #8 on: April 10, 2019, 07:31:35 »
Emails between losing and gaining units have always worked in my experience, including myself this year :-/
Army's gonna Army...

Offline Lumber

  • Donor
  • Army.ca Veteran
  • *
  • 59,794
  • Rate Post
  • Posts: 2,104
Re: RFD vs COS
« Reply #9 on: April 10, 2019, 08:38:04 »
Army's gonna Army...

It's not just the army. From my experience it's command team to command team.

IMO, you only should need a memo if you need to convince someone of something, and therefore the memo is your opportunity to layout your arguments in a clear and concise manner.

If all you are doing is asking for an entitlement, or asking that an approved process be actioned, then you should need to do all the damn staff work involved with writing, correcting, reviewing, and passing up and down the CoC that's involved with staffing a memo.

At most, a very brief minute sheet should be all that is required.
"Sir, Cpl Bloggins' is requesting an RFD iof #### based on the closing date of his new revidence. This is within 30 days of his COS date of ####."
"Approved"
Done.

It's soooo easy with an email, and when it's in an email, no one cares if you misspelled "residence"... ;)
"Aboard his ship, there is nothing outside a captain's control." - Captain Sir Edward Pellew

“Extremes to the right and to the left of any political dispute are always wrong.”
― Dwight D. Eisenhower

Death before dishonour! Nothing before coffee!

Offline 211RadOp

  • Sr. Member
  • *****
  • 26,043
  • Rate Post
  • Posts: 886
  • Now is the tyme....damn missed again....Now is the
Re: RFD vs COS
« Reply #10 on: April 10, 2019, 09:17:28 »
I have twice asked for a change in RFD while in Army units and both times were by e-mail.  It makes it easier for the loosing CO to forward to the gaining CO for concurrence.  While I was at CFSCE, it was highly encouraged to request this by e-mail and the turn around time was usually 1 day, sometimes the same day.
“Behind every great man is a woman rolling her eyes." Jim Carrey
"Do unto others, then run." Benny Hill
"There's no better feeling in the world than a warm pizza box on your lap." Kevin James

Offline Navy_Pete

  • Army.ca Subscriber
  • Sr. Member
  • *
  • 31,185
  • Rate Post
  • Posts: 874
Re: RFD vs COS
« Reply #11 on: April 10, 2019, 16:12:50 »
Army's gonna Army...

For postings to ships, Navy does a lot of messages to formally approve the RFD change (after an email exchange approval). It seems pedantic, but makes it official and is used for sea pay. Doesn't matter at the time, but makes it a lot easier if you get audited years later, and you don't need to rely on your email account from multiple postings ago.