Download PDF (141 KB)
PDF version — print or share with your team.
Transport and logistics operators want to know whether Claude Cowork can clear the document backlog without exposing a customer contract or a rate card. According to Statistics Canada, 12.2% of Canadian businesses now use AI, double the rate a year earlier, so back-office staff are already trying these tools. The duty to protect customer data and contract terms stays with the firm.
Mike Pearlstein, CISSP, MSc AI, founder of Fusion Computing, which has secured IT for Canadian transport and logistics firms across Toronto, Hamilton, and Metro Vancouver since 2012.
Key takeaways
- A transport firm can use Claude Cowork on a Team or Enterprise plan with access scoped to one account or lane folder and a written policy.
- Scope it to one account, never the whole TMS or customer drive.
- Cowork stores its work locally, so it sits outside your audit logs. Safety and customer audits need traceable records you build yourself.
- A person reviews anything sent to a customer or a carrier.
Can transport and logistics firms use Claude Cowork with customer and operational data?
Yes, a transport firm can use Claude Cowork on a Team or Enterprise plan, with access scoped to one account or lane folder and a written policy. The firm owns customer-contract confidentiality and its PIPEDA duties, and no vendor setting removes them. On the business plans, your content is not used to train Anthropic’s models by default, which is why customer work belongs there and never on a personal account.
The control that matters is scope: which files the agent opens, which plan governs the data, and who reviews the output before it reaches a customer. Customer trust depends on keeping rates and terms controlled, so the setup around the tool is what keeps it safe.
It’s the same secure-adoption logic from the pillar guide on using Claude Cowork securely in your business, applied to a carrier or broker, and it sits alongside our broader IT for transport and logistics work.
What Claude Cowork actually does in a transport back office
Claude Cowork completes multi-step document work rather than answering a single question. For a transport firm, the practical jobs are processing customer and carrier documents, drafting rates and quotes, summarizing dispatch and shipment records, organizing safety and compliance documents, and cleaning up claims and invoices. Each output is a draft for a person to verify before it leaves the office.
Here’s how those jobs map to the work, with the guardrail that protects the customer. Fusion Computing walks operators through this before any pilot, the same way we scope any AI services engagement.
Book a 30-minute call to scope Claude Cowork for your operation safely →
| Task | What Cowork does | The guardrail |
|---|---|---|
| Customer and carrier documents | Reads BOLs, rate confirmations, and contracts; extracts terms | Scope to one account; ops verifies |
| Rate and quote drafting | Drafts rates and quotes from your templates | Rate cards stay in a scoped folder |
| Dispatch and shipment summaries | Drafts shipment and status summaries from records | A draft for review, not the system of record |
| Safety and compliance docs | Organizes National Safety Code and safety documents | Internal documents, reviewed before filing |
| Claims and invoice cleanup | Deduplicates and categorizes claims and invoices | A draft for review |
The customer-data and contract guardrails
The core guardrail is least privilege: scope Cowork to one account or lane folder, not the whole TMS or customer drive. Classify what is allowed in (working documents for the active account) and what stays out (rate cards and customer identifiers beyond the scoped folder). Keep a person reviewing anything customer-facing. Cowork runs in an isolated virtual machine, but prompts still reach Anthropic, so scope is the control that limits exposure.
The mistake we flag most often is scope. When a firm connects the agent to the whole TMS, a single task can read every customer’s rates. Scope it to the active account and you’ve cut most of the risk.
Field note. In the operator pilots I’ve run, the first thing I change is access. I’ve watched a dispatcher point an agent at a drive holding every customer’s negotiated rate. We scoped it to one account folder, and the workflow that felt reckless became routine. The work’s identical; the exposure isn’t.
The policy is the other half. A short rule set, the kind we cover in our guide on what belongs in an AI acceptable use policy, names the approved tool, the data that may go in, and who may run it. Fusion Computing pairs that with a cybersecurity review so the firm protects its customer relationships, in line with PIPEDA.
The oversight gap for compliance records and audits
Claude Cowork stores its conversation history locally on each user’s computer, and that activity is not captured by audit logs, the Compliance API, or data exports. For a transport firm this matters: safety programs and customer audits assume the firm can trace its records. Team and Enterprise owners can stream Cowork events to a SIEM through OpenTelemetry, which Anthropic notes does not replace audit logging for compliance.
According to Anthropic’s guidance on using Cowork on Team and Enterprise plans, the local history “is not subject to Anthropic’s standard data retention policies and cannot be centrally managed or exported by admins.” The Enterprise audit logs that do exist capture metadata, not the work.
Fusion Computing wires the OpenTelemetry stream into the same monitoring we run for managed detection and response, so a firm sees tool calls and file access even though the transcript stays on the device. If a document supports a claim or a safety record, the firm keeps that trace on purpose.
Plan tier and a setup checklist for a transport firm
The plan tier is the first decision: only Team and Enterprise carry the “not trained on by default” commitment plus the admin controls a firm needs. From there, a safe rollout is short: scope to one account folder, keep “ask before acting” on, write a usage policy, turn on OpenTelemetry monitoring, keep a person signing off on customer-facing output, and review the vendor terms against your customer contracts.
Cowork runs on Pro, Max, Team, and Enterprise plans per Anthropic’s release notes, and on the business tiers your content is not used to train models by default, as Anthropic’s privacy commitments set out. Here’s the checklist Fusion Computing runs with an operator.
Get a CISSP-led review of where AI tools touch your customer and rate data →
Why Canadian firms bring this work to Fusion Computing
CISSP-led, a Microsoft Solutions Partner and a CompTIA Managed Services Trustmark holder, securing IT for Canadian SMBs across Toronto, Hamilton, and Metro Vancouver since 2012.
- Choose Team or Enterprise. Customer rate data on a personal account is the first risk to fix.
- Scope to one account folder. Never the whole TMS or customer drive. Widen only with a reason.
- Default to “ask before acting.” Cowork always asks before deleting files; keep approvals on.
- Write an acceptable use policy. Name the approved tool, the data that may go in, and who may run it.
- Turn on OpenTelemetry monitoring. It’s the only visibility you have into what the agent did.
- Keep a person signing off. Nothing customer-facing ships without review.
- Map the terms to your contracts. Check Anthropic’s data handling against your customer agreements before go-live.
None of it’s exotic, and most of it takes an afternoon. Fusion Computing sets it up as part of the managed IT work we already do for firms, and the same pattern carries to manufacturers, construction firms, and accounting firms. If you want a second set of eyes before your firm pilots Cowork, talk to us or read more about how we work.
Claude Cowork is worth adopting for the document and customer work that fills a transport back office. The firms that set the plan, the scope, and the policy first are the ones that’ll use it calmly while their competitors are still arguing about whether it’s allowed.
Fusion Computing helps Canadian businesses across Toronto and the GTA, Hamilton, and Metro Vancouver with managed IT, cybersecurity, and Microsoft 365.
Frequently Asked Questions
Is Claude Cowork safe for customer and rate data?
Claude Cowork can be safe for customer and rate data on a Team or Enterprise plan, with access scoped to one account folder and a person reviewing the output. The work runs locally, though prompts reach Anthropic, so expose only the documents a task needs. On the business plans your content is not used to train models by default, which is why customer data belongs there.
Can Claude Cowork work with our TMS exports?
Cowork can read files and use approved connectors, so it can work with TMS exports or a scoped folder rather than a live connection to your whole system. Point it at one account, never the entire customer drive. A person should verify anything Cowork extracts before it informs a rate, a quote, or a customer message.
What plan does a transport firm need for Claude Cowork?
A transport firm should use the Team or Enterprise plan, never a personal Pro or Max account. Only the business tiers carry Anthropic’s commitment not to train on your content by default, plus the owner and admin controls a firm needs. Customer rate data on a personal account is the first risk to remediate.
Is our data used to train the model?
On Team and Enterprise plans, your content is not used to train Anthropic’s models by default, so documents processed under a business plan stay out of training. Personal Pro and Max plans follow individual privacy settings, which differ from the business default. For a firm guarding customer relationships, that difference is the reason to use a business plan.
Want an AI use policy that protects your customer contracts? →
How is Claude Cowork different from logistics AI?
Logistics AI is usually built into a TMS, routing, or visibility platform and scoped to those systems. Claude Cowork is a general desktop agent that works across your own files and apps, which suits document, rate, and claims work more than routing or tracking. The practical differences are where the data lives and how broadly the agent can reach.
Does Claude Cowork help with safety paperwork?
Yes. Cowork can draft and organize National Safety Code records, driver files, and safety policies from your own materials. Treat the output as a draft for a safety lead to review, and keep a record of how it was produced, because Cowork’s own session history is local and is not captured in central audit logs.
Does Claude Cowork work on Windows or only Mac?
Claude Cowork works on both macOS and Windows through the Claude desktop app, and it reached general availability on both on April 9, 2026. It is not available on the web or on mobile. Some capabilities, such as computer use, arrived first as research previews, so confirm the current feature list for your platform inside the app.
Who at the firm should run Claude Cowork?
Start with a small group in operations or the back office who understand customer confidentiality, never the whole firm. Cowork is an organization-wide setting that owners can switch on or off, and granular per-user controls are limited, so a deliberate pilot with named users beats a broad rollout. Pair it with training and a written policy first.
