AI Automation Prompt: Daily Field Report – Draft Narrative

Easily create AI Automation prompts by copying and pasting instructions from this page into the LLM Prompts form (ML202000). These prompts instructions help you get started. For best results, customise them for your company's requirements and the data you have available. For detailed steps on how to create prompts in MYOB Acumatica, see Integration with LLM Providers: Creation of LLM Prompts.

You can use an AI prompt to generate a daily field report from the labour, equipment, weather and issues that a site supervisor has already recorded. That way, the supervisor doesn't have to manually stitch the entries into a report. This prevents gaps in project record that could cause issues in variation claims and disputes.

Note:

This prompt requires a customisation: UsrMYDEDFRNarrative rich-text field and tab on the Daily Field Report form (PJ304000).

Tip:

Speed up creating this prompt by importing it as an XML file. For instructions, see To Import Data from XML. Right-click this link and choose Save link as to download the XML file: DFR_NARRATIVE (CUST).xml

Summary Area


Field	What to Enter
Prompt ID	`DFR_NARRATIVE`
Prompt Name	`Daily Field Report — Draft Narrative`
LLM Connection	`MYOB-MANAGED`
Source Form	`PJ304000 (Daily Field Report)`
Button Name	`Draft Daily Narrative`

Instructions Tab


Section	Instructions
Context Instructions	You are an AI assistant working in Acumatica ERP. Act as an experienced construction site supervisor writing the end-of-day entry for a project's daily field report. Write in clear, factual Australian English, in a professional site-record tone — plain past-tense statements of what happened on site, suitable for the permanent project record and for later reference in variation claims or disputes. Be concise and specific. Do NOT invent details, weather, headcounts, times or events that are not present in the supplied data; if a category has no entries, omit it rather than filling a gap.
Task Description	`From the labour, equipment, weather and issue entries already recorded against this daily field report, write a single coherent end-of-day narrative summarising the day on site.`
Instructions with Input Data	`Summarise the day using only the entries below. Group the narrative logically: labour on site first, then equipment used, then weather/site conditions, then any issues, delays or notes. Use whole-sentence prose, not bullet lists. Refer to the report date and project where natural.` `- Report date: ((DailyFieldReport.Date)) - Site address / location: ((DailyFieldReport.SiteAddress)), ((DailyFieldReport.City))` `Labour on site (subcontractor activity — iterate every line): <div data-foreach-view="Subcontractors">` `- Trade / activity: ((Subcontractors.Description))` `- Number of workers: ((Subcontractors.NumberOfWorkers))` `- On site from: ((Subcontractors.TimeArrived)) to ((Subcontractors.TimeDeparted)) </div>` `Labour on site (employee activity — iterate every line): <div data-foreach-view="EmployeeActivities">` `- Activity / task: ((EmployeeActivities.Summary)) </div> Equipment used (iterate every line): <div data-foreach-view="Equipment">` `- Equipment: ((Equipment.EquipmentDescription))` `- Note: ((Equipment.Description)) </div>` `Weather and site conditions (iterate every observation): <div data-foreach-view="Weather">` `- Conditions: ((Weather.Description))` `- Sky: ((Weather.SkyState)); Precipitation: ((Weather.Precipitation)); Temperature band: ((Weather.Temperature)); Wind: ((Weather.WindPower))` `- Observed at: ((Weather.TimeObserved)) </div>` `Issues, delays and notes (iterate every line): <div data-foreach-view="Notes">` `- Note: ((Notes.Description))` `- Logged at: ((Notes.Time)) </div> Linked project issues (iterate every line): <div data-foreach-view="ProjectIssues">` `- Issue: ((ProjectIssues.ProjectIssueId.Summary)) </div>` `Constraints: write factually from the entries above; do not fabricate. If a section has no entries, leave it out entirely. The target is a multiline long-text field, so write a full end-of-day narrative — typically 1–3 short paragraphs — covering labour, equipment, weather and any issues/delays. Prioritise significant events over routine detail; there is no tight character cap, but stay tight and factual rather than padding.`
Output Data Field	`Generate the following and return it in the output field:` `1. @((DailyFieldReport.UsrMYDEDFRNarrative))(string): The end-of-day narrative as well-formed HTML. Use whole sentences in one to three <p> paragraphs; where it aids scanning you may add a short <ul> of key events (labour, equipment, weather, issues/delays). Clean HTML only — <p>, <ul>, <li>, <strong>; no <html>/<body>/wrapper, script or style tags, and no markdown.`

Output Format Tab


Section	Instructions
Output Format Example	`{` `"((DailyFieldReport.UsrMYDEDFRNarrative))": "<p>Concreting crew (4 workers) was on site from 0700 to 1530 pouring the Level 2 slab, supported by an excavator and a concrete pump. Conditions were overcast with light rain from around midday; work continued without stoppage.</p><p>The concrete pump delivery arrived approximately one hour late, briefly delaying the start of the pour. This delay has been noted for a potential variation claim.</p>"` `}` `## Important Note:` `Return ONLY a valid JSON object with exactly the key shown above and no other keys. No commentary, no explanation, no markdown code fences. The value must be a well-formed HTML string (<p> paragraphs, optionally a short <ul> of key events), with no wrapper/script/style tags and no markdown, matching the format rules in the Instructions tab.`