Meeting Summary Sample Clauses

Meeting Summary. Summary of a meeting between a supervisor and employee that provides constructive and corrective feedback. This is not considered to be disciplinary and will not be placed in the employees personnel file.
Sample 1Sample 2
AutoNDA by SimpleDocs
Meeting Summary. ‌ The agenda of the meeting was broadly divided into three parts, which are discussed separately here. 14xxxxx://xxx.xxxx.xx
Sample 1Sample 2
Meeting Summary. Bi-weekly meetings between Contractor and City (in-person and conference calls, anticipated total of 6 and 12, respectively). · Monthly invoices and project progress reports. · Project Work Plan.
Sample 1
Meeting Summary. I&L will prepare meeting summary notes in PDF format and submit them to the County and attending agencies via email. I&L will incorporate any comments received from the County and attending agencies into the meeting notes.
Sample 1
Meeting Summary. An account of the discussions in these meetings is prepared by a Committee member, and is given to each Committee representative within five (5) days following the meeting. However, members of the Committee may, especially in the case of the confidential or sensitive nature of certain subjects, agree that the subject be discussed in confidentiality. LETTER OF UNDERSTANDING #6 Re: Employee benefit assistance program The purpose of this letter is to assist the workers and dependents that are enrolled in the Health portion of the benefit plan offered by the company and who have exceeded the maximum amount of the drug benefit. The company is prepared to do either of the following:
Sample 1
Meeting Summary. I&L will prepare meeting summary notes in PDF format and submit them to the CITY via email. I&L will incorporate any comments received from the CITY into the meeting notes.
Sample 1
Meeting Summary. The Chicken Board updated BCFIRB on the status of other provincial signatories. All provincial supervisory and chicken boards have signed the amended Operating Agreement with the exception of Ontario, Quebec and BC. The discussion also covered some of the pros and cons of the Atlantic Canada Safeguard Agreement, the background, potential impacts on BC production, and the overall outcome for BC based on the Operating Agreement to date. There was some discussion about the importance of determining BC’s interests for when the Operating Agreement comes due for renewal in 2024, along with related considerations such as a potential national cost of production and the current Global Affairs Canada tariff rate quota consultations. British Columbia Farm Industry Review Board Mailing Address: PO Box 9129 Stn Prov Govt Victoria BC V8W 9B5 Telephone: 000 000-0000 Facsimile: 000 000-0000 Location: 1st Floor, 000 Xxxxxxxxx Xxxxxx Xxxxxxxx XX X0X 0X0 Email: xxxx@xxx.xx.xx Website: xxx.xxx.xx.xx/XXXxxxXxxxxxxxXxxxxxXxxxx Xxxx Xxxxxxxxxx July 18, 2019 After discussing the Chicken Board’s process to date, and the responses received from the BC Chicken Growers Association and the Primary Poultry Processors Association, BCFIRB and the Chicken Board agreed to the signatory review process set out below. Signatory Review Process Based on the July 16, 2019 meeting, the Chicken Board and BCFIRB agree to establish the following overall process: Chicken Board The Chicken Board will request further information, based on specific questions, from stakeholders, including the BC Chicken Growers Association, the Primary Poultry Processors Association of BC and the BC Broiler Hatching Egg Commission. Once the Chicken Board has completed its information collection and analysis, it will submit its decision and rationale to BCFIRB. BCFIRB expects the Chicken Board will keep its stakeholders and BCFIRB informed on its process and timelines.
Sample 1
AutoNDA by SimpleDocs
Meeting Summary. The following provides a summary of key discussion points, comments, and questions during the informational meeting. An in-depth meeting outline is provided in the attached PowerPoint presentation with complete details provided in the Informational Meeting Packet. The meeting was initiated by Xxxxxxx Xxx (RS&H Consultant Project Manager). After brief welcome by Xxxx Xxxxxxxx (USACE), Xxxxxxx led the attendees through the PowerPoint presentation. Xxxx Xxxxxx (RS&H), Xxxxxx Xxxxxx (RS&H), and Xxx Xxxxxxx (RS&H) provided updates on past public involvement efforts and service roads, traffic operations and lane configurations, and detailed project designs (as shown on the December 2021 Public Meeting Maps). The outline for the meeting presentation (shown in the attached PowerPoint) included:
Sample 1
Meeting Summary. Xxxx Xxxxxxx presented the updated work streams, participants signed-up thus far and dependency relationships in the Semantics Repository. Discussion lead to the following actions: The following work streams calls/schedules will be organized: General Call: Monthly, starting May 4th 2011 (please note new time: 1.30-2.30 PM, US EDT). Please note the dial-in/Live meeting information will remain the same (for the general call ONLY) Thursdays 1 – 2pm Eastern US time: Technical Modeling Framework (weekly) Thursdays 2 - 3 pm Eastern US time: Content Disposition; Shared Semantics (alternate weeks); Shared Semantics weekly once CD complete. These will be on the EDM Council GoToMeeting (web plus dial-up, including free Voice over IP). See Appendix Slide (meeting presentation document) for details Xxxxx Xxxxxx presented the ‘data view’ of how business requirements such as regulatory reporting, AML, Trade Surveillance could leverage concepts modeled in the semantic repository including OMG modeling languages needed (see slide 8). On May 4th session (call starting at 1.30 PM US EDT), Xxxxxxx Xxxxxx, Director of Financial Reform, PEW Trusts will go thru an outline of the proposed white paper on Global Data Standards and Strategy (30 min). White paper will ultimately serve as a layer on top of the semantic models and OMG modeling languages (how these things fit together as the data strategy for financial reform and other applications such as Trade Surveillance, AML…) Remaining time will be used to continue to validate the work streams specific Tasks and also agenda for the June 2011 OMG-EDMC meeting in Salt Lake City (June 21/22nd). Meeting Notes Topic Description Discussion lead/participant Action Item/Next Steps, Owner Target Date/Period Technical Modeling Framework work stream Co-Leads: Xxxxxx Xxxxxx, Xxxx Xxxxxx MB added that work on the basics of this work stream has already been taking place with Xxxxx Xxxxxxx and Xxx Xxxxx, who are unable to make today's call. I would very much hope that one of them is also a Co-chair. Members expressed a preference for having both main sets of calls on the same day back to back. At present we have Content Disposition and Shared Semantics as alternate weeks, and the Content Disposition is temporary. MB noted that the Content Disposition working group will have a short life of 2 - 3 sessions, and that the Shared Semantics could potentially be a lot of work and therefore would benefit from being weekly once the Content Disposition w...
Sample 1

Related to Meeting Summary

  • Meeting Space Union representatives may request the use of state property to hold union meetings. Upon prior notification, the Employer will provide meeting spaces where feasible. Such meetings will not interrupt state work and will not involve employees who are working. The Employer shall make space available for Union representatives to have confidential discussions with employees on an as needed basis subject to availability.

  • Meeting Attendance The Contractor shall attend such meetings of the Town relative to the Scope of Work set forth in Exhibit A as may be requested by the Town. Any requirement made by the named representatives of the Town shall be given with reasonable notice to the Contractor so that a representative may attend.

  • PAYMENT FOR MEETING ATTENDANCE 17.01 When the Employer requires an employee to be present at a meeting called by the Employer during the employee's scheduled working hours, time spent at such meeting shall be considered as time worked.

  • Meeting Times ‌ Meetings shall be held at least quarterly, but no more than monthly, at a time that is convenient for both Parties.

  • Scoping Meeting 4.2.1 A scoping meeting will be held within ten (10) Business Days after the Interconnection Request is deemed complete, or as otherwise mutually agreed to by the Parties. The Utility and the Interconnection Customer will bring to the meeting personnel, including system engineers and other resources as may be reasonably required to accomplish the purpose of the meeting. The scoping meeting may be omitted by mutual agreement in writing.

  • Pre-Operations Meeting PURCHASER shall meet with STATE no later than 30 days from execution of the contract to discuss the Threatened and Endangered Species survey, protection, and planning requirements. Operations Plan. PURCHASER shall prepare an Operations Plan for all operations to be conducted under this contract and submit the plan to STATE at least 5 calendar days prior to commencement of any operation. This plan shall be prepared on a form provided by STATE, and shall be used for all types of operations, including road maintenance, project work, logging, and postharvest requirements. STATE may require an on-site meeting prior to approval of the plan, attended by PURCHASER, subcontractor, and STATE representatives. STATE's approval of the plan must be obtained prior to commencement of any operation, and PURCHASER must comply with this plan. If PURCHASER fails to comply with any of the terms of the plan, including completion dates, STATE may, after giving written notice, suspend PURCHASER's operations until such time as an acceptable alternate plan is submitted by PURCHASER and that alternate plan is accepted by STATE, as provided in Section 29, "Violations, Suspensions, and Cancellation." PURCHASER shall notify STATE whenever operations will be inactive for more than 3 days, and again when operations will be resumed. Upon approval by STATE, the Operations Plan shall automatically be incorporated into, and made part of, this contract. PURCHASER's strict compliance with the Operations Plan, as approved by STATE, is a material condition and covenant of this contract. STATE has prepared the required Forest Practices Act (FPA) "Written Plan" for operations within 100 feet of Type F or Type D streams. Any changes to the plan must have STATE approval. PURCHASER shall comply with all provisions of the Written Plan. Seasonal Restrictions. PURCHASER shall adhere to the following restrictions, unless otherwise approved in writing by STATE:

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