Prompts
Prompts de IA jurídica para Energy & Natural Resources
9 prompts que você pode colar direto no HAQQ ou em qualquer outro assistente. Cada um está escrito por inteiro. Abra, copie e altere as partes entre colchetes.
Power Purchase Agreement Clause Review for EgyptClause / ScheduleExpertReview / Redline
You are counsel to a power project developer reviewing the change-in-law, currency and force majeure provisions of a draft power purchase agreement with an Egyptian state-owned offtaker, and reporting to the board in formal terms. Return a clause-by-clause review that ends in proposed replacement wording for the clauses you flag. Where the offtaker's draft, the lenders' requirements and the construction contract pull in different directions, show the conflict and how each proposed clause resolves it. Facts: the developer is [Developer Name], the offtaker is [Offtaker Name], the project is [Project Description], the tariff and its currency are [Tariff and Currency], the clauses under review are [Clause References], the lenders require [Lender Requirements], and the EPC contractor's relief for delay is [EPC Relief Terms]. Deliverables: 1. For each clause under review, the text summarised in one sentence and its effect on the developer. 2. A rating of each clause as acceptable, negotiable or unacceptable, with the reason. 3. Proposed replacement wording for each clause rated negotiable or unacceptable, drafted so that it can be inserted into the agreement. 4. A table showing where the offtaker's draft, the lenders' requirements and the EPC terms conflict, and which clause resolves each conflict. 5. The risk the board retains after the proposed changes, stated by cause: currency devaluation, change in law, force majeure and offtaker payment default. 6. Questions for Egyptian counsel on state-entity payment obligations, convertibility of currency and enforcement, and the points on which the board's approval is needed. Mandatory rules: never invent a statute, article number, case name or citation; cite the named source for every rule, rate or deadline, or mark it unverified and flag it for local counsel in Egypt. Do not assume that a stabilisation, indemnity or currency clause binds a state-owned party as written; flag the point. Quote the draft's wording only from the text supplied. Do not state that any clause will be enforced.
Take-or-Pay Clause Review ReportReportStandardReview / Redline
You are reviewing the take-or-pay clause in an energy supply contract on behalf of [Our Party] and writing an analytical report that will be shared with the counterparty. The report should show where the clause is clear, where it is open to dispute and what each side would need to prove. Facts: the clause says [Clause Text], the contract is governed by the law of [Jurisdiction], and the volumes at issue are [Contract Volumes and Shortfall]. Deliverables: 1. A plain reading of the clause: who pays, for what, when and on what calculation. 2. The ambiguities and gaps in the clause, each with the two readings and which side each favours. 3. The effect of force majeure, make-up rights and carry-forward on the payment obligation. 4. A proposed clarification for each ambiguity, written as neutral replacement wording. Mandatory rules: never invent a statute, article number, case name or citation; cite the clause for every reading and the named source for any rule of the governing law, or mark it unverified and flag it for local counsel. Do not reveal our client's commercial position or fallback. Do not conclude that the payment is or is not due unless the facts and the clause make that certain.
Brazilian Energy Project Licensing Explainer MemoMemoAdvancedExplain / Advise
You are a lawyer in Brazil writing a concise memo that explains to a client, who is not a lawyer, how a proposed energy project will be authorised and what could delay it. Describe the Brazilian federal structure in general terms, including the roles of the federal energy regulator, the environmental licensing authorities at federal and state level, and the grid operator, and say where state or municipal rules add steps. Facts: the client is [Client Name] and the project is a [Project Type] of about [Project Capacity] in [Project Location]; the owner of the land is [Land Status]; the connection to the grid is planned through [Grid Connection]; the offtake arrangement is [Offtake Arrangement]; the funding source is [Funding Source]; and the target date for operation is [Target Operation Date]. Deliverables: 1. A short summary of the path from site control to operation, in the order the steps usually occur. 2. A table of each permit or approval, the authority that grants it, what triggers it and what typically delays it. 3. An explanation of how environmental licensing, land rights and indigenous or community consultation can change the timeline. 4. A list of the contract and financing steps that depend on a permit being in place. 5. The three decisions the client should take in the next month. Mandatory rules: never invent a statute, article number, case name, regulator resolution or citation, and cite the named source for every rule, time limit or fee you mention or mark it unverified and flag it for Brazilian counsel. Do not promise a timetable or the grant of any licence. Do not describe the rules of one state as the rule for all of Brazil. Explain each technical term the first time it is used, and keep the memo to two pages.
Landowner Letter on an Energy Project in TurkeyLetter / EmailStarterExplain / Advise
You are writing a plain-language letter from an energy developer to the owners of land in Turkey that a planned power project may need, explaining what the process means for them in words they can follow without a lawyer. Facts: the developer is [Developer], the project is [Project type and location], the land concerned is [Parcels and owners], and the landowner can contact [Contact name and details]. Deliverables: 1. Why the developer is writing and what the project is, in three sentences. 2. The ways the land might be used, such as a lease, an easement right or a purchase, and how each differs for the owner. 3. What the owner is free to decide, what the owner can ask for and what happens if no agreement is reached. 4. The owner's right to take independent advice and the next steps with dates. Mandatory rules: never invent a statute, article number, case name or citation, and cite the named source for every rule or deadline you state or mark it unverified and flag it for local counsel. Do not promise a price, a permit or a timetable that the facts do not give. Do not pressure the owner to sign and do not suggest that expropriation is certain.
Board Report on a Bahrain Energy Project Contract SetReportEnterpriseSummarize / Extract
You are summarizing the legal position on an energy project in Bahrain for the board of the sponsor company, drawing on a set of linked contracts, and writing an analytical report that directors without legal training can use to decide whether to approve final investment. Facts: the sponsor is [Sponsor Name] and the project is [Project Description] with a capacity of [Project Capacity]; the contracts supplied are [Contract List] and their text is pasted below [Contract Texts]; the offtaker is [Offtaker Name] and the lenders are [Lender Names]; the project company is [Project Company Name] and the construction contractor is [Contractor Name]; the board decision needed is [Board Decision]; the board's risk appetite is [Risk Appetite]; the planned financial close is [Financial Close Date]. Deliverables: 1. A one-page executive summary with a recommendation to proceed, proceed with conditions or pause, and the three reasons that matter most. 2. A map of how the contracts connect, showing which obligations of one contract depend on another. 3. A table of key commercial terms across the offtake, construction, supply and financing contracts, such as tariff, term, availability, termination payments and step-in rights. 4. The allocation of the main risks among sponsor, project company, offtaker, contractor and lenders, with the gaps where nobody clearly bears a risk. 5. A list of conditions precedent to financial close and which ones are outside the sponsor's control. 6. The regulatory and licensing position, including consents still outstanding and the foreign ownership or local content points to confirm. 7. The sponsor's own exposure through guarantees, equity commitments and cross-defaults, in figures where the contracts allow. 8. An assessment of dispute resolution across the contract set and any mismatch in forums or governing laws. 9. The decisions the board must take and the information it should demand before voting. Mandatory rules: never invent a statute, article number, regulator name, tariff or citation; cite the named source for every rule, or mark it unverified and flag it for local counsel in Bahrain. Report only what the pasted contracts say and write not provided where a contract is missing. Where terms in two contracts conflict, set out both and say which one the board should treat as controlling and why. Do not assess technical or financial viability beyond what the contracts state. Do not tell the board to approve; give a reasoned recommendation and the assumptions behind it. This report is not legal advice on the sponsor's specific situation.
Public Compliance Table for a Solar Project in EgyptTable / TimelineEnterpriseCompliance / Due Diligence
You are preparing a public compliance table for a solar power project in Egypt, to be published for communities, landowners, investors and officials who are not lawyers. The text must be concise, accurate and safe to publish, and it must not overstate what the project has achieved. Facts: the developer is [Developer Name] and the project is [Project Name] in [Project Location] with a capacity of [Project Capacity]; the land is held through [Land Arrangement]; the grid connection and power sale are with [Grid and Offtake Arrangement]; the consents and reports the developer says it holds are [Consents Held]; the local-benefit and employment commitments are [Community Commitments]; the status of each obligation, as the developer reports it, is [Reported Status]. Deliverables: 1. A table with one row per obligation, showing the obligation in plain words, who owes it, who checks it and its status as reported. 2. A section on land, permits and environmental and social assessment duties, with the authority that grants each consent. 3. A section on grid connection, power sales and any foreign currency or payment obligations that affect the project. 4. A section on worker safety, local hiring and local content commitments. 5. A status label for each row: complete, in progress, overdue or not evidenced, with the proof needed to move it to complete. 6. A short notice for readers explaining how to raise a concern and which body to approach. 7. An internal list, kept apart from the public table, of rows where the developer's status claim cannot be checked and must be confirmed before publication. Mandatory rules: never invent a statute, article number, regulator name, licence number or citation; cite the named source for every obligation, or mark it unverified and flag it for local counsel in Egypt. Label a status as complete only when the facts supplied show evidence for it, never on the developer's word alone. Keep confidential commercial terms such as tariff and financing out of the public table. Do not promise benefits or timelines the facts do not support. The public table is information only and is not legal advice to any reader.
Board Playbook for a Municipal Power Purchase NegotiationPlaybookExpertNegotiate / Counter
You are acting for a private power producer in South Africa that is negotiating a long-term supply agreement with a municipality as buyer, and you are writing a persuasive negotiation playbook for the producer's board. The playbook must help the board see why the recommended positions are worth holding and what to trade away. Facts: the producer is [Producer Name] and the project is [Project Description]; the municipality is [Municipality Name]; the proposed term is [Contract Term] and the tariff structure is [Tariff Structure]; the municipality's credit position and payment record are [Municipal Credit Position]; the grid access arrangement is [Grid Access Arrangement]; the producer's walk-away conditions are [Walk-Away Conditions]; the lenders' requirements are [Lender Requirements]. Deliverables: 1. A one-page case for the board stating the deal it should aim for and the reasons that make it persuasive. 2. The ten terms that matter most, each with an opening position, a fallback and a walk-away point. 3. The municipality's likely interests and constraints, including budget approval processes, public procurement and finance rules and its dependence on the national utility. 4. Payment security options for a municipal buyer, such as escrow, guarantees and step-in rights, with the objection each is likely to meet and a reply. 5. A trading table showing what the producer can concede cheaply and what it must not. 6. A sequence for the talks, naming who should speak at each stage and which decisions need board approval. 7. The legal risks that could undo the contract after signing, such as an unlawful procurement step or missing approval, and how to test for them early. Mandatory rules: never invent a statute, regulation, regulator name, tariff or citation; cite the named source for every rule on municipal finance, procurement or electricity trading, or mark it unverified and flag it for local counsel in South Africa. Argue from the producer's interests, but state plainly where the municipality's position is stronger. Do not suggest any step that would breach procurement or competition rules. Do not promise that a particular term will be accepted. If the facts do not show the municipality's authority to contract for this term, make confirming it the first action. This playbook is not legal advice on the producer's specific situation.
Internal Policy for Energy Regulator Information RequestsPolicyAdvancedOperations
You are drafting an internal policy for the legal department of a retail electricity and gas supplier in Spain that sets out how the company handles information requests, inspections and sanction proceedings from the energy regulator. The policy is written for the in-house legal team and must be formal enough to be approved by the general counsel. Facts: the company is [Company Name], supplying [Customer Segments] with [Energy Products]; the regulators and bodies that contact it are [Regulators and Bodies]; the team that receives requests today is [Receiving Team]; the escalation owner is [Escalation Owner]; the record system in use is [Record System]; recent problems with the process are [Known Problems]. Deliverables: 1. A policy statement of purpose and scope in no more than one page. 2. A table of roles stating who receives, who triages, who approves and who signs each type of response. 3. A triage guide separating routine data requests, formal information orders, on-site inspections and notice of sanction proceedings, with a response clock for each marked as to be confirmed against the source. 4. Rules on privilege, confidential commercial information and personal data when producing documents to the regulator. 5. A procedure for dawn visits or unannounced inspections, including who accompanies officials and what is logged. 6. Record keeping and litigation hold rules once a request or proceeding opens. 7. Escalation triggers to the general counsel and the board. Mandatory rules: never invent a statute, regulation, regulator name, deadline or citation; cite the named source for every legal duty and time limit the policy relies on, or mark it unverified and flag it for local counsel in Spain. The policy must not instruct staff to withhold, alter or delay documents, and must say so. Keep national and regional regulator roles separate and ask which applies where the facts do not say. Mark every deadline as to be confirmed rather than stating a number from memory. This policy is a draft for approval by the company's counsel and is not legal advice on any specific matter.
Board FAQ on Permitting a Spanish Renewable ProjectQ&A / ExplainerExpertSummarize / Extract
Summarise the permitting and grid position of a renewable energy project in Spain for the board of [Company Name], as a concise FAQ in which each answer is two or three sentences and ends with what the board must decide or watch. The project involves national, regional and local authorities, so show how their roles fit together. Facts: the project is [Project Name and Capacity] using [Technology]; it is located in [Autonomous Community]; the current permit status is [Permit Status]; the electricity will be sold under [Offtake Arrangement]; the decision in front of the board is [Board Decision]. Deliverables: 1. Which authorities decide what: grid access and connection, the energy authorisations, environmental review and planning or local licences, and the order in which they come. 2. What the permits are and what stage the project has reached, with the milestones and expiry points that could make a permit lapse. 3. What happens if two authorities disagree or one is late, including silent refusal or silent approval where the law provides for it. 4. What can be challenged by third parties, by what route, and the effect of a challenge on the construction timetable. 5. How the offtake arrangement depends on the permits, and what the company is exposed to if a permit slips. 6. A short list of open questions the board should ask management before taking [Board Decision]. Mandatory rules: never invent a statute, article number, case name or citation; cite the named source for every rule, rate or deadline or mark it unverified and flag it for local counsel. Treat every permit deadline as unverified until a named source is given. Do not predict that a permit will be granted. Separate what is general to Spain from what depends on [Autonomous Community]. This FAQ informs the board's discussion and is not advice on the company's specific situation.