Skip to content
THE CARIBBEAN & LATIN AMERICA ADRIAN DUNKLEY ↗

Guyana

AI use cases, sectors, and small business playbook for Guyana. Proposed workflows for local review.

Capital
Georgetown
Languages
English, Guyanese Creole
Region
Caribbean

Practical AI guidance for Guyana

These examples focus on local-content records, agriculture, mining-community engagement, forest reporting and services for interior communities. They avoid forecasts and investment promises based on the oil economy.

Before using these prompts

These are draft-work examples, not evidence of measured savings or better outcomes. Start with a small test and record preparation time, correction time and errors against your usual process.

Use public, synthetic or properly de-identified material in a general-purpose AI tool. Do not paste client files, patient records, account details, employee files, children’s information or confidential operating data. De-identification alone does not authorise use: follow your organisation’s approved data policy and tool settings.

Ask for a source and date for every legal, financial, technical or programme claim. If the source is missing, leave the answer unresolved. A qualified local reviewer must approve regulated work. Do not let a model decide treatment, credit, insurance, employment, benefits or legal rights, or issue emergency instructions or equipment operating changes.

1. Local-content evidence checklist

For: Supplier and compliance teams

Using current official Local Content Secretariat requirements [dated sources], build
an evidence checklist for [registration/reporting task]. Use fictional business data.
For each requirement, show the source, records needed, responsible reviewer and gaps.
Do not infer Guyanese ownership or eligibility, invent procurement figures, certify
compliance or prepare a report for automatic submission.

Review before use: The official Local Content Portal provides requirements and registration routes. An authorised compliance reviewer must confirm the requirements for the specific business and task.

2. Oil-revenue scenario documentation

For: Public-finance researchers

From these published fiscal tables and Natural Resource Fund reports [sources/dates],
explain the reported figures, periods and units. Separately model fictional scenarios
using only the assumptions supplied here. Label each scenario as illustrative.
Do not call an allocation optimal, promise returns or invent future government revenue.

Review before use: Recalculate all tables and have a public-finance specialist review assumptions. This is research preparation, not investment or budget authority.

3. Oil-spill exercise documentation

For: Environmental and emergency-planning teams

Turn this approved exercise plan into an agenda, observer checklist and document index.
Use only the authority-approved roles and contact details supplied here.
Flag missing approvals and outdated references. Do not create a response plan,
model a spill trajectory, direct deployment or prescribe wildlife-handling procedures.

Review before use: Use this only for preparation or a retrospective exercise review. Live incidents require the approved response plan and responsible authorities; do not rely on AI instructions.

4. Rice and sugar farm records

For: Farm managers and agricultural advisers

Organise these de-identified records from [Demerara/Essequibo/Berbice] into a seasonal
summary: field area, varieties, recorded inputs, labour, water observations and yield.
Keep units explicit and flag missing data. Draft questions for an agricultural adviser.
Do not diagnose disease, choose pesticides, prescribe application rates or invent
export certifications or government support programmes.

Review before use: An agricultural professional interprets field conditions. Check any later input choice against local approvals and product labels; do not use a language model as a spraying or irrigation controller.

5. Mining-community consultation preparation

For: Community representatives and programme teams

Draft a consultation agenda from community-approved priorities for [location].
Possible topics: livelihoods, environmental concerns, access to education and public services.
Record differing views and questions requiring technical advice. Use no identifying
information about children or health histories. Do not assume consent or design
mercury handling, mining safety or clinical procedures.

Review before use: Community representatives must review wording and participation arrangements. Specialists assess environmental and health issues; an agenda is not an intervention plan.

6. Forest and carbon-project document comparison

For: Forest researchers and community representatives

Compare these published forest or carbon-project documents [sources and dates].
Separate measured observations, model estimates, contractual claims and unknowns.
List questions about land rights, consultation, verification and benefit-sharing.
Do not invent forest-cover figures, value carbon credits, certify credits or determine
community entitlements. Do not substitute a document summary for community consent.

Review before use: Qualified technical and legal reviewers must assess project evidence and agreements. Keep community decisions and disputed claims visible.

7. Household financial-literacy materials

For: Educators and workplace programme organisers

Create a fictional GYD household-budget exercise with income, recurring expenses,
savings goals and irregular costs supplied here. Show calculations and questions
for a regulated financial adviser. Do not recommend particular investments, banks,
offshore arrangements, tax strategies or personalised asset allocations.

Review before use: Check arithmetic and explain that the figures are fictional. Do not request participants’ balances or account identifiers.

8. Interior service-access and tourism information

For: Service designers, lodges and local guides

Draft a low-bandwidth information sheet for [service or visitor itinerary] using
confirmed details supplied by the provider. Include operating hours, transport,
accessibility, costs, language needs and what must be checked before travel.
Use Kaieteur or Rupununi references only where the itinerary actually includes them.
Do not invent connectivity, medical evacuation arrangements, permits or availability.

Review before use: The provider must confirm service and transport details. Health records, land decisions and benefits eligibility require separate authorised workflows.

Sources and verification

Guyana Local Content Portal provides official requirements, registration and renewal information. Checked 11 November 2026. This guide does not state current oil reserves, GDP growth, forest cover or investment returns.

Check the result before using it

  • Verify names, dates, prices, availability and permissions with the responsible organisation.
  • Recalculate figures independently. Keep assumptions separate from observations.
  • Check local language and cultural references with someone who knows the audience. Do not imitate a dialect for effect.
  • Keep a record of the source material, model draft, corrections and final reviewer.
  • Measure whether the draft is useful; do not promise revenue gains, compliance or time savings without evidence.

Created by Adrian Dunkley | MaestrosAI | maestroailabs.com | ceo@maestrosai.com
Educational resource. Editorial safety review: 11 November 2026.

KEEP LEARNING

PLAYBOOK UPDATES.

Regional guidance, practical skills and project news.

By subscribing you request AI Playbook emails. Your email and optional country are sent to the project through Netlify Forms. For questions or to request removal, contact the project.

Cite this page

Dunkley, Adrian. “Guyana.” LAC AI Playbook. https://aiplaybooklac.netlify.app/countries/guyana/. Include your access date when citing this changing resource.

Geographic coverage: Guyana. This describes the subject of the guidance, not the author's location or a service address.

Map reference: 5.124317, -58.942643 (latitude, longitude). This approximate cartographic label point may fall offshore or between islands; it is not a surveyed GPS fix, capital or address. Source: Natural Earth Admin-0, v5.1.1, public domain. It does not determine legal boundaries or sovereignty.

Credit Adrian Dunkley when quoting or adapting the playbook. Cite the original research for its findings. Third-party text, photographs and other materials retain their own rights; citation alone does not grant permission to reproduce them.