- Home
- Skills
- Business & Operations
- Daily Site Report + Delay Notice Draft
Works with the AI Agents you already use
Daily Site Report + Delay Notice Draft
Turns foreman notes into a daily report (weather, manpower, work, delays, safety) and, when a delay or verbal change appears, drafts the contractual notice for PM review.
Free
Daily Site Report + Delay Notice Draft
Example session with this skill installed
Daily report for today, and draft the notice if we need one.
Project: Example Medical Office Building (fictional). Date: Oct 20, 2026. Clear, 64°F.
Crews: concrete 8, ironworkers 5, electricians 3, our laborers 4.
Work: poured level 2 slab, east half (110 cy per the foreman). Ironworkers set steel for stair 1.
Owner's rep (J. Sample) verbally told our super at 10:15 to move the lobby wall 2 ft north. No written direction yet.
City inspector at 14:00 for the level 2 deck — passed.
Near-miss: an unsecured plywood sheet blew off level 3 at 11:30, nobody hurt; area barricaded and remaining sheets tied down.
Contract: written notice of any change required within 7 days of the event.
Photos 31–38.
- Read your context and instructions
- Compiled the daily site report
DAILY REPORT HEADER
Project: Example Medical Office Building (fictional) | Job: Not provided | Report date: Oct 20, 2026 | Prepared by: Not provided
Note: You asked for "today's" report, but the system date is Oct 19, 2026, and your notes say Oct 20, 2026. I used Oct 20 as written. Please confirm the date, because it also sets the event dates and the notice timing below.
WEATHER
Clear, 64°F.
MANPOWER
Trade Subcontractor Headcount Hours
Concrete Not provided 8 Not provided
Ironworkers Not provided 5 Not provided
Electricians Not provided 3 Not provided
Laborers Own forces 4 Not provided
Total 20
Calculation: 8 + 5 + 3 = 16 subcontracted/other, plus 4 own laborers = 20. This assumes the crews do not overlap; confirm.
WORK PERFORMED
Completed: Poured level 2 slab, east half (110 cy per the foreman; reporting foreman not identified, confirm attribution).
Steel: Ironworkers set steel for stair 1. Status (complete vs. in progress) not stated; confirm.
In progress: Not provided.
DELAYS, INSPECTIONS AND DIRECTIONS
-
Oct 20, 2026, 10:15 | Verbal direction
Description: Owner's rep verbally directed the lobby wall be moved 2 ft north. No written direction yet.
Parties: J. Sample (Owner's rep) to our superintendent (name not provided).
Impact as stated: Not provided. -
Oct 20, 2026, 14:00 | Inspection
Description: City inspection, level 2 deck. Result: passed.
Parties: City inspector (name not provided).
Impact as stated: Not provided.
Verbal-direction follow-up: Obtain written confirmation from the Owner's rep. No request has been sent yet.
Notice timing (provisional calendar-day calculation):
Oct 20, 2026 + 7 calendar days = Oct 27, 2026.
If the event was actually Oct 19, the result would be Oct 26, 2026.
Counting basis: The event date is day zero, and weekends and holidays are included. The contract wording says "within 7 days of the event" without specifying calendar or business days. This calculation does not establish the contractual deadline. The PM and counsel must confirm the trigger, the counting rules, and the operative deadline.
SAFETY
Incidents: Not provided.
Near-misses: 11:30. An unsecured plywood sheet blew off level 3. Nobody hurt.
Corrective actions: Area barricaded and remaining sheets tied down.
Toolbox talks: Not provided.
OSHA recordkeeping is separate from this report.
PHOTOS
Photos 31–38. Captions not provided.
DRAFT NOTICE (FOR PM REVIEW)
DRAFT – FOR PM / CONTRACT REVIEW – NOT SENT
To: [Owner / Owner's designated notice recipient]
From: [Contractor]
Notice date: [to confirm]
Project: Example Medical Office Building
Re: Notice of Directed Change – Lobby Wall Relocation
On Oct 20, 2026, at approximately 10:15, the Owner's representative, J. Sample, verbally directed [Contractor]'s superintendent to move the lobby wall 2 ft north. [Contractor] has not received written direction for this change. Impact: [to be determined / confirm].
Contract notice requirement, as supplied: "written notice of any change required within 7 days of the event." Clause reference: [to confirm].
Please provide written direction and, where applicable, a change order concerning this event.
[Contractor] reserves its rights under the Contract concerning this event.
MISSING / TO CONFIRM
- Report date and event date: Oct 20 per your notes vs. Oct 19 system date.
- Header details: job number and report author.
- Superintendent's name, for the verbal direction.
- Manpower: subcontractor names, hours, and whether any crews overlap.
- Foreman behind the 110 cy figure.
- Stair 1 steel: complete or in progress.
- Pour time vs. the 14:00 deck inspection: did the inspection cover the east half before the pour? Confirm the sequence and the area inspected.
- Inspector's name and any inspection record number.
- Impact of the lobby wall direction on schedule, cost, and work already in place. The notes give none.
- Safety: incidents and toolbox talks were not reported.
- Captions for photos 31–38.
- Notice details: governing clause, recipient, sender, notice date, delivery method, and receipt requirements.
- Calendar vs. business days, and the operative deadline. The PM and counsel must confirm these before sending.
- Whether a written-confirmation request to J. Sample should go out separately and immediately.
Connects securely to your tools. The creator never sees your data.
About this skill
Turns field notes into a daily site report without adding facts or changing reported conditions. When a delay, disruption, or directed change is reported, it also prepares a draft notice for PM and contract review. It separates recorded facts, arithmetic, missing information, and items requiring professional confirmation.
Built and tested by AI Professions, where we test AI on real professional tasks. Before this skill was written, we locked a 5-criterion rubric and a fictional test input. Then Claude Opus 5.5, Claude Sonnet 5, Claude Fable 5.1 each ran it 3 times, and a model from another family (GPT-6 Astra) graded every run.
Test results (English, current version v1.2): Claude Opus 5.5: 4.67 of 5 · Claude Sonnet 5: 5.0 of 5 · Claude Fable 5.1: 4.33 of 5. Full transcripts and verdicts are public: prompt-benchmark on GitHub.
What you give it
- Project name, job number, report date, and report author.
- Weather wording and units exactly as recorded.
- Manpower headcounts by trade; subcontractor names and hours if tracked.
- Completed and in-progress work, with any reported percentages and the reporting foreman.
- Delays, inspections, RFIs, and verbal directions: event date/time, parties, details, results, and stated impact.
- Safety notes: incidents, near-misses, corrective actions, and toolbox talks, including attendance if given.
- Photo references and captions.
- For notices: event date, contractual notice wording, clause reference if supplied, period, recipient, and delivery requirements.
Ask once in a consolidated question about missing or conflicting information needed to complete the report. If instructed to proceed, use "Not provided" for missing fields and list unresolved items under "Missing / to confirm"; never guess. Do not treat an omitted item as "none," "no incidents," or "no impact."
Also available
- Spanish, French (France) and Brazilian Portuguese versions adapted to local practice, not translated: skill page · GitHub
- Claude Code plugin:
/plugin marketplace add aiprofessions/claude-skills
Important
The skill produces drafts. A licensed or responsible professional checks every output before use. Do not paste client, patient or personal data into tools your organization has not approved.
Free under CC BY 4.0. Credit: AI Professions (aiprofessions.ai).
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.
Requires manual verification by a PM. Does not determine legal entitlement or certify OSHA compliance. User must provide specific contract notice periods for arithmetic to function.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 25 days ago
- Free with an Agensi account
Permissions
No special permissions declared or detected