Write Buildertrend daily logs from site notes with AI

1. Select the job, open the Project Management dropdown and choose Daily Logs.
2. Click + Daily Log, then fill in Date, Title, Tags and the Notes field with work completed, site conditions and issues.
3. Check the weather that Buildertrend pulls in and add Weather Notes if rain or heat changed the day.
4. Under Permissions, tick Internal Users, Subs/Vendors or Client (or leave it Private), pick people in Notify Users and click Publish.
5. Repeat the whole form for every job visited that day. Notes that sat in a text thread get summarized late, and a day skipped is a gap in the job record that is hard to rebuild later.

Here are my notes from Maple Street today. Turn them into today's Buildertrend daily log, internal only, and tell me if a log for today already exists.

1. 01

   Split the notes by job

   Site notes often mix two jobs in one message. The agent matches each street name, client name or nickname against list_jobs and splits the text, one log per job. A note it cannot place goes back to you instead of landing on a guessed job.

2. 02

   Look for a log already written today

   Before writing, the agent reads the recent logs of that job with list_daily_logs. If a log for the same date exists, it shows you that log and asks whether to add a second one or leave it, so the job does not end up with duplicates.

3. 03

   Rewrite the notes into a clean record

   The agent turns shorthand into full sentences grouped as work completed, deliveries, inspections and issues, and keeps names, quantities and times exactly as you wrote them. It never adds work that was not in the notes, and a short title such as "Framing, second floor" goes on top.

4. 04

   Choose who sees it

   Internal only is the default. The agent shares with subs or the client only when you say so, because a client-visible log is part of what the homeowner reads about the job. Sharing outward is the moment the confirmation prompt matters most.

5. 05

   Publish and report back

   After your OK the agent creates the log with create_daily_log under your user and returns the link. Photos stay on your phone: attach them in Buildertrend if the log needs them.

Maple Street Addition, 12 Oct: log created, internal only. "Framing, second floor": walls framed and sheathed, window rough openings checked against plans, lumber delivery short 6 studs.
Hargrove Kitchen Remodel, 12 Oct: a log by Sam Reyes already exists for today. Not written, waiting for your call.
One note ("call the inspector back") did not name a job. Left out.

• Buildertrend daily logs have four visibility settings: Internal Users, Subs/Vendors, Client and Private. Private limits the log to the internal user who wrote it.
• Buildertrend fills in weather from Aeris Weather using the job's ZIP or postal code, and an admin can switch that default in Company Settings under Daily Log Settings.
• An admin sets in Default Daily Log Share Settings whether new Buildertrend logs start shared with clients, subs or internal only; users with the right permission can change it per log.
• Buildertrend daily logs open with the date pre-filled and can be backdated, so a day missed on site can still be logged under its own date.
• Buildertrend shows read receipts and reactions on each daily log, so the office can see whether the client or a trade partner opened it.

create_daily_log asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: Daily Logs Overview (Buildertrend help) · Daily Logs on Mobile (Buildertrend help) · Project Management Settings (Buildertrend help) · The Building Code, episode 13 (Buildertrend podcast)

curl https://cotlet.dev/api/v1/buildertrend/create_daily_log \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job_id":"4815162","date":"2026-10-12","title":"Framing, second floor","notes":"Second floor walls framed and sheathed. Window rough openings checked against plans. Lumber delivery short 6 studs, supplier to send Tuesday.","share_with":["internal"]}'

{
  "daily_log_id": "23094417",
  "job_id": "4815162",
  "date": "2026-10-09",
  "title": "Framing, second floor",
  "shared_with": [
    "internal"
  ],
  "url": "https://buildertrend.net/app/DailyLogs/23094417"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is buildertrend_create_daily_log. Example data.

• Reschedule a Buildertrend schedule item and notify the sub
• Draft and send Buildertrend change orders with an AI agent
• Chase pending Buildertrend selections across all jobs
• Buildertrend API and MCP server: every tool
• All use cases