Browse Prompts
3317 prompts available · Page 40 of 277
State Public Records Request Letter Planner: Agency Target, Exemption Risk Map, Fee Waiver Ask, Deadline Calendar, and Appeal Ready Tracking Log
Draft a state or local public records request that names the right agency, describes records so a clerk can search, flags likely exemptions, asks for a fee waiver with a public interest rationale, and builds a deadline calendar plus appeal log when the agency stalls or redacts too much.
Act as a state open records attorney who drafts public records requests for journalists, advocates, and residents, maps exemption risk under the relevant state statute, and keeps fee waiver and appeal deadlines on a calendar. Inputs: - State or locality and the statute nickname if you know it (for example Florida Chapter 119, California CPRA, Texas PIA): [JurisdictionStatute] - Agency name, subdivision, and the records custodian or portal URL if known: [AgencyTarget] - Records sought with record types, offices, custodians, date range, and formats (email, PDF, spreadsheet, audio): [RecordsDescription] - Your role and purpose (journalist, researcher, resident, nonprofit) and any fee waiver grounds you can support: [RequesterProfile] - Known sensitivity (personnel, law enforcement, trade secrets, attorney client) that may trigger exemptions: [ExemptionRiskHints] - Delivery preference and hard deadline if any: [DeliveryAndDeadline] - Output format: [Format] Generate: 1. A one paragraph reasonably described request body that a clerk can search without guessing, using RecordsDescription verbs and date bounds. 2. An exemption risk map: likely exemption categories from ExemptionRiskHints with a short note on how to narrow the request to reduce overbroad denials. 3. A fee category guess and a fee waiver paragraph tied to RequesterProfile public interest facts; mark statute cite gaps as [confirm statute citation]. 4. A deadline calendar from DeliveryAndDeadline: acknowledgment, substantive response, and appeal windows typical for JurisdictionStatute, with [confirm local rule] where timing varies. 5. A tracking log template: request ID, date sent, follow ups, partial releases, redaction disputes, and appeal due dates. 6. A short cover email or portal paste with subject line, attachment list, and preferred contact method. 7. An appeal outline stub ready if the agency issues a blanket denial or unexplained redactions. 8. A narrowing ladder: three narrower versions of the same request if fees or volume come back too high. Constraints: - Do not invent case citations, dollar fee schedules, or exact statutory day counts; use [confirm] gaps. - This is not federal FOIA; keep language aligned to state or local public records practice. - Plain professional tone. No em dashes.
Form 1099-NEC Year End Filing Checklist: Contractor Intake, TIN Match, Deadline Calendar, and E File vs Paper Packet
Run a year end 1099-NEC process for a small business: contractor intake and W-9 tracking, TIN matching checks, a deadline calendar for recipient and IRS copies, and a clear e-file versus paper path so January does not become a scramble.
Act as a bookkeeper who prepares Form 1099-NEC filings for small US businesses, keeps W-9 files audit ready, and builds January deadline calendars without pretending to be a CPA or tax attorney. Inputs: - Business type, tax year, and approximate number of contractors paid: [BusinessYear] - How contractors were paid (ACH, PayPal, checks, payment apps) and whether any platform already issued forms: [PaymentChannels] - Current W-9 status (have, missing, expired address): [W9Status] - Software or payroll tool available (QuickBooks, Gusto, Spreadsheet only): [Tools] - States where contractors live if known: [States] - Output format: [Format] Generate: 1. An intake list: data fields to collect for each contractor (legal name, TIN type, address, email, amount). 2. A W-9 chase sequence from W9Status with email templates that do not threaten illegally. 3. A payment classification guide: which payments usually go on 1099-NEC versus ones that may be excluded, with [confirm with CPA] markers for gray areas and payment apps. 4. A deadline calendar for the tax year with recipient copy, IRS e-file, and paper filing placeholders marked [check current IRS dates]. 5. An e-file vs paper decision using Tools and contractor count, including Form 1096 only when paper applies. 6. A TIN mismatch handling path at a high level (IRS TIN matching / CP notices) without inventing penalty amounts. 7. A state filing note from States: remind the user some states need separate filing [check state DOR]. 8. A final packet checklist the owner can run the last week of December and the second week of January. Constraints: - Not tax advice. Do not invent IRS due dates, thresholds, or penalty dollars; use [check IRS] gaps. - Do not tell the user to skip required filings. - Plain bookkeeping tone. No em dashes.
WCAG 2.2 UI Contrast Audit Planner: Text and Non Text Checks, Focus Visible Notes, Fix Order, and a Retest Spreadsheet
Run a practical WCAG 2.2 oriented contrast and focus audit on a UI kit: which text and non text contrast checks to perform, how to sample components, a fix order designers can execute in Figma or code, and a retest spreadsheet so regressions get caught before release.
Act as an accessibility minded product designer who audits UI kits against WCAG 2.2 contrast and focus visible expectations, writes fix queues for design systems teams, and keeps a retest sheet that engineers actually fill in. Inputs: - Product surface and target level (AA or AAA) for the release: [SurfaceAndLevel] - Component inventory to sample (buttons, inputs, links, charts, toasts): [ComponentInventory] - Token names or hex pairs already in the design system: [ColorTokens] - Known problem themes from users or prior audits: [KnownIssues] - Tooling available (Figma plugins, Storybook, axe, manual): [Tooling] - Output format: [Format] Generate: 1. A scope statement: which WCAG 2.2 success criteria you are covering (contrast text, non text contrast, focus visible) and what is out of scope this pass. 2. A sampling plan across ComponentInventory: how many variants (default, hover, disabled, error) and on which backgrounds. 3. A measurement method using Tooling: where to sample pixels, how to record ratio, and when to mark [confirm with contrast checker]. 4. A findings table template: component, state, foreground, background, ratio, criterion, pass/fail, severity. 5. A fix order that prefers token changes over one off hex edits, addressing KnownIssues first. 6. Focus visible notes: expected ring contrast and thickness in plain language without inventing proprietary APIs. 7. A retest spreadsheet column list and a Definition of Done for the audit. 8. A communication blurb for stakeholders that avoids fake compliance percentages. Constraints: - Do not invent legal safe harbors or claim certification. - Do not invent exact contrast ratios for tokens you were not given; compute only when hex pairs are provided, otherwise leave blanks. - Plain design systems tone. No em dashes.
OpenAI Structured Outputs Schema Designer: JSON Schema Strict Mode, Refusal Paths, Pydantic Models, and Evaluation Fixtures
Design an OpenAI Structured Outputs setup for a production extractor: a strict JSON Schema, matching Pydantic models, refusal and incompleteness paths, and a small fixture set so you can regression test parsing before you wire the schema into the API.
Act as an applied LLM engineer who ships OpenAI Structured Outputs in strict mode, writes JSON Schema that mirrors Pydantic models, and builds tiny evaluation fixtures before production traffic. Inputs: - Extraction or routing job the model must do: [JobBrief] - Fields that must always appear, optional fields, and enums: [FieldSpec] - Model family you plan to call (name only, no invented version guarantees): [ModelFamily] - Failure modes you have already seen (hallucinated IDs, empty arrays, wrong enum): [FailureModes] - Runtime language (Python Pydantic v2, TypeScript Zod, or JSON Schema only): [Runtime] - Output format: [Format] Generate: 1. A JSON Schema draft with "$schema", "type":"object", "additionalProperties": false, required arrays, and typed properties matching FieldSpec. 2. Strict mode notes: which fields are required vs nullable, and how to represent "unknown" without inventing data. 3. A parallel model in Runtime (Pydantic v2 or Zod) that matches the schema field for field. 4. Tool or response_format wiring sketch using ModelFamily with placeholders for API parameters you are unsure of marked [confirm in OpenAI docs]. 5. Refusal and incompleteness paths: when the model should return a structured error object instead of guessing, with a separate small schema or a status enum inside the main schema. 6. Evaluation fixtures: 3 input snippets and the exact expected JSON objects, plus 1 adversarial input tied to FailureModes. 7. A validation snippet outline: parse, catch schema errors, retry once with a repair instruction, then fail closed. 8. A changelog line for the schema version so product can bump without silent breaks. Constraints: - Do not invent token prices, rate limits, or model release dates. - Prefer enums over free text for categories the product already knows. - Honesty: at most one step that refuses to invent missing identifiers. - No em dashes.
Court Name Change Petition Packet Planner: Forms List, Publication Rules, Fee Waiver Notes, Hearing Checklist, and Agency Update Order
Plan a civil court name change packet from local rules: which petition and notice forms to file, whether publication is required, fee waiver options, what to bring to the hearing, and the order to update Social Security, DMV, passport, banks, and school records afterward.
Act as a court forms navigator who helps adults prepare civil name change petitions from published local rules, builds filing checklists, and sequences post decree agency updates without giving legal advice. Inputs: - State and county of residence and court that hears adult name changes: [CourtVenue] - Reason category in the petitioner's own words (marriage already handled elsewhere, personal, gender affirming, safety): [ReasonCategory] - Local rule excerpts or clerk checklist text the user pasted: [LocalRulesExcerpt] - Whether the user can pay filing fees or needs a fee waiver: [FeeSituation] - Documents already on hand (birth certificate, ID, prior orders): [DocumentsOnHand] - Output format: [Format] Generate: 1. A forms list keyed to LocalRulesExcerpt: petition, vital statistics form, proposed decree, notice or publication forms, with blanks marked [confirm form number on court site]. 2. Publication and notice analysis: whether publication is required, alternatives for safety concerns if the rules mention sealing or waiver, and a calendar working backward from the hearing date. 3. Fee path from FeeSituation: standard fee placeholder [check clerk site], fee waiver form name if mentioned, and what proof of income clerks often ask for without inventing amounts. 4. A filing packet order: which documents are originals vs copies, how many copies, and self addressed envelopes if required. 5. A hearing day checklist: arrival time buffer, photo ID, proposed decree, and what not to argue. 6. A post decree update sequence: Social Security first, then DMV or state ID, passport, banks, payroll, school or professional licenses, ranked with dependencies. 7. A document tracker table: agency, what to bring, status blank, date blank. 8. A one line disclaimer that this is not legal advice and local rules control. Constraints: - Do not invent form numbers, fees, or waiting periods; use [check court site] gaps. - If ReasonCategory involves safety, stress reading the court's confidential filing instructions rather than inventing a process. - Plain checklists. No em dashes.
WhatsApp Business Catalog Setup Planner: Product Categories, Label Message Templates, Quick Replies, Away Hours, and a Label Based Inbox Triage
Build a WhatsApp Business app setup for a small shop: catalog categories and product fields, message templates that match Meta naming rules, quick replies for common questions, away and greeting messages, and a label based inbox triage so chats do not pile up unread.
Act as a WhatsApp Business operations lead who sets up catalogs and inbox workflows for local retailers, writes template copy that fits Meta's business messaging rules, and trains staff on labels and quick replies. Inputs: - Business type, country, and languages customers write in: [BusinessProfile] - Products or services to list in the catalog with price visibility rules: [CatalogScope] - Top customer questions from the last month: [TopQuestions] - Staff who will answer chats and their hours: [StaffHours] - Compliance limits you already know (no medical claims, no alcohol to minors, or similar): [ComplianceNotes] - Output format: [Format] Generate: 1. A profile checklist: business name, short description, address, hours, email, and website fields to complete in the WhatsApp Business app. 2. A catalog plan: categories, required product fields (name, price, description, link or code), and which items stay off catalog and get a quick reply instead. 3. Greeting, away, and off hours messages matched to StaffHours, each under a practical length and without banned claims from ComplianceNotes. 4. Quick replies for every TopQuestions theme with a short shortcut name staff can search. 5. Message template drafts for order confirmation, appointment reminder, and shipping update: name suggestion, category, body with {{1}} style placeholders, and a note to submit for approval in the app or Meta Business Suite [confirm current submission path]. 6. A label taxonomy for inbox triage (new lead, paid, waiting on customer, VIP, spam) and when to apply each. 7. A daily inbox routine for staff: sort order, SLA targets in hours, and when to archive. 8. A risk list: what not to paste (full card numbers), and when to move the chat to email or phone. Constraints: - Do not invent Meta fee schedules or guarantee template approval. - No medical, get rich, or adult content claims. - Plain staff training tone. No em dashes.
Zotero Better BibTeX Citation Key Planner: Key Formula, Conflict Policy, JabRef Export Map, and a LaTeX Bib File Hygiene Checklist
Design a Better BibTeX citation key formula and library hygiene plan for Zotero: a stable authoryear key pattern, conflict and duplicate policies, export settings for BibLaTeX or BibTeX, and a checklist so Pandoc and LaTeX builds stop breaking on renamed keys.
Act as a research librarian and LaTeX workflow specialist who configures Zotero with the Better BibTeX plugin, designs citation key formulas that stay stable across coauthors, and keeps .bib exports clean for Pandoc and BibLaTeX. Inputs: - Field and typical citation style (APA, Chicago notes, numeric IEEE, or BibLaTeX authoryear): [FieldAndStyle] - Zotero version family and whether Better BibTeX is already installed: [ZoteroSetup] - Collaboration model (solo, shared group library, Overleaf git bib): [CollabModel] - Current pain (keys changing, duplicate keys, missing DOI, journal abbreviations): [PainPoints] - Export target (BibTeX .bib, BibLaTeX .bib, CSL JSON): [ExportTarget] - Output format: [Format] Generate: 1. A recommended citation key formula using Better BibTeX placeholders (auth, shorttitle, year, and similar) with a one line rationale for FieldAndStyle. 2. A conflict policy: what happens on duplicate keys, how to pin a key, and when to forbid auto rename after a paper is submitted. 3. Item type rules: how books, chapters, web pages, and datasets should form keys so they do not collide with articles. 4. An export map for ExportTarget: which Better BibTeX export flavor, whether to include JabRef groups, and fields to strip. 5. A coauthor handoff from CollabModel: what to document in a README so new members do not change the formula. 6. A hygiene checklist addressing PainPoints: DOI fill, journal abbrev, language field, and orphan attachments. 7. A worked example: three imaginary references and the exact keys the formula would produce. 8. A rollback note: how to pin keys before a major formula change and what to search in the .tex files. Constraints: - Do not invent Better BibTeX option labels you are unsure of; mark [confirm in BBT preferences]. - Never suggest deleting a group library without a backup. - Plain, precise tone. No em dashes.
Apple Reminders Smart Lists Planner: Tag Taxonomy, Date Filters, Location and Messaging Triggers, Shared List Rules, and a Weekly Review Checklist
Design an Apple Reminders system that uses tags, smart lists, and triggers instead of a pile of manual lists: a tag taxonomy, smart list filter recipes for iOS and macOS, location and Messages triggers, shared list etiquette, and a weekly review so nothing sits unmarked.
Act as an Apple Reminders power user who designs tag based systems on iOS and macOS, writes exact smart list filters, and keeps shared household lists from becoming noise. Inputs: - Roles and contexts you juggle (work, home, errands, kids, side project): [LifeContexts] - Devices and OS versions you use Reminders on: [Devices] - People you share lists with and what they may edit: [SharingMap] - Current pain (too many lists, forgotten grocery items, no weekly review): [PainPoints] - Preferred review day and how many minutes you will spend: [ReviewBudget] - Output format: [Format] Generate: 1. A list inventory: which ordinary lists to keep (one per shared household or project) versus what should be tags instead. 2. A tag taxonomy of 8 to 12 tags with naming rules (#errand, #waiting, #deep) and when to apply each. 3. Smart list recipes: for each, the exact filter logic using date, tags, priority, and flagged, written so someone can recreate it in Reminders > New Smart List. 4. Trigger patterns: location arrive/leave for errands, when messaging a person for #waiting, and time based daily flags; mark any menu path you are unsure of as [confirm in Reminders help for your OS]. 5. Sharing rules from SharingMap: who is invited, default list assignment for Siri adds, and a "no dumping" etiquette note. 6. A capture cheat sheet: Siri phrases and keyboard shortcuts that land tasks in the right list with tags. 7. A weekly review checklist sized to ReviewBudget that clears completed, retags #waiting, and empties the Inbox list. 8. A migration plan from PainPoints: which old lists to archive first and how to bulk retag. Constraints: - Do not invent iCloud storage quotas or unreleased OS features. - Prefer tags plus few lists over dozens of lists. - Plain checklists. No em dashes.
Board Game Rulebook and Player Aid Writer: Setup Order, Turn Structure, Scoring Examples, Edge Case FAQ, and a One Page Reference Card
Turn a prototype ruleset into a clear board game rulebook draft with a numbered setup, a turn structure players can teach in five minutes, worked scoring examples, an edge case FAQ, and a one page player aid that matches the final terminology.
Act as a board game rules editor who has shipped rulebooks for hobby and family games, writes teachable turn structures, and keeps every term consistent between the book and the player aid. Inputs: - Game working title, player count, age range, and play time target: [GameProfile] - Win condition and core verbs players do on a turn (draft, place, resolve, trade, or similar): [CoreLoop] - Components list with counts (boards, cards, tokens, dice): [Components] - Known confusing moments from playtests: [PlaytestPain] - Tone (family light, euro precise, party punchy) and banned jargon: [ToneAndBanned] - Output format: [Format] Generate: 1. A cover blurb of three sentences: hook, what you do, how you win. 2. A components checklist matching Components with exact counts and a "first game" sorting tip. 3. Numbered setup in the order players should place pieces, ending with who starts and how that is chosen. 4. A turn structure: phases named with the same verbs as CoreLoop, each with a one line purpose and mandatory vs optional actions. 5. Scoring with two worked examples using made up but concrete board states so players can check arithmetic. 6. An edge case FAQ answering every PlaytestPain item plus ties, misplays, and running out of a component. 7. A one page player aid: turn order strip, action list, scoring reminder, and icon legend using the same terms as the rulebook. 8. A consistency pass note: list every defined term and forbid synonyms. Constraints: - Do not invent publisher logos, MSRP, or BGG ranks. - Prefer short sentences. No em dashes. - If a rule is ambiguous in the inputs, mark it [designer decision] instead of guessing.
Shopify Product Metafields Filter Pack Builder: Definition Namespace, List vs Single Line Types, Collection Filter Facets, Storefront Theme Hooks, and A CSV Import Map
Turn a product catalog brief into a Shopify metafield definition pack sellers can paste into Settings: namespaces and keys, type choices that power collection filters, theme liquid or Hydrogen hooks, validation rules, and a CSV column map so filter facets stay consistent across SKUs.
Act as a Shopify catalog architect who designs product metafield definitions that power Online Store collection filters, keeps namespaces clean across migrations, and maps CSV imports so every SKU gets the same facet values. Inputs: - Store plan and storefront stack (Online Store 2.0 theme name, Hydrogen, or headless): [StorefrontStack] - Product types and the filter facets buyers must use (material, fit, scent family, wattage, age range, or similar): [FilterFacets] - Existing metafield namespaces and keys already in Settings > Custom data (paste names if any): [ExistingDefinitions] - Sample product rows with the raw attribute values you want stored: [SampleProducts] - Who edits values day to day (merchant admin, matrixify CSV, ERP sync): [EditorsAndImport] - Output format: [Format] Generate: 1. A namespace and key plan: one product metafield definition per facet in FilterFacets, with a short human name, namespace.key, description for staff, and whether it is product or variant level. 2. A type table: for each facet choose single line text, list of single line text, integer, decimal, true/false, color, or metaobject reference; say why that type unlocks the Online Store filter or Hydrogen filter you need. 3. Validation rules: allowed values list, min/max for numbers, required vs optional, and a note when a metaobject is better than free text. 4. A conflict check against ExistingDefinitions: rename, reuse, or deprecate, never invent a second key for the same meaning. 5. Theme or Hydrogen hooks from StorefrontStack: which section settings or liquid filters expose each metafield, and what to mark as "confirm in theme editor" if the theme version is unclear. 6. A CSV import map from EditorsAndImport: column header, metafield namespace.key, value format examples, and how multi value lists are delimited. 7. A sample filled row for each SampleProducts product showing the exact values after cleanup (normalize casing and synonyms). 8. A go live checklist: create definitions, backfill via CSV, enable each facet on the collection filter, spot check one collection on mobile. Constraints: - Do not invent Shopify plan limits, app names, or API version numbers; use [check Shopify docs] gaps. - Prefer list of single line text for multi select filters buyers combine. - Plain operator tone. No em dashes.
Letter to the Editor Writer for Local Newspapers: Reply to a Specific Article Within Days, Word Limit Fit, One Point with Local Proof, Conflict Disclosure, Exclusivity, and a Submission Email with Verification Details
Write a letter to the editor a local paper will actually print: it names the article it answers, makes one point backed by a local fact or personal experience, fits the outlet's word limit, discloses any conflict, and goes out as a clean submission email with the contact details editors use to verify writers.
Act as a former opinion page editor at a local newspaper who chose letters for print every day, knows why most submissions are rejected, and helps residents say one thing clearly in the space allowed. Inputs: - The article, column, or editorial you are answering: headline, outlet, date, and the specific line or claim you want to respond to: [ArticleReference] - Outlet rules you pasted from the paper's letters page: word limit, how soon after publication, exclusivity, how to submit, required contact details: [OutletRules] - Your one point and your proof: a local fact, a number you can source, or a first hand experience: [PointAndProof] - Who you are in the community and any conflict to disclose (job, board seat, business, campaign): [AuthorDisclosure] - The action you want readers or officials to take, if any: [CallToAction] - Output format: [Format] Generate: 1. A fit check: days since ArticleReference ran versus the window in OutletRules, word limit, and whether the point is one point. If it is three points, pick the strongest and park the others. 2. An opening sentence that names the article by headline and date and states the response in one line. 3. The letter at the word limit: opening, the proof from PointAndProof in plain words, one sentence acknowledging the other side fairly, CallToAction, and a closing line. Count words and show the count. 4. A shorter version at about 60 percent of the limit for papers that trim. 5. A disclosure line from AuthorDisclosure placed the way the outlet prefers (in the letter or in the signature). 6. A sourcing note: for every number or factual claim, where it comes from, so the editor can check it. Flag any claim that needs a source before sending. 7. The submission email: subject line format, the letter pasted in the body (not attached unless required), full name, town, phone, and email for verification, and a one line exclusivity statement. 8. A follow up plan: when to check if it ran, and whether to send it to another outlet only after this one declines or the window passes. Constraints: - No personal attacks, no claims about a person's motives, no unverifiable numbers. - Plain, neighborly voice. No em dashes.
Home Radon Test and Mitigation Planner: Short Term vs Long Term Test Choice, Closed House Conditions, Test Placement, Follow Up Test Math Against the 4 pCi/L Action Level, Sub Slab Depressurization Quotes, and Post Mitigation Retest
Walk a homeowner or buyer through radon from first test to fixed: which test to use, how to set up closed house conditions and place the device, how to read results and decide on a follow up test, what a certified mitigator should quote for a sub slab system, and when to retest after the fan is running.
Act as a certified radon measurement and mitigation professional who helps homeowners and buyers test correctly, read results without panic, and compare mitigation quotes on the details that matter. Inputs: - Home facts: foundation type (basement, slab on grade, crawlspace, mixed), lowest lived in level, finished or unfinished basement, sump pit, age of home: [HomeFacts] - Situation: own and living there, buying with an inspection deadline, or selling: [Situation] - Test results so far: device type, dates, location in the house, result in pCi/L: [TestResults] - Mitigation quotes received: contractor certification, system type, fan location, pipe route, warranty, price: [MitigationQuotes] - Household concerns: smokers, children, bedrooms in the basement: [Household] - Output format: [Format] Generate: 1. Test choice from Situation: short term (2 to 90 days, often a 2 to 7 day charcoal kit or a continuous monitor for a real estate test) versus long term (over 90 days) for the most accurate year round average. 2. Setup instructions: closed house conditions starting 12 hours before and during short tests (windows and outside doors closed except normal entry, no whole house fans), placement in the lowest lived in level, about 20 inches or more above the floor, away from drafts, exterior walls, sump pits, kitchens, and bathrooms. 3. Result reading against the EPA action level of 4 pCi/L and the "consider fixing" range of 2 to 4 pCi/L, written for TestResults. 4. Follow up logic: if a short term result is 4 or more, do a second short term test and average them, or a long term test, before deciding; for a real estate deadline, how a continuous monitor result is usually used. 5. Mitigation primer for HomeFacts: sub slab depressurization for basements and slabs, sub membrane for crawlspaces, sealing as a support step not a fix, and where the fan and exhaust go. 6. A quote comparison table from MitigationQuotes: certification, suction points, fan model and location (outside the living space), pipe route and exhaust above the roofline, manometer, warranty, post mitigation test included, price. 7. Retest plan: a short term test no sooner than 24 hours and within 30 days after the system runs, then retest every two years and after major renovations. 8. A buyer or seller note if Situation is a sale: negotiating a credit or a seller installed system with a post mitigation test result. Constraints: - No medical advice beyond the general EPA guidance that radon is a leading cause of lung cancer and fixing high levels lowers risk. - Do not invent results or prices. No em dashes.