Write Customer-Friendly Invoice Line Descriptions
Use this when your invoice line items are vague and you need descriptions the customer can approve without emailing back with questions.
Prompts for your job
Use this when your invoice line items are vague and you need descriptions the customer can approve without emailing back with questions.
Need consistent daily records of site activity.
Need to create a plain-language guide that helps stakeholders understand how to read and filter a performance dashboard.
Need clear descriptions, owners, and rules for tables or fields in a catalog.
Have raw tabular, text or image data and need cleaning, splitting and transformation code you can run yourself.
Need to create tests for nulls, duplicates, or range violations in a dataset.
Must specify how long each data type is kept, where it lives, and how it is purged or archived.
Need help creating a calculated measure, column, or table expression.
Need to write handoff notes so another team can edit or present your slide deck.
Need to inform a customer about a fulfillment delay and apologize.
Need to remind a prospect about a booked demo and want to cut no-shows.
Need to spell out spacing, sizing, and interaction behavior next to a mockup for developers.
Want to generate an AI image or need a precise written description to guide your own or another illustrator's artwork.
Need to brief models or actors on tone and mood before a shoot.
Need a Docker setup for a local or production service.
Have analysed your ecological results and need to draft a Discussion section that interprets findings, compares them with literature, and sets out conservation implications.
Are pitching a gig, confirming details, or following up with a promoter.
Need to turn your architecture decisions and diagrams into clear design notes for the team.
Want a simple card with emergency numbers and meeting steps for your tour group.
Need a clear, step-by-step emergency escalation and contact procedure for maintenance staff.
Need to report on compliance with environmental regulations and want to ensure every required element is covered and every gap is visible.
Have a photo or description of a problem and need help writing a clear symptom report for a technician.
Need to document or generate the rules that convert source field values into ERP-ready values.
Have an error condition and need calm, helpful copy that tells the user what to do.