Establish the Pool Sample Clauses

Establish the Pool. To qualify for the seniority provisions contained in this paragraph, faculty must have taught at least one (1) fall or spring course in University College (or former CCDE) within the prior two (2) years. The seniority rank for fall or spring courses assignments shall be determined by the number of University College (or former CCDE) courses a particular faculty member has taught within a given department. Faculty members who are tied in seniority will have their seniority determined by a coin toss, where the loser receives priority over the winner in the next assignment in University College (either in the same or a subsequent semester). The Department shall email priority lists to each faculty member within the department and the Union by August 15th annually. .
AutoNDA by SimpleDocs
Establish the Pool. To qualify for the Session Pool, faculty must have taught at least one (1) course in that Continuing Education session (Summer, Winter, or Spring/Fall) within the past two (2) years. Seniority Rank Within That Pool shall be determined by the number of Continuing Education courses a particular faculty member has taught within a given department. Faculty members who are tied in Pool Seniority will have their seniority determined by a coin toss, where the loser receives priority over the winner on the next occasion on which they are both in a pool (either for additional courses in that Session or in subsequent Sessions) for the assignment of Continuing Education courses.

Related to Establish the Pool

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Administrative Controls The Contractor must have the following controls in place:

  • Separate Accounting Our policies may permit separate accounting to be applied to your SIMPLE IRA for the benefit of your beneficiaries. If permitted, separate accounting must be applied in accordance with Treasury Regulation 1.401(a)(9)-8, Q&A 2 and 3. A beneficiary is considered the only designated beneficiary of his/her share of the SIMPLE IRA assets if separate accounting applies.

  • Appropriate Use It will use its Project property for appropriate purposes (including joint development purposes as well as uses that provide program income to support public transportation) for the duration of the useful life of its Project property, which may extend beyond the duration of the Award, and consistent with other requirements FTA may impose.

  • Program Reporting Contractor shall provide such data as may be required by the Board, in the form required by the Board to fulfill its obligations as a public school district, as well as academic, financial and other program records and reports as requested by the Board for program accreditation, monitoring, payment, and auditing. Such data and reports shall include, but not be limited to, all of the following:

  • Carried to Collection R Section 1 Bill No. 1 Preliminaries Contract instructions (Clause 17). 17 F: ……….… V: ….……… T: ….……... Item Setting out of the works (Clause 18). The contractor shall notify the principal agent if any encroachments of adjoining foundations, buildings, structures, pavements, boundaries, etc., exist in order that the necessary arrangements may be made for the rectification of any such encroachments. 18 F: ……….… V: ….……… T: ….……... Item Assignment (Clause 19). 19 F: ……….… V: ….……… T: ….……... Item Nominated subcontractors (Clause 20). 20 F: ……….… V: ….……… T: ….……... Item Selected subcontractors (Clause 21). 21 F: ……….… V: ….……… T: ….……... Item Employer's Direct contractors (Clause 22). 22 F: ……….… V: ….……… T: ….……... Item Contractor's Domestic subcontractors (Clause 23). 23 F: ……….… V: ….……… T: ….……... Item COMPLETION Practical completion (Clause 24). 24 F: ……….… V: ….……… T: ….……... Item Works completion (Clause 25). 25 F: ……….… V: ….……… T: ….……... Item Final completion (Clause 26). Carried to Collection R

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

  • Entity Accounts Not Required to Be Reviewed, Identified or Reported Unless the Reporting Singaporean Financial Institution elects otherwise, either with respect to all New Entity Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in Singapore provide for such election, a credit card account or a revolving credit facility treated as a New Entity Account is not required to be reviewed, identified, or reported, provided that the Reporting Singaporean Financial Institution maintaining such account implements policies and procedures to prevent an account balance owed to the Account Holder that exceeds $50,000.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.

Time is Money Join Law Insider Premium to draft better contracts faster.