Public Engagement and Consultation Process Sample Clauses

Public Engagement and Consultation Process. SQCF aims to develop and maintain positive working relationships and effective communication with all potentially affected stakeholders identified as having interest in the Community Forest landbase. Potentially affected stakeholders are defined as those stakeholders with an identified interest in, or with the responsibility to manage, specific resource values within the Community Forest. This includes community groups and organizations, industrial tenure holders, commercial recreation tenures, government agencies and the general public using portions of the SQCF landbase. The SQCF will also develop communication strategies to provide information to the general public and other interested parties who self-identify. Consultation regarding operational/block level activities will be carried out on an ongoing basis with all known potentially affected stakeholders. Where forest management activities are contemplated, the SQCF will identify any interests and resource values with the potential to be affected. SQCF will notify potentially affected stakeholders of planned activities and invite them to share their comments or concerns relating to management of the identified value or resource. SQCF will consider all comments and input received and incorporate them as much as possible in management decisions and activities. Measures for ongoing communication with stakeholders may include emails, letters, phone calls and/or meetings as needed to address specific concerns. A website will also be developed as a means to broadcast information. The appropriate timelines and method of notification will be unique to each stakeholder and situation. The overarching goal and intent is to develop and maintain positive working relationships and strong communications with all relevant stakeholders. Public open houses (in person or online) will be held at least once per calendar year, during which recent and planned activities will be presented and opportunity for feedback provided. Additionally, a web site will be developed as a source of information. It is envisioned that the website will provide information regarding overall management and planning in the SQCF, current and proposed forestry activities, upcoming public engagement events and how to provide input (e.g. contact information where to direct comments and questions). All proposed road construction and harvest plans will be made available for public review and comment before being submitted to the BC Ministry of Forests...
Sample 1
AutoNDA by SimpleDocs

Related to Public Engagement and Consultation Process

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • INFORMATION AND CONSULTATION 8.1 You are entitled under the General Data Protection Regulation to access personal data we hold on you in our housing files. We will provide you with a copy of any such information we hold within one calendar month of your request. You may have other rights under the General Data Protection Regulation in relation to your personal data, which we will honour. You are entitled to check information you have provided in connection with your housing application free of charge. 8.2 We will publish an annual report on our housing management performance which, you may obtain from us on request. We will give you information about our complaints procedure. 8.3 On request, we will provide you with free information relating to: ▪ The terms of your tenancy; ▪ Our policy and procedures on setting rent and service charges; ▪ Our policy and rules about; o Admission to the housing lists; o Allocations; o Transfer of tenants between houses; o Exchanges of houses between our tenants, and tenants of other landlords; o Repairs and maintenance; o Our tenant participation strategy; o Our arrangements for taking decisions about housing management and services. 8.4 We will consult you about making or changing: ▪ Policies regarding housing management, repairs and maintenance if the proposal is likely to significantly affect you; ▪ Proposals for changes in rent and service charges where they affect all or a class of tenants (and you are to be affected); ▪ Proposals for the sale or transfer of your house to another landlord; ▪ Decisions about the information to be provided relating to our standards of housing management and performance; ▪ Performance standards or targets in relation to housing management repairs and maintenance; ▪ Our tenant participation strategy. We will take into account any views that you have before making a final decision. Any consultation with you will include giving you comprehensive information in an accessible form and reasonable time to express views.

  • Review and Consultation Employee acknowledges and agrees he (a) has read this Agreement in its entirety prior to executing it, (b) understands the provisions and effects of this Agreement and (c) has consulted with such attorneys, accountants and financial or other advisors as he has deemed appropriate in connection with the execution of this Agreement. Employee understands, acknowledges and agrees that he has not received any advice, counsel or recommendation with respect to this Agreement from Employer’s attorneys.

  • Consultative Process This Agreement recognises a commitment of the parties to develop working arrangements which will bring success to the operations of the Company through the ability to implement flexible work arrangements to meet the requirements of customers and the personal, study or family commitments of employees.

  • Notification and Consultation 1. A Party shall promptly notify the other Party in writing upon: (a) initiating a bilateral safeguard proceeding under this Section; (b) applying a provisional bilateral safeguard measure; and (c) taking a final decision to apply or extend a bilateral safeguard measure. 2. A Party shall provide to the other Party a copy of the public version of the report of its competent investigating authority in accordance with Article 8.4.1. 3. Upon request of a Party whose good is subject to a bilateral safeguard proceeding under this Section, the Party conducting that proceeding shall enter into consultations with the requesting Party to review a notification under paragraph 1 or any public notice or report that the competent investigating authority has issued in connection with the proceeding. 4. All notifications during any bilateral safeguard investigation shall be exchanged in English.

  • Consultation Services The company hereby employs the consultant to perform the following services in accordance with the terms and conditions set forth in this agreement: The consultant will consult with the officers and employees of the company concerning matters relating to the management and organization of the company, their financial policies, the terms and conditions of employment, and generally any matter arising out of the business affairs of the company.

  • JOINT CONSULTATION 25.01 The parties acknowledge the mutual benefits to be derived from joint consultation and will consult on matters of common interest. 25.02 The subjects that may be determined as appropriate for joint consultation will be by mutual agreement of the parties. 25.03 Wherever possible, the Council shall consult with representatives of the Professional Institute at the appropriate level about contemplated changes in conditions of employment or working conditions not governed by this Agreement.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Consultation Procedure If a party hereto is unable to meet the provisions of the Service Level Agreement, or in the event that a dispute arises relating to performance goals set forth in the Service Level Agreement, either party to this Agreement shall address any concerns it may have by requiring a consultation with the other party.

  • Technical Consultations If a Party has a significant concern with respect to food safety, plant health, or animal health, or an SPS measure that the other Party has proposed or implemented, that Party may request technical consultations with the other Party. The Party that is the subject of the request should respond to the request without undue delay. Each Party shall endeavour to provide the information necessary to avoid a disruption to trade and, as the case may be, to reach a mutually acceptable solution.

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