Requested Effective Date Clause Samples
The Requested Effective Date clause establishes the specific date on which the terms of an agreement or contract are intended to become operative. In practice, this clause identifies when the rights and obligations of the parties begin, which may differ from the date the contract is signed. For example, parties may sign a contract in advance but agree that it will only take effect on a future date to align with business needs or regulatory requirements. This clause ensures clarity and mutual understanding about when contractual commitments start, preventing disputes over timing and helping coordinate related activities.
Requested Effective Date. PG&E requests that the Commission issue a resolution approving this advice filing as soon as possible. Justification for this date is provided in Confidential Appendix D.
Requested Effective Date. PG&E requests that the Commission issue a resolution approving this advice filing no later than December 15, 2011.
Requested Effective Date. PG&E requests that this supplemental filing becomes effective concurrent with Advice Letter 3735-E.
Requested Effective Date. PG&E requests that this advice filing be approved on or before November 10, 2011. PG&E submits this request as a Tier 3 advice letter.
Requested Effective Date. Date you are requesting to begin services. Please note, dates requested in excess of the date MC-19 is submitted must include written request with with supporting narrative. 4. Provider Name and Address: This is the address DHHS will use for correspondence. Enter the full name of the provider. When enrolling as an individual/solo practice or group member, enter the individual provider’s name AND title. When enrolling as a group practice, enter the group name. Enter the physical ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇, ▇▇▇▇▇, zip code + 4, your telephone and fax number, and an e-mail address to contact you. Also provide a contact name for the group, their title, phone and fax numbers. Note: A post office box without a physical location address will not be accepted. Each location must enroll separately. Each group member must enroll separately.
Requested Effective Date. (...continued) concerns addressed in Notice 2001-82 do not apply to BELD. However, because ▇▇▇▇’▇ interconnection arrangements are tax-exempt by operation of other Internal Revenue Code provisions (26 U.S.C. §§ 103, 115, 141), BELD is able to make the other representations contained in Article 5.17 with respect to the tax exempt status of its interconnection arrangements under this LGIA.
Requested Effective Date. The ISO and BELD respectfully request that the Commission accept the Interconnection Agreement, as submitted or as modified by the Commission, with an effective date of December 1, 2008.
Requested Effective Date. The Filing Parties respectfully request that the Commission accept the Interconnection Agreement, as submitted, to become effective March 26, 2024, to coincide with the date that the Filing Parties and Interconnection Customer executed the Interconnection Agreement. A March 26, 2024 effective date is appropriate as the Interconnection Agreement is being filed within thirty days of execution pursuant to 18 C.F.R. § 35.3(a)(2).
Requested Effective Date. Optional NOTE: The system will be updated on the day it receives the request if left blank. If the date is in the future, Unisys will update the file on that day.
Requested Effective Date. The Provider certifies that all services rendered on or