Adapting the GRB guidance Sample Clauses

Adapting the GRB guidance. The MA engaged a gender consultant experienced in NGO-led gender analysis at the local level, as well as with federal gender policies and gender budget initiatives in Ethiopia. The consultant started by visiting, two SAIPs (ADA and RCWDO) so that she could develop a clear understanding of the ongoing SA practice and the difficulties faced during GRB implementation. Findings were:  GRB is regarded as a stand-alone tool, and is not linked to the ongoing SA process.  SAIPs did not recognise that their findings from the focus group discussions already contained information about women’s priorities as well as men’s priorities. With gender analysis experience they realised how easy it could be to merge GRB with other SA tools. The field visit was immediately followed by a consultative meeting (May 2014) with the implementing partners that had selected the GRB tool, to know the status of GRB tool implementation, to discuss difficulties and to explore the expectations regarding a revised GRB tool. This meeting also helped to understand the capacity of each of the SAIPS: the gender expert was able to conduct a rapid assessment of their ability to implement GRB using follow-up questionnaires. It transpired that some had significant gender and development expertise, others less so. In this process of exploring what would be feasible in terms of implementing Gender Responsive Budgeting, a significant innovation emerged, namely to integrate GRB principles with the other SA tools: when practical steps for GRB were worked out, it started to look like Participatory Planning and Budgeting with a strong gender mainstreaming component, while at the same time it became clear that understanding the gender implications of sector problem analysis and related budget implications to solve these problems were relevant for all SA tools. For these reasons, we agreed to develop a GRB mainstreaming tool rather than a stand-alone tool. The GRB manual was adapted to make it more user-friendly and to provide key steps to guide SAIPs through the GRB process (see table 2) and training was provided to ensure that SAIPs were fully able to implement the process. With the adaptation of the GRB tool, a key issue was clarified regarding its use in conjunction with other tools. In practice, it became evident that the tool was best used as a way of mainstreaming gender awareness into other SA tool practices. The steps in the revised GRB tool are presented in Box 1.
AutoNDA by SimpleDocs

Related to Adapting the GRB guidance

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Withdrawal of Licensed Materials The Publisher reserves the right to withdraw from the Licensed Materials any item or part of an item for which it no longer retains the right to publish, or which it has reasonable grounds to believe infringes copyright or is defamatory, obscene, unlawful, or otherwise objectionable. The Distributor shall ensure that the Publisher will give prior written notice of the withdrawal to the Licensee and the Participating Institutions as soon as is practicable, but in no event less than thirty (30) days in advance of such withdrawal, specifying the item or items to be withdrawn.

  • How to File an Appeal of a Prescription Drug Denial For denials of a prescription drug claim based on our determination that the service was not medically necessary or appropriate, or that the service was experimental or investigational, you may request an appeal without first submitting a request for reconsideration. You or your physician may file a written or verbal prescription drug appeal with our pharmacy benefits manager (PBM). The prescription drug appeal must be submitted to us within one hundred and eighty (180) calendar days of the initial determination letter. You will receive written notification of our determination within thirty (30) calendar days from the receipt of your appeal. How to File an Expedited Appeal Your appeal may require immediate action if a delay in treatment could seriously jeopardize your health or your ability to regain maximum function, or would cause you severe pain. To request an expedited appeal of a denial related to services that have not yet been rendered (a preauthorization review) or for on-going services (a concurrent review), you or your healthcare provider should call: • our Grievance and Appeals Unit; or • our pharmacy benefits manager for a prescription drug appeal. Please see Section 9 for contact information. You will be notified of our decision no later than seventy-two (72) hours after our receipt of the request. You may not request an expedited review of covered healthcare services already received.

  • Modification of Licensed Materials The Participating Institutions or the Authorized Users shall not modify or manipulate the Licensed Materials without the prior written permission of the Licensor.

  • Drawings Submitted During the Contract Term Where required to develop maintain and deliver diagrams or other technical schematics regarding the scope of work, Contractor shall do so on an ongoing basis at no additional charge, and must, as a condition of payment, update drawings and plans during the Contract term to reflect additions, alterations, and deletions. Such drawings and diagrams shall be delivered to the Authorized User’s representative.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Single User License A Single-User license is for a named individual who is identified as the only Authorized User. This user is not permitted to re-assign, transfer, or sublicense the software, except as described in Section 5, Transfer. This user may install and use the software on up to three computers, as long as the single-user Customer is the sole user of the software. If the computer on which this Software is loaded is attached to a network, this Software must not be accessible by any other user on such network. Single-user licenses may not be installed or used in a virtualized environment in order to or in a manner that circumvents the single user license type.

  • Service Documentation The “Service Documentation” includes;

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Additional mechanisms within the Programme 5.1 Pre-defined projects

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