Posting of Field Trips Sample Clauses

Posting of Field Trips. Field trips shall be designated as weekday or weekend/holiday trips. Separate trip rotation list shall be maintained for each type of trip. Trips shall be posted on the first of the month, from the 16th to the end of the month. On the 16th of the month, trips will be posted from the 1st to the 15th of the following month. The trips will be posted as soon as possible in the morning. All trips logged in the book will be posted. The School Bus Driver Specialist will make every effort to confirm the trips with the schools, prior to posting. Any trips received by the School Bus Driver Specialist after the trips have been posted will become a “Bonus Trip”.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Posting of Field Trips. ‌ Field trips will be posted on the transportation employees board with easy access at all times each week for each driver. Field trips shall be handed out every Tuesday for the following week. Drivers taking non-routine trips that require an overnight or multiple night stay shall be given a food allowance not to exceed fifteen dollars ($15.00) per each eight (8) hours they are outside of the District. Drivers shall be eligible for food allowance payment upon submission of supporting receipts. If a food vendor does not provide receipts, the employee shall have the food vendor complete the District issued form documenting the purchase.
Sample 1
Posting of Field Trips. 1. The Supervisor or designee shall maintain two (2) trip lists. List #I - (Monday through Friday, until 2:30 p.m.). List II - (Monday through Friday after approximately 2:30 p.m., including all day Saturday, Sunday and holidays). Field Trip List List #I Trips occurring Monday thru Friday until approximately 2:30 P.M. which are less than (6) hours in length. (Special Provision) On this list, drivers with mid-day runs will be marked N/A (not available) if the field trip interferes with their mid-day run as determined by the Supervisor or designee. All regular drivers will not be pulled off their A.M. runs or Mid-Day runs. Field Trips six (6) hours or more shall be used from list II. A driver who has a mid-day run may only be taken off the mid-day run when a trip is six (6) hours or more. This shall not include pre-trip. Trips occurring Monday thru Friday, beginning after approximately 2:30 P.M. and all day Saturday, Sunday, holidays, and overnight. Field trips in excess of six (6) hours shall be assigned from List II. A driver who has a mid-day run may be taken off the mid-day run when a trip is more than six (6) hours in duration. The length of the trip shall not include the required pre-trip inspection. 2. The extra-trip rotation rosters shall be visibly posted. 3. Extra-trips will be assigned on a rotating basis from the appropriate list, in order of seniority.
Sample 1
Posting of Field Trips. 13.12.1.1 A list of extracurricular trips, as they are known, may be posted in the bus garage up to two weeks in advance. The list shall show destination and approximate time of the trip. Additional trips for the week shall be added as scheduled. 13.12.1.2 Once the driver assignments have been made and posted, no change shall be made except when a driver would forfeit a trip. 13.12.1.3 All activity trips will be granted on a rotating basis subject to the following conditions: 13.12.1.3.1 A regular driver may sign up for an activity trip. Every attempt to obtain a sub for the regular driver will be made as soon as possible. If a sub is not obtained 24 hours before the trip is scheduled to depart, the driver will have to revert back to taking his/her regular run. If a regular driver is awarded the trip and if the trip is canceled one (1) hour or less before departure, the driver forfeits his/her right to drive their regular run that day and will lose the scheduled hours for the regular run. Unscheduled activity trips will not be subject to this provision. 13.12.1.3.2 Drivers will be asked in line of seniority until they have reached a total of forty (40) hours for the week. The average hours worked for each regular run will be established during the first three (3) weeks of each school year. 13.12.1.3.3 Drivers assigned forty (40) hours per week or eight (8) hours per day shall become eligible for an activity trip before a substitute driver is assigned to the trip. 13.12.1.3.4 Drivers shall be paid their regular rate of pay for all time on extra- curricular/field trips. Minimum driving time shall be one (1) hour of driving time to destination and one (1) hour of driving time back to storage. 13.12.1.3.5 Layover time shall be paid at rate of $11.00 per hour for the term of this contract. 13.12.1.3.6 By seniority and rotation, drivers shall be allowed to select any trip from the posted list, not necessarily in the chronological order for the trips. 13.12.1.3.7 Cancelled trips shall be replaced by trips added for the week or from the list posted for the next week.
Sample 1

Related to Posting of Field Trips

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • AT WEBSITE XXX XXXXXXXXXXXXXXXX.XXX

  • Public Posting of DPA Pursuant to SOPPA, the LEA shall publish on its website a copy of the DPA between the Provider and the LEA, including this Exhibit G.

  • Posting of Schedules The Employer shall post the weekly work schedule for all employees not later than Monday 6:00 p.m. and twenty-two (22) days in advance. An employee's schedule may be changed without notice in the event of absence of other staff due to sickness or accident or in the event of emergencies. In all other cases, at least twenty-four (24) hours' notice of any change must be given or four (4) additional hours' pay given in lieu of notice. All requests for time off for special personal events to be made to Management for their approval prior to the posting of the schedule, and will be granted wherever possible. It is understood that this clause does not apply to casual employees. There shall be a daily starting time for each employee. Daily hours of work for full time employees shall be consecutive, with the exception of meal periods.

  • Filing of Materials All records related to a grievance shall be filed separately from the personnel files of the employees.

  • Posting of Agreement To ensure that the Parties are aware of the terms of the Agreement, and to assist in any resolution of a disputes or the avoidance thereof a copy of this Agreement shall be retained by the Employer at all times for ready access by any Employee on a project site or via access to the Employer’s intranet, and the Employer will provide a permanent copy for each Union Delegate or Employee representative and Health and Safety Representative on a project site.

  • Publication of Results The National Aeronautics and Space Act (51 U.S.C. § 20112) requires NASA to provide for the widest practicable and appropriate dissemination of information concerning its activities and the results thereof. As such, NASA may publish unclassified and non-Proprietary Data resulting from work performed under this Agreement. The Parties will coordinate publication of results allowing a reasonable time to review and comment.

  • Posting licensed content on any Website The following terms and conditions apply as follows: Licensing material from an Elsevier journal: All content posted to the web site must maintain the copyright information line on the bottom of each image; A hyper-text must be included to the Homepage of the journal from which you are licensing at xxxx://xxx.xxxxxxxxxxxxx.xxx/science/journal/xxxxx or the Elsevier homepage for books at xxxx://xxx.xxxxxxxx.xxx; Central Storage: This license does not include permission for a scanned version of the material to be stored in a central repository such as that provided by Heron/XanEdu. Licensing material from an Elsevier book: A hyper-text link must be included to the Elsevier homepage at xxxx://xxx.xxxxxxxx.xxx . All content posted to the web site must maintain the copyright information line on the bottom of each image.

  • Posting of Work Schedules Work schedules shall be written in ink and posted and maintained in such a way as to provide every employee an opportunity to know her shift schedule for an advanced period of six (6) weeks.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!