How to use Claude to run analysis of Toolbox Talk attendance
With a prompt, you can have Claude record the topic, date, attendance, and crew sign-on on every toolbox talk that you have recorded. Connect your project to Claude and have it evaluate patterns across dozens of toolbox talks and return a clear picture of the attendance trends to check and act on.
Northgate Stage 2, last 13 weeks. 47 Toolbox Talks, average 6 sign-ons each.
- Three crew signed on to fewer than half: J. Reyes (5 of 47), M. Okafor (9), D. Nguyen (11)
- Two talks have no sign-on recorded at all, both week ending 22 August
- Working at heights ran twice, turnout down from 11 to 4 the second time
Want the full list by crew?
Trusted by companies, projects and teams of all sizes
The short answer
Connect your Dashpivot workspace to Claude, specify the crew or date range you need, and allow it to read across the Toolbox Talk forms in the database. It can show you who signed on, who's been missing, the turn-out rates on your talks, and verify other attendance data that you can act and follow up on.
How to get Claude running analysis of your Toolbox Talk attendance
Three things have to be true before Claude can read your attendance. Two of them are about your records rather than the assistant, and they're the ones people skip.
-
Step 1
Get the talks onto digital forms
The Toolbox Talk has to be captured on a form with a consistent attendee sign-on, the same fields every time. A photo of a paper sign-in sheet is a picture to an assistant, not a record it can read.
-
Step 2
Build up enough talks to read back over
One talk answers nothing. The pattern shows up once there are weeks of talks against the same crew or project, because that's when a run of missed sign-ons or a thin turnout becomes visible.
-
Step 3
Connect Claude over MCP
With the records in place, your assistant needs a way to reach them. That's what MCP does: it lets an assistant query a system it doesn't own, using the permissions you already have. Depending on which system you use, the process may vary. We cover Sitemate MCP later in this article.
Prompt guidance for Toolbox Talk attendance analysis with Claude
The prompt is the thing worth building, not the conversation around it. Get it right once and it becomes your attendance prompt, where only the dates or the crew change. One rule matters more than the rest: it queries one form template at a time, so name the exact template, the project and the dates.
- "What workspaces do I have access to? List the projects and teams."
- "What form templates are available in [team name]?"
- "Pull the [exact Toolbox Talk template name] forms for [project] between [date] and [date]. Put each one in a table with the date, the topic and the number of attendees who signed on."
- "From those, tell me which talks had the lowest turnout, and list anyone who signed on to fewer than half of them."
- "Same prompt, new dates: [project], [start] to [end]. Flag any talks with no sign-on recorded at all."
Troubleshooting prompts for Toolbox Talk attendance analysis
A thin answer is usually a thin record rather than a bad prompt. The sign-on is the source, so these fixes are about what the form holds, in the order worth trying.
- Attendance comes back empty: the talk has no sign-on field, or it's a free-text name box rather than a signature. Add a signature or attendee field to the template
- The count looks low: only the people who signed the tablet are counted, so ask the crew to sign on rather than one person signing for the group
- Nobody's name resolves: attendees are typed as free text, so spellings vary. A register or a picklist fixes it
- Whole talks are missing: those talks were captured on a different template, so query each template separately
- It can't compare crews: the crew or project isn't recorded on the form, so there's nothing consistent to group by
Limitations
Claude can easily track attendance data across your toolbox talk form, but it is only limited to the quality of data in the forms you provide. You still have to review its output so partial sign-ons are not misinterpreted as the complete picture.
What it can do today
Given access to the correct workspaces, it can easily complete these tasks.
- Read existing Toolbox Talk forms for sign-on count and other attendance data
- Break down attendance data by crew, project, or date
- Flag talks with low turnout and people missing across multiple talks
- Only works within the user's own permissions, and does not widen their access
What it cannot do
Claude can read your records, but can't paint the entire picture. Here are some limitations and tasks it cannot perform.
- Count toolbox talk attendees that did not sign-on
- Evaluate talks that were recorded manually on paper or with photos
- Change the attendance and sign-on records
- Decide on who or what to follow up
What this assumes you already do
This page assumes the talks already exist somewhere. Claude is reading attendance from records your crews have already signed, so if the sign-ons are patchy the picture will be too. Nothing here's a setup step, it's the working habit the analysis is built on.
- Your crews already run Toolbox Talks and sign on to them, most weeks
- The talks land against the same crew or project each time
- The person reading the answer knows which crews were actually on site
Why run Toolbox Talk attendance analysis with Claude
Collating data from toolbox talk forms can get overwhelming quickly, especially if you hold talks every day or every week. Manual tracking means opening every form individually to tally sign-ons, topics, and other attendance data, which can tie down a supervisor to the office when they could be out on the field doing real work.
Manually keeping track of attendance over longer periods or date ranges also introduces possibility of human error as well. Holding count on a legacy software or, worse, in your head, can make missing four attendance checks look like missing one. There's just no time for this manual paper-pushing on a busy job site.
What a good attendance analysis covers
A good read of Toolbox Talk attendance tells you who's turning up, who isn't, and where the record itself is thin. Most cover the same ground:
- Turnout per talk, and how it trends over the weeks
- Who signed on to most talks, and who's been missing
- Talks with no sign-on recorded at all
- Crews or projects running below a weekly cadence
- Where the gap is a real absence versus a missing record
The incident review asks who was briefed on working at heights that month. The talks all ran, the crew remembers them, and the sign-on sheets are in a folder somewhere across three different sites.
Connecting Sitemate MCP to Claude
Three steps, and the first one isn't in Claude. An Org Controller has to switch MCP access on in Dashpivot before the connector will authenticate for anyone.
-
Step 1
Turn on MCP access in Dashpivot
An Org Controller opens Settings, then Security, and sets the MCP Access toggle to anything other than None. Save changes. Until this is on, the connector won't authenticate.
-
Step 2
Add the Sitemate connector in Claude
In Claude, go to Settings, then Connectors, then Add and Browse connectors. Search for Sitemate, pick the connector tagged Community, and click Connect. Sign in with your Sitemate credentials and approve access when prompted.
-
Step 3
Pick it in a chat
Start a new chat, click the plus button, open Connectors and select Sitemate. What you can read is whatever your Dashpivot permissions already allow, so connecting Claude doesn't widen anyone's access.
If the connector will not appear
Three things account for almost every failed connection, and the first is the most common by a distance.
- Nothing connects at all: MCP Access is still off in Dashpivot, and only an Org Controller can turn it on
- Sitemate isn't in the connector list: search "Sitemate" exactly, and look for the Community tag
- The connector doesn't show in a chat: start a new chat, click the plus button, and pick it under Connectors
How the record gets captured
A good answer is only as good as the sign-ons behind it, so it's worth seeing how they get captured in the first place.
-
Storm captures it on site
The talk and its sign-on get captured while the crew is standing there, on a phone or tablet, rather than written up on a sheet that has to be chased later.
-
Dashpivot holds it as the record
Each talk lands against its project as a structured record, with the sign-on attached, which is what makes a run of them countable rather than a folder to dig through.
-
Sitemate MCP reads it back
Connecting Claude to Dashpivot is what lets it answer from your own sign-ons instead of the internet. Your own permissions still apply.
Storm fills the records Claude reads
An attendance answer is only as good as the sign-ons behind it, and the gaps are almost always the talks nobody logged. Storm captures the talk and its sign-on as it happens, on site, so the record is there before anyone goes looking for it.
AI Form Fill
Capture what you see and say, and Storm drafts the form for you. The details land in the right fields, so there is a record to check the moment the work is done, and you review and submit it yourself.
Listens to the work
Captures voice cleanly through machinery, wind, and movement. Accents and trade language understood. No headset needed.
Works on site
Built for gloves, cabs, and screen protectors. Captures inputs offline and processes in the background. No waiting on the field.
You stay in control
Storm never commits a record on its own. Every output is a draft for human review. Admins control what Storm can write to.
Frequently Asked Questions
Can Claude actually see my Toolbox Talk records?
Yes, once you connect your Dashpivot workspace to Claude, it can read projects, folders, forms, and your Toolbox Talk records directly, including sign-on attendance data of your talks. There is no reliance on the content or prompts that are pasted in the chat.
Does it count who was actually there?
No, Claude can only count sign-ons on the Dashpivot forms. This means that if crew members attended but did not sign on, they will not be included in the count that Claude produces. A consistent sign-on field on the form matters more than your prompts as the sign-on is the only source Claude will draw from.
What can Claude see or access, exactly?
Claude can see your Dashpivot workspaces, projects, folders, templates, and, in this case, your Toolbox Talk records, sign-ons, and register lists.
Does this work with ChatGPT and Microsoft Copilot as well?
Yes, you can connect ChatGPT and Microsoft Copilot to Dashpivot the same way you would for Claude.
Can Claude see or access workspaces it shouldn't?
No, Claude won’t be able to see or access other workspaces that aren’t accessible by the requesting user. Every request to Claude you make is checked against existing workspace permissions, so it can only access what the user can access. Connecting Dashpivot workspaces to Claude doesn’t widen access within the platform.
What if the talks are on different templates?
Claude reads one form template at a time. This means that you will need to query each template separately and combine the answers across templates yourself.