Download PDF (140 KB)
PDF version — print or share with your team.
Architecture and engineering firms want to know whether Claude Cowork can take on the document load of a project without putting client confidentiality or design IP at risk. According to Statistics Canada, professional, scientific, and technical services lead Canadian AI adoption at 31.7%, so design staff are already reaching for these tools. The professional duty to protect client information stays with the firm.
Mike Pearlstein, CISSP, MSc AI, founder of Fusion Computing, which has secured IT for Canadian architecture and engineering firms across Toronto, Hamilton, and Metro Vancouver since 2012.
Key takeaways
- A design firm can use Claude Cowork on a Team or Enterprise plan with access scoped to one project folder and a written policy.
- Scope it to one project, never the whole project archive or drawing library.
- Cowork stores its work locally, so it sits outside your audit logs. Professional records and project audits need a trace you build yourself.
- A licensed professional signs off on anything stamped or client-facing.
Can architecture and engineering firms use Claude Cowork on client projects?
Yes, a design firm can use Claude Cowork on a Team or Enterprise plan, with access scoped to one project folder and a written policy. The firm owns the confidentiality and professional duty, and no vendor setting removes it. On the business plans, your content is not used to train Anthropic’s models by default, which is why client project 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 carries a stamp or reaches a client. Professional obligations to bodies like Professional Engineers Ontario sit with the firm, so the setup around the tool is what keeps it defensible.
It’s the same secure-adoption logic from the pillar guide on using Claude Cowork securely in your business, applied to a design practice, and it sits alongside our broader IT for architecture and engineering firms work.
What Claude Cowork actually does for a design practice
Claude Cowork completes multi-step document work rather than answering a single question. For a design firm, the practical jobs are drafting specifications and reports, assembling RFP responses and proposals, organizing project documents and drawing sets, summarizing codes and standards for a project, and turning meeting notes into minutes and transmittals. Each output is a draft for a professional to verify, never a stamped deliverable.
Here’s how those jobs map to the work, with the guardrail that protects the client. Fusion Computing walks firms 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 firm safely →
| Task | What Cowork does | The guardrail |
|---|---|---|
| Specification and report drafting | Drafts specs and reports from your templates and notes | Scope to one project; an engineer reviews |
| RFP and proposal drafting | Assembles a proposal from past work and the brief | Client data stays in a scoped folder |
| Project-document organization | Sorts and renames drawings, transmittals, and records | One project folder, not the whole archive |
| Code and standard research | Summarizes building codes and standards for a project | A professional verifies against the source |
| Meeting minutes and transmittals | Turns notes into minutes and transmittal drafts | A draft for the file, reviewed before sending |
The client-confidentiality and design-IP guardrails
The core guardrail is least privilege: scope Cowork to one project folder, not the whole project archive or drawing library. Classify what is allowed in (working documents for the active project) and what stays out (other clients’ files and proprietary details beyond the scoped folder). Keep a professional reviewing anything stamped or client-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 points the agent at the whole project archive, a single task can read every client’s drawings. Scope it to the active project and you’ve cut most of the risk. That’s the change that matters most.
Field note. In the design-firm pilots I’ve run, the first thing I change is access. I’ve watched a project lead point an agent at a server holding every project the firm had ever drawn. We scoped it to one job, 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 clients and its professional standing.
The oversight gap for professional records and project 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 design firm this matters: professional record-keeping and project audits assume the firm can trace how a document was produced. 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 professional record, the firm keeps that trace on purpose.
Plan tier and a setup checklist for a design 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 project folder, keep “ask before acting” on, write a usage policy, turn on OpenTelemetry monitoring, keep a professional signing off on stamped output, and review the vendor terms against your client 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 a firm.
Get a CISSP-led review of where AI tools touch your project files →
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. Client project files on a personal account is the first risk to fix.
- Scope to one project folder. Never the whole archive or drawing library. 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 professional signing off. Nothing stamped or client-facing ships without review.
- Map the terms to your contracts. Check Anthropic’s data handling against your client 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 law firms, accounting firms, and manufacturers under their own rules. 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 specifications, proposals, and project documents that fill a design week. 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 project files and drawings?
Claude Cowork can be safe for project files on a Team or Enterprise plan, with access scoped to one project folder and a professional 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 project work belongs there.
Can Claude Cowork draft specs and reports?
Yes. Cowork can draft specifications, reports, and proposals from your templates and project notes, which saves a design team time on the first pass. Treat every draft as a starting point for a licensed professional to review and stamp. Keep the source documents in a scoped project folder so the agent sees only what it needs.
What plan does a design firm need for Claude Cowork?
A design 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. Client project files on a personal account is the first risk to remediate.
Is our project data used to train the model?
On Team and Enterprise plans, your content is not used to train Anthropic’s models by default, so project data processed under a business plan stays out of training. Personal Pro and Max plans follow individual privacy settings, which differ from the business default. For a firm with client confidentiality duties, that difference is the reason to use a business plan.
Want an AI use policy that fits your client contracts and professional duties? →
How is Claude Cowork different from design-specific AI?
Design-specific AI is usually built into CAD, BIM, or project-management platforms and scoped to those systems. Claude Cowork is a general desktop agent that works across your own files and apps, which suits specs, proposals, and document work more than modelling. The practical differences are where the data lives and how broadly the agent can reach.
Does Claude Cowork help with building-code research?
Yes, with a caveat. Cowork can summarize building codes and standards for a project and pull the relevant clauses together, which speeds up research. A professional should verify every reference against the official source before it informs a design decision, because a summary is a starting point, never the authority.
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 of project managers and senior staff who understand client 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.
