For what the connector is, how to set it up, and permission requirements, see Claude MCP Connector Overview. This article picks up from there and focuses on write actions: the changes Claude can make on your behalf, not just the questions it can answer.
What's live today
Time and labour entries: create, edit, submit, approve, process, individually or in bulk
Punch items: create, update, complete, bulk update
RFIs: create, update, submit, respond, close
Change orders and PCOs: draft, update totals, submit, approve, attach files
Purchase orders: create, update, submit, approve, process
Submittals: create, send, respond, close, revise
Budgeting: groups, line items, allocations and expenses
Company settings: company info, RFI reminders, change order defaults, contact sources, geotracking, materials, budgeting defaults, company notice, Sage export toggle, and connector user access
This list covers the everyday actions. The full breakdown further down includes less common operations in each area (for example, reopening a cancelled change order, or reverting a punch item change) along with the specific limitations of each module.
Example requests
"Log 9 hours for the crew on the Main Street job Tuesday against cost code 200"
"Create a punch item for the drywall on level 3, assign it to the sub, due Friday"
"Approve every submitted timecard for last week that has no missing cost codes"
"Draft a change order for the extra electrical work on the east wing, itemized"
"Show me every purchase order over $5,000 still waiting on approval"
How changes are confirmed
Claude checks first. It looks up the current, live information so it knows exactly what it's changing, never a cached or remembered value.
Claude shows the before and after. A plain-language summary such as "Status: Pending to Approved" is shown before anything happens.
Claude waits for confirmation. Nothing is applied until you explicitly approve it. If any detail changes, the proposal is discarded and a new one is prepared.
Claude never opens a browser window to complete a change, and never applies a change without an explicit confirmation.
General rules and limitations
These apply across all eight write areas, not just one module. Access itself follows the roles and permissions covered in the connector overview article.
Confirmations expire after 15 minutes. If too much time passes before you approve a proposed change, Claude re-checks the latest data and presents a fresh version before proceeding.
Live data is re-checked immediately before applying. If a record changed after the proposal was shown, Claude stops and presents the new situation instead of applying an outdated change.
Bulk actions are not always all-or-nothing. When updating, approving, or rejecting a batch of items, some can succeed while others fail. Claude always reports exactly which items were applied and which were not.
Email and notification delivery cannot be confirmed. Claude can confirm that SiteMax accepted a request to send something (an RFI, a change order, a PO), but SiteMax does not report back on whether it was actually received.
Deletions are usually permanent. SiteMax has no undo for most deletions: draft change orders, punch items, budget entries, files, and so on. Claude flags this clearly before a delete is confirmed.
Required steps are never skipped. Claude follows the same workflow rules as the SiteMax interface. For example, it will not approve something that hasn't been submitted yet.
Capabilities by Module:
Time
Time
What it does: Add a timecard entry, edit one, delete one, or submit it for approval. On the approval side: approve, reject, or reverse an approval and reprocess entries. Works on a single entry or a whole batch at once.
Limitations:
Cannot flag or resolve a "time discrepancy." There is no equivalent action in SiteMax.
A deleted time entry cannot be restored.
Cannot create a single entry that spans midnight. This must be split into one entry per day.
Bulk-creating entries only works with clock-in/out times, not the "total duration" entry mode.
Does not push entries to QuickBooks, link a Budget Action Item, or create material log lines from a time entry. These remain separate steps in SiteMax.
Change Orders
Change Orders
What it does: Create a draft, edit details or pricing, submit for review, approve or reject, cancel or reopen, add a response, attach or remove files, resend a notification, mark paid, send to accounting, or send for signature. Can also copy an approved PCO into a new change order.
Limitations:
Once a response is added to a change order, its attached files cannot be edited afterward. Files can only be added when the response is first created.
Editing a change order and changing its status (for example, "update this and approve it") always happens as two separate confirmed steps.
Claude cannot sign a document on your behalf. Signature requests go out to the actual signer.
Cannot create a new "manual" project location on the fly. It must already exist in SiteMax.
Once a change order is created as lump-sum or itemized breakdown pricing, that format cannot be switched later.
Submittals
Submittals
What it does: Create a submittal, edit it, attach or remove files, send it into review, close it out, create a revision, and distribute a closed submittal by email. Also manages review steps: add, edit, approve, reject, or forward a step in the chain.
Limitations:
A reply's attached files cannot be changed after the reply is posted.
Replacing a submittal's PDF or adding stamps/cover pages is not yet supported.
Forwarding a review step only works from the last step in the chain, and always adds to the end. It cannot be inserted partway through.
A submittal package, once created, cannot be renamed or deleted.
Editing a submittal and sending it always happens as two separate confirmed steps.
Purchase Orders
Purchase Orders
What it does: Create a PO, edit it, add a line item, submit for approval, approve or reject (including a whole batch at once), mark approved POs as processed, email the PDF, and manage photos or files attached to it.
Limitations:
A PO's number is always assigned automatically by SiteMax and cannot be set manually.
A deleted photo or PDF attachment cannot be restored, and deleting one does not automatically refresh the main PO's PDF.
Bulk approve/reject on a batch of POs is not guaranteed all-or-nothing. Claude reports the exact outcome for each item.
Does not run QuickBooks or budget exports. These remain separate SiteMax workflows.
Cannot attach a new "manual" billing or shipping address. An existing one can be kept, but a new one must be set up in SiteMax first.
RFIs
RFIs
What it does: Covers an RFI from first draft through to being answered and closed: submit for internal approval, send to recipients, respond, attach files, close with final answers, cancel, reopen, or resend the notification.
Limitations:
Adds official RFI responses, not general comments. SiteMax's RFI tool has no separate comment feature.
An RFI cannot be linked to a change order, cost code, or specification section. This is not supported by SiteMax's RFI feature.
If an RFI has a location set, a specific drawing must also be selected. Claude will not let SiteMax auto-select one.
Adding certain recipients can, as a side effect within SiteMax itself, link their contact record to the project. Removing them later does not undo that link. This is native SiteMax behavior.
Budget
Budget
What it does: Covers SiteMax's newer Budgeting ledger: create or edit a budget group, add or edit a line item, and create or advance budget entries (allocations and expenses), individually or in bulk.
Limitations:
Covers only the new Budgeting module. This is separate from the legacy Budget/Action Plan tool, which is not managed through the connector.
Cannot attach files to a budget item.
Cannot copy a budget from one project to another, or import Time/Labour reports into it.
Cost type categories (such as "Labour" or "Materials") are fixed reference data and cannot be created or edited.
Deleting a budget group, line item, or entry cannot be undone.
Bulk actions (up to 500 items at once) are not guaranteed all-or-nothing.
Punch List
Punch List
What it does: Create a punch item, edit it, mark it complete, update a batch of them at once, or revert a mistaken change. Also adds comments and photos.
Limitations:
Marking an item "complete" does not accept a resolution note in the same step. A note must be added as a separate edit first.
"Revert" undoes a change by creating a new corrective change. It does not erase the original action from the history.
A file (non-photo) attachment's description cannot be edited or deleted once uploaded. This is a current limitation on SiteMax's side.
Bulk updates to a batch of punch items are not guaranteed all-or-nothing.
Company Settings
Company Settings
What it does: Company info and branding, RFI reminder settings, change order defaults, contact sourcing for different modules, default project folder setup, drawing behaviour, geotracking and its legal notice, materials and inventory settings, budgeting defaults, the company-wide notice banner, the Sage export toggle, and which users are allowed to use the connector.
Limitations:
The list of users allowed to use the connector is all-or-nothing when updated. Anyone not included in the new list loses access, so this change is flagged as higher risk before confirmation.
Only the specific setting areas listed above are configurable through the connector.
Limitations, in general:
Nothing is deleted permanently without a clear warning that it cannot be undone.
Email delivery cannot be confirmed, only that SiteMax accepted the request.
Claude does not bypass a workflow step or a permission your account doesn't have.
Every change is proposed first. Nothing is applied and reported after the fact.
Confirmations cannot be reused. Every change requires its own approval.