Claude (Formerly Cowork) for Architects: Five Admin Tasks to Try First

Claude (formerly Cowork) can work through a project folder you connect: it reads PDFs, Word and Excel files, then builds registers, trackers and summaries as new files. Try five low-risk admin jobs first: an open-actions list from meeting notes, a drawing register, a conditions tracker, a fee-against-invoices check, and, last, a folder tidy-up on a copy.

Anthropic now says Claude Cowork is "just Claude": depending on your account you may still see a Chat and Cowork switch, or the newer single message box. Either way, local folders need the desktop app, and the work runs on Anthropic's servers rather than staying on your computer, which matters for client files. Start with copies, read every output against its source, and treat each result as a draft.

Follow me on Instagram@sagnikteaches

Cowork is now just Claude: what a practice should know first

The line "Claude Cowork is now just Claude" sits at the top of Anthropic's Cowork page, and its getting-started help article explains the practical result. Chat and Cowork share one home, and when a task involves your files Claude brings in the Cowork abilities automatically. The rollout is staged, so as of early November 2026 some accounts still show separate Chat and Cowork options. The help article says that if your message box no longer shows them you have the new experience, and some steps may look different. The five tasks below work either way.

Connect on LinkedInSagnik Bhattacharya

These are the facts an architect needs before pointing it at a project, and what I would do about each:

Subscribe on YouTube@sagnikteaches

One more point sits outside the table. Pro and Max are individual plans with a model-training setting in the privacy settings, so find it and decide before any client material goes in. Team and Enterprise plans do not train on your content by default. If you have not yet written down what your practice allows, an AI policy checklist with ready-to-use clauses takes an afternoon, and the copyright and client-data risks of AI in architecture practices explains what the clauses are guarding against.

Set up a working copy and standing instructions

Anthropic's own safety advice is to create a dedicated working folder for Claude rather than grant broad access, and to keep backups of important files. For a practice that turns into a simple routine: copy one finished project into a scratch area, keep only documents, PDFs and spreadsheets in the copy, and give Claude one place to write its results.

ClaudeWork/
  2307_Rear-extension/        a COPY of the project folder, no CAD or BIM files
    01_Appointment/
    02_Consents/
    03_Drawings_issued/
    04_Meetings/
    05_Invoices/
    Incoming/
  Outputs/                    Claude writes every new file here

Leave native CAD and BIM files out of the copy. Claude cannot read them, and renaming a live drawing file breaks any external references that point to it by name. If you want Claude to help with a drawing set, export it to PDF first.

Claude supports folder instructions, which Anthropic describes as project-specific context that applies when you select a local folder on the desktop. Write them once, as rules you would give a new junior who has never seen your filing system. Here is a filled-in set for the illustrative project:

Project 2307, rear extension and refurbishment. Six-person practice.
Rules for every task in this folder:
1. Never change, move, rename or delete anything in the project folders. Write every new file to /Outputs.
2. Use the spelling in our existing documents, and dates in the form 14 Feb 2026.
3. Every row you produce must name its source file and page. If you cannot find a source, write "not stated".
4. Never guess. If a value is unreadable or ambiguous, write "unreadable" or "unclear" and list it on a sheet called Check these.
5. Drawing numbers look like A-101. Issued drawings carry letter revisions (A, B, C); work in progress carries P01, P02.
6. You are not giving legal or contractual advice. Do not mark any condition, invoice or action as closed, discharged or paid unless a document in the folder says so in plain words.

Rule 1 does the most for safety, and rules 3 and 4 do the most for checking: every row traces to a page, and every doubt lands on one sheet you read first. Anthropic also offers projects in Cowork, workspaces with their own files, instructions and memory, but for these tasks a connected folder with folder instructions is easier to audit.

Task 1: Roll twenty weeks of meeting notes into one actions list

Start here because it only reads, the inputs are short, and the job plays to what an assistant does best and people do worst: holding twenty weeks of notes in mind at once. If you write the minutes yourself, recording, summarising and issuing architect meeting minutes the same day covers that step. This task comes after it, when the notes exist and nobody has reconciled them.

In the illustrative project, the folder holds 22 sets of notes from site and design-team meetings: Word files, PDF minutes and three plain-text transcripts.

Read every file in 04_Meetings. Build a spreadsheet in /Outputs called Open actions with one row per action: action ID (A-001 upwards), action text, owner (use the role named in the notes), date raised, due date, source file, latest status (open, closed or unclear) and a Changes column.
If an action appears in several meetings, keep one row and record each restatement in Changes. If the owner or due date changes, say so there.
Mark an action closed only if a later note says it was done, issued, received or agreed in plain words. Otherwise mark it unclear.
Never invent a date: write "not stated". Add a second sheet called Check these listing anything you were unsure about.

The result might look like this, with invented rows:

Say it comes back with 31 open items and nine on the Check these sheet. The value is in rows like A-014, an action restated three meetings running that nobody owned. What you fix: owner names will vary ("site manager", "SM", "contractor"), so add an alias list to the folder instructions. The "closed only if" sentence is doing real work, because without it assistants tend to read "discussed" as "done". Review every closed and unclear row against its named source file, and you have audited the whole list.

Task 2: Build a drawing register from a folder of issued PDFs

A register is the classic admin job that nobody enjoys and everybody needs when a contractor asks which revision is current. Keeping a drawing issue register and transmittal log with AI covers the record of what was sent to whom. This task is narrower: reading the title blocks of what is in the folder and listing them.

The illustrative folder holds 38 PDFs, named inconsistently, some of them scans.

Read the title block of every PDF in 03_Drawings_issued. Build a sheet in /Outputs called Drawing register with: drawing number, title, revision, revision date, scale, status (as printed in the title block), file name and page number.
If two files carry the same drawing number, treat the later revision date as current and list the other under a sheet called Superseded.
If any field is unreadable, write "unreadable". Do not use the file name as a substitute for what the title block says. List every conflict between file name and title block on Check these.

On 38 PDFs, expect trouble in three places: scans, stamps or annotations sitting over a title block, and files that hold several sheets, which is why the page number matters. Spot-check ten rows against the PDFs and read every line on Check these. Then be clear about what you have: a register of what is in the folder, not the issue record. The issue record is what you actually sent, and a register that matches the folder can still be wrong about that.

Task 3: Pull every condition from a decision notice into a tracker

A planning decision notice or permit approval with a dozen conditions is a small project inside the project. Some conditions must be met before work starts, some before occupation, some run for the life of the job, and the evidence sits in different consultants' hands. The illustrative folder holds a six-page decision notice and two follow-up letters.

Read the decision notice and the letters in 02_Consents. Build a sheet in /Outputs called Conditions tracker with one row per condition: number, short wording, type (before work starts, before occupation, ongoing, time limit), evidence needed, likely lead (architect, engineer, contractor, client), related drawing numbers named in the notice, and status.
Status is open unless a letter in the folder says in plain words that the condition has been discharged. A letter saying discharge is pending or awaited means open. Quote the sentence you relied on in a Source column.
List sub-conditions as separate rows. Put before-work-starts conditions first.

The conditions below are invented for illustration, not taken from any real decision:

Check the count first: the last condition number in the notice should match the highest row, with sub-conditions separate. Then read the Source column, because the failure to watch for is a status misread. A letter that says discharge of condition 8 "is pending" must stay open, and rule 6 in the folder instructions exists to stop an assistant treating "discharge" as the answer. Keep the interpretation of what a condition requires with a person. The tracker tells you what to chase and from whom; whether the evidence satisfies the condition is a professional decision.

Task 4: Check stage fees against invoices to date

Fee admin tends to slip when the work is busy, and the first sign is an invoice that does not match any stage. Automating the path from enquiry to fee invoice covers how to get the invoice out. This check runs afterwards, across what has already been sent. In the illustrative project, the folders hold the fee proposal, seven invoices and one variation letter.

Decide first whether these files belong in the working copy at all. Anthropic's safety article advises against connecting local files with sensitive information such as financial documents. A practical middle course is to copy only the proposal and the invoices, with bank details and client contact details removed, or to export stage fees and invoice lines from your accounts software into one spreadsheet and connect just that file.

From the fee proposal in 01_Appointment, list each stage with its fee. From the invoices in 05_Invoices, list each invoice: number, date, stage, amount, and whether it refers to a variation.
Build a sheet in /Outputs called Fee check with: stage, fee, invoiced to date, remaining, over or under, and notes. Use Excel formulas for totals.
Flag any invoice that does not map to a stage in the proposal, any invoice that refers to a variation with no variation letter in the folder, and any total that does not add up. Do not estimate how complete any stage is.

The sum checks out: 4,000 + 9,500 + 15,400 + 10,500 = 39,400, and 64,000 minus 39,400 is 24,600. Even so, re-add the invoiced column in Excel yourself, because a misread digit in a scanned invoice (15,100 read as 15,400) would still produce tidy-looking totals. The sentence "do not estimate how complete any stage is" matters too, since percentage complete is your judgement and the one number an assistant should never supply. Check whether the invoices and the proposal treat tax the same way before comparing them, and treat the flagged variation as a prompt to find the letter or write one.

Task 5: Tidy and rename an incoming folder, last and on a copy

This is the demonstration everyone reaches for first, and it belongs fifth. It is the only task here that changes files, and deletion protection does not cover renaming or moving. Run it on a copy, in two passes: first a proposal that touches nothing, then the changes once you have read the proposal.

The illustrative Incoming folder holds 140 files with names like scan0043.pdf, Final_FINAL_v3.docx and IMG_2210.jpg. The practice's convention is project number, type, description and date.

Pass 1. Do not move, rename or delete anything. Read the files in Incoming and build a sheet in /Outputs called Proposed renames with: current name, proposed name, proposed folder, reason, confidence.
Convention: 2307_[Type]_[Description]_[YYYY-MM-DD].[ext] for letters, reports and photos; 2307_[Drawing number]_[Title]_Rev[X].pdf for drawings.
If two files would end up with the same name, say so. If two files look like versions of the same document, list them together under a sheet called Possible duplicates and do not choose between them.
Pass 2 will follow only after I approve the sheet.

Read the Medium rows and the Possible duplicates sheet with the originals open. Photo dates come from file metadata, which some messaging apps strip, so expect a few "date unknown" rows. When the proposal is right, approve pass 2 and ask for a Changes made sheet listing every rename and move. Never ask for deletions: ask for a duplicates list and decide yourself. Rename only documents, PDFs and photos, never live CAD or BIM files, and only copy the tidy folder back to the live location once the register and tracker still point at the right files.

Checking Claude's work before anyone relies on it

All five tasks share one checking routine, which takes minutes rather than hours when the folder instructions are doing their job:

1. Read the Check these sheet first. It lists what the assistant itself was unsure about, which is where errors cluster.
2. Count. Files in the folder against rows in the sheet; conditions in the notice against rows in the tracker; invoices against invoice lines.
3. Spot-check ten rows, or one in five on a large set, against the named source file and page.
4. Re-add every money column in Excel yourself.
5. Read every closed, discharged or paid status against the quoted sentence.
6. Keep the original folder untouched until a person has signed off the output, and note who checked it and when.

Expect patterns rather than random errors. Three realistic ones, described as illustrations: a register that lists a superseded revision as current because both files sit in the folder; a tracker that marks a condition discharged because a letter mentions "discharge" in the future tense; and a fee check that misses a variation because the letter was saved as an image with no readable text. The folder instructions above target the first two. For the third, run a quick count of files that return no readable text and handle them by hand.

What five tasks cost in usage, and when to move up a plan

Anthropic's help article says multi-step tasks, such as ones that run code, create files or use your connected apps and browser, use more of your allowance than a quick question, and its Cowork product page says agentic tasks consume more capacity than regular chat. It suggests grouping related work into one task, starting a new conversation for unrelated work, telling Claude when you only need a quick answer, and checking Settings, then Usage. It does not publish a per-task figure, so measure your own: run each task once on the practice's Pro account, look at the usage meter afterwards, and note what a task took. Claude (formerly Cowork) cost: which plan and what usage limits apply goes deeper on plan choice.

The saving is easier to estimate than the usage. Say a drawing register takes two hours by hand and 40 minutes to check once Claude has drafted it. At 12 issues a year that saves 12 × 80 = 960 minutes, or 16 hours, from one task. Time your last manual version before you start, so the comparison uses your own numbers, not mine.

Once a task runs cleanly, Anthropic's scheduled tasks can repeat it on a cadence you choose. Anthropic's safety article says a session cannot reach your computer while the desktop app is offline, so a task that reads local files needs the app open and connected when it runs. Schedule a weekly actions roll-up for a time your computer is on. The same article warns against scheduling tasks that touch sensitive files, so the meeting-notes roll-up is a good candidate for a schedule and the fee check is not.

What stays with the architect

None of these tasks issues anything. A register, a tracker and a fee check are internal working papers, and each one needs a named person to check it before it informs a decision or leaves the practice. Three things should stay out of an assistant's hands altogether: judging whether evidence satisfies a condition, certifying or approving anything, and any document with legal effect. Treat Claude as a fast, literal assistant that reads everything and understands your filing system only as far as your folder instructions describe it. On a finished project, with a copy of the folder and a patient hour, the first four tasks will tell you whether it earns a place in the practice.

Questions architects ask before connecting a folder

Is Claude Cowork the same thing as Claude now?

In name, yes. Anthropic's Cowork page says Claude Cowork is now just Claude, and chat and Cowork are merging into one experience that is rolling out in stages. Some accounts still show separate Chat and Cowork options. Cowork needs a paid plan, and working in local folders needs the Claude desktop app open on your computer.

Can Claude read DWG or Revit files?

Anthropic's list of readable file types covers documents, PDFs, spreadsheets, presentations, images and code. It does not name CAD or BIM formats such as DWG or RVT. Export PDFs and Excel schedules from your drawing or modelling software and work from those, and keep native CAD files out of the connected folder.

Does Claude keep my client's files?

Cowork sessions run on Anthropic's servers, and files opened through the desktop app are processed there. Sessions and files are saved to your account until you delete the task, and Anthropic says a deleted task leaves its backend storage within 30 days. Turn memory off for confidential tasks, check the model-training setting on individual plans, and read your client agreements first.

Which plan should a small practice start on?

Start on Pro to test these tasks on copies of one finished project. If the usage allowance runs out often, or several people will use it, compare Max, Ultra and Team. Team seats list Cowork, add admin controls and, by default, do not train on your content, with a two-seat minimum. Check Anthropic's pricing page before buying, because plans have changed recently.

Further reads

• Claude vs ChatGPT vs Gemini for Architects: Which to Pay For — Which assistant to pay for before you choose a folder workflow
• Architect Site Visit Report: Notes and Photos to a Clear Report With AI — Site notes and photos into a clear report, a chat-sized task
• Can AI Write an Architect's Snagging List From Site Photos? — Photo-based snagging lists and what AI tends to miss
• AI Software for Architectural Drawings: Notes, Schedules and Sheet Checks — Notes, schedules and sheet checks across a whole drawing set
• How to Use Claude AI in Architecture: Specs and Planning Reports — Summarise specifications and planning documents with Claude, check every clause against the original, and keep client material out with a never-paste list.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Anthropic's Claude Cowork product page; Claude help articles 'Get started with Claude Cowork' and 'Use Claude Cowork safely'; Claude pricing page (all read November 2026). Project figures, file names and conditions in the examples are invented for illustration.