-
Notifications
You must be signed in to change notification settings - Fork 4
Transfer of Care Document Breakdown
- Why is this form required?
Transfer of Care is required to maintain the responsibility and care of all animals. It allows CFIA to track the responsible parties involved under any incident of compromised rules & regulations. As mentioned by HAR section 153 it allows transporters to receive acknowledgement of their shipment and receivers to report or comment on any inconsistencies. Purpose of this form quoted from HAR Interpretive Guidance for Regulated Parties:
“This is done to ensure that the individual responsible for caring for the animals can be clearly identified at all times.”
- What time(s) interval(s) should the form be filled out, updated or made copy of?
Transfer of Care needs to be filled upon arrival at an abattoir, assembly yard or auction market. Transporter must present this document and receive acknowledgement(retrievable and unalterable legal receipt) failure to do so will hold the transporter accountable for any future non compliance or accident.
According to HAR, this document can be requested by CFIA inspectors anytime therefore transporters are advised to keep the record for 2 years time interval.
- Are there particular format requirements specified by HAR?
There is no particular required format for Transfer of Care i.e. the document can be digital as well as printed form. However, HAR does require both parties(transporters and receivers) to keep a copy of the document.
- Are there any sections in this form to be filled out with reference to other forms?
Transfer of Care refers to Feed, Watered & Rest (FWR) document for recording the most recent date, time and place where animals were last fed, watered and rested.
- What information must be recorded for Transfer of Care?
Information guidance provided by Interpretive Guidance section 20.2:
- Name of transporting company and the driver
- Receiving company and their representative
- Condition of animals on arrival (Notify receiver of any immediate attention required for any animal)
- Date, time and place from last FWR record
- Date, time and place of arrival
- Acknowledgement from receiver (transporters are not allowed to leave the shipment without any acknowledgement)
Note: According to HAR specifications the receiver does not need to be physically present for providing receipt, provision of legal receipt will be considered as acknowledgement.
LEGAL RECEIPT: According to Interpretive Guidance, a legal receipt is any written document of acknowledgment that can be retrieved later if needed and can not be altered after it has been issued.
- In case of any inconsistencies are there specific steps to be taken by either parties?
Interpretive Guidance for Regulated Parties has covered all the details of HAR Pt XII section 153: According to section 20.1, transporters can choose not to deliver upon noticing any compromised conditions or rules and regulations. However, HAR does require them to document their decision:
“The transporter must document their decision taken and why it was in the best interest of the welfare of the animals.”
If the receiver notices any inconsistencies, they are required to fill out the information on Transfer of Care along with the comments on these issues.
Deliverables pages (see website)
- Progress Update and Project Requirement Questions Oct 5, 2020
- Progress Update Meeting Oct 29, 2020
- Progress Update Meeting and USM-related questions Nov 11, 2020
- Mentor Progress Update Meeting Nov 25, 2020
- Livestock Services Saskatchewan Project Meeting Dec 3, 2020
- Team and Instructor, Mentor, and Faculty Meeting Minutes
- Sprint 0
- Sprint 1
- Sprint 1 Retrospective
- Sprint 2
- Sprint 2 Retrospective
- Sprint 3
- Sprint 3 Retrospective
- Sprint 4
- Sprint 4 Retrospective
- Sprint 5
- Sprint 5 Retrospective
- Sprint 6
- Sprint 6 Retrospective
- Sprint 7
- Sprint 8
- Sprint 7/8 Retrospective
- Sprint 9
- Sprint 10
- Animal Record Transport Template Breakdown
- Transfer of Care Document Breakdown
- FWR Document Breakdown
- Contingency Plan Breakdown
- C4-Model for Client-Server Architecture
- Data Modelling Design Process
- Guide to GUI Prototyping Structure