Hand over real work.

Build 1 on a phone, a locked laptop or the free plan: four steps

The same four steps are on slide 22 of the deck, so you can follow either. Dictation is the default, not the exception.

1. 1

   App or browser → Settings → Capabilities → Cloud code execution and file creation: ON. It is there on Free.

   If it refusesMissing? Any browser.

2. 2

   New chat → plus icon → attach your function's short extract. It is in your Downloads from yesterday and holds the same tabs at the same cell addresses as the full workbook.

   If it refusesCannot attach? Run tonight.

3. 3

   Paste the brief with its Short version line under it, or dictate it. One dictated line is enough: "Short version", plus your unit: dealer, SKU or campaign. Send.

   If it refusesAllowance gone? The 4:40 catch-up.

4. 4

   Tap the file → open it in Excel or Sheets → go to the last tab, Verify Cells. Your three addresses are waiting there for the check at 4:52.

   If it refusesWill not open? Tonight, at a desk.

Same brief, same check. Half the room, and not the slow lane.

By the clock

Three public posts all afternoon: FILE, CHECKED, MONDAY. Scores and numbers never. Stuck: a private message to the host.

1. 3:30

   Answer the poll: B (paid, phone or locked laptop), C (free) or D (other tool)

2. 3:37

   Do not only watch the opening demo. Run it. New chat → plus icon → attach Nivara_Workbook_Extract_Sales.xlsx → paste the short opening brief (C3-P) → send. Then watch the facilitator. At about 3:44 read your answer: is your August billing total the same as the one on his slide 1? Free plan: it costs allowance. If you would rather protect it for Build 1 and Build 2, watch
3. 3:47

   Ready already? Start: dictate your weak one-liner under the brief coach (C4) while the Frame is explained. Nobody needs to be told
4. 3:59

   Check the files are in Downloads and file creation is on. Tap the green tick reaction in Zoom

5. 4:04

   Lab, the phone default. Do not write v2 or v3. Dictate one line: what you want, for whom, by when. Paste it under the brief coach (C4). Answer its three questions by voice. It writes all five letters. Read its Abort line aloud to yourself. Fix it by voice if it is weak

   Public chat(optional: paste your Abort line if you would like it read out)
6. 4:22

   Build 1. Note your baseline minutes. New chat → plus icon → attach your short extract (free) or the workbook and the report (paid) → paste the Build 1 brief (B1) for your function, with your function's "Short version" line under it → send. You get the minimum useful file: one workbook, one or two tabs, anything else as a few lines in chat. The brief makes it list the tabs it read before anything else
7. 4:32

   Watch the facilitator's phone for four minutes: the Operations brief, by the same route as yours

8. 4:40

   Catch-up here. No file yet? Open _finished_examples/ → your function. You are level with the room

9. 4:45

   Download the file. Open it in the Excel, Word or PowerPoint app, or in Google Sheets. Tap one total: is it a formula? Dictate one change under fix one thing (V4)

   Public chatFILE + function + one thing it flagged
10. 4:52

    The check. Paste ask for proof (V1). Open your short extract in the Excel app and go to its last tab, Verify Cells. Your three checks are listed there with the tab and the cell address. Tap each cell, write what you see under "My check", mark Y or N. Then answer the two judgement questions on the slide. Paste self-review (V2). Re-adding a total is a desk job. Do it tonight, or hand it to your team with the same tab. Your score, 3/3, 2/3 or 1/3, goes in your Proof Log and nowhere else

    Public chatCHECKED + function

    Your three checks
11. 5:03

    Look up. The lender's ninety seconds on the facilitator's screen: profit doubled, every ratio improved, then one fee and one release came out. Nobody is writing during it. Your own second pass starts at 5:05

12. 5:05

    Second pass. Same chat. Paste the second pass (S2) for your function. While it runs, write in your Workbook's Second Pass tab which number you think will move. Then write what did. Low allowance: read the saved second pass instead
13. 5:15

    Break. Not finished? Finish now

14. 5:23

    Watch five minutes. Answer one question, in your Workbook beside the note to IT: can you add an add-in from Microsoft's store at work? STORE, BLOCKED or DON'T KNOW

15. 5:28

    Web task, Route B: new chat → paste the web task (W1) for your function with the link already in it. Route C, if B refuses: open the link in your phone browser → select all → copy → paste under the paste-the-page version (W1-C). Then open one link and find one number on the page. Write it in your Proof Log
16. 5:36

    Build 2 opens. Open your Chief of Staff Project from the app's side menu. Watch the proof count at 5:37 and the live refusal at 5:44, seated. Your own run starts at 5:47

17. 5:47

    Build 2, the phone path. Open your Chief of Staff Project from the app's side menu. Plus icon → attach the report PDF → paste the phone version (K1-P) with your role line → send. It is three steps, not six: the headline number, the one disagreement, the one decision. No Project on your phone: run the five-minute hire (K0) and the phone version (K1-P) in one chat, and create the Project tonight

    K0No Project yet? The five-minute hireOpen to view
18. 5:56

    Open what came back: three slides, or text in chat. Use the PDF viewer's page jump to check one page number

19. 6:01

    Write two roles in Who gets which file. That is HANDS done: tick it in the commitment form at 6:23. the skeleton brief (K2) is for tonight on a phone: five dictated answers, at a desk or in a cab

    K2For tonight: the skeleton brief, your own monthly reviewOpen to view
20. 6:06

    Owners, and anyone who pays from their own pocket: start the ROI tab on your own screen now. The facilitator reaches it at 6:09. Nothing personal goes in the public chat

21. 6:16

    Monday Card, phone-first version: paste the Monday handover card (M2), dictate, attach one Green file. Fifteen minutes in a cab is enough for the brief. Do the check at a desk

    Public chatfunction + the job I will hand over this week. Then the commitment form, which is private

What happens to what you type, by plan

Anthropic's privacy pages, read 27 Sep 2026. Your company's policy overrides every row.

Off does not mean nothing is stored. Your chats stay in your history until you delete them. Fictional files today. Policy wins.

Every company: DPDP. Then RBI and SEBI if they are yours

Which lines are yours. Every company: the traffic light, the DPDP line, the eight folder rules. Listed companies: add the SEBI line. Banks and NBFCs: add the RBI line. If you are private, unlisted and not RBI-regulated, those two lines are not yours, and on Sunday you make your folder while I read them.

Three rules, said first

1. Copies, in one working folder, never a synced drive. The mistake: selecting Documents or the OneDrive folder "just for a minute". A synced folder is your whole company, one level up.
2. The traffic light decides what goes in. Red never goes in. Amber goes in only on a company-approved plan. Labels, not names. Rounded numbers. The mistake: a customer drawing, an audit finding or an appraisal note that was already lying in the folder you selected.
3. It saves. It never sends. And it never logs in. No passwords, no OTPs, no banking, no portals. It saves files. You send them. The mistake: letting it "just email the dealer".

Eight folder rules

1. Copies, not originals. The agent works on a copy. The original never enters the folder.
2. One working folder, made for this job. Select that folder and nothing above it.
3. Never a synced root. Not Desktop, not Documents, not the OneDrive, Google Drive or SharePoint folder. A synced folder is your whole company, one level up.
4. No credentials, anywhere. No passwords, OTPs, net-banking details, digital-signature tokens or API keys. Not in the folder, not in the brief, not in the browser it uses.
5. Read the plan before you approve it. Keep approvals on "ask". If it asks to delete or overwrite, read exactly what, then decide.
6. Nothing sends. No email, no message, no form, no upload to a third-party site. It saves files. You send them.
7. The traffic light decides what goes into the folder. Red never goes in. Amber goes in only on a company-approved plan. Labels, not names. Rounded numbers.
8. Clean up. When the job is done, move the outputs you need and delete the working copies. On the desktop, the session history stays on your laptop.

In the browser or phone route your files are uploaded to Anthropic's servers for the session and saved to your Claude account. So: fictional files only, until your company says otherwise.

Do it now: a folder of copies, then the green tick

Desktop lane: confirm Nivara_Work exists on the local drive, outside any synced folder, with copies of the files. Phone or locked laptop: runsheet row 3:59. Everyone: tap the green tick reaction in Zoom when you are ready. Nothing is typed.

Phone, locked laptop or Free: your files are in Downloads, and Settings → Capabilities → Cloud code execution and file creation is on. It is there on Free too. Then the green tick.

Manager's Rule Card

1. Copies in one working folder. Never the original, never a synced or shared drive.
2. The traffic light decides what enters the folder. Red never does. Labels, not names. Rounded numbers.
3. No passwords, OTPs, banking, tax portals, HR or customer systems in any browser the AI is driving.
4. It saves files. It sends nothing. A person sends.
5. Every brief has a stop line: "If anything is missing or two sources disagree, stop and ask."
6. Three numbers traced to source by me. One total re-added by me. Source file, date and tool named on the working paper. Then it carries my name.

Before you hit Enter

• Context: would a new analyst know who this is for?
• Steps: are they numbered?
• End state: have I named the files and the units?
• Abort: does it know when to stop and ask?
• Review: have I asked for three sourced numbers and a "could not do" list?
• Reversible: if this goes wrong, can I undo it? If not, add a human step.

In this pack: the CLEAR skeleton (C0) · the brief coach (C4) · your function's Build 1 brief (B1), at 4:22.

Your weak brief, rewritten with the brief coach (C4)

Copy the weak one-liner for your function. Then paste the brief coach (C4) and ask it to rewrite into CLEAR. The skeleton with all five letters, the CLEAR skeleton (C0), is also the CLEAR Builder tab in the Workbook.

Delegation Lab · Path 1 (paid desktop)

1. v1 (2 min). On screen: the brief most finance heads would have typed. v1 (C1): "Do the variance analysis for August with comments." The facilitator shows the saved v1 output and reads the damage aloud. Started at 3:47? You have your own v1 already. Go straight to step 2.
2. v2 (4 min). You write. Activity Pack → your function → your weak one-liner is already there. Rewrite it with C, L and E in the CLEAR Builder tab of the Workbook. Meanwhile the facilitator shows v2 (C2) and its saved output: the right two files, the right shape, and commentary written on a total that leaves out a row. It looks finished. That is what makes it the dangerous version.
3. v3 (4 min). You write. Add A and R. Then paste your brief into an ordinary chat under the brief coach (C4). It scores your brief against CLEAR, names the missing letter and asks you up to three questions. It does not start the work. The lender's ninety seconds, Lender L under the Finance brief's second pass, is shown at 5:03, just before your own second pass, when nobody is writing.
4. Abort lines, read out (2 min). Optional, and not a checkpoint. If you would like yours read, paste your Abort line in chat.

What changed, version by version

Delegation Lab · Path 2 (phone and free)

1. Watch v1 with the room (2 min).
2. Dictate one line: what you want, for whom, by when. Paste it under the brief coach (C4). Answer its three questions by voice, in short phrases (5 min).
3. the brief coach (C4) writes all five letters. You do one thing a machine cannot: read its Abort line and ask, "would this have stopped the last mistake a junior made on this job?" Fix it by voice if not (3 min).
4. Optional (2 min). Paste the Abort line in chat if you would like it read out. Otherwise keep improving it.

Three dials

• Folder instructions. A standing note that applies every time this folder is selected. Global instructions apply to every session. Claude can update folder instructions, so read them now and then. Put your house rules there once: state the unit in every table, never edit originals, save outputs to /out. That is folder instructions (F1).
• Parallel sub-tasks. For a big job it may split the work and run the pieces side by side: one reads the workbook, one reads the report, one drafts the slides. You can ask for this: "Do steps 2, 3 and 4 in parallel, then reconcile." It is faster. It also uses more of your allowance.
• Approvals. Three modes: it asks each time, it decides with safety checks, or it skips approval. Today: ask each time. Deletion always asks, in any mode. This line is what the agent is allowed to touch, so it is never cut, at any delay.

You have a file with your function's name on it. A confident file is not a correct file. The ten-minute check: four ways it fails, a tell for each, three numbers traced to a cell, two questions no tab can answer, and one line you can sign. The checking prompts: ask for proof (V1) · self-review (V2) · what did you touch (V3) · fix one thing (V4).

The best place to handle a failure is the original brief. Every counter above is already inside the A and R lines of the Build 1 brief (B1).

Your three checks

The ten-minute check, step by step

1. Paste ask for proof (V1). It must give, for each of three numbers: the value, the source file, the tab, and the cell or page.
2. Open the last tab of the source workbook, or of your short extract: Verify Cells. Find your function. Your three checks are listed with the tab and the cell address. The tab gives addresses only. It never gives the answer. Go to each cell, write what you see under "My check", compare it with the number Claude's file used, and mark Y or N. This is a glance, not a search, on a laptop or a phone. Phone: runsheet row 4:52.
3. The judgement check. Two questions no tab can answer. Write one line for each in the Proof Log.
   • Does the biggest number in this file match what I already know from the field: from my regional managers, my plant heads, my last review? If not, which of the two is wrong?
   • What is the first question my CFO, my CEO or my banker would ask of this file, and does the file answer it?
4. Re-add one total. Desktop: select one column in your own copy of the source and read the sum in the status bar. Compare it with the output. If the output's totals are typed numbers, not formulas, send fix one thing (V4). Phone lane: this is a desk job. Tonight, or delegated.
5. Paste self-review (V2). Read its "could not do" list. An empty list on a workbook with nine tabs is itself a tell.
6. Log it: Workbook → Proof Log. Three rows from the Verify Cells tab, your two judgement lines, and your score: 3/3, 2/3 or 1/3. The score stays in your Proof Log. It is not posted. It goes into the commitment form at 6:23, which only the facilitator reads, and next Sunday's slide shows the room's split with no names. Public post 2 of 3, in chat: CHECKED + function. That tells the room the check was done. It does not say how it went.

Leading a large team? Split the check the way you split any work. Steps 2 and 4, the tracing and the re-adding, are an analyst's job. From Monday they belong to a named role on your team, on a Verify Cells tab of your own: the same seven columns, your own three cells. Step 3 cannot be delegated, and nor can the signature. Do steps 2 and 4 once yourself today. You cannot delegate a check you have never done, and with the tab it takes three minutes.

Sales, Marketing, Finance and CXO on the phone and free lanes: your minimum useful file may not hold the number for every check. Write what you see in the cell anyway. The "Short version" line for your function says which check you compare now and which you compare with your second pass at 5:05.

It drafts. You sign.

It drafts. You sign. Cite the workbook and the cell, never the assistant. Save the output beside the source with the date and the words "first draft by Claude, checked by [your initials]". If an auditor asks "what was the source?", the working paper answers. If your team did the tracing, their initials and the date sit on the Verify Cells tab, and the line you say is: "traced and re-added by [role], judged and signed by me." The standard is the same. Only the hands differ.

Who consents to what

Anthropic's Office pages, read 27 Sep 2026. The owners go first, because the enterprise words are not for you.

One answer in your Workbook

At work, can you add an add-in from Microsoft's store? Write STORE, BLOCKED or DON'T KNOW beside the note to IT in your Workbook. Nothing is posted. If you wrote DON'T KNOW, that is the first question in your note to IT.

Outlook (a beta: it drafts, it never sends, Exchange Online only). Claude Docs and Slides (launched 16 Sep 2026) and Claude Design (April): paid betas, on by default for Pro, Max and Team, off by default on Enterprise, and anyone you share with needs a Claude account. Betas change, so nothing today depends on them. On Team and Enterprise a Doc cannot yet leave the organisation.

For M365 shops where Copilot is already licensed: your approved route to the same idea is Microsoft Copilot inside Excel and Word. More at 6:06.

Limits, said plainly: no macros, no VBA, no data tables, not on iPad or Android. The add-in's chat history stays on the device and is not in Enterprise audit logs.

The proof count, 5:37

Same brief, same PDF, two windows: your Chief of Staff Project and an Incognito chat. Paste the review-deck brief (K1) into both, read the two ten-line plans, and count three things in each.

• a · Role-specific lines. Lines that use something about you that the review-deck brief (K1) did not say: your stakeholders, the numbers you are judged on, your meeting, how you like a brief.
  • b · Standing instructions honoured. Open your Project's instructions. Take the first five by name, for example "amounts in ₹ Cr", "decisions first", "one page", "label what you infer", "end with Verify first". How many does the plan follow without being told?
  • c · Red lines respected. Of the seven red lines, how many does the plan state or apply on its own, for example "no individual is named"?

Your counts stay in the Proof count tab. Nothing is posted in the public chat. If you are willing, send PROOF · P a/b/c · I a/b/c as a private message to the host, where P is the Project and I is Incognito.

If the windows tieIf your two windows tie, your instructions are thin, not the idea: run tune the instructions (X1) tonight and count again.

The live refusal, 5:44

Said aloud at the refusalThat is the mistake most likely to be made in your company this month: a manager pasting appraisal notes about a named employee into a personal AI account. You just watched a red line fire on it. It is still a reminder, not a control. By the time it objects, the name has already left the laptop. The control is you, and the rule you give your managers.

Build yours, 5:47 to 6:03

Which data may you use here? The lane rule, three cases (3:57) decides: case one may use its own extract as labels and rounded numbers; cases two and three use the fictional Nivara files or a listed peer's published results, and so do their managers.

1. 0
   By 5:51

   Catch-up, only if you need it. No Project, or an empty one: open a new Project named Chief of Staff — [first name], paste the five-minute hire (K0), answer in short phrases, approve. Five minutes. Policy says no, or you would rather not describe your role? Build Aditi's. Her answers are in the participants' folder. Then go to step 1, five minutes behind the room

2. 1
   By 5:48, or 5:53 after step 0

   In the Project, attach the management report PDF. Paste the review-deck brief (K1), or type "go" if your plan from the proof is already on screen. Your role line is already filled in for your function. Owners: your role line makes this the pack for your next bank review. Paid, with Cowork: you may run it as a task instead. Same brief. Phone: the phone version (K1-P), three steps

3. 2
   By 5:56

   Open the deck. Run the check: ask for proof (V1), then trace two numbers to the report's pages yourself. Your function's pages are in the Verify line under the review-deck brief (K1). Fix one slide with one line

4. 3
   By 6:00

   The Monday version. Paste the skeleton brief (K2): the skeleton of your own monthly review. Headings, the question each slide must answer, the numbers it will need and who owns each, as labels and rounded numbers only. Policy says no: run the skeleton brief (K2) with no numbers at all. A skeleton of headings and questions is Green

5. 4
   By 6:03

   Decide who gets which file. Read your function's row in the table below. Write two names by role in the Workbook tab Who gets which file. That is HANDS done. Nothing is posted: you tick it in the commitment form at 6:23. Save the skeleton in the Project as My monthly review skeleton

Catch-up hire (only if you need it)

Then paste the seven red lines (H2) from last Sunday, word for word.

You do not need to test it yourself today: the whole room watches it fire at 5:44. Test yours tonight with the made-up "Kavita Rao" line from the demo.

Your monthly review

Role line: · Pages:

Look at what the skeleton brief did not ask forLook at what the skeleton brief (K2) did not ask for: your numbers. On Monday you hand the skeleton to your team, and they fill it in your company's own system. The hours you get back are the hours your people spent deciding what the deck should contain. For operations leaders, that is the promise from last week: the first draft of the review deck is delegated. Log the hours your plant heads spent on the last one. That is your baseline.

Who gets which file on Monday

The red lines still hold. A monthly review names no individual. People matters stay out, exactly as in H4.

What each one calls "do the work"

Pick per job

Where Claude loses today, for "Do": no Cowork on the free plan · no audit-log cover for Cowork yet · Claude in Chrome does not run in Edge · no images · and if your company has approved Copilot or Gemini, the approved tool beats the better tool.

Pay or not, 6:09

For the owner who pays herself, and for anyone who pays from their own pocket. Nothing personal goes into the public Zoom chat: not the price on your screen, not the value of your hour, not your overdue money. No price is quoted here, because the price shown in India depends on where and how you buy. You put your own numbers into the ROI tab of your Workbook, on your own screen.

1. "Open claude.ai/upgrade on your own account. Read the monthly price on your own screen. Write it in the ROI tab as P. Do not type it in chat."
2. First sum, hours. "P ÷ the value of one hour of your time = the hours it must save you each month." Your hour is your own business. The tab does the division.
3. Second sum, rupees, from your own second pass. "At 5:05 the owners worked out what Nivara's overdue money costs. At 9.5% a year, which is my assumption, not a number in the files, the five dealers' ₹31.4 Cr past 90 days costs about ₹3.0 Cr a year, which is about ₹82,000 a day. Now yours, in the tab: your own overdue past 90 days, rounded to the nearest ₹ lakh, × your bank's rate ÷ 365 = what one day costs you. Then: 12 × P ÷ that figure = how many days earlier one customer must pay to cover a year of the price on your screen."
4. Want your sum checked? "Send me your rounded figure and your rate as a private message to the host. I read back only the answer, for example 'eleven days'. Never the inputs, never a name."
5. The decision rule, unchanged from last week: "If you have not handed over a job on five working days in a month, cancel. What Free did today: every build, the check, the second pass and the web task, through chat. What paying adds: Cowork on a folder, so no uploading and downloading, longer jobs, and the browser tools. Decide tonight, with your own numbers, in your own tab."

The same sum at ₹ 150 Cr scale: ₹ 4 Cr past 90 days at 9.5% a year, the same assumption, is about ₹ 10,400 a day. P is about ₹ 80 a day. So the question is whether one customer pays one day earlier. That sum needs no CA.