[{"data":1,"prerenderedAt":4438},["ShallowReactive",2],{"site-nav-content":3,"hub:use-cases:posts":179,"site-cta-content":4406,"hiring-banner-content":4426},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":163,"title":164,"archived":165,"authors":166,"badge":166,"body":167,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":175,"relatedHeading":166,"seo":176,"series":166,"sitemap":165,"status":166,"stem":177,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":178},{"productLabel":5,"loginLabel":6,"contactLabel":7,"contactSalesLabel":8},"Product","Log in","Contact","Get started for free",[10,14,18,22,26,30,34,38],{"label":11,"to":12,"description":13},"Overview","\u002Foverview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","\u002Fproduct\u002Fconflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","\u002Fproduct\u002Fagent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","\u002Fproduct\u002Flifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","\u002Fproduct\u002Fwiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","\u002Fproduct\u002Fworkstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","\u002Fproduct\u002Fperception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","\u002Fproduct\u002Fgovernance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","\u002Fmodels",{"label":47,"to":48},"Pricing","\u002Fpricing",{"label":50,"to":51},"Integrations","\u002Fintegrations",{"label":53,"to":54},"Security","\u002Fsecurity",{"label":56,"to":57},"Partners","\u002Fpartners",{"label":59,"to":60},"Insights","\u002Fblog",{"productHeading":5,"companyHeading":62,"resourcesHeading":63,"legalHeading":64,"docsLabel":65,"docsUrl":66,"statementLines":67,"copyright":70,"companyLinks":71,"resourcesLinks":86,"legalLinks":102,"socialLinks":109,"bottomLinks":119},"Company","Resources","Legal","Docs","https:\u002F\u002Fdocs.gonimbus.ai",[68,69],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[72,73,74,75,76,78,81,84],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":77,"to":57},"Partner Program",{"label":79,"to":80},"Careers","\u002Fcareers",{"label":82,"to":83},"System status","\u002Fstatus",{"label":7,"to":85},"\u002Fcontact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","\u002Fglossary",{"label":91,"to":92},"Compare","\u002Fcompare",{"label":94,"to":95},"Evaluate","\u002Fevaluate",{"label":97,"to":98},"Problems","\u002Fproblems",{"label":100,"to":101},"Use cases","\u002Fuse-cases",[103,106],{"label":104,"to":105},"Terms of Service","\u002Fterms",{"label":107,"to":108},"Privacy Policy","\u002Fprivacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fgonimbusai\u002F",{"label":114,"href":115},"X","https:\u002F\u002Fx.com\u002Fgonimbusai",{"label":117,"href":118},"Instagram","https:\u002F\u002Fwww.instagram.com\u002Fgonimbus_ai\u002F",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","\u002Fcompliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","\u002Fllms.txt",true,{"text":133,"prompt":134},"Ask AI about Nimbus",{"I'm researching enterprise intelligence platforms and want to know how Nimbus combines perception, collaboration, and autonomous agents to drive strategic decision-making":135,"platforms":137},{" Summarize the highlights from Nimbus's website":136},"https:\u002F\u002Fgonimbus.ai",[138,143,148,153,158],{"name":139,"label":140,"icon":141,"hrefPrefix":142},"chatgpt","ChatGPT","simple-icons:openai","https:\u002F\u002Fchatgpt.com\u002F?prompt=",{"name":144,"label":145,"icon":146,"hrefPrefix":147},"perplexity","Perplexity","mdi:magnify","https:\u002F\u002Fwww.perplexity.ai\u002Fsearch\u002Fnew?q=",{"name":149,"label":150,"icon":151,"hrefPrefix":152},"grok","Grok","simple-icons:x","https:\u002F\u002Fx.com\u002Fi\u002Fgrok?text=",{"name":154,"label":155,"icon":156,"hrefPrefix":157},"claude","Claude","simple-icons:anthropic","https:\u002F\u002Fclaude.ai\u002Fnew?q=",{"name":159,"label":160,"icon":161,"hrefPrefix":162},"google-ai","Google AI","simple-icons:google","https:\u002F\u002Fwww.google.com\u002Fsearch?udm=50&aep=11&q=","content\u002Fshared\u002Fnav.md","Site navigation",false,null,{"type":168,"value":169,"toc":170},"minimark",[],{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[],"md","\u002Fshared\u002Fnav",{"title":164,"description":171},"shared\u002Fnav","1dD7ahDRl0SQ4hz53-kKo0tEFrGaLuaztZ3PPfp6a9k",[180,449,1025,1570,2043,2492,2698,3146,3362,4009,4221],{"id":181,"title":182,"archived":165,"authors":183,"badge":186,"body":188,"date":422,"definedTerm":166,"department":166,"description":423,"extension":174,"eyebrow":166,"faqHeader":424,"faqs":427,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":440,"relatedHeading":166,"seo":441,"series":442,"sitemap":131,"status":166,"stem":443,"subhead":166,"tags":444,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":448},"content\u002Fblog\u002Fcollaborative-ai-and-personal-assistants.md","Collaborative AI and personal assistants: when to use which",[184],{"name":185,"to":136},"Nimbus Research",{"label":187},"Use case",{"type":168,"value":189,"toc":415},[190,194,207,212,215,218,228,231,235,238,241,257,260,268,275,278,282,285,288,302,305,308,317,321,324,332,335,347,355,363,367,370,373,387,390,397,412],[191,192,193],"p",{},"A personal AI assistant at work helps one person finish their own draft faster. Collaborative AI is several people on one named job — the same files, the same history, and a person who can stop a change — with the model in that shared place rather than only in each person’s private chat.",[191,195,196,197,201,202,206],{},"Keep the personal tool for solo writing. Add a shared layer where two teams must stand on the same number, clause, or customer change. The ",[198,199,100],"a",{"href":200},"\u002Fuse-cases\u002F"," hub is the series. ",[198,203,205],{"href":204},"what-is-collaborative-ai","What is collaborative AI"," is the definition. This page is the side-by-side with the tool most people already have.",[208,209,211],"h2",{"id":210},"what-is-a-personal-ai-assistant-at-work","What is a personal AI assistant at work?",[191,213,214],{},"A personal assistant is a model that works for one user. That person types, pastes a file, copies a paragraph out, and sends it under their own name. If a colleague needs the same answer, they open their own window and start again.",[191,216,217],{},"At work that usually looks like a copilot in mail, a chatbot in the browser, or a plugin in the CRM that follows the logged-in user. The “team” plan on a pricing page is still this shape: more seats, each person alone.",[191,219,220,221,227],{},"Microsoft and LinkedIn’s ",[198,222,226],{"href":223,"rel":224},"https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fworklab\u002Fwork-trend-index\u002Fai-at-work-is-here-now-comes-the-hard-part",[225],"nofollow","Work Trend Index"," (2024) found that 75% of knowledge workers use generative AI at work, and that 78% of those users bring their own tools. Personal use is already common. That is useful data about desks. It does not tell you whether two departments share one job.",[191,229,230],{},"Memory in a personal assistant is that user’s thread, folder, or custom GPT. When the user leaves, the memory leaves with them. A prompt library can help the next person start. It does not carry the customer file or last week’s rejection.",[208,232,234],{"id":233},"how-is-collaborative-ai-different-from-a-copilot","How is collaborative AI different from a copilot?",[191,236,237],{},"A copilot is a personal assistant sitting next to the product you already use. Collaborative AI treats the job as the unit: who is on it, which files it may use, and who can refuse a change.",[191,239,240],{},"At minimum the shared product has four parts:",[242,243,244,248,251,254],"ul",{},[245,246,247],"li",{},"A named job, not “the channel.”",[245,249,250],{},"People who can see the same files and history.",[245,252,253],{},"Tools that read, and sometimes write, with a recorded step.",[245,255,256],{},"Someone who can say the change does not go out.",[191,258,259],{},"Write-back is when AI changes a live system — a CRM field, a ticket, a customer message. Collaborative AI treats that as a different class of action from drafting. The model proposes a payload: the exact change, field by field. A named person signs. Fail-closed means if nobody approves, nothing happens.",[191,261,262,263,267],{},"RBAC — who is allowed to do what — belongs on the job. A guest sees a slice. A member proposes. Someone else can reject. ",[198,264,266],{"href":265},"rbac-for-enterprise-ai","RBAC for enterprise AI"," is the access shape.",[191,269,270,274],{},[198,271,273],{"href":272},"multiplayer-ai-and-multi-agent-ai","Multiplayer AI vs multi-agent AI"," is the sibling distinction for several people in one session. Collaborative AI stresses the shared job, including what happens after the session ends.",[191,276,277],{},"A shared login is not this. Five people in one ChatGPT account is still one personal assistant: you cannot say who did what, and you cannot remove one person.",[208,279,281],{"id":280},"when-is-a-personal-assistant-the-right-tool","When is a personal assistant the right tool?",[191,283,284],{},"It is the right tool when the work has one owner and does not write to a live system.",[191,286,287],{},"Examples that stay personal:",[242,289,290,293,296,299],{},[245,291,292],{},"Summarising notes from a meeting you attended.",[245,294,295],{},"Drafting an email you will send in your own name after you read it.",[245,297,298],{},"Asking a question about a file you already have.",[245,300,301],{},"Rewriting a paragraph you wrote, for you.",[191,303,304],{},"Buy that. Sanction it. The Work Trend Index 2024 figure on bringing your own tools is a reminder that people will use something; a sanctioned personal tool is easier to see than an unofficial one.",[191,306,307],{},"It is not enough when two departments must stand on the same number, when the output can change CRM or a customer message, when a person who was not in last week’s chat has to pick up the job, or when someone has to show later what was proposed and who signed.",[191,309,310,311,316],{},"McKinsey’s ",[198,312,315],{"href":313,"rel":314},"https:\u002F\u002Fwww.mckinsey.com\u002Fcapabilities\u002Fquantumblack\u002Four-insights\u002Fthe-state-of-ai",[225],"State of AI"," (2025) found that 88% of organisations use AI in at least one function, while most are still piloting. A common pilot is one person and one copilot. That can be the right first step. The next step, if the work is shared, is a room — not forty copies of the same prompt.",[208,318,320],{"id":319},"how-do-you-use-both-without-confusing-the-team","How do you use both without confusing the team?",[191,322,323],{},"Say which product you are in, out loud, for each recurring job.",[191,325,326,327,331],{},"Keep the personal assistant for first drafts that one person owns. Keep the shared place for the artefact two teams will file. Do not paste the shared number into three private chats “to get a second opinion” if those chats become unofficial sources of truth. ",[198,328,330],{"href":329},"decisions-made-in-direct-messages","decisions made in direct messages"," is how a draft becomes three drafts.",[191,333,334],{},"A simple split:",[336,337,338,341,344],"ol",{},[245,339,340],{},"Solo thinking and wording — personal assistant.",[245,342,343],{},"Files both teams must use — the job.",[245,345,346],{},"A change to a live system — the job, with a named stop.",[191,348,349,350,354],{},"If you are asking how the model is boxed in — which tools it may call, when it must stop — that is a ",[198,351,353],{"href":352},"what-is-harness-engineering","harness",": the tools, stops, and checks around the model, not only the wording of the ask.",[191,356,357,358,362],{},"An ",[198,359,361],{"href":360},"what-is-an-ai-workstream","AI workstream"," and a Slack channel are a useful pair to keep straight. A bot in a channel can still be one person asking in public. Presence is not a roster.",[208,364,366],{"id":365},"how-do-you-decide-for-one-job","How do you decide for one job?",[191,368,369],{},"Use a short test on the next piece of work that already has two owners.",[191,371,372],{},"Ask:",[242,374,375,378,381,384],{},[245,376,377],{},"Does more than one department have to stand on the result?",[245,379,380],{},"Could the output change a live system or a customer-facing sentence?",[245,382,383],{},"Will someone who missed last week’s chat need to pick this up?",[245,385,386],{},"Would you need to show a proposal, a rejection, and a landing six months later?",[191,388,389],{},"If you answer no to all four, a personal assistant is enough. If you answer yes to any, put the brief in one place, add the people who already argue about it, attach the two files they always forward, and name who can say no. Run it once with the model drafting and the humans deciding.",[191,391,392,393,396],{},"Sales wants a discount exception. Finance wants the margin intact. A personal assistant can draft the email. Collaborative AI would be a shared workstream: the CRM excerpt, the margin sheet, both teams in the same history, and a recorded approve before anything writes back to the account. Nimbus’s ",[198,394,395],{"href":32},"workstreams"," are built for that shape. You can try the same shape in a wiki plus a ticket if that is what you have.",[191,398,399,400,404,405,408,409,411],{},"For the jobs that already look like this in RevOps, planning, or legal review, see ",[198,401,403],{"href":402},"collaborative-ai-for-revenue-operations","collaborative AI for revenue operations"," and ",[198,406,407],{"href":360},"what an AI workstream is",". For who may see the room, start with ",[198,410,266],{"href":265},".",[191,413,414],{},"You do not need a programme called “collaborative AI.” You need one honest label per job: personal draft, or shared result.",{"title":171,"searchDepth":172,"depth":172,"links":416},[417,418,419,420,421],{"id":210,"depth":172,"text":211},{"id":233,"depth":172,"text":234},{"id":280,"depth":172,"text":281},{"id":319,"depth":172,"text":320},{"id":365,"depth":172,"text":366},"2026-08-15","A personal AI assistant helps one person draft. Collaborative AI is several people on one job, with shared files and a named stop. A guide to using both without mixing them up.",{"eyebrow":425,"title":426},"Short answers","Copilot or shared job?",[428,431,434,437],{"question":429,"answer":430},"Can we just share one ChatGPT login across the team?","That is still a personal assistant used by several people. Context is not shared, you cannot say who did what, and you cannot remove one person without removing the tool.",{"question":432,"answer":433},"When is a personal assistant the right buy?","When the work has one owner and does not change a live system: summarising your own notes, drafting your own email, or asking a question about a file you already have.",{"question":435,"answer":436},"Is a copilot the same as collaborative AI?","A copilot is a personal assistant in the product you already use. Collaborative AI is the shared job — the same files, the same history, and someone other than the prompter who can stop a change.",{"question":438,"answer":439},"Do we need both?","Often yes. Keep the personal tool for solo drafting. Use a shared place when two teams must stand on the same number, clause, or customer change.","\u002Fblog\u002Fcollaborative-ai-and-personal-assistants",{"title":182,"description":423},"collaborative-ai","blog\u002Fcollaborative-ai-and-personal-assistants",[442,445,446,447],"collaborative AI","personal assistant","copilot","sl3SmHhEF7ojj-0EmjeUP_vc26pdfWiOf2NVVB1a9fU",{"id":450,"title":451,"archived":165,"authors":452,"badge":454,"body":455,"date":997,"definedTerm":166,"department":166,"description":998,"extension":174,"eyebrow":166,"faqHeader":999,"faqs":1002,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1015,"relatedHeading":166,"seo":1016,"series":1017,"sitemap":131,"status":166,"stem":1018,"subhead":166,"tags":1019,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1024},"content\u002Fblog\u002Floops-for-finance-and-planning.md","Loops for Finance and Planning",[453],{"name":185,"to":136},{"label":187},{"type":168,"value":456,"toc":988},[457,466,482,485,523,545,549,557,577,593,605,609,619,622,632,643,646,660,671,675,719,727,731,734,740,750,756,761,788,794,801,808,860,872,876,879,893,899,902,906,916,919,936,939,958,961,965,974,984],[191,458,459,460,465],{},"Finance and planning already have a Monday ritual. Actuals arrive. Someone rebuilds variance against a plan version. Someone lists exceptions. Someone drafts a commentary the line will treat as a target. The failure mode is a pack nobody can reconstruct when audit asks which extract it cited — and a journal that posted because someone clicked confirm. ",[198,461,464],{"href":462,"rel":463},"https:\u002F\u002Fwww.govinfo.gov\u002Fcontent\u002Fpkg\u002FPLAW-107publ204\u002Fhtml\u002FPLAW-107publ204.htm",[225],"Sarbanes-Oxley"," (US Congress, 2002) does not mention standing orders; it still asks issuers for a trail showing how a number became the number.",[191,467,468,469,473,474,477,478,411],{},"This page is ",[470,471,472],"strong",{},"unattended standing-order work",", not the shared collaborative room where controller, FP&A, and the business partner sign a forecast or variance. The standing order runs when the Monday pack is due or the numbers moved in the ledger, and it ",[470,475,476],{},"skips"," when the extract hash matches last run. It compiles the same scoped reads into the same outputs. It does not post journals. For the room that signs what people act on, read ",[198,479,481],{"href":480},"collaborative-ai-for-finance-and-planning","collaborative AI for finance and planning",[191,483,484],{},"Three nouns, as vocabulary:",[242,486,487,497,513],{},[245,488,489,492,493,411],{},[470,490,491],{},"Eval loop"," — a completion sensor. After a signed journal, read-back accounts and amounts. See ",[198,494,496],{"href":495},"eval-loops-for-enterprise-agent-harnesses","eval loops for enterprise agent harnesses",[245,498,499,502,503,507,508,512],{},[470,500,501],{},"Standing-order loop"," — a compiled recipe that admits a run when a trigger fires. See ",[198,504,506],{"href":505},"what-is-loop-engineering","what is loop engineering"," and the ",[198,509,511],{"href":510},"what-is-a-nimbus-loop","standing-order loop"," definition.",[245,514,515,518,519,411],{},[470,516,517],{},"Agentic workflow"," — open-ended replan, such as “close the books” with no saved recipe. See ",[198,520,522],{"href":521},"what-is-an-agentic-workflow","what is an agentic workflow",[191,524,525,528,529,534,535,540,541,544],{},[198,526,464],{"href":462,"rel":527},[225]," (US Congress, 2002) does not mention standing orders. It asks issuers for internal control over financial reporting — a trail showing how a number became the number. ",[198,530,533],{"href":531,"rel":532},"https:\u002F\u002Fwww.law.cornell.edu\u002Fuscode\u002Ftext\u002F15\u002F7262",[225],"Section 404",", as implemented in the ",[198,536,539],{"href":537,"rel":538},"https:\u002F\u002Fwww.sec.gov\u002Ffiles\u002Frules\u002Finterp\u002F2007\u002F33-8810.pdf",[225],"SEC’s ICFR guidance",", still wants evidential matter a third party can consider. You do not need to be an issuer for the reconstruction test to bite. If the Monday pack becomes what the line manages against, ",[470,542,543],{},"SOX reconstruction still matters for what the loop produced",": which extract, which period, which recipe version, who was notified, what was skipped.",[208,546,548],{"id":547},"what-a-finance-standing-order-loop-is","What a finance standing-order loop is",[191,550,551,552,556],{},"Three common starts, from ",[198,553,555],{"href":554},"six-things-that-start-a-loop","six things that start a loop",":",[336,558,559,565,571],{},[245,560,561,564],{},[470,562,563],{},"When the calendar says Monday"," — the recurring pack: actuals vs plan, exception list, driver tab refresh.",[245,566,567,570],{},[470,568,569],{},"When the numbers moved"," — ledger extract updated, cube refreshed, material variance against threshold.",[245,572,573,576],{},[470,574,575],{},"When the file lands"," — business partner uploads the operational file that explains the line.",[191,578,579,580,583,584,587,588,592],{},"The job is narrow: detect the start, pull the ",[470,581,582],{},"same scoped reads"," every time, produce the pack or exception list, and ",[470,585,586],{},"skip"," when the extract hash matches last run. It does not post journals. Posting belongs on the collaborative job with a named controller sign. ",[198,589,591],{"href":590},"a-loop-is-not-an-agent","A loop is not an agent",": the standing order does not sign the pack.",[191,594,595,596,600,601,604],{},"Pin the plan version and the definitions — currency, BU map, bookings versus pipeline — on the job ",[597,598,599],"em",{},"before"," the recipe runs. “Latest workbook in email” is how last August’s commentary cannot be replayed. The standing order should rebuild variance against the ",[470,602,603],{},"locked"," plan version, not against whichever file arrived last.",[208,606,608],{"id":607},"why-fpa-or-the-controller-should-care","Why FP&A or the controller should care",[191,610,611,612,615,616,411],{},"Because speed is the usual failure mode, and unattended ",[470,613,614],{},"drafting"," is safer than unattended ",[470,617,618],{},"posting",[191,620,621],{},"FP&A’s personal assistant can already draft a fluent variance note. The failure is custody: which actuals file, which tab was live, whether the partner saw the commitment implied. A standing order that compiles the same reads into the same run record every week reduces version-chasing. It does not replace the signer.",[191,623,624,625,628,629],{},"The common belief is that controls live at the ERP write. The plan and the commentary often become management truth ",[470,626,627],{},"weeks"," before they become entries. Protect only the post, and the loop’s most consequential output — the pack leaders act on — travels with no signature. Hence the split: ",[470,630,631],{},"the standing order produces the draft pack; the collaborative job signs what people act on.",[191,633,310,634,637,638,642],{},[198,635,315],{"href":313,"rel":636},[225]," (2025) keeps showing high adoption and low redesign. Most organisations use AI somewhere in finance. Few can replay last Monday’s pack without the author. ",[198,639,641],{"href":640},"what-auditors-are-asking-for","What auditors are asking for"," overlaps: identity, content, time, custody. Reconstruction is the test even when you are not mapping every SOX article.",[191,644,645],{},"You should care if:",[242,647,648,651,654,657],{},[245,649,650],{},"the “Monday pack” is already a chain of exports nobody can replay",[245,652,653],{},"a commentary cited August actuals and nobody can find that extract",[245,655,656],{},"journals still post from a confirm box the analyst clicks through",[245,658,659],{},"the line received a “new target” from an automation that nobody signed",[191,661,662,666,667,670],{},[198,663,665],{"href":664},"what-is-write-back-governance","Write-back governance"," stays on the journal path. ",[198,668,669],{"href":402},"Collaborative AI for revenue operations"," is the sibling when the moving number is pipeline, not books.",[208,672,674],{"id":673},"words-you-will-hear","Words you will hear",[242,676,677,683,689,695,701,707,713],{},[245,678,679,682],{},[470,680,681],{},"Extract hash."," A fingerprint of the actuals file or ERP pull. Unchanged hash → skip.",[245,684,685,688],{},[470,686,687],{},"Locked plan version."," The plan the recipe rebuilds against. Not “latest.”",[245,690,691,694],{},[470,692,693],{},"Exception list."," Rows that crossed a threshold, with sources cited.",[245,696,697,700],{},[470,698,699],{},"Commentary skeleton."," Draft language that points at attached sources — not a private rewrite.",[245,702,703,706],{},[470,704,705],{},"SOX reconstruction."," An independent reader can chain extract → inputs → signed pack.",[245,708,709,712],{},[470,710,711],{},"Eval loop."," After a signed journal, read-back matches payload.",[245,714,715,718],{},[470,716,717],{},"Agentic workflow."," “Explain variance” with no saved recipe — expensive, uneven.",[191,720,721,726],{},[198,722,725],{"href":723,"rel":724},"https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fuk-gdpr-guidance-and-resources\u002Fartificial-intelligence\u002F",[225],"The ICO’s AI guidance"," is a reminder that purpose and minimisation apply when the “user” is automation touching personal data in payroll or headcount extracts. Scope the read.",[208,728,730],{"id":729},"how-to-compile-one-finance-standing-order","How to compile one finance standing order",[191,732,733],{},"Start from a close ritual someone already runs.",[191,735,736,737],{},"Example: ",[470,738,739],{},"Weekly variance when actuals refresh",[191,741,742,745,746,749],{},[470,743,744],{},"Trigger:"," file lands in the controlled folder ",[470,747,748],{},"or"," ERP actuals extract event.",[191,751,752,755],{},[470,753,754],{},"Preconditions:"," read-only ERP or warehouse connection; pinned definitions; last extract hash stored.",[191,757,758],{},[470,759,760],{},"Steps:",[336,762,763,766,772,779,785],{},[245,764,765],{},"Pull actuals for the agreed period and scope.",[245,767,768,769,771],{},"Compare hash to last run. If unchanged, ",[470,770,586],{}," and log.",[245,773,774,775,778],{},"Rebuild variance against the ",[470,776,777],{},"locked plan version"," — not “latest workbook in email.”",[245,780,781,782,411],{},"Draft exception list and commentary skeleton that ",[470,783,784],{},"cites attached sources",[245,786,787],{},"Land outputs on the run record; notify FP&A and controller roster.",[191,789,790,793],{},[470,791,792],{},"Explicit non-goals:"," no journal post; no planning-cube write that behaves like books; no email to the line with “your new target.”",[191,795,796,797,800],{},"When commentary must commit the business, open the ",[470,798,799],{},"collaborative"," planning job. Partner rejects there. Controller signs there. The standing order may attach the run record as input.",[191,802,803,804,807],{},"A second common compile: ",[470,805,806],{},"Monday calendar",". Same recipe, time-based trigger, same skip if the extract has not moved. Prefer the file-lands trigger when actuals already arrive in a folder — you avoid running theatre on a bank holiday when nothing refreshed.",[809,810,814],"pre",{"className":811,"code":812,"language":813,"meta":171,"style":171},"language-mermaid shiki shiki-themes github-light github-dark","flowchart LR\n  actuals[\"Actuals file lands\"] --> hashCheck{\"Same file as last week?\"}\n  hashCheck -->|yes| skipNode[\"Skip, logged\"]\n  hashCheck -->|no| compilePack[\"Compile the Monday pack\"]\n  compilePack --> runPage[\"Outputs on the run page\"]\n  runPage --> notifyFpna[\"Notify the roster\"]\n  runPage --> signOffRoom[\"Sign-off room\"]\n","mermaid",[815,816,817,825,830,836,842,848,854],"code",{"__ignoreMap":171},[818,819,822],"span",{"class":820,"line":821},"line",1,[818,823,824],{},"flowchart LR\n",[818,826,827],{"class":820,"line":172},[818,828,829],{},"  actuals[\"Actuals file lands\"] --> hashCheck{\"Same file as last week?\"}\n",[818,831,833],{"class":820,"line":832},3,[818,834,835],{},"  hashCheck -->|yes| skipNode[\"Skip, logged\"]\n",[818,837,839],{"class":820,"line":838},4,[818,840,841],{},"  hashCheck -->|no| compilePack[\"Compile the Monday pack\"]\n",[818,843,845],{"class":820,"line":844},5,[818,846,847],{},"  compilePack --> runPage[\"Outputs on the run page\"]\n",[818,849,851],{"class":820,"line":850},6,[818,852,853],{},"  runPage --> notifyFpna[\"Notify the roster\"]\n",[818,855,857],{"class":820,"line":856},7,[818,858,859],{},"  runPage --> signOffRoom[\"Sign-off room\"]\n",[191,861,862,863,866,867,871],{},"Eval loops still matter on the ",[470,864,865],{},"write"," path: after a signed journal, read-back accounts and amounts. That sensor is not the Monday pack. Do not collapse them because both contain the word “loop.” ",[198,868,870],{"href":869},"how-to-evaluate-loop-engineering","How to evaluate loop engineering"," asks whether you can replay triggers and skips — the finance equivalent of audit reconstruction.",[208,873,875],{"id":874},"what-done-looks-like","What “done” looks like",[191,877,878],{},"A good finance standing-order week:",[242,880,881,884,887,890],{},[245,882,883],{},"The run record shows extract period, hash, recipe version, skip or delta.",[245,885,886],{},"The exception list points at sources on the job, not at a private chat rewrite.",[245,888,889],{},"No ERP post from the standing order.",[245,891,892],{},"An independent reader can open the collaborative signed pack and trace inputs to the loop run without the authors’ memory.",[191,894,895,896,898],{},"Retention on run logs should match how long you must explain the number — not how long chat keeps threads. ",[198,897,266],{"href":265}," applies: the standing order uses read grants. Posting tokens stay on human signers.",[191,900,901],{},"When audit or SOX asks how a commentary was produced, the answer should chain: extract on the run record → inputs on the collaborative job → signed pack. If the chain breaks at “someone ran a prompt,” the standing order did not fail — custody did.",[208,903,905],{"id":904},"how-to-start-with-one-trigger","How to start with one trigger",[191,907,908,909,912,913,915],{},"Pick ",[470,910,911],{},"when the file lands"," if actuals already arrive in a folder — or ",[470,914,806],{}," if timing is fixed.",[191,917,918],{},"This cycle:",[336,920,921,924,927,930,933],{},[245,922,923],{},"Name the artefact the standing order may produce: exception list, variance tab — not the signed board number.",[245,925,926],{},"Pin definitions and plan version on the job.",[245,928,929],{},"Add controller or deputy and FP&A to the roster for notifications.",[245,931,932],{},"Require skip logs when hash unchanged.",[245,934,935],{},"After four runs, ask an independent reader to reconstruct the pack from the run record alone.",[191,937,938],{},"Partner-facing numbers still belong in the collaborative room, not in an email the standing order generates. If the loop notifies the line, restrict it to “pack ready” — not “your new target.” That distinction is what keeps unattended compile separate from management commitment.",[191,940,941,404,945,949,950,404,952,954,955,957],{},[198,942,944],{"href":943},"loops-for-revenue-operations","Loops for revenue operations",[198,946,948],{"href":947},"loops-for-legal-and-compliance","loops for legal and compliance"," cover pipeline and policy triggers. If the pack is still a chat ritual, read ",[198,951,506],{"href":505},[198,953,555],{"href":554}," before you pick a trigger. ",[198,956,591],{"href":590}," is why the Monday compile should not invent a journal.",[191,959,960],{},"Automate the pack compile. Leave the signature on the artefact people act on — and keep journals off the unattended path entirely.",[208,962,964],{"id":963},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[191,966,967,968,404,970,973],{},"Nimbus ",[198,969,395],{"href":32},[198,971,972],{"href":40},"governance"," can host the standing-order pack and the sign-off room together: extract hash, locked plan version, run page, roster notification — and a separate job where the controller signs. Journals stay fail-closed.",[191,975,976,979,980,983],{},[198,977,978],{"href":510},"What is a Nimbus Loop"," is the product noun for the standing order. Score skip logs and recipe version with ",[198,981,982],{"href":869},"how to evaluate loop engineering"," before you let a Monday compile look like a close.",[985,986,987],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":171,"searchDepth":172,"depth":172,"links":989},[990,991,992,993,994,995,996],{"id":547,"depth":172,"text":548},{"id":607,"depth":172,"text":608},{"id":673,"depth":172,"text":674},{"id":729,"depth":172,"text":730},{"id":874,"depth":172,"text":875},{"id":904,"depth":172,"text":905},{"id":963,"depth":172,"text":964},"2026-09-12","A standing-order loop for finance is the unattended Monday pack when numbers move — not the collaborative forecast sign-off room. SOX reconstruction still applies to what the loop produced.",{"eyebrow":1000,"title":1001},"Common questions","Monday packs vs the sign-off room",[1003,1006,1009,1012],{"question":1004,"answer":1005},"Is a standing-order loop the same as the planning sign-off meeting?","No. Sign-off is collaborative AI — controller, FP&A, partner, named signer. A standing-order loop compiles the Monday pack or reacts when actuals move, and skips when nothing material changed. It produces the draft pack and the exception list. It does not post journals and it does not sign the number people will manage against. If you collapse the two, you either get an unattended post or a meeting that still starts from a chat ritual. Automate the compile. Leave the signature on the artefact people act on.",{"question":1007,"answer":1008},"Does SOX apply to a loop that only reads the ERP?","The loops outputs can become management truth before anything posts. If leaders act on the pack, you need the same reconstruction test: what ran, on which extract, with what skip log. Sarbanes-Oxley does not mention standing orders. It asks issuers for internal control over financial reporting — a trail showing how a number became the number. You do not need to be an issuer for that test to bite. A fluent variance commentary is not that trail. Retention on run logs should match how long you must explain the number.",{"question":1010,"answer":1011},"What is the difference between a standing-order loop and an eval loop?","A standing-order loop is an operator recipe that admits a run when a trigger fires. An eval loop is a harness sensor — schema check, read-back, human gate — that grades whether the job finished correctly. After a signed journal, the eval loop asks whether accounts and amounts match the ERP. That sensor is not the Monday pack. An agentic workflow is the third noun: open-ended replan, such as close the books with no saved recipe. Do not collapse the three because a slide said loops.",{"question":1013,"answer":1014},"Can the loop email the line their new target?","No. Partner-facing numbers belong in the collaborative room, not in an email the standing order generates. If the loop notifies the line, restrict it to pack ready — not your new target. That distinction keeps unattended compile separate from management commitment. A forecast can become a hiring freeze weeks before it is a ledger entry. Put a name on the artefact people act on, not only on the post.","\u002Fblog\u002Floops-for-finance-and-planning",{"title":451,"description":998},"use-case","blog\u002Floops-for-finance-and-planning",[1017,1020,1021,1022,1023],"finance","FP&A","loops","planning","aZM01FaAac4-SKaA6xSdi1RT5SUa3dldoE6yjJM4uRA",{"id":1026,"title":1027,"archived":165,"authors":1028,"badge":1030,"body":1031,"date":997,"definedTerm":166,"department":166,"description":1547,"extension":174,"eyebrow":166,"faqHeader":1548,"faqs":1550,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1562,"relatedHeading":166,"seo":1563,"series":1017,"sitemap":131,"status":166,"stem":1564,"subhead":166,"tags":1565,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1569},"content\u002Fblog\u002Floops-for-legal-and-compliance.md","Loops for Legal and Compliance",[1029],{"name":185,"to":136},{"label":187},{"type":168,"value":1032,"toc":1538},[1033,1046,1059,1061,1086,1089,1093,1097,1116,1130,1141,1144,1148,1158,1161,1176,1195,1197,1211,1222,1224,1266,1269,1273,1276,1281,1286,1291,1295,1326,1331,1334,1339,1344,1350,1402,1407,1409,1412,1430,1433,1438,1458,1462,1472,1475,1493,1496,1515,1518,1520,1528,1536],[191,1034,1035,1036,1039,1040,1045],{},"Legal and compliance already watch incoming paper and policy changes — or they mean to. Customer paper lands in a folder. A playbook PDF is replaced. A regulator feed publishes. Sales learns “legal is comfortable” from a retrieval snippet. Incoming MSAs sit until someone remembers. The failure mode is fluency treated as review, and a watch that ",[470,1037,1038],{},"guesses"," which version applies instead of escalating. The ",[198,1041,1044],{"href":1042,"rel":1043},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2024\u002F1689\u002Foj",[225],"EU Artificial Intelligence Act"," (Regulation (EU) 2024\u002F1689, 2024) is not a clause playbook; it is a reminder that automated systems carry duties chat etiquette does not satisfy.",[191,1047,468,1048,1050,1051,1054,1055,411],{},[470,1049,472],{},", not the shared collaborative room where legal, sales, and compliance quote a clause, pin a playbook version, and a named lawyer refuses or signs. The standing order watches a clause source, a policy repository, or an incoming file queue. It quotes or hashes what changed, compares it to the version on the job, and ",[470,1052,1053],{},"escalates",". It does not approve send. It does not paraphrase the clause into “legal OK.” For that room, read ",[198,1056,1058],{"href":1057},"collaborative-ai-for-legal-and-compliance-review","collaborative AI for legal and compliance review",[191,1060,484],{},[242,1062,1063,1070,1079],{},[245,1064,1065,1067,1068,411],{},[470,1066,491],{}," — a completion sensor. Did the sent message match the signed payload hash? See ",[198,1069,496],{"href":495},[245,1071,1072,1074,1075,507,1077,512],{},[470,1073,501],{}," — a compiled watch that admits a run when a trigger fires. See ",[198,1076,506],{"href":505},[198,1078,511],{"href":510},[245,1080,1081,1083,1084,411],{},[470,1082,517],{}," — open-ended replan, such as “review this contract” with no quote, version, or rejector. See ",[198,1085,522],{"href":521},[191,1087,1088],{},"A watch that logs what it saw is more useful than a bot that guesses comfort. Escalate. Do not guess.",[208,1090,1092],{"id":1091},"what-a-legal-and-compliance-standing-order-loop-is","What a legal and compliance standing-order loop is",[191,1094,551,1095,556],{},[198,1096,555],{"href":554},[336,1098,1099,1105,1110],{},[245,1100,1101,1104],{},[470,1102,1103],{},"When the policy changes"," — playbook PDF updated, wiki revision, grid effective date crossed.",[245,1106,1107,1109],{},[470,1108,575],{}," — customer paper in the intake folder, vendor MSA upload, RFP attachment.",[245,1111,1112,1115],{},[470,1113,1114],{},"When the clause source moves"," — standard terms URL changed, registry filing published, regulator update feed.",[191,1117,1118,1119,1122,1123,1126,1127,1129],{},"The job is narrow: detect the start, ",[470,1120,1121],{},"quote or hash"," what changed, compare to the version pinned on the job, and ",[470,1124,1125],{},"escalate"," — open a collaborative matter or notify the named lawyer roster. It does not approve send. ",[198,1128,591],{"href":590},": the standing order does not bind the company.",[191,1131,1132,1133,1136,1137,1140],{},"Do not let the watch ",[470,1134,1135],{},"guess"," which playbook applies when three PDFs share a title. Escalate with the diff and let the lawyer pick the version on the collaborative job. Retrieval that prefers an obsolete doc because it ranked well is a harness failure, not a legal skill issue. ",[198,1138,1139],{"href":352},"What is harness engineering"," covers pinning versions on the job.",[191,1142,1143],{},"Skip when the file is a duplicate of an open matter, or when the policy diff is empty. That skip is a first-class outcome. A watch that always opens a matter trains lawyers to ignore it. A watch that writes “skipped: hash matches open matter” is evidence you are not paging people for theatre.",[208,1145,1147],{"id":1146},"why-legal-should-care","Why legal should care",[191,1149,1150,1151,1154,1155,411],{},"Because fluency is not review, and ",[470,1152,1153],{},"watching"," is not ",[470,1156,1157],{},"signing",[191,1159,1160],{},"Legal is often late because nobody routed the matter — not because the model cannot summarise. A standing order fixes routing: file landed, policy delta detected, matter opened with sources attached. The collaborative room fixes substance: quote, version, named rejector, send gate.",[191,1162,1163,1164,1169,1170,1175],{},"In February 2024 Air Canada was held to chatbot-invented fare terms — ",[198,1165,1168],{"href":1166,"rel":1167},"https:\u002F\u002Fwww.cbc.ca\u002Fnews\u002Fcanada\u002Fbritish-columbia\u002Fair-canada-chatbot-lawsuit-1.7116416",[225],"CBC News",", decision ",[198,1171,1174],{"href":1172,"rel":1173},"https:\u002F\u002Fdecisions.civilresolutionbc.ca\u002Fcrt\u002Fcrtd\u002Fen\u002F525448\u002F1\u002Fdocument.do",[225],"Moffatt v. Air Canada",". A watch would not have saved that alone; a send gate on customer-facing claims would. Standing orders and collaborative review are complementary: detect and route fast; refuse and sign in the room.",[191,1177,1178,1179,1184,1185,1188,1189,1194],{},"NIST’s ",[198,1180,1183],{"href":1181,"rel":1182},"https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fai-risk-management-framework",[225],"AI Risk Management Framework"," (2023) maps govern-measure-manage for AI systems. A watch that logs triggers and skips is a ",[470,1186,1187],{},"measure"," input. It is not a substitute for a named rejector on Tuesday’s concession. In June 2023 a New York federal judge sanctioned two lawyers who filed a brief citing cases ",[198,1190,1193],{"href":1191,"rel":1192},"https:\u002F\u002Fwww.reuters.com\u002Flegal\u002Fnew-york-lawyers-sanctioned-using-fake-chatgpt-cases-legal-brief-2023-06-22\u002F",[225],"ChatGPT had invented",". Fiction had been written into a court record. The analogue here is “legal OK” written into a CRM field because a summary ranked well.",[191,1196,645],{},[242,1198,1199,1202,1205,1208],{},[245,1200,1201],{},"policy changes already arrive as email attachments and sales learns from a snippet",[245,1203,1204],{},"incoming MSAs sit in a folder until someone remembers",[245,1206,1207],{},"three playbook PDFs share a title and retrieval picks the obsolete one",[245,1209,1210],{},"customer-facing claims leave the building without a send gate",[191,1212,1213,1216,1217,1221],{},[198,1214,1215],{"href":664},"What is write-back governance"," stays on customer messages, contract repositories, and CRM terms fields. ",[198,1218,1220],{"href":1219},"what-is-ai-governance","What is AI governance"," is the wider map.",[208,1223,674],{"id":673},[242,1225,1226,1232,1238,1244,1250,1256,1261],{},[245,1227,1228,1231],{},[470,1229,1230],{},"Quote."," The clause as written, extracted — not a paraphrase.",[245,1233,1234,1237],{},[470,1235,1236],{},"Pinned playbook version."," The version the watch diffs against. Not “the legal PDF.”",[245,1239,1240,1243],{},[470,1241,1242],{},"Diff."," What changed between pinned version and new source, as an artefact.",[245,1245,1246,1249],{},[470,1247,1248],{},"Escalate."," Open a collaborative matter or notify the named roster. Do not guess.",[245,1251,1252,1255],{},[470,1253,1254],{},"Skip."," Duplicate hash or empty diff, recorded with a reason.",[245,1257,1258,1260],{},[470,1259,711],{}," After send, did the message match the signed payload?",[245,1262,1263,1265],{},[470,1264,717],{}," “Handle contracts” with no saved escalation path.",[191,1267,1268],{},"Regulators and general counsel reconstruct matters, not token traces. Your watch should produce: file hash, quoted sections, playbook version pinned, diff summary, skip log, matter id opened. Engineers may need traces for debugging; the company needs the matter record.",[208,1270,1272],{"id":1271},"how-to-compile-one-legal-standing-order","How to compile one legal standing order",[191,1274,1275],{},"Start from intake people already perform badly when busy.",[191,1277,736,1278],{},[470,1279,1280],{},"Incoming customer paper",[191,1282,1283,1285],{},[470,1284,744],{}," file lands in the legal-intake folder with extension pdf or docx.",[191,1287,1288,1290],{},[470,1289,754],{}," job pinned to current playbook version; roster includes the duty lawyer.",[191,1292,1293],{},[470,1294,760],{},[336,1296,1297,1302,1309,1316,1319],{},[245,1298,1299,1300,771],{},"Hash file; if duplicate of open matter, ",[470,1301,586],{},[245,1303,1304,1305,1308],{},"Extract ",[470,1306,1307],{},"quoted"," limitation-of-liability and data-processing sections — not summary-only.",[245,1310,1311,1312,1315],{},"Compare keywords against pinned playbook sections; flag deltas as ",[470,1313,1314],{},"questions",", not approvals.",[245,1317,1318],{},"Open a collaborative matter with quote, file, playbook version, and flag list.",[245,1320,1321,1322,1325],{},"Notify the named roster. ",[470,1323,1324],{},"Disable send"," on any draft until a lawyer joins the matter.",[191,1327,1328,1330],{},[470,1329,792],{}," no customer email; no CRM “legal approved” field; no auto-redline send.",[191,1332,1333],{},"When policy changes:",[191,1335,1336,1338],{},[470,1337,744],{}," playbook repository commit or effective date.",[191,1340,1341,1343],{},[470,1342,760],{}," diff old vs new pinned version; list clauses affected; open matters for templates that reference changed sections; skip if diff empty.",[191,1345,1346,1347,411],{},"Write-back — customer messages, contract repositories, CRM terms fields — stays on the collaborative path with ",[198,1348,1349],{"href":664},"write-back governance",[809,1351,1353],{"className":811,"code":1352,"language":813,"meta":171,"style":171},"flowchart TD\n  watchTrigger[\"Policy changes or a file lands\"] --> seen{\"Already seen this file?\"}\n  seen -->|yes| skipLegal[\"Skip, logged\"]\n  seen -->|no| quoteExtract[\"Quote the key clauses\"]\n  quoteExtract --> diffPlaybook[\"Compare to the pinned playbook\"]\n  diffPlaybook --> escalate[\"Open a review matter\"]\n  escalate --> notifyLawyer[\"Notify the named lawyer\"]\n  escalate --> reviewRoom[\"Collaborative review\"]\n  reviewRoom -->|signed| sendGate[\"Send or write\"]\n",[815,1354,1355,1360,1365,1370,1375,1380,1385,1390,1396],{"__ignoreMap":171},[818,1356,1357],{"class":820,"line":821},[818,1358,1359],{},"flowchart TD\n",[818,1361,1362],{"class":820,"line":172},[818,1363,1364],{},"  watchTrigger[\"Policy changes or a file lands\"] --> seen{\"Already seen this file?\"}\n",[818,1366,1367],{"class":820,"line":832},[818,1368,1369],{},"  seen -->|yes| skipLegal[\"Skip, logged\"]\n",[818,1371,1372],{"class":820,"line":838},[818,1373,1374],{},"  seen -->|no| quoteExtract[\"Quote the key clauses\"]\n",[818,1376,1377],{"class":820,"line":844},[818,1378,1379],{},"  quoteExtract --> diffPlaybook[\"Compare to the pinned playbook\"]\n",[818,1381,1382],{"class":820,"line":850},[818,1383,1384],{},"  diffPlaybook --> escalate[\"Open a review matter\"]\n",[818,1386,1387],{"class":820,"line":856},[818,1388,1389],{},"  escalate --> notifyLawyer[\"Notify the named lawyer\"]\n",[818,1391,1393],{"class":820,"line":1392},8,[818,1394,1395],{},"  escalate --> reviewRoom[\"Collaborative review\"]\n",[818,1397,1399],{"class":820,"line":1398},9,[818,1400,1401],{},"  reviewRoom -->|signed| sendGate[\"Send or write\"]\n",[191,1403,1404,1406],{},[198,1405,870],{"href":869}," applies to watch loops too: can you replay why a matter opened, or why it skipped?",[208,1408,875],{"id":874},[191,1410,1411],{},"A good legal standing-order week:",[242,1413,1414,1421,1424,1427],{},[245,1415,1416,1417,1420],{},"Every new file either opened a matter with ",[470,1418,1419],{},"quotes"," or logged a skip with reason.",[245,1422,1423],{},"Policy-change runs produced a diff artefact, not a chat summary.",[245,1425,1426],{},"No customer send from the standing-order path.",[245,1428,1429],{},"A later reader can reconstruct intake without asking who “checked the bot.”",[191,1431,1432],{},"The signed review still lives on the collaborative job: quoted text, playbook version, rejector, send log. The standing order is the doorbell, not the judge.",[191,1434,1435,1437],{},[198,1436,266],{"href":265}," applies: outside counsel may see the matter, not every connector. Retention should match how long you must explain the language.",[191,1439,1440,1441,1444,1445,1448,1449,1453,1454,1457],{},"Website and support bots need the same escalation split: a watch may ",[470,1442,1443],{},"detect"," that public terms changed; the ",[470,1446,1447],{},"send"," of customer-facing language still routes to ",[198,1450,1452],{"href":1451},"collaborative-ai-for-customer-support","collaborative AI for customer support"," or the legal review room with a signer class. ",[198,1455,1174],{"href":1172,"rel":1456},[225]," is the reminder that the message can be the write.",[208,1459,1461],{"id":1460},"how-to-start-with-one-watch","How to start with one watch",[191,1463,908,1464,1467,1468,1471],{},[470,1465,1466],{},"file lands"," for one intake folder you already have — or ",[470,1469,1470],{},"policy change"," if version chaos is the pain.",[191,1473,1474],{},"Four weeks:",[336,1476,1477,1480,1487,1490],{},[245,1478,1479],{},"One folder or one playbook repo path.",[245,1481,1482,1483,1486],{},"Quote extraction plus diff against a ",[470,1484,1485],{},"pinned"," version — no approval language.",[245,1488,1489],{},"Automatic open of a collaborative matter with sources attached.",[245,1491,1492],{},"Zero sends from the standing order.",[191,1494,1495],{},"Measure: time from upload to lawyer on the matter; count of “legal OK” messages in side chat. If side chat wins, you built notification, not routing.",[191,1497,1498,404,1502,1505,1506,1508,1509,1511,1512,1514],{},[198,1499,1501],{"href":1500},"loops-for-finance-and-planning","Loops for finance and planning",[198,1503,1504],{"href":943},"loops for revenue operations"," cover packs and pipeline triggers. If you are still choosing the discipline, start with ",[198,1507,506],{"href":505}," and score a vendor with ",[198,1510,982],{"href":869}," before you let a watch open matters on its own. ",[198,1513,591],{"href":590}," is the rule that keeps the watch from drafting a customer email at 3am.",[191,1516,1517],{},"Watch faithfully. Escalate honestly. Leave the signature to the room where a lawyer can refuse.",[208,1519,964],{"id":963},[191,1521,967,1522,1524,1525,1527],{},[198,1523,395],{"href":32}," can host the watch and the review room: file hash, quoted clauses, pinned playbook, run page, and a collaborative matter the named lawyer can refuse. ",[198,1526,39],{"href":40}," is the send gate — not a prompt that says “ask legal.”",[191,1529,1530,1532,1533,1535],{},[198,1531,978],{"href":510}," is the product noun for the standing order. Score it with ",[198,1534,982],{"href":869}," before you let a watch look like review.",[985,1537,987],{},{"title":171,"searchDepth":172,"depth":172,"links":1539},[1540,1541,1542,1543,1544,1545,1546],{"id":1091,"depth":172,"text":1092},{"id":1146,"depth":172,"text":1147},{"id":673,"depth":172,"text":674},{"id":1271,"depth":172,"text":1272},{"id":874,"depth":172,"text":875},{"id":1460,"depth":172,"text":1461},{"id":963,"depth":172,"text":964},"A standing-order loop for legal watches clause sources, policy changes, and incoming files — then escalates to a person. It is not the collaborative clause-review room, and it must not guess.",{"eyebrow":1000,"title":1549},"Watchers vs the review room",[1551,1554,1557,1559],{"question":1552,"answer":1553},"Is a standing-order loop the same as shared legal review?","No. Review is collaborative AI — quoted clause, playbook version, named lawyer who can refuse. A standing-order loop watches for change or arrival and routes a matter; it does not approve language. It is the doorbell, not the judge. If you collapse the two, you get a watch that writes legal OK into chat, or a review room that never sees the file because nobody routed it. Detect and route fast. Refuse and sign in the room.",{"question":1555,"answer":1556},"Can the loop rewrite the clause if the policy changed?","No. Escalate to a person with the quote, the new policy version, and the diff. Drafting without a named rejector is how obsolete PDFs win because they ranked well. Do not let the loop guess which playbook applies when three PDFs share a title. Pin a version on the job and let the lawyer pick. Retrieval that prefers an obsolete doc is a harness failure, not a legal skill issue. The standing order quotes and flags. It does not bind the company.",{"question":1010,"answer":1558},"A standing-order loop is a watch that admits a run when a file lands or a policy changes. An eval loop is a harness sensor — for example, did the sent message match the signed payload — not a watch on incoming contracts. An agentic workflow is the third noun: review this contract with no quote, version, or rejector. Score the watch on whether you can replay why a matter opened or skipped. Score the send on whether the message matched the signed text.",{"question":1560,"answer":1561},"Can the loop send a customer email if the flags look clean?","No. Disable send on any draft until a named lawyer joins the matter. Clean flags are questions, not approvals. Air Canada was held to chatbot-invented fare terms with no CRM write. A watch would not have saved that alone; a send gate on customer-facing claims would. The standing order may open the matter with quotes attached. The collaborative room still refuses or signs. Zero sends from the loop path.","\u002Fblog\u002Floops-for-legal-and-compliance",{"title":1027,"description":1547},"blog\u002Floops-for-legal-and-compliance",[1017,1566,1567,1022,1568],"legal","compliance","policy","HuWs_EuMXxdW-9WB8YQhVQTlC0KN4Zl-NUriFdPYzCk",{"id":1571,"title":1572,"archived":165,"authors":1573,"badge":1575,"body":1576,"date":997,"definedTerm":166,"department":166,"description":2020,"extension":174,"eyebrow":166,"faqHeader":2021,"faqs":2023,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":2035,"relatedHeading":166,"seo":2036,"series":1017,"sitemap":131,"status":166,"stem":2037,"subhead":166,"tags":2038,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":2042},"content\u002Fblog\u002Floops-for-revenue-operations.md","Loops for Revenue Operations",[1574],{"name":185,"to":136},{"label":187},{"type":168,"value":1577,"toc":2011},[1578,1585,1595,1598,1623,1626,1630,1634,1652,1658,1661,1664,1677,1681,1684,1687,1698,1700,1714,1722,1724,1769,1772,1776,1779,1784,1792,1797,1801,1817,1822,1831,1837,1886,1895,1897,1900,1922,1925,1928,1935,1937,1947,1949,1966,1977,1989,1992,1994,2002,2009],[191,1579,1580,1581,1584],{},"Revenue operations already lives between systems. CRM says one Amount. The regional sheet says another. The AE’s message says “slipped.” Monday hygiene is the ritual that tries to list those conflicts before finance signs a number: missing close dates, stages that do not match activity, commit deals with no activity, duplicates. The failure mode is a fluent story that hides the disagreement — or an unattended job that “fixes” stages in bulk before anyone names who wins. McKinsey’s ",[198,1582,315],{"href":313,"rel":1583},[225]," (2025) finds AI adoption deep in commercial functions while scaling governance lags: hygiene still wins forecast quality, not a better paragraph.",[191,1586,468,1587,1589,1590,1592,1593,411],{},[470,1588,472],{},", not the shared collaborative room where RevOps, sales, and finance sign a forecast. The standing order runs when the opportunity moves, the sheet lands in the folder, or the calendar says Monday, and it ",[470,1591,476],{}," when nothing material changed. It produces the artefact the room needs — a conflict list, a hygiene CSV, a skip log — and stops. For the room that resolves conflicts and signs the number, read ",[198,1594,403],{"href":402},[191,1596,1597],{},"Three nouns get conflated in every vendor deck. Keep them as vocabulary, not as a product menu:",[242,1599,1600,1607,1616],{},[245,1601,1602,1604,1605,411],{},[470,1603,491],{}," — a sensor that grades a run after the fact. Did the write match the signed payload? See ",[198,1606,496],{"href":495},[245,1608,1609,1611,1612,507,1614,512],{},[470,1610,501],{}," — a compiled recipe that admits a run when a trigger fires. Trigger, steps, run record, notify. See ",[198,1613,506],{"href":505},[198,1615,511],{"href":510},[245,1617,1618,1620,1621,411],{},[470,1619,517],{}," — an interactive path that still reasons when the route is not fully known. See ",[198,1622,522],{"href":521},[191,1624,1625],{},"The hygiene and definitional work still wins forecast quality, not better paragraph generation. Automate the hygiene signal. Keep the number on the roster.",[208,1627,1629],{"id":1628},"what-a-revops-standing-order-loop-is","What a RevOps standing-order loop is",[191,1631,551,1632,556],{},[198,1633,555],{"href":554},[336,1635,1636,1642,1647],{},[245,1637,1638,1641],{},[470,1639,1640],{},"When the opportunity moves"," — stage, close date, or Amount changes in CRM against the rule set finance cares about.",[245,1643,1644,1646],{},[470,1645,575],{}," — the regional sheet appears in the shared location with yesterday’s timestamp.",[245,1648,1649,1651],{},[470,1650,563],{}," — the hygiene list: missing fields, duplicates, commit deals with no activity.",[191,1653,1654,1655,1657],{},"The job is narrow: detect that start, run the saved steps, produce the artefact the room needs, and stop. It does not resolve conflicts. Resolution has a name on the collaborative job. ",[198,1656,591],{"href":590},": the standing order does not negotiate with sales. It runs the recipe or skips.",[191,1659,1660],{},"Deterministic triggers matter more here than model routing. If the start condition is fuzzy, you will run every Monday even when nothing moved — or miss the week the sheet arrived on Tuesday. Prefer sensors you can explain to finance: field delta, file mtime, calendar with a timezone.",[191,1662,1663],{},"Skip when nothing changed. That skip is a first-class outcome. A loop that always produces a narrative trains people to ignore it. A loop that writes “skipped: no delta since last run” is evidence you are not burning tokens for theatre.",[191,1665,1666,1667,1671,1672,1676],{},"Compare ",[198,1668,1670],{"href":1669},"loop-vs-workflow-vs-agent","loop vs workflow vs agent",": the standing order is the deployed, unattended instance; the collaborative forecast is the human-stopped workflow; an agent is the reasoning actor for unknown branches. ",[198,1673,1675],{"href":1674},"loop-vs-rpa","Loop vs RPA"," is the cousin when someone still wants a bot to click the CRM screen.",[208,1678,1680],{"id":1679},"why-revops-should-care","Why RevOps should care",[191,1682,1683],{},"Because the conflict is the work, and unattended listing is the part worth automating.",[191,1685,1686],{},"RevOps already pays a reinterpretation tax every week. Someone re-exports. Someone else filters a different region. Audit — or just next quarter’s new hire — asks what ran last Monday and the answer is “ask Sarah.” A personal script, a fragile Zap, or a heroic analyst export can produce a list. They rarely produce a skip log, a recipe version, and a run record the controller would recognise.",[191,1688,1689,1690,1693,1694,1697],{},"The failure mode for automation is picking the fluent story. The model summarises “pipeline is healthy” while Amount still disagrees with the sheet. Or the automation writes stages in bulk because the demo looked tidy. The collaborative room exists so ",[470,1691,1692],{},"resolution"," stays human and signed. The standing order exists so ",[470,1695,1696],{},"detection and listing"," do not depend on someone remembering to export.",[191,1699,645],{},[242,1701,1702,1705,1708,1711],{},[245,1703,1704],{},"Monday hygiene already happens in a personal script, a Zap, or an export nobody can replay",[245,1706,1707],{},"Amount disagrees with the board pack and nobody can tell what ran last week",[245,1709,1710],{},"“CRM fixes” still happen in side chats after the list exists",[245,1712,1713],{},"finance opens the meeting by asking whether the sheet arrived",[191,1715,1716,1718,1719,1721],{},[198,1717,205],{"href":204}," remains the definition for the room. This page is only the standing order beside it. ",[198,1720,870],{"href":869}," is the buying sheet: triggers, skip logs, and replay matter more than eloquence.",[208,1723,674],{"id":673},[242,1725,1726,1732,1738,1743,1749,1755,1764],{},[245,1727,1728,1731],{},[470,1729,1730],{},"Trigger."," What admits a run: field change, file landing, Monday calendar, manual start.",[245,1733,1734,1737],{},[470,1735,1736],{},"Compiled recipe."," The fixed steps for this hygiene job. Not “fix pipeline.”",[245,1739,1740,1742],{},[470,1741,1254],{}," A deliberate halt when nothing changed or preconditions failed. Recorded, not hidden.",[245,1744,1745,1748],{},[470,1746,1747],{},"Run record."," What ran, on which scope, with which recipe version, what was produced or skipped.",[245,1750,1751,1754],{},[470,1752,1753],{},"Write-back."," A CRM field change. Default off for the standing order.",[245,1756,1757,1759,1760,1763],{},[470,1758,711],{}," The sensor ",[597,1761,1762],{},"after"," a signed write: read-back Amount matches the payload.",[245,1765,1766,1768],{},[470,1767,717],{}," Open-ended replan — “make pipeline healthy” with no saved recipe.",[191,1770,1771],{},"Do not collapse those last two with the standing order because a slide said “agentic loops.” Ask what starts the run, what is compiled, and what grades the finish.",[208,1773,1775],{"id":1774},"how-to-compile-one-revops-standing-order","How to compile one RevOps standing order",[191,1777,1778],{},"Start from a job people already run without the model.",[191,1780,736,1781],{},[470,1782,1783],{},"Monday hygiene for Region West",[191,1785,1786,1788,1789,1791],{},[470,1787,744],{}," Monday 07:00 Europe\u002FLondon ",[470,1790,748],{}," manual “run hygiene.”",[191,1793,1794,1796],{},[470,1795,754],{}," read-only CRM connection scoped to West pipeline; last-run timestamp stored.",[191,1798,1799],{},[470,1800,760],{},[336,1802,1803,1806,1811,1814],{},[245,1804,1805],{},"Query opportunities missing close date, stage inconsistent with last activity, Amount null.",[245,1807,1808,1809,771],{},"Compare to last run’s id set. If identical, ",[470,1810,586],{},[245,1812,1813],{},"If delta, write the hygiene list and attach a CSV.",[245,1815,1816],{},"Notify the RevOps roster — not the whole company.",[191,1818,1819,1821],{},[470,1820,792],{}," no stage writes; no customer email; no forecast number.",[191,1823,1824,1825,1827,1828,1830],{},"When a row needs a CRM write, open or update the ",[470,1826,799],{}," forecast job for that week. The standing order may attach the hygiene list there. Finance still signs the number in the room. ",[198,1829,665],{"href":664}," applies to the write, not to the read-only list.",[191,1832,803,1833,1836],{},[470,1834,1835],{},"when Amount moves",". Trigger on field delta against finance’s rule set. Produce a conflict row with both CRM and sheet values if the sheet trigger also fired. Do not average them. Do not pick the fluent story. List both. Name who wins on the collaborative job.",[809,1838,1840],{"className":811,"code":1839,"language":813,"meta":171,"style":171},"flowchart TD\n  trigger[\"Opportunity moved or Monday\"] --> precheck{\"Ready to run?\"}\n  precheck -->|no| skipLog[\"Skip with a reason\"]\n  precheck -->|yes| delta{\"Anything changed?\"}\n  delta -->|no| skipLog\n  delta -->|yes| recipe[\"Run the saved recipe\"]\n  recipe --> runPage[\"Outputs on the run page\"]\n  runPage --> notify[\"Notify the roster\"]\n  runPage --> collabRoom[\"Forecast room, if needed\"]\n",[815,1841,1842,1846,1851,1856,1861,1866,1871,1876,1881],{"__ignoreMap":171},[818,1843,1844],{"class":820,"line":821},[818,1845,1359],{},[818,1847,1848],{"class":820,"line":172},[818,1849,1850],{},"  trigger[\"Opportunity moved or Monday\"] --> precheck{\"Ready to run?\"}\n",[818,1852,1853],{"class":820,"line":832},[818,1854,1855],{},"  precheck -->|no| skipLog[\"Skip with a reason\"]\n",[818,1857,1858],{"class":820,"line":838},[818,1859,1860],{},"  precheck -->|yes| delta{\"Anything changed?\"}\n",[818,1862,1863],{"class":820,"line":844},[818,1864,1865],{},"  delta -->|no| skipLog\n",[818,1867,1868],{"class":820,"line":850},[818,1869,1870],{},"  delta -->|yes| recipe[\"Run the saved recipe\"]\n",[818,1872,1873],{"class":820,"line":856},[818,1874,1875],{},"  recipe --> runPage[\"Outputs on the run page\"]\n",[818,1877,1878],{"class":820,"line":1392},[818,1879,1880],{},"  runPage --> notify[\"Notify the roster\"]\n",[818,1882,1883],{"class":820,"line":1398},[818,1884,1885],{},"  runPage --> collabRoom[\"Forecast room, if needed\"]\n",[191,1887,1888,1890,1891,1894],{},[198,1889,266],{"href":265}," belongs here: the standing order runs with ",[470,1892,1893],{},"read"," grants. It does not inherit a human’s write token.",[208,1896,875],{"id":874},[191,1898,1899],{},"A good RevOps standing-order week:",[242,1901,1902,1909,1916,1919],{},[245,1903,1904,1905,1908],{},"The hygiene list exists ",[470,1906,1907],{},"only if"," something changed — or a skip log says why not.",[245,1910,1911,1912,1915],{},"Conflicts are visible with ",[470,1913,1914],{},"both"," CRM and sheet values when the sheet trigger fired.",[245,1917,1918],{},"No CRM field changed without a collaborative sign.",[245,1920,1921],{},"A new team member can open last Monday’s run and reconstruct what ran without asking the hero who “owns the script.”",[191,1923,1924],{},"The signed forecast still lives on the collaborative job: number, definition, signer, accepted conflicts. The standing order feeds that job. It does not replace it.",[191,1926,1927],{},"Measure: Did finance open the list before the forecast meeting? Did side-chat “CRM fixes” fall? If not, you built another report. Keep a run-log habit the controller would recognise: trigger type, scope, row counts, skip reason, recipe version. When board week goes wrong, you want to open 14 September’s run — not Slack.",[191,1929,1930,1931,1934],{},"That log is also the bridge to ",[470,1932,1933],{},"eval loops"," on the write path: the list is feed-forward; the read-back after sign is the oracle. Do not collapse them because both contain the word “loop.”",[208,1936,905],{"id":904},[191,1938,1939,1940,1942,1943,1946],{},"Pick one start from ",[198,1941,555],{"href":554},". ",[470,1944,1945],{},"File lands"," is often easiest — the sheet already has a ritual.",[191,1948,1474],{},[336,1950,1951,1954,1960,1963],{},[245,1952,1953],{},"Read-only CRM plus folder watch for one region’s sheet.",[245,1955,1956,1957,411],{},"A conflict or hygiene list with ",[470,1958,1959],{},"skip when unchanged",[245,1961,1962],{},"Outputs on a run record, not in email only.",[245,1964,1965],{},"No CRM writes from the standing order — zero.",[191,1967,1968,1971,1972,404,1974,1976],{},[198,1969,1970],{"href":480},"Collaborative AI for finance and planning"," may consume the same hygiene output when pipeline disputes affect the number finance signs. ",[198,1973,1501],{"href":1500},[198,1975,948],{"href":947}," are the sibling patterns when the trigger is a close pack or a policy file.",[191,1978,1979,1980,1982,1983,1985,1986,1988],{},"If you are still naming the object, ",[198,1981,506],{"href":505}," is the discipline and ",[198,1984,982],{"href":869}," is how you refuse a vendor that cannot skip. ",[198,1987,591],{"href":590}," is why hygiene should not invent a stage change.",[191,1990,1991],{},"Unattended work should be boring: same recipe, honest skip, a run record audit trail. Leave the forecast number to the room where someone signs.",[208,1993,964],{"id":963},[191,1995,967,1996,1998,1999,2001],{},[198,1997,395],{"href":32}," can host the standing-order loop and the collaborative forecast room side by side: trigger, compiled recipe, run page, roster notification — and a separate job where finance signs the number. ",[198,2000,39],{"href":40}," stays on the CRM write, not on the read-only hygiene list.",[191,2003,2004,1532,2006,2008],{},[198,2005,978],{"href":510},[198,2007,982],{"href":869}," before you let it touch stages.",[985,2010,987],{},{"title":171,"searchDepth":172,"depth":172,"links":2012},[2013,2014,2015,2016,2017,2018,2019],{"id":1628,"depth":172,"text":1629},{"id":1679,"depth":172,"text":1680},{"id":673,"depth":172,"text":674},{"id":1774,"depth":172,"text":1775},{"id":874,"depth":172,"text":875},{"id":904,"depth":172,"text":905},{"id":963,"depth":172,"text":964},"A standing-order loop for RevOps is unattended hygiene when the opportunity moves, the file lands, or Monday is due — not the shared forecast room. Skip when nothing changed.",{"eyebrow":1000,"title":2022},"Standing orders vs the forecast room",[2024,2027,2029,2032],{"question":2025,"answer":2026},"Is a standing-order loop the same as the weekly forecast meeting?","No. The meeting is collaborative AI — conflicts, a named finance signer, a signed number. A standing-order loop is the unattended recipe that runs when data moves or the calendar says Monday, and skips when nothing material changed. It produces the list the room needs. It does not resolve conflicts and it does not sign the forecast. If you collapse the two, you either get a bot that rewrites stages before a signer exists, or a meeting that still starts with a heroic export. Keep listing unattended. Keep the number on the roster.",{"question":1010,"answer":2028},"An eval loop is a sensor that checks whether a harness job finished correctly — tests, read-backs, payload hash. A standing-order loop is an operator recipe that admits a run when a trigger fires: detect change, run saved steps, land outputs, notify the roster. An agentic workflow is the third noun: an interactive path that still reasons when the route is not fully known. Vendors blur all three because they contain the word loop or the word agent. Ask what starts the run, what is compiled, and what grades the finish. Those are three jobs.",{"question":2030,"answer":2031},"Should the loop fix CRM stages on its own?","List and draft first. Treat stage or Amount changes as write-back. If nobody approves on the collaborative job, nothing happens in CRM — even if the loop flagged the row. Bulk cosmetics before a signer exists are how data goes wrong quickly. The loop may attach the hygiene list to the forecast job for that week. Finance still signs the number in the room. A loop that inherits a humans write token is not a standing order. It is an unattended clerk.",{"question":2033,"answer":2034},"What does a good skip look like?","A skip is a first-class outcome: the trigger fired, preconditions were checked, nothing material changed, and the run page says so. A loop that always produces a narrative trains people to ignore it. A loop that writes skipped, no delta since last run is evidence you are not burning tokens for theatre. Ten runs with unchanged inputs should produce ten skip records and zero spurious writes. If Finance still got paged, you built an alert, not a standing order.","\u002Fblog\u002Floops-for-revenue-operations",{"title":1572,"description":2020},"blog\u002Floops-for-revenue-operations",[1017,2039,1022,2040,2041],"RevOps","pipeline","CRM","AIiSyje3ZsKCEAyuwW_39_gz20h7-427-Sy5APLE0TI",{"id":2044,"title":2045,"archived":165,"authors":2046,"badge":2048,"body":2049,"date":997,"definedTerm":166,"department":166,"description":2467,"extension":174,"eyebrow":166,"faqHeader":2468,"faqs":2470,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":2483,"relatedHeading":166,"seo":2484,"series":442,"sitemap":131,"status":166,"stem":2485,"subhead":166,"tags":2486,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":2491},"content\u002Fblog\u002Fcollaborative-ai-for-customer-support.md","What is collaborative AI for customer support?",[2047],{"name":185,"to":136},{"label":187},{"type":168,"value":2050,"toc":2458},[2051,2054,2064,2075,2079,2082,2110,2113,2123,2127,2130,2143,2150,2163,2165,2208,2213,2217,2220,2223,2243,2246,2274,2277,2288,2297,2346,2350,2353,2360,2363,2381,2392,2396,2399,2401,2415,2418,2427,2438,2441,2443,2451,2456],[191,2052,2053],{},"Customer support already has a path for when the playbook runs out. The frontline agent knows the customer, the ticket history, and what was promised in this thread. A specialist knows the product edge case, the known defect, the escalation path. A named person — team lead, billing ops, or a delegate with a spend limit — can issue a credit or a policy exception. Sometimes legal joins when the words might bind the company. The failure mode is a commitment without a signer, and fluency mistaken for resolution.",[191,2055,2056,2057,1169,2060,2063],{},"In February 2024 the Civil Resolution Tribunal of British Columbia held Air Canada to a bereavement fare its chatbot had invented — reported by ",[198,2058,1168],{"href":1166,"rel":2059},[225],[198,2061,1174],{"href":1172,"rel":2062},[225],". No CRM write was required. The message was the write. That caution belongs in the first screen of every support AI conversation: the customer-facing sentence is often the system of record for the relationship.",[191,2065,2066,2067,2069,2070,2074],{},"This guide is about one shared exception case — not a project to replace the helpdesk with a bot that closes tickets faster, and not a deflection metric. ",[198,2068,205],{"href":204}," is the definition. ",[198,2071,2073],{"href":2072},"collaborative-ai-and-personal-assistants","Collaborative AI and personal assistants"," is when an agent’s private draft should stay private until there is a case.",[208,2076,2078],{"id":2077},"what-collaborative-ai-for-support-actually-is","What collaborative AI for support actually is",[191,2080,2081],{},"Support already has roles before anyone mentions a model. Collaborative AI puts those people on one job with the same ticket view and the same policy.",[242,2083,2084,2091,2097,2104],{},[245,2085,2086,2087,2090],{},"The ",[470,2088,2089],{},"agent"," keeps the customer voice accurate, attaches context, and does not sign credits above their limit.",[245,2092,2086,2093,2096],{},[470,2094,2095],{},"specialist"," proposes product facts and cannot override billing policy without an approver.",[245,2098,2099,2100,2103],{},"A ",[470,2101,2102],{},"named approver"," rejects or signs the exact credit or policy exception — amount, currency, reason code, tax treatment.",[245,2105,2106,2109],{},[470,2107,2108],{},"Legal or compliance"," joins when the words might bind, and can refuse the send.",[191,2111,2112],{},"The AI role is named: it may read this case and this knowledge article; it may draft the customer reply and the credit memo; it may not post the refund; it may not state a fare-like rule on the website without a signer class. Attach the approver to the case before the model proposes money.",[191,2114,2115,2116,2119,2120,2122],{},"A ticket closed without the exception recorded is a metric, not a job. Write-back is when AI changes a live system — a billing credit, a subscription change, a CRM field the customer can see. It also includes ",[470,2117,2118],{},"customer messages that bind"," when the customer could rely on the sentence. Fail-closed means if nobody approves, nothing happens. ",[198,2121,1215],{"href":664}," is the control on that step.",[208,2124,2126],{"id":2125},"why-a-commitment-without-a-signer-is-the-failure","Why a commitment without a signer is the failure",[191,2128,2129],{},"The usual pattern inside the company is softer than Air Canada and just as familiar. An agent asks a personal assistant to “draft the apology and 15% credit.” The draft is polished. Billing never sees the amount. The customer replies “thanks for the $40 credit” when the draft said 15% of an unclear base. The specialist learns on Friday.",[191,2131,2132,2133,2138,2139,2142],{},"Zendesk’s ",[198,2134,2137],{"href":2135,"rel":2136},"https:\u002F\u002Fcxtrends.zendesk.com\u002F",[225],"Customer Experience Trends Report"," tracks rising expectations for personalised support and AI-assisted agents — alongside pressure on first-contact resolution. Speed without a shared case recreates the DM problem: a fluent answer in a private window that the next shift cannot find. McKinsey’s ",[198,2140,315],{"href":313,"rel":2141},[225]," (2025) shows the same gap at the industry level: adoption in customer-facing functions outruns the shared process behind the reply.",[191,2144,2145,2146,2149],{},"The common belief is that AI should ",[470,2147,2148],{},"replace tier-one"," and free humans for hard cases. Replacement without a shared case and a named exception path scales the wrong failure: tidy closure in the tool, messy truth in billing and in the customer’s inbox. Collaborative AI is the opposite pattern — keep the humans on exceptions, automate the listing and drafting inside a room everyone can reopen.",[191,2151,2152,2155,2156,2158,2159,2162],{},[198,2153,2154],{"href":1057},"Collaborative AI for legal and compliance review"," is the sibling when the artefact is binding language. ",[198,2157,669],{"href":402}," is the pattern when the case affects forecast or renewal truth. ",[198,2160,2161],{"href":329},"Decisions made in direct messages"," is the failure this page is trying to stop on the helpdesk.",[208,2164,674],{"id":673},[242,2166,2167,2173,2179,2185,2190,2196,2202],{},[245,2168,2169,2172],{},[470,2170,2171],{},"Exception."," The case the playbook does not finish: a credit, an SLA breach, a policy statement that sounds like a fare.",[245,2174,2175,2178],{},[470,2176,2177],{},"Named approver."," The identity with a spend limit or a policy-exception grant. “Whoever is on chat” is not a signer.",[245,2180,2181,2184],{},[470,2182,2183],{},"Payload."," The exact credit or the exact customer sentence, shown before it lands.",[245,2186,2187,2189],{},[470,2188,1753],{}," A change to billing, CRM, subscription, or a message the customer can rely on.",[245,2191,2192,2195],{},[470,2193,2194],{},"Fail-closed."," Missing approval means nothing posts and nothing sends.",[245,2197,2198,2201],{},[470,2199,2200],{},"Deflection."," Closing a ticket without recording the exception. A metric, not a job.",[245,2203,2204,2207],{},[470,2205,2206],{},"Signer class."," The same bar you would use for an agent email, applied to a website bot.",[191,2209,2210,2212],{},[198,2211,1220],{"href":1219}," is the wider programme. This page is the support subset: one case, one exception, one name on the money or the sentence.",[208,2214,2216],{"id":2215},"how-to-use-ai-on-tickets-without-losing-the-exception-path","How to use AI on tickets without losing the exception path",[191,2218,2219],{},"Ask the model for a case summary and a proposed payload, not an unsupervised close.",[191,2221,2222],{},"Put on the job:",[242,2224,2225,2231,2237],{},[245,2226,2086,2227,2230],{},[470,2228,2229],{},"ticket or case id",", read-only, with the thread the customer can see.",[245,2232,2086,2233,2236],{},[470,2234,2235],{},"policy or macro version"," that applies — refunds, SLAs, goodwill limits — with a date.",[245,2238,2086,2239,2242],{},[470,2240,2241],{},"billing or subscription view",", read-only, if money moves.",[191,2244,2245],{},"Then:",[336,2247,2248,2255,2262,2268,2271],{},[245,2249,2250,2251,2254],{},"Generate a ",[470,2252,2253],{},"draft reply"," that cites those sources, not a private rewrite.",[245,2256,2257,2258,2261],{},"If money moves, show the ",[470,2259,2260],{},"exact credit",": amount, currency, reason code, tax treatment.",[245,2263,2264,2265,2267],{},"Assign the ",[470,2266,2102],{}," on the roster before the write is possible.",[245,2269,2270],{},"Treat a billing post as write-back with a payload: before and after.",[245,2272,2273],{},"Keep fail-closed: if nobody approves, nothing posts and the customer message does not send.",[191,2275,2276],{},"Do not start with unsupervised auto-close for exceptions above your threshold. Do not let the website bot state prices, fares, or cancellation rules without the same signer class you would use for an agent email. Air Canada did not need a CRM API. The sentence was enough.",[191,2278,2279,2280,2282,2283,2287],{},"The harness — the tools, stops, and checks around the model — is what keeps “just refund them” from becoming an unsupervised clerk. ",[198,2281,1139],{"href":352}," is the guide to that environment. ",[198,2284,2286],{"href":2285},"what-is-human-in-the-loop-ai","What is human-in-the-loop AI"," is why a checkbox is not a quote.",[191,2289,2290,2291,2293,2294,2296],{},"For unattended hygiene — duplicate tickets, stale fields, Monday queue scans — that is standing-order work, not this room. See ",[198,2292,1504],{"href":943}," when the queue is commercial, and ",[198,2295,506],{"href":505}," for the compile-and-skip discipline. Exception cases with a signer belong in the collaborative room.",[809,2298,2300],{"className":811,"code":2299,"language":813,"meta":171,"style":171},"flowchart TD\n  ticket[\"Ticket\"] --> sharedCase[\"Shared case\"]\n  policy[\"Policy version\"] --> sharedCase\n  agent[\"Frontline agent\"] --> sharedCase\n  specialist[\"Specialist\"] --> sharedCase\n  model[\"Draft\"] --> sharedCase\n  approver[\"Named approver\"] -->|sign or reject| sharedCase\n  sharedCase --> billing[\"Billing change\"]\n  sharedCase --> customer[\"Customer reply\"]\n",[815,2301,2302,2306,2311,2316,2321,2326,2331,2336,2341],{"__ignoreMap":171},[818,2303,2304],{"class":820,"line":821},[818,2305,1359],{},[818,2307,2308],{"class":820,"line":172},[818,2309,2310],{},"  ticket[\"Ticket\"] --> sharedCase[\"Shared case\"]\n",[818,2312,2313],{"class":820,"line":832},[818,2314,2315],{},"  policy[\"Policy version\"] --> sharedCase\n",[818,2317,2318],{"class":820,"line":838},[818,2319,2320],{},"  agent[\"Frontline agent\"] --> sharedCase\n",[818,2322,2323],{"class":820,"line":844},[818,2324,2325],{},"  specialist[\"Specialist\"] --> sharedCase\n",[818,2327,2328],{"class":820,"line":850},[818,2329,2330],{},"  model[\"Draft\"] --> sharedCase\n",[818,2332,2333],{"class":820,"line":856},[818,2334,2335],{},"  approver[\"Named approver\"] -->|sign or reject| sharedCase\n",[818,2337,2338],{"class":820,"line":1392},[818,2339,2340],{},"  sharedCase --> billing[\"Billing change\"]\n",[818,2342,2343],{"class":820,"line":1398},[818,2344,2345],{},"  sharedCase --> customer[\"Customer reply\"]\n",[208,2347,2349],{"id":2348},"what-a-shared-support-case-looks-like","What a shared support case looks like",[191,2351,2352],{},"One case, one exception.",[191,2354,2355,2356,2359],{},"The agent attaches context and keeps the customer voice accurate. The specialist proposes product facts. The named approver rejects or signs the ",[470,2357,2358],{},"exact"," credit or policy exception. Finance or billing ops may appear as guest on high-value cases. After signature, a new customer message that changes the deal is a new proposal. A side-channel “actually make it $50” is a new version with a new sign — not an edit to the closed ticket note.",[191,2361,2362],{},"The signed outcome contains the customer message if it sent, the credit payload if it posted, the policy version, the approver’s name, and the ticket id. The model’s draft is not the signature.",[191,2364,2365,2367,2368,2371,2372,2376,2377,2380],{},[198,2366,266],{"href":265}," keeps a guest from inheriting the billing write token. ",[198,2369,2370],{"href":272},"Multiplayer AI and multi-agent AI"," is why several agents passing tickets to each other is not the same as finance seeing the credit payload. ",[198,2373,2375],{"href":2374},"how-to-evaluate-collaborative-ai","How to evaluate collaborative AI"," is the sheet for the job. ",[198,2378,2379],{"href":360},"What an AI workstream is"," is one container shape.",[191,2382,2383,2384,2386,2387,2391],{},"When the case touches renewal or pipeline truth, pull finance or RevOps onto the roster as guest — the same week’s ",[198,2385,403],{"href":402}," job may need the exception visible before a forecast signs. ",[198,2388,2390],{"href":2389},"collaborative-ai-for-human-resources","Collaborative AI for human resources"," is the pattern when the case is an employee-facing commitment rather than a customer credit.",[208,2393,2395],{"id":2394},"how-to-start-with-one-exception-type","How to start with one exception type",[191,2397,2398],{},"Pick one recurring exception: goodwill credits above a named amount, SLA credits, subscription pauses, policy statements that sound like fares or cancellation rules.",[191,2400,1474],{},[336,2402,2403,2406,2409,2412],{},[245,2404,2405],{},"Read-only ticket plus billing view for that slice.",[245,2407,2408],{},"A draft reply the model may not send alone.",[245,2410,2411],{},"A named approver with a real spend limit.",[245,2413,2414],{},"No production billing writes until the first rejection is stored.",[191,2416,2417],{},"Count how many credits were still decided in side chats. If that number does not fall, you automated deflection rather than the case. Keep a short note: who was on the roster, how many credits were proposed and rejected, whether billing matched the signed payload, whether a customer-facing sentence left without a signer class.",[191,2419,2420,2421,2423,2424,1457],{},"Website and support bots need the same split. A bot may detect that a customer asked about a fare-like rule. The ",[470,2422,1447],{}," of that language still routes to a person with a signer class, or stays draft-only. ",[198,2425,1174],{"href":1172,"rel":2426},[225],[191,2428,2429,2430,2433,2434,2437],{},"For high-volume ",[470,2431,2432],{},"non-exception"," work — categorisation, duplicate detection, suggested macros — a standing-order loop on the queue may be the right unattended layer. Keep exceptions in the collaborative case. ",[198,2435,2436],{"href":505},"Loop engineering"," is the compile-and-skip discipline; it is not a substitute for the approver on money.",[191,2439,2440],{},"Support AI is not measured only by tickets closed. It is measured by whether the exception that left the building had a name on it — and whether the customer can rely on a sentence that nobody signed.",[208,2442,964],{"id":963},[191,2444,967,2445,2447,2448,2450],{},[198,2446,395],{"href":32}," hold the shared support case next to the roster: ticket view, policy version, proposed credit, named approver. ",[198,2449,39],{"href":40}," is where customer-facing claims and billing writes have to live as fail-closed behaviour. You can start with a shared folder and a written billing stop if that is what you have.",[191,2452,2453,2455],{},[198,2454,2375],{"href":2374}," is still the sheet for the job. The product is useful only if last Friday’s credit can be reconstructed without asking the agent who drafted the apology.",[985,2457,987],{},{"title":171,"searchDepth":172,"depth":172,"links":2459},[2460,2461,2462,2463,2464,2465,2466],{"id":2077,"depth":172,"text":2078},{"id":2125,"depth":172,"text":2126},{"id":673,"depth":172,"text":674},{"id":2215,"depth":172,"text":2216},{"id":2348,"depth":172,"text":2349},{"id":2394,"depth":172,"text":2395},{"id":963,"depth":172,"text":964},"Collaborative AI for support is one shared case — agent, specialist, and a named person who can issue a credit or policy exception — not a chatbot that replaces the helpdesk. A guide to exceptions, not deflection.",{"eyebrow":1000,"title":2469},"Cases, credits, and a named exception",[2471,2474,2477,2480],{"question":2472,"answer":2473},"Should AI resolve tickets without a human?","It may draft and may suggest. Resolution that changes billing, policy, or a commitment still needs a named person who can issue the exception — with the exact payload visible before it lands. A ticket closed without the exception recorded is a metric, not a job. Fail-closed means if nobody approves, nothing posts and the customer message does not send. Speed without a shared case recreates the side-chat problem: a fluent answer in a private window that the next shift cannot find. Keep the humans on exceptions. Automate listing and drafting inside a room everyone can reopen.",{"question":2475,"answer":2476},"Is a chatbot on the website the same as support collaborative AI?","Only if the bots sentences are governed like writes. Air Canada was held to chatbot text with no CRM change. Treat customer-facing claims as payloads with a signer class, or keep the bot draft-only. A website sentence about fares, credits, or cancellation rules is often the system of record for the relationship. Collaborative AI for support is the shared case behind exceptions, not a project to replace the helpdesk with a bot that closes tickets faster. If the customer could rely on the sentence, treat it as a write even when no billing API fired.",{"question":2478,"answer":2479},"Where should we start?","Start with one exception type: credits above a threshold, SLA breaches, or fare-like policy statements. Put a read-only ticket view and a read-only billing view on the case. Name the approver with a real spend limit. Do not enable production billing writes until the first rejection is stored. Count how many credits were still decided in side chats. If that number does not fall, you automated deflection rather than the case.",{"question":2481,"answer":2482},"Does this replace tier-one support?","No. Replacement without a shared case and a named exception path scales the wrong failure: tidy closure in the tool, messy truth in billing and in the customers inbox. Collaborative AI keeps humans on exceptions and uses the model to draft inside a room the next shift can reopen. High-volume non-exception work — categorisation, duplicate detection, suggested macros — can sit on a standing-order loop. Keep money, policy, and commitments on the collaborative case with a named signer.","\u002Fblog\u002Fcollaborative-ai-for-customer-support",{"title":2045,"description":2467},"blog\u002Fcollaborative-ai-for-customer-support",[442,2487,2488,2489,2490],"customer-support","helpdesk","exceptions","write-back","EW3KHdyTpOqlvwMq_95TC8IThMjAUBfXvihjuDvgNSw",{"id":2493,"title":2494,"archived":165,"authors":2495,"badge":2497,"body":2498,"date":2678,"definedTerm":166,"department":166,"description":2679,"extension":174,"eyebrow":166,"faqHeader":2680,"faqs":2682,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":2692,"relatedHeading":166,"seo":2693,"series":442,"sitemap":131,"status":166,"stem":2694,"subhead":166,"tags":2695,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":2697},"content\u002Fblog\u002Fcollaborative-ai-for-finance-and-planning.md","What is collaborative AI for finance and planning?",[2496],{"name":185,"to":136},{"label":187},{"type":168,"value":2499,"toc":2671},[2500,2503,2506,2517,2520,2523,2526,2532,2535,2539,2542,2545,2548,2551,2557,2561,2564,2567,2584,2587,2590,2593,2603,2607,2610,2613,2616,2619,2625,2630,2634,2637,2639,2656,2663,2668],[191,2501,2502],{},"Collaborative AI for finance and planning is the roles you already have — controller, FP&A, business partner, and a later audit reader — on one job, with a model that may draft and may not post. The shared object holds the workbook, the actuals, the definition in force, and the signature. A personal assistant that writes a variance note from a downloaded sheet is a different product.",[191,2504,2505],{},"You should care if a forecast becomes management truth — a freeze, a target, a board number — before anyone treats it like a control. This is a how-to for one planning cycle. Plenty of teams will keep copilots for private analysis and add a shared layer only where two roles must stand on the same pack.",[191,2507,2086,2508,2510,2511,1942,2514,2516],{},[198,2509,100],{"href":200}," definition is ",[198,2512,2513],{"href":204},"what collaborative AI is",[198,2515,641],{"href":640}," is the companion for the signature.",[208,2518,2494],{"id":2519},"what-is-collaborative-ai-for-finance-and-planning",[191,2521,2522],{},"The controller owns the books: close, recognition, a journal, a mapping that will be used as if it were the chart of accounts. FP&A owns the plan, the forecast, the variance, the driver pack. The business partner sits with the line that will live with the number. Audit asks later whether an independent person can reconstruct what was proposed, signed, and landed.",[191,2524,2525],{},"Collaborative AI keeps those duties on one job instead of collapsing them into one chat. The AI role is narrow: read this period’s extract; draft a list of exceptions or a commentary that cites the attached sources; do not post.",[191,2527,2528,2531],{},[198,2529,464],{"href":462,"rel":2530},[225]," (US Congress, 2002) does not mention copilots. It requires issuers to keep internal control over financial reporting: a trail showing how a number became the number. You do not need to be an issuer for the reconstruction test to be a useful test. If you cannot reconstruct, you cannot explain.",[191,2533,2534],{},"Write-back is when AI changes a live system — including an ERP post. The payload is the exact journal: accounts, amounts, period, text, before and after. Fail-closed means if nobody approves, nothing happens. A prompt that says “don’t post” is not that control.",[208,2536,2538],{"id":2537},"why-should-fpa-or-planning-care","Why should FP&A or planning care?",[191,2540,2541],{},"Because speed is the usual failure mode, and the plan is watched less than the ledger.",[191,2543,2544],{},"FP&A gets a good commentary from a personal assistant and pastes it into the board pack. The controller has not seen the drivers. The partner has not seen the commitment implied. Audit later asks how the commentary was produced, and “we asked the model” is not a control.",[191,2546,2547],{},"A common belief is that the control boundary is the ERP write, so protecting posting protects the function. The plan is often treated as truth long before it becomes an entry. The commentary pasted on Tuesday is what the line is managed against. Protect only the post, and the model’s most consequential output travels with no signature.",[191,2549,2550],{},"Finance pilots that auto-post are a risky kind of scale. Scale the room first: same files, named signer, stored rejection. Version-chasing a planning pack is the tax. One live tab on the job is an attempt to stop it.",[191,2552,2553,2554,2556],{},"When the number has to travel to legal or sales at quarter-end, keep it on the same job rather than forwarding a new export. ",[198,2555,669],{"href":402}," is the sibling when the artefact is pipeline rather than books.",[208,2558,2560],{"id":2559},"how-do-you-use-ai-on-forecasts-without-losing-the-trail","How do you use AI on forecasts without losing the trail?",[191,2562,2563],{},"Attach the sources. Cite them. Sign the artefact people will act on.",[191,2565,2566],{},"A practical loop:",[336,2568,2569,2572,2575,2578,2581],{},[245,2570,2571],{},"Put the live workbook tab and the actuals extract on the job. Agree which tab is live.",[245,2573,2574],{},"Lock the definitions the controller already uses — currency, bookings versus pipeline, one-time items.",[245,2576,2577],{},"Let the model draft a commentary that points at those sources, not at a private rewrite.",[245,2579,2580],{},"Invite the partner to reject a commitment the line cannot keep, before the pack is locked.",[245,2582,2583],{},"File the signed pack on the job. A later rewrite is a new version with a new sign.",[191,2585,2586],{},"Name the journals, or class of journals, the model will never post on its own: revenue recognition, manual accruals above a stated amount, anything that reverses a control account, mappings that change how a BU hits the P&L. The model may draft those as a payload. A named controller or deputy signs.",[191,2588,2589],{},"If your vendor cannot show a stored rejection of a journal, you have a demo that has not failed yet. A confirmation box the analyst clicks through is not the same as a named signer.",[191,2591,2592],{},"Planning cubes tempt a softer story: “it is only a forecast journal.” If that cube is used as if it were books, treat it as books. If it is a sandbox, keep it off the ERP write identity.",[191,2594,2595,2596,2599,2600,2602],{},"The harness — the tools, stops, and checks around the model — is how draft-and-sign stays in place when close week gets late. ",[198,2597,2598],{"href":352},"Harness engineering"," is the guide to that environment. Keep the ERP from writing until a named controller can refuse; ",[198,2601,1349],{"href":664}," is the same checklist on a different object.",[208,2604,2606],{"id":2605},"what-does-a-shared-planning-job-look-like","What does a shared planning job look like?",[191,2608,2609],{},"Controller, FP&A, partner, and an audit guest on one roster.",[191,2611,2612],{},"The controller sees the same extract everyone else is using, sees the payload before anything posts, and remains the signer for posting even when FP&A opened the job. Name the person: “Controller’s office” cannot sign, and neither can a shared close mailbox. If a deputy signs on a given night of close, put them on the roster for that night, then remove them.",[191,2614,2615],{},"FP&A attaches the model, the sheet, and the actuals, and proposes narrative. They do not silently become the ERP writer because they have the friendlier prompt. Guests are common: a BU finance manager, an intern on actuals. If the planning product cannot invite a guest without an ERP token, you have the wrong room.",[191,2617,2618],{},"The partner sees the drivers, not only the total, and can attach the operational file that is true on the ground. A channel of “GMs” is an audience. The AI must not mail the line “your new target” from a personal assistant; that is a write to a relationship inside the company.",[191,2620,2621,2622,2624],{},"Audit opens a completed job and reconstructs identity, content, time, and custody without a tour from the hero who “knows the prompt.” If they need the hero, the control is the hero. ",[198,2623,641],{"href":640}," overlaps: identity, content, time, custody.",[191,2626,2627,2628,411],{},"RBAC — who is allowed to do what — keeps the intern from inheriting a post token. See ",[198,2629,266],{"href":265},[208,2631,2633],{"id":2632},"how-do-you-start-with-one-planning-cycle","How do you start with one planning cycle?",[191,2635,2636],{},"Put one close or one forecast cycle on this roster before you connect a second ERP module.",[191,2638,918],{},[336,2640,2641,2644,2647,2650,2653],{},[245,2642,2643],{},"Name the artefact: the pack, the variance, the journal class that must not auto-post.",[245,2645,2646],{},"Attach two files the team already emails — workbook and actuals.",[245,2648,2649],{},"Add the controller or deputy, FP&A, and the partner who will live with the number.",[245,2651,2652],{},"Keep the ERP read-only until you have a stored rejection: the first no is the control.",[245,2654,2655],{},"After the cycle, ask an independent reader to reconstruct the signed number without the authors.",[191,2657,967,2658,404,2660,2662],{},[198,2659,395],{"href":32},[198,2661,972],{"href":40}," are one attempt at draft-and-sign. You can start with a shared folder and a written stop if that is what you have.",[191,2664,2665,2667],{},[198,2666,2073],{"href":2072}," is when a planner’s private scratch model should stay personal. Shared planning begins when two roles must file the same pack.",[191,2669,2670],{},"The exposure in planning is not only the posting API. It is that a plan becomes management truth with nobody’s name on it, and the model made producing those plans easy. Put the signature on the artefact people act on.",{"title":171,"searchDepth":172,"depth":172,"links":2672},[2673,2674,2675,2676,2677],{"id":2519,"depth":172,"text":2494},{"id":2537,"depth":172,"text":2538},{"id":2559,"depth":172,"text":2560},{"id":2605,"depth":172,"text":2606},{"id":2632,"depth":172,"text":2633},"2026-08-24","Collaborative AI for FP&A is controller, planner, and partner on one job — the model drafts, a named person signs, the trail stays. A guide to one planning cycle, not auto-posting.",{"eyebrow":425,"title":2681},"Forecasts, signatures, and the trail",[2683,2686,2689],{"question":2684,"answer":2685},"Can the model post journals if someone clicks confirm?","A confirm box the analyst clicks through is not a named controller signature. Draft the journal as the exact accounts and amounts. If nobody approves, nothing posts.",{"question":2687,"answer":2688},"Does protecting the ERP protect the plan?","Not always. A forecast can become a hiring freeze or a discount grid weeks before it is a ledger entry. Put a name on the artefact people act on, not only on the post.",{"question":2690,"answer":2691},"What does Sarbanes-Oxley have to do with copilots?","The 2002 Act does not mention copilots. It asks issuers for a trail of how a number became the number. A fluent variance commentary is not that trail.","\u002Fblog\u002Fcollaborative-ai-for-finance-and-planning",{"title":2494,"description":2679},"blog\u002Fcollaborative-ai-for-finance-and-planning",[442,1020,1021,1023,2696],"audit","gMzb6q5cPfszzFTH7ECLNuT3uOrAXrvFQGczwDS7R28",{"id":2699,"title":2700,"archived":165,"authors":2701,"badge":2703,"body":2704,"date":997,"definedTerm":166,"department":166,"description":3124,"extension":174,"eyebrow":166,"faqHeader":3125,"faqs":3127,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":3139,"relatedHeading":166,"seo":3140,"series":442,"sitemap":131,"status":166,"stem":3141,"subhead":166,"tags":3142,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":3145},"content\u002Fblog\u002Fcollaborative-ai-for-human-resources.md","What is collaborative AI for human resources?",[2702],{"name":185,"to":136},{"label":187},{"type":168,"value":2705,"toc":3113},[2706,2709,2718,2726,2730,2733,2758,2761,2776,2781,2785,2788,2800,2809,2817,2819,2860,2865,2869,2872,2875,2892,2895,2902,2906,2914,2920,2932,2935,2939,2942,2978,2981,2992,3031,3035,3038,3041,3044,3054,3064,3068,3071,3073,3090,3093,3096,3098,3106,3111],[191,2707,2708],{},"Human resources already runs people decisions through a committee, whether anyone calls it that. The manager knows the operational fact — the project slip, the customer complaint, the pattern of absence. The HR business partner knows which policy version applies, what precedent looks like, and which step in the process is next. Legal joins when the words might bind the company. A named signer — often HR, sometimes a delegated director — is the person who can refuse the outcome. The failure mode is a decision with nobody’s name on it, and personal data sitting in a room that was never scoped.",[191,2710,2711,2712,2717],{},"A manager asks a personal assistant to “draft the PIP.” The draft is confident. It cites no policy section. HR learns about it when the employee replies. Alternatively, HR and the manager agree in a side channel, and the only artefact is a paraphrase in email. Six months later someone asks which version of the leave policy applied. The folder has three PDFs with similar names. ",[198,2713,2716],{"href":2714,"rel":2715},"https:\u002F\u002Fwww.shrm.org\u002Ftopics-tools\u002Femployment-law",[225],"SHRM’s employment law resources"," are a reminder that the paperwork is not decorative. Decisions about people carry discrimination, retaliation, and documentation duties that a fluent paragraph does not satisfy.",[191,2719,2720,2721,2069,2723,2725],{},"This guide is about one shared people decision — a leave exception, an offer band, a conduct step — not a claim that AI should replace your employee relations team, and not a path to auto-firing. ",[198,2722,205],{"href":204},[198,2724,2073],{"href":2072}," is when a manager’s private draft should stay private until there is a job.",[208,2727,2729],{"id":2728},"what-collaborative-ai-for-hr-actually-is","What collaborative AI for HR actually is",[191,2731,2732],{},"People work already has roles before anyone mentions a model. Collaborative AI keeps those duties on one job instead of collapsing them into one chat.",[242,2734,2735,2741,2747,2752],{},[245,2736,2086,2737,2740],{},[470,2738,2739],{},"manager"," attaches operational context they can stand behind, and can reject claims they cannot.",[245,2742,2086,2743,2746],{},[470,2744,2745],{},"HR business partner"," attaches the policy version in force, proposes language, and usually remains the signer for HRIS writes even when the manager opened the job.",[245,2748,2749,2751],{},[470,2750,64],{}," joins when the draft might bind — settlement language, regulatory wording, cross-border transfer text — and can refuse the send without sitting in every leave request.",[245,2753,2099,2754,2757],{},[470,2755,2756],{},"named signer"," is a person, not “HR team” and not a shared mailbox.",[191,2759,2760],{},"The AI role is narrow: read the attached policy and the employee facts you chose to put on the job; draft the exception memo or the letter language; do not change the HRIS; do not send mail to the employee; do not recommend termination as an unattended conclusion. Fluency is a draft. Employment is a signed outcome.",[191,2762,2763,2764,2769,2770,2775],{},"When the job holds personal data — and almost every HR job does — ",[198,2765,2768],{"href":2766,"rel":2767},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2016\u002F679\u002Foj",[225],"GDPR"," still applies to purpose, minimisation, and access. The ",[198,2771,2774],{"href":2772,"rel":2773},"https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fuk-gdpr-guidance-and-resources\u002Femployment\u002F",[225],"UK ICO’s employment guidance"," is explicit that workers’ data in automated or semi-automated processes needs a lawful basis and a trail. A shared job is processing. Scope what you attach. Name who may see it.",[191,2777,2778,2779,2602],{},"Write-back is when AI changes a live system — including an HRIS status, a payroll code, or an email that commits the company. The payload is the exact field change or the exact message. Fail-closed means if nobody approves, nothing happens. A prompt that says “don’t fire anyone” is not that control. ",[198,2780,1215],{"href":664},[208,2782,2784],{"id":2783},"why-the-unsigned-people-decision-is-the-failure","Why the unsigned people decision is the failure",[191,2786,2787],{},"The common belief is that HRIS permissions protect people decisions. Permissions protect fields. They do not automatically produce a reconstructable decision: who saw which policy, who proposed the exception, who signed, what was sent. If you cannot reconstruct, you cannot defend — in an employment tribunal, in an internal audit, or in a simple “why did we treat these two cases differently?” conversation.",[191,2789,310,2790,2793,2794,2799],{},[198,2791,315],{"href":313,"rel":2792},[225]," (2025) reports broad adoption of AI in functions including HR, while most organisations are still piloting governance. Adoption outruns the shared room. That gap is where “the model said” becomes the record. Yang and colleagues, writing in ",[198,2795,2798],{"href":2796,"rel":2797},"https:\u002F\u002Fwww.nature.com\u002Farticles\u002Fs41562-021-01196-4",[225],"Nature Human Behaviour"," (2022), found that firm-wide remote work made collaboration networks more static and siloed. People decisions already fight that pull. AI that lives only in a manager’s private thread can make the silo worse: each person has a fluent answer, and nobody has the same file.",[191,2801,2802,2803,2808],{},"This is not about auto-firing. Termination and serious discipline are among the outcomes that must never be an unattended model conclusion. The ",[198,2804,2807],{"href":2805,"rel":2806},"https:\u002F\u002Fwww.eeoc.gov\u002Feeoc-disability-related-resources\u002Fartificial-intelligence-and-ada",[225],"U.S. Equal Employment Opportunity Commission"," has already warned that software, algorithms, and AI used to assess applicants and employees can screen people out in ways that violate the ADA if accommodations and human review are missing. A collaborative job is the opposite pattern: slow the path enough that a named HR or legal signer sees the exact language before it lands in a system or in an inbox.",[191,2810,2811,2813,2814,2816],{},[198,2812,2154],{"href":1057}," is the sibling when the artefact is a clause or a customer-facing sentence. ",[198,2815,2161],{"href":329}," is the failure this page is trying to stop inside HR.",[208,2818,674],{"id":673},[242,2820,2821,2827,2833,2839,2844,2848,2854],{},[245,2822,2823,2826],{},[470,2824,2825],{},"Policy version."," The PDF or wiki page with a date that the team agrees is live. “The leave policy” is not a version.",[245,2828,2829,2832],{},[470,2830,2831],{},"Named signer."," The identity that can refuse the outcome. Shared mailboxes destroy this.",[245,2834,2835,2838],{},[470,2836,2837],{},"Facts on the job."," The minimum employee information needed for this decision — not the entire personnel file.",[245,2840,2841,2843],{},[470,2842,1753],{}," A change to a live system, including an employee-facing message that commits the company.",[245,2845,2846,2195],{},[470,2847,2194],{},[245,2849,2850,2853],{},[470,2851,2852],{},"Purpose and minimisation."," GDPR vocabulary for why you attached those facts and why you did not attach more.",[245,2855,2856,2859],{},[470,2857,2858],{},"Reconstruction."," An independent reader can open the signed outcome and explain it without the authors.",[191,2861,2862,2864],{},[198,2863,1220],{"href":1219}," is the wider programme. This page is the people-decision subset: one job, one policy version, one signer.",[208,2866,2868],{"id":2867},"what-the-model-may-do-and-must-not","What the model may do — and must not",[191,2870,2871],{},"The model may draft. It may point at sources you attached. It may list questions the manager still needs to answer. It may propose letter language next to the policy section it claims to follow.",[191,2873,2874],{},"The model must not:",[242,2876,2877,2880,2883,2886,2889],{},[245,2878,2879],{},"Change an HRIS status, compensation field, termination code, or access removal on its own.",[245,2881,2882],{},"Send mail to the employee.",[245,2884,2885],{},"Recommend termination or serious discipline as an unattended conclusion.",[245,2887,2888],{},"Pull the whole employee file “for context.”",[245,2890,2891],{},"Treat a manager’s confirmation click as an HR signature.",[191,2893,2894],{},"Name the HRIS changes the model will never post on its own. The model may draft those as a payload. A named HR or system delegate signs. If your vendor cannot show a stored rejection of a proposed status change, you have a demo that has not failed yet. A confirmation box the manager clicks through is not the same as an HR signature.",[191,2896,2897,2898,2282,2900,2287],{},"The harness — the tools, stops, and checks around the model — is how draft-and-sign stays in place when the case is urgent. ",[198,2899,1139],{"href":352},[198,2901,2286],{"href":2285},[208,2903,2905],{"id":2904},"shrm-ico-and-gdpr-the-paperwork-is-not-decorative","SHRM, ICO, and GDPR — the paperwork is not decorative",[191,2907,2908,2909,2913],{},"Employment law does not pause because a draft was generated. ",[198,2910,2912],{"href":2714,"rel":2911},[225],"SHRM"," collects the practical duties: documentation, consistency, retaliation risk, and the difference between a coaching note and a formal step. If two employees in similar facts get different letters because one manager had a better assistant, you have a discrimination problem wearing a productivity story.",[191,2915,2916,2919],{},[198,2917,2768],{"href":2766,"rel":2918},[225]," Article 5 still wants purpose, minimisation, accuracy, and storage limitation. Article 22 still restricts decisions based solely on automated processing that produce legal or similarly significant effects — and employment outcomes sit in that neighbourhood even when a human later clicks confirm. You do not need to litigate every article to need a reconstructable log. You do need to know that a shared job is processing, that a retrieval index of personnel files is still processing, and that “the model needed context” is not a lawful basis.",[191,2921,2086,2922,2926,2927,2931],{},[198,2923,2925],{"href":2772,"rel":2924},[225],"UK ICO employment guidance"," is written for organisations that already hold workers’ data. It asks for a lawful basis, for access that matches the purpose, and for a trail when processing is automated or semi-automated. The ",[198,2928,2930],{"href":723,"rel":2929},[225],"ICO’s AI guidance"," adds the same instinct for systems that infer or rank people. Attach the performance note you need for this leave exception. Do not attach five years of Slack because it was easy.",[191,2933,2934],{},"Retention on the signed outcome should match how long you must explain the decision — not how long chat keeps threads. A later rewrite is a new version with a new sign. A later prompt that “updates” the outcome because someone remembered a detail is not an edit. It is a new proposal.",[208,2936,2938],{"id":2937},"how-to-run-one-people-decision-with-ai","How to run one people decision with AI",[191,2940,2941],{},"Attach the policy version. Cite it. Sign the outcome people will act on.",[336,2943,2944,2951,2958,2965,2968,2975],{},[245,2945,2946,2947,2950],{},"Put the ",[470,2948,2949],{},"policy PDF or wiki page with a date"," on the job. Agree which version is live.",[245,2952,2953,2954,2957],{},"Attach only the ",[470,2955,2956],{},"facts needed for this decision"," — not the entire personnel file.",[245,2959,2960,2961,2964],{},"Let the model draft a memo that ",[470,2962,2963],{},"points at those sources",", not at a private rewrite.",[245,2966,2967],{},"Invite the manager to reject operational claims they cannot stand behind.",[245,2969,2970,2971,2974],{},"Name the ",[470,2972,2973],{},"HR signer"," before any HRIS write or employee message is possible.",[245,2976,2977],{},"File the signed outcome on the job. A later rewrite is a new version with a new sign.",[191,2979,2980],{},"Do this for one decision type you already escalate: leave above the grid, offer outside the band, remote work in a restricted country, a conduct step that needs employee-relations eyes. Do not start with termination. Do not start with a bulk “clean up performance ratings” job.",[191,2982,2983,2984,2988,2989,2991],{},"After signature, a new fact in a side channel is a new proposal. ",[198,2985,2987],{"href":2986},"search-is-not-memory","Search is not memory"," is why “search Teams for the PIP thread” is not a file. ",[198,2990,266],{"href":265}," is why the intern must not inherit an HRIS post when they join as a guest.",[809,2993,2995],{"className":811,"code":2994,"language":813,"meta":171,"style":171},"flowchart LR\n  manager[\"Manager facts\"] --> job[\"Shared HR job\"]\n  policy[\"Policy version\"] --> job\n  model[\"Draft\"] --> job\n  hrbp[\"HR business partner\"] -->|approve or reject| job\n  legal[\"Legal, if needed\"] --> job\n  job -->|signed| hris[\"HR system write\"]\n",[815,2996,2997,3001,3006,3011,3016,3021,3026],{"__ignoreMap":171},[818,2998,2999],{"class":820,"line":821},[818,3000,824],{},[818,3002,3003],{"class":820,"line":172},[818,3004,3005],{},"  manager[\"Manager facts\"] --> job[\"Shared HR job\"]\n",[818,3007,3008],{"class":820,"line":832},[818,3009,3010],{},"  policy[\"Policy version\"] --> job\n",[818,3012,3013],{"class":820,"line":838},[818,3014,3015],{},"  model[\"Draft\"] --> job\n",[818,3017,3018],{"class":820,"line":844},[818,3019,3020],{},"  hrbp[\"HR business partner\"] -->|approve or reject| job\n",[818,3022,3023],{"class":820,"line":850},[818,3024,3025],{},"  legal[\"Legal, if needed\"] --> job\n",[818,3027,3028],{"class":820,"line":856},[818,3029,3030],{},"  job -->|signed| hris[\"HR system write\"]\n",[208,3032,3034],{"id":3033},"what-a-shared-hr-job-looks-like","What a shared HR job looks like",[191,3036,3037],{},"Manager, HRBP, optional legal, and sometimes an audit guest on one roster.",[191,3039,3040],{},"The manager sees the same facts everyone else is using. They do not sign policy exceptions unless they are also the named delegate. HR attaches the policy, proposes language, and remains the signer for HRIS writes. Legal joins when the draft might bind, and can refuse the send. Guests are common: a department head, an ER specialist in another region. If the product cannot invite a guest without giving them the write token, you have the wrong room.",[191,3042,3043],{},"The signed outcome contains the decision, the policy version in force, the date, the named signer, and the facts that were on the job — not a model paraphrase of facts that lived only in chat. The narrative the model drafted is support, not signature.",[191,3045,3046,3048,3049,3051,3052,2380],{},[198,3047,2370],{"href":272}," matters here: several people in one session is not the same as a job that still exists on Monday. ",[198,3050,2375],{"href":2374}," is the sheet for that job. ",[198,3053,2379],{"href":360},[191,3055,3056,3057,3060,3061,3063],{},"For unattended repetition — the Monday headcount extract that nobody changed — that is standing-order work, not this room. See ",[198,3058,3059],{"href":1500},"loops for finance and planning"," when the extract is payroll or planning, and ",[198,3062,506],{"href":505}," for the compile-and-skip discipline. People decisions with a signer belong in the collaborative room first.",[208,3065,3067],{"id":3066},"how-to-start-with-one-decision-type","How to start with one decision type",[191,3069,3070],{},"Pick one recurring exception your team already escalates.",[191,3072,918],{},[336,3074,3075,3078,3081,3084,3087],{},[245,3076,3077],{},"Name the artefact: the memo, the letter, the HRIS change class that must not auto-post.",[245,3079,3080],{},"Attach the policy version the team already cites — with a date.",[245,3082,3083],{},"Add the manager, HRBP, and the signer who will live with the outcome.",[245,3085,3086],{},"Keep the HRIS read-only until you have a stored rejection: the first no is the control.",[245,3088,3089],{},"After the cycle, ask an independent reader to reconstruct the signed decision without the authors.",[191,3091,3092],{},"Count how many people decisions still happened in side chats. If that number does not fall, you automated a draft rather than the decision. Keep a short note: who was on the roster, which policy version was attached, whether the HRIS matched the signed payload, whether anyone rejected.",[191,3094,3095],{},"The exposure in HR is not only the HRIS API. It is that a people decision becomes operational truth with nobody’s name on it, and the model made producing those drafts easy. Put the signature on the artefact people and systems will act on — and keep termination and discipline off the unattended path entirely.",[208,3097,964],{"id":963},[191,3099,967,3100,3102,3103,3105],{},[198,3101,395],{"href":32}," are one container for the shared HR job: policy version, scoped facts, roster, and a named signer before any HRIS write. ",[198,3104,39],{"href":40}," is where fail-closed write-back has to live as behaviour, not as a prompt. You can start with a matter folder and a written stop if that is what you have.",[191,3107,3108,3110],{},[198,3109,2375],{"href":2374}," is still the sheet for the job. The product is useful only if a later reader can reconstruct the signed people decision without asking the authors.",[985,3112,987],{},{"title":171,"searchDepth":172,"depth":172,"links":3114},[3115,3116,3117,3118,3119,3120,3121,3122,3123],{"id":2728,"depth":172,"text":2729},{"id":2783,"depth":172,"text":2784},{"id":673,"depth":172,"text":674},{"id":2867,"depth":172,"text":2868},{"id":2904,"depth":172,"text":2905},{"id":2937,"depth":172,"text":2938},{"id":3033,"depth":172,"text":3034},{"id":3066,"depth":172,"text":3067},{"id":963,"depth":172,"text":964},"Collaborative AI for HR is one shared people decision — a policy version, manager and HRBP on the roster, a named signer — not a chatbot that decides someone’s employment. A guide to one decision, not auto-firing.",{"eyebrow":1000,"title":3126},"Policy, people, and a named signer",[3128,3131,3134,3136],{"question":3129,"answer":3130},"Can the model recommend termination if a manager clicks confirm?","No. Employment outcomes still need a named HR or legal signer, the policy version in force, and a record a later reader can reconstruct. A fluent recommendation is not a decision, even when a confirmation box is clicked. Termination and serious discipline are among the outcomes that must never be an unattended model conclusion. The collaborative pattern is the opposite of auto-firing: slow the path enough that a named person sees the exact language before it lands in a system or in an inbox. A stored rejection of a proposed status change is the control. A prompt that says do not fire anyone is etiquette, not that control.",{"question":3132,"answer":3133},"Does GDPR apply if the job only holds a performance note?","If the note identifies a person, yes. Personal data in a shared job still needs a purpose, access control, and retention that match how long you must explain the decision. The UK ICO employment guidance is explicit that workers data in automated or semi-automated processes needs a lawful basis and a trail. Scope what you attach. Name who may see it. Do not dump the whole employee file into a retrieval index so the model has context. A later reader should be able to see why those facts were on the job, not reconstruct a private chat.",{"question":2478,"answer":3135},"Start with one decision type you already run through a committee: a policy exception, a leave approval above a threshold, or a job-offer band. Attach the policy version with a date. Invite the manager, the HR business partner, and the named signer. Keep the HRIS read-only until someone signs the exact payload. After the first cycle, ask an independent reader to reconstruct the signed decision without the authors. If they cannot, you automated a draft, not a people process.",{"question":3137,"answer":3138},"Is a manager's personal assistant drafting a PIP the same as collaborative HR?","No. A personal assistant helps one person write. Collaborative AI for HR is the shared job where the policy version, the facts you chose to attach, and the named signer live together. The private draft can stay private until there is a job. Once language might reach the employee or change the HRIS, it belongs on the shared job with a signer who can refuse. Fluency in a private window is not a people decision.","\u002Fblog\u002Fcollaborative-ai-for-human-resources",{"title":2700,"description":3124},"blog\u002Fcollaborative-ai-for-human-resources",[442,3143,3144,1568,2768],"human-resources","HR","BpOEcg9ziLA6hJ4VMY9Ld_eYIx0b5kCx-zSIDoWcbjE",{"id":3147,"title":3148,"archived":165,"authors":3149,"badge":3151,"body":3152,"date":3342,"definedTerm":166,"department":166,"description":3343,"extension":174,"eyebrow":166,"faqHeader":3344,"faqs":3346,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":3356,"relatedHeading":166,"seo":3357,"series":442,"sitemap":131,"status":166,"stem":3358,"subhead":166,"tags":3359,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":3361},"content\u002Fblog\u002Fcollaborative-ai-for-legal-and-compliance-review.md","What is collaborative AI for legal and compliance review?",[3150],{"name":185,"to":136},{"label":187},{"type":168,"value":3153,"toc":3335},[3154,3157,3160,3175,3178,3181,3198,3204,3207,3212,3216,3219,3222,3234,3237,3241,3244,3247,3264,3267,3272,3278,3284,3288,3291,3294,3297,3300,3305,3309,3312,3315,3326,3332],[191,3155,3156],{},"Collaborative AI for legal and compliance review is a shared artefact: the clause as written, the playbook version, a named lawyer who can refuse, and a log that would still make sense if someone asked how that language left the company. It is not a copilot that paraphrases a contract in a private window. The model may propose a rewrite next to the quote. A person compares quote to rewrite.",[191,3158,3159],{},"You should care if sales already pastes “legal is comfortable” into a thread, or if a website bot can state terms. This is a how-to for one clause type. A private drafting aid for a lawyer who still works alone can be useful. It is not shared review.",[191,3161,2086,3162,201,3164,3166,3167,3170,3171,3174],{},[198,3163,100],{"href":200},[198,3165,641],{"href":640}," is the evidence cut. ",[198,3168,3169],{"href":664},"What write-back governance is"," is the rule that a model may not change a live system, or send a binding message, until a person has signed the exact change. ",[198,3172,3173],{"href":40},"Product governance"," is where that rule has to live as behaviour.",[208,3176,3148],{"id":3177},"what-is-collaborative-ai-for-legal-and-compliance-review",[191,3179,3180],{},"At minimum the shared job holds:",[242,3182,3183,3186,3189,3192,3195],{},[245,3184,3185],{},"The language under review as the words that will be signed or sent — quoted, not only summarised.",[245,3187,3188],{},"The playbook, grid, or clause list that applied, with a version or a date.",[245,3190,3191],{},"A named lawyer or named delegate who can refuse the send.",[245,3193,3194],{},"A stored refusal so the next draft cannot pretend the first one was approved.",[245,3196,3197],{},"A log a later reader can open without the people who were there.",[191,3199,2086,3200,3203],{},[198,3201,1044],{"href":1042,"rel":3202},[225]," (Regulation (EU) 2024\u002F1689, 2024) is the Union text on placing AI systems on the market and putting them into service. It is not a clause-review playbook. It is a reminder that generated systems used in the Union carry duties that chat etiquette does not satisfy. You do not need to map every article to need a reconstructable log.",[191,3205,3206],{},"Write-back here includes customer messages and contract files, not only CRM fields. When AI changes a live system, or when it sends language that binds, the lawyer’s stop has to be in the path. Fail-closed means if nobody approves, nothing happens. The payload is the exact text, not “we tightened it.”",[191,3208,3209,3211],{},[198,3210,1970],{"href":480}," is the sibling gate: the journal that must not auto-post is the same idea as the clause that must not auto-send.",[208,3213,3215],{"id":3214},"why-should-legal-care","Why should legal care?",[191,3217,3218],{},"Because fluency is not review, and late addition is the usual pattern.",[191,3220,3221],{},"Legal is often asked to “sanity-check this email” after the commercial conversation has already happened. If the email went out, it is already a write to the relationship. Multiplayer work puts legal on the job before the send is possible.",[191,3223,3224,3225,3228,3229,3233],{},"In February 2024 the Civil Resolution Tribunal of British Columbia held Air Canada to a bereavement fare its chatbot had invented — ",[198,3226,1174],{"href":1172,"rel":3227},[225],". No CRM write was required. The message was the write. In June 2023 lawyers were sanctioned for filing ChatGPT-invented cases — ",[198,3230,3232],{"href":1191,"rel":3231},[225],"Mata v. Avianca",", as reported by Reuters. Both are sequence-and-custody stories as much as model-quality stories.",[191,3235,3236],{},"A perfectly accurate discount sent without finance is still an incident. A well-drafted clause legal never saw still binds the company. Accuracy is about whether a sentence is true. The roster is about whether anyone with a duty to refuse it had the chance.",[208,3238,3240],{"id":3239},"how-do-you-keep-review-shared-without-putting-everything-in-a-chatbot","How do you keep review shared without putting everything in a chatbot?",[191,3242,3243],{},"Keep the matter on the job. Keep the bot from being the vault.",[191,3245,3246],{},"Practical rules:",[336,3248,3249,3252,3255,3258,3261],{},[245,3250,3251],{},"Attach the source PDF. Do not trust a retrieval snippethe clause — snippets miss the proviso on the next page.",[245,3253,3254],{},"Diff the proposal against the quote. If the product only stores “legal OK,” you have neither review nor a record.",[245,3256,3257],{},"Name the playbook version. “Follow the playbook” with a folder of PDFs is an instruction to guess.",[245,3259,3260],{},"Confirm retrieval cannot prefer an obsolete PDF because it ranked well.",[245,3262,3263],{},"List the channels this job can emit on. Each has a signer class, or it is disabled. Draft-only is the default.",[191,3265,3266],{},"If you have no official playbook, stop asking the model to “sound like legal.” You are generating tone. Write the fallback you actually use, date it, and put that dated artefact on the job before the next draft.",[191,3268,2099,3269,3271],{},[198,3270,446],{"href":2072}," can still help a lawyer rephrase in private. The shared job starts when sales, operations, or compliance must stand on the same words. Do not put the whole contract corpus into a chatbot “so everyone can ask.” That is reach without a matter.",[191,3273,3274,3275,3277],{},"The harness — the tools, stops, and checks around the model — includes which playbook version the model may retrieve. ",[198,3276,2598],{"href":352}," is the guide to that environment.",[191,3279,1178,3280,3283],{},[198,3281,1183],{"href":1181,"rel":3282},[225]," (2023) is a voluntary map for governing AI systems. It does not replace a named rejector on Tuesday’s concession. It is a useful reminder that the system, not only the paragraph, is what you manage.",[208,3285,3287],{"id":3286},"what-does-a-shared-review-job-look-like","What does a shared review job look like?",[191,3289,3290],{},"A concession matter might hold: the quoted clause, the playbook version dated this quarter, finance’s commercial exception still visible, a lawyer named as rejector, a draft customer message that cannot send while a reject is in force, and a guest seat for outside counsel who cannot turn on a CRM write.",[191,3292,3293],{},"Sales can propose. Sales cannot emoji-approve as “legal.” A Slack group is an audience. If any member of a large channel can approve, you have named whoever was online.",[191,3295,3296],{},"Internal messages that commit a BU — “your new discount is approved” — are writes too when they would be quoted later.",[191,3298,3299],{},"The log a regulator or general counsel needs is not a token trace of agent steps. Engineers need traces. The company needs who proposed, what the quoted clause was, which playbook version, who signed or rejected, when, and whether the send landed. Retention on that log should match how long you must explain the language, not how long the chat tool keeps messages.",[191,3301,3302,3303,411],{},"RBAC — who is allowed to do what — is how outside counsel sees the matter and not every connector. See ",[198,3304,266],{"href":265},[208,3306,3308],{"id":3307},"how-do-you-start-with-one-clause-type","How do you start with one clause type?",[191,3310,3311],{},"Pick one type that will leave the company this month: limitation of liability fallback, data-processing sentence, discount that changes terms, website bot copy that states a fare-like rule.",[191,3313,3314],{},"On that matter:",[336,3316,3317,3320,3323],{},[245,3318,3319],{},"Print five checks: quoted text, version, named rejector, send gate, reconstructable log.",[245,3321,3322],{},"Mark pass or fail with a date. Fix the first fail you cannot live with before you add a second matter.",[245,3324,3325],{},"Run the checks once with sales, legal, and compliance in the same sitting if they would mark differently. The disagreement is information.",[191,3327,3328,3329,3331],{},"Do not roll out “legal AI” as a seat count. A seat is a private window. Nimbus ",[198,3330,395],{"href":32}," hold the matter next to the roster. You can start with a matter folder and a written send stop if that is what you have.",[191,3333,3334],{},"If you cannot pass the checks, the model is a drafting aid for a lawyer who still works alone. That can be the right tool for that week. Shared review begins when the quote, the version, and the name sit on one job.",{"title":171,"searchDepth":172,"depth":172,"links":3336},[3337,3338,3339,3340,3341],{"id":3177,"depth":172,"text":3148},{"id":3214,"depth":172,"text":3215},{"id":3239,"depth":172,"text":3240},{"id":3286,"depth":172,"text":3287},{"id":3307,"depth":172,"text":3308},"2026-08-25","Collaborative legal review is a quoted clause, a named playbook version, and a lawyer who can refuse — on a shared job, not in a private chatbot. A guide to starting with one clause type.",{"eyebrow":425,"title":3345},"Quoted clauses and a named refusal",[3347,3350,3353],{"question":3348,"answer":3349},"Is a chatbot summary the same as legal review?","No. Review needs the clause as quoted, the playbook version, and a named lawyer who can refuse. A paraphrase can drop a defined term. Comfort in chat is not a clause.",{"question":3351,"answer":3352},"Are customer emails “only messages”?","If a customer could rely on the sentence, treat it as a write. Air Canada was held to a chatbot fare in 2024 with no CRM write required. The message was the write.",{"question":3354,"answer":3355},"Do we need the EU AI Act to care about a log?","No. The 2024 Act is one reason Union operators will be asked about systems. Reconstruction — who proposed, what was quoted, who signed — is useful even without mapping every article.","\u002Fblog\u002Fcollaborative-ai-for-legal-and-compliance-review",{"title":3148,"description":3343},"blog\u002Fcollaborative-ai-for-legal-and-compliance-review",[442,1566,1567,3360,2490],"review","huICeCN1RmHLUgm2YYv-KQBnaYlh5Ojgy-QlxJ7xsS4",{"id":3363,"title":3364,"archived":165,"authors":3365,"badge":3367,"body":3368,"date":997,"definedTerm":166,"department":166,"description":3987,"extension":174,"eyebrow":166,"faqHeader":3988,"faqs":3990,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":4002,"relatedHeading":166,"seo":4003,"series":442,"sitemap":131,"status":166,"stem":4004,"subhead":166,"tags":4005,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":4008},"content\u002Fblog\u002Fcollaborative-ai-for-operations.md","What is collaborative AI for operations?",[3366],{"name":185,"to":136},{"label":187},{"type":168,"value":3369,"toc":3975},[3370,3379,3386,3395,3399,3402,3421,3428,3435,3440,3452,3456,3459,3466,3472,3491,3498,3502,3509,3516,3530,3536,3540,3550,3559,3568,3571,3574,3585,3588,3606,3613,3616,3628,3672,3675,3694,3698,3704,3710,3716,3722,3732,3743,3749,3754,3758,3765,3797,3806,3809,3819,3826,3830,3833,3836,3862,3865,3879,3887,3891,3897,3903,3909,3915,3921,3931,3935,3942,3945,3947,3956,3962,3973],[191,3371,3372,3373,3378],{},"Collaborative AI for operations is one shared job that ops, finance, and partners already run on exceptions: a hold on an order, a lane down in the warehouse, a shipment that cannot leave until someone names the risk and the closer. Asana’s ",[198,3374,3377],{"href":3375,"rel":3376},"https:\u002F\u002Fwww.businesswire.com\u002Fnews\u002Fhome\u002F20220405005399\u002Fen\u002FAsana-Anatomy-of-Work-Index-2022-Work-About-Work-Hampering-Organizational-Agility",[225],"Anatomy of Work Index"," (2022), from a survey of more than 10,000 knowledge workers, attributed 58% of the day to coordination — “work about work.” Ops feels that tax as “why is this hold still here?” asked four times across shifts. The model belongs in the room that already pays that tax. It lists what changed, drafts the release note, and stops before anything executes unless a named person signs.",[191,3380,3381,3382,3385],{},"You should care if the hold reason lives in three places — WMS, a spreadsheet, a partner email — and the night shift asks the day shift for a reconstruction. A personal assistant can summarise each inbox. It cannot give the next shift ",[470,3383,3384],{},"one job"," with the same files, the same rejection from finance, and a named closer who owns release.",[191,3387,3388,3390,3391,3394],{},[198,3389,205],{"href":204}," is the definition. This page is the ",[470,3392,3393],{},"during"," question: how ops, finance, and a 3PL partner share the exception while it is open. It is not a dashboard of why a field moved last week.",[208,3396,3398],{"id":3397},"what-collaborative-ai-for-operations-is","What collaborative AI for operations is",[191,3400,3401],{},"Operations runs on exceptions. The plan is steady until it is not: a credit hold, an allocation shortfall, a lot quarantined, a carrier cutoff missed. Each exception crosses roles:",[242,3403,3404,3410,3416],{},[245,3405,3406,3409],{},[470,3407,3408],{},"Ops"," knows the WMS state, the pick face, the SLA clock.",[245,3411,3412,3415],{},[470,3413,3414],{},"Finance"," knows credit limits, margin floors, and who may override.",[245,3417,3418,3420],{},[470,3419,56],{}," (3PL, carrier, supplier) know what they can still ship tonight.",[191,3422,3423,3424,3427],{},"Collaborative AI puts those roles on ",[470,3425,3426],{},"one named job"," with the same attachments — not five forwarded threads. The AI role is bounded: read this WMS view and this AR extract; draft the release checklist; do not post journals; do not clear the hold until the named closer signs.",[191,3429,3430,3431,3434],{},"A Monday report nobody acts on by Wednesday is noise. Collaborative ops attaches ",[470,3432,3433],{},"owners on the roster"," to each open exception class and keeps rejections on the job.",[191,3436,3437,3439],{},[198,3438,273],{"href":272}," matters here: the night shift and finance must see the same payload when a release is proposed, not two summaries in parallel chats. A cast of specialist models that cannot show the 3PL the scoped pick note is still a silo.",[191,3441,3442,3444,3445,3448,3449,411],{},[198,3443,2379],{"href":360}," is the container: brief, files, people, finish line. The warehouse already thinks in tickets and holds. The missing object is often the ",[470,3446,3447],{},"shared"," ticket that finance and the partner can stand on, not another bot in ",[815,3450,3451],{},"#warehouse",[208,3453,3455],{"id":3454},"why-operations-should-care","Why operations should care",[191,3457,3458],{},"The cost is measured in missed cutoffs and re-asks, not in model quality.",[191,3460,3461,3462,3465],{},"Yang and colleagues, writing in ",[198,3463,2798],{"href":2796,"rel":3464},[225]," (2022), used email, calendar, and message data from more than 60,000 information workers and found that firm-wide remote work made collaboration networks more static and siloed, with fewer bridges between groups. Handoffs that used to cross a desk now die in channels the next shift does not watch. Warehouse and control-tower work inherited the same shape even when people are on site: the “desk” is a WMS queue, a finance inbox, and a partner portal that do not share a room.",[191,3467,310,3468,3471],{},[198,3469,315],{"href":313,"rel":3470},[225]," (2025) found widespread use and limited scale. Ops pilots often look like a supervisor with a copilot on a hold extract. Scale would be the next three shifts using the same job. If the model only lives in a private thread, the exception dies with the shift change.",[191,3473,3474,3478,3479,3482,3483,3485,3486,3490],{},[198,3475,3477],{"href":3476},"agents-should-be-disposable","Agents should be disposable",": the ",[470,3480,3481],{},"job"," survives; the agent is shift labour. ",[198,3484,2987],{"href":2986}," is why “search Teams for HOLD-4421” is not a handoff. ",[198,3487,3489],{"href":3488},"what-is-institutional-memory-in-enterprise-ai","Institutional memory in enterprise AI"," is the company-scale layering; do not turn the live hold into a retrieval project. Keep the decision on the job while it is open.",[191,3492,220,3493,3497],{},[198,3494,3496],{"href":223,"rel":3495},[225],"2024 Work Trend Index"," reported that 78% of AI users bring their own tools. In a warehouse, that looks like a lead pasting a WMS screenshot into a consumer model on a phone. Convenient. Invisible to finance. Gone at 06:00. Collaborative ops is how you channel that instinct onto a roster instead of pretending people will stop.",[208,3499,3501],{"id":3500},"how-this-differs-from-after-the-fact-replay","How this differs from after-the-fact replay",[191,3503,3504,3508],{},[198,3505,3507],{"href":3506},"what-is-causal-ai-for-operations","What is causal AI for operations"," reconstructs the chain after the field moved: brief, sources, proposal, approval, write, system response. That is essential for audit and for Monday’s “why did this ship?”",[191,3510,3511,3512,3515],{},"Collaborative AI for operations is the ",[470,3513,3514],{},"live"," chain while the hold is open:",[242,3517,3518,3521,3524,3527],{},[245,3519,3520],{},"Who is on the roster tonight?",[245,3522,3523],{},"What files are attached once?",[245,3525,3526],{},"What release did finance reject an hour ago?",[245,3528,3529],{},"Who is the named closer for this exception type?",[191,3531,3532,3533,3535],{},"You need collaborative shape ",[470,3534,3393],{}," the exception to make later replay trustworthy. If the rejection lived only in a huddle, after-the-fact tools have nothing honest to reconstruct. This page stays on the open room. Link the replay question once; do not run it here.",[208,3537,3539],{"id":3538},"worked-example-order-hold-on-a-strategic-line","Worked example: order hold on a strategic line",[191,3541,3542,3545,3546,3549],{},[470,3543,3544],{},"Situation."," Order ",[815,3547,3548],{},"SO-88412"," is blocked in WMS — credit hold on the account, but ops also sees allocation pressure on a promotional SKU. The 3PL must know by 18:00 whether to pick tonight. Finance is in close week. The AE pasted a promise from the customer into mail that is not in CRM.",[191,3551,3552,3555,3556,3558],{},[470,3553,3554],{},"Without a shared job."," Ops posts in ",[815,3557,3451],{},". Finance sees it hours later. Someone runs a personal copilot on the ageing extract in a private window. A release note drafts fluently; nobody signs. The 3PL picks the wrong line because “hold lifted” meant two different things in two channels. Night shift inherits a mess and a cutoff.",[191,3560,3561,3564,3565,411],{},[470,3562,3563],{},"With a shared job."," One named exception: ",[815,3566,3567],{},"Release hold — SO-88412",[191,3569,3570],{},"On the roster: ops supervisor, finance delegate, AE as guest (read-only on margin), 3PL coordinator as guest (pick instruction slice only).",[191,3572,3573],{},"Attachments once:",[242,3575,3576,3579,3582],{},[245,3577,3578],{},"WMS hold snapshot with reason codes.",[245,3580,3581],{},"AR ageing excerpt for the account.",[245,3583,3584],{},"Customer PO PDF the AE would otherwise re-forward.",[191,3586,3587],{},"The model’s bounded role:",[242,3589,3590,3593,3596,3603],{},[245,3591,3592],{},"Read attachments and CRM credit status (read-only).",[245,3594,3595],{},"Draft a release checklist: what must be true to lift hold, what remains allocation-risk.",[245,3597,3598,3599,3602],{},"Propose a WMS release ",[470,3600,3601],{},"payload"," — order, hold code, before\u002Fafter — for sign.",[245,3604,3605],{},"Not release. Not email the customer. Not change credit limit.",[191,3607,3608,3609,3612],{},"Finance rejects: margin on the promo line still below floor; require revised pricing or CFO delegate. Rejection ",[470,3610,3611],{},"stored on the job"," with name and time — visible to ops and the 3PL without a side call.",[191,3614,3615],{},"Ops adjusts pick plan: ship non-promo lines tonight; keep promo on hold. 3PL sees the scoped update on the same job. Named closer for this exception type — finance delegate — signs the partial release payload. Fail-closed: unsigned payload does not touch WMS.",[191,3617,3618,3619,3622,3623,3627],{},"Next shift opens the ",[470,3620,3621],{},"same job",". No reconstruction. ",[198,3624,3626],{"href":3625},"governance-as-a-multiplayer-primitive","Governance as a multiplayer primitive"," is why roster, rejection, and inherited authority lived in the room.",[809,3629,3631],{"className":811,"code":3630,"language":813,"meta":171,"style":171},"flowchart LR\n  wms[\"Warehouse hold\"] --> job[\"Ops exception\"]\n  ar[\"Finance ageing\"] --> job\n  partner[\"Partner order\"] --> job\n  agent[\"Draft checklist\"] --> job\n  job --> finance{\"Finance signs?\"}\n  finance -->|no| stored[\"Rejection stored\"]\n  finance -->|yes| release[\"Hold released\"]\n",[815,3632,3633,3637,3642,3647,3652,3657,3662,3667],{"__ignoreMap":171},[818,3634,3635],{"class":820,"line":821},[818,3636,824],{},[818,3638,3639],{"class":820,"line":172},[818,3640,3641],{},"  wms[\"Warehouse hold\"] --> job[\"Ops exception\"]\n",[818,3643,3644],{"class":820,"line":832},[818,3645,3646],{},"  ar[\"Finance ageing\"] --> job\n",[818,3648,3649],{"class":820,"line":838},[818,3650,3651],{},"  partner[\"Partner order\"] --> job\n",[818,3653,3654],{"class":820,"line":844},[818,3655,3656],{},"  agent[\"Draft checklist\"] --> job\n",[818,3658,3659],{"class":820,"line":850},[818,3660,3661],{},"  job --> finance{\"Finance signs?\"}\n",[818,3663,3664],{"class":820,"line":856},[818,3665,3666],{},"  finance -->|no| stored[\"Rejection stored\"]\n",[818,3668,3669],{"class":820,"line":1392},[818,3670,3671],{},"  finance -->|yes| release[\"Hold released\"]\n",[191,3673,3674],{},"The same shape applies to allocation shorts, quarantine lots, and missed carrier cutoffs. Change the attachments and the closer. Keep the rule: one job, one roster, one stored “no” before execute.",[191,3676,3677,3678,3681,3682,3685,3686,3689,3690,3693],{},"Sibling walkthroughs if your exception is not a hold: ",[198,3679,3680],{"href":402},"revenue operations"," for stage conflicts, ",[198,3683,3684],{"href":480},"finance and planning"," for close exceptions, ",[198,3687,3688],{"href":1451},"customer support"," for ticket commitments, ",[198,3691,3692],{"href":2389},"human resources"," for people decisions. Ops is the physical-clock version.",[208,3695,3697],{"id":3696},"what-belongs-on-the-ops-roster","What belongs on the ops roster",[191,3699,3700,3703],{},[470,3701,3702],{},"Ops supervisor"," — owns the SLA clock, proposes pick plans, cannot sign a credit override unless also named delegate.",[191,3705,3706,3709],{},[470,3707,3708],{},"Finance delegate"," — signs or rejects release payloads; sees margin sheets; does not inherit 3PL pick scopes.",[191,3711,3712,3715],{},[470,3713,3714],{},"AE or CS guest"," — customer context, read-only on finance slices; no write token.",[191,3717,3718,3721],{},[470,3719,3720],{},"3PL \u002F carrier guest"," — pick and ship instruction for their lane only.",[191,3723,3724,3727,3728,3731],{},[470,3725,3726],{},"Named closer"," — the role allowed to clear ",[470,3729,3730],{},"this"," hold class after fail-closed review. Not “whoever is online.”",[191,3733,3734,3736,3737,3739,3740,3742],{},[198,3735,266],{"href":265}," is the access model. ",[198,3738,665],{"href":664}," is the execute gate on WMS or ERP writes. ",[198,3741,2286],{"href":2285}," is the closer on this job, for this payload.",[191,3744,3745,3746,3748],{},"Inherited authority matters more in ops than in a drafting copilot. A WMS connector that can release any hold is a loaded tool. A warehouse supervisor without credit authority must not inherit that tool because the prompt was confident. ",[198,3747,3626],{"href":3625}," is the architecture; the roster is the instance.",[191,3750,3751,3753],{},[198,3752,2073],{"href":2072}," is when to stay personal. A supervisor drafting a shift note that never leaves the building can keep a copilot. A hold that a 3PL will pick against cannot.",[208,3755,3757],{"id":3756},"how-to-get-more-from-ai-on-exceptions","How to get more from AI on exceptions",[191,3759,3760,3761,3764],{},"Ask for ",[470,3762,3763],{},"lists and payloads",", not narratives.",[336,3766,3767,3773,3779,3785,3791],{},[245,3768,3769,3772],{},[470,3770,3771],{},"Exception queue on the job"," — hold ID, age, reason code, owner on roster.",[245,3774,3775,3778],{},[470,3776,3777],{},"Conflict list"," when sources disagree — WMS says credit; AR says within terms; AE mail says rush.",[245,3780,3781,3784],{},[470,3782,3783],{},"Release checklist"," tied to policy version — what must be true before sign.",[245,3786,3787,3790],{},[470,3788,3789],{},"Payload quote"," before any WMS write — exact order, hold code, partial vs full.",[245,3792,3793,3796],{},[470,3794,3795],{},"Stored rejection"," as a first-class outcome — finance’s “no” is data, not drama.",[191,3798,3799,3800,3802,3803,3805],{},"The harness — tools, stops, checks around the model — keeps “just release it” from becoming an unsupervised clerk. ",[198,3801,2598],{"href":352}," is the environment guide. ",[198,3804,2375],{"href":2374}," is the sheet to score whether any vendor keeps files, rejections, and second departments on the same job.",[191,3807,3808],{},"Do not start with customer-facing mail from the exception room, or bulk hold releases across a region. Those are writes to relationships and systems of record. Read, list, reject, then sign.",[191,3810,3811,3812,3814,3815,3818],{},"If the exception is already a known Monday checklist — same extract, same rules, same notify list — do not restaff it with an improvising agent every week. ",[198,3813,2436],{"href":505}," compiles that path; ",[198,3816,3817],{"href":590},"a loop is not an agent"," is the distinction. Collaborative ops still needs a roster on the exceptions the loop cannot close. The loop lists; the room decides.",[191,3820,3821,3825],{},[198,3822,3824],{"href":1181,"rel":3823},[225],"NIST’s AI Risk Management Framework"," asks for measurable governance. In a warehouse, measure reopen time across a shift change, signer completeness on release payloads, and how often a hold is re-asked in chat after the job exists. If chat re-asks stay high, the room is not the system of record yet.",[208,3827,3829],{"id":3828},"how-to-start-with-one-hold-reason","How to start with one hold reason",[191,3831,3832],{},"Pick one recurring hold — credit, allocation, quarantine — that already pings three roles daily.",[191,3834,3835],{},"Four cycles:",[336,3837,3838,3844,3850,3856],{},[245,3839,3840,3843],{},[470,3841,3842],{},"Week 1:"," Read-only WMS and AR on one named job; roster ops and finance; model lists open holds; no write.",[245,3845,3846,3849],{},[470,3847,3848],{},"Week 2:"," Finance stores a rejection on a real release proposal; 3PL guest sees a scoped pick note on the same job.",[245,3851,3852,3855],{},[470,3853,3854],{},"Week 3:"," Swap shift lead; reopen job; continue without Slack.",[245,3857,3858,3861],{},[470,3859,3860],{},"Week 4:"," Enable fail-closed WMS write with payload quote; named closer signs one partial release.",[191,3863,3864],{},"You can start with a shared folder and a written stop if that is what you have — but measure whether Monday still has finance’s “no.” A folder without a roster is still five inboxes with a nicer icon.",[191,3866,3867,404,3869,3873,3874,3878],{},[198,3868,2375],{"href":2374},[198,3870,3872],{"href":3871},"how-to-evaluate-an-agent-harness","how to evaluate an agent harness"," are the sibling sheets if a vendor is in the room. Run them on this hold, not on a polished demo order. ",[198,3875,3877],{"href":3876},"four-pillars-of-an-enterprise-ai-platform","Four pillars of an enterprise AI platform"," is the wider stack if you need language for wiki, routing, and governance around the exception.",[191,3880,3881,3886],{},[198,3882,3885],{"href":3883,"rel":3884},"https:\u002F\u002Fwww.iso.org\u002Fstandard\u002F42001",[225],"ISO\u002FIEC 42001"," wants named actors. A hold class with a named closer is closer to that instinct than a shared WMS login and a hopeful prompt. You do not need a management-system project to name the closer on credit holds this month.",[208,3888,3890],{"id":3889},"what-people-get-wrong","What people get wrong",[191,3892,3893,3896],{},[470,3894,3895],{},"“The chatbot can see WMS, so we are collaborative.”"," Sight is not a roster. A private window with a connector is a personal assistant with a larger blast radius.",[191,3898,3899,3902],{},[470,3900,3901],{},"“We’ll email the 3PL the summary.”"," That forks the truth. The partner needs a scoped view on the same job, or they will pick against a stale sentence.",[191,3904,3905,3908],{},[470,3906,3907],{},"“Finance can look it up in the ERP.”"," They can. They will not, at 17:40, in close week, for every hold. Put them on the job or accept the re-ask.",[191,3910,3911,3914],{},[470,3912,3913],{},"“Night shift will search the channel.”"," That is the coordination tax Asana measured. A named job is how you stop paying it.",[191,3916,3917,3920],{},[470,3918,3919],{},"“Release everything the model is confident about.”"," Confidence is not authority. Inherited authority and fail-closed writes are the primitive. Fluency is not.",[191,3922,3923,3926,3927,3930],{},[470,3924,3925],{},"“We will add the closer after we see value.”"," Value on exceptions ",[597,3928,3929],{},"is"," the closer. A fluent checklist without a signer is how holds clear for the wrong reason.",[208,3932,3934],{"id":3933},"the-operational-finish-line","The operational finish line",[191,3936,3937,3938,3941],{},"Collaborative AI for operations ends when the exception has a ",[470,3939,3940],{},"closer",", not when the model produces a fluent summary. The signed release payload, the stored rejection, and the attachments outlive the agent and the shift.",[191,3943,3944],{},"Put the room where the handoff already happens — on the job, with roster and fail-closed write — and ops stops paying the tax of re-asking why the hold is still there.",[208,3946,964],{"id":963},[191,3948,3949,3950,3953,3954,411],{},"In Nimbus, the exception room is a ",[198,3951,3952],{"href":32},"workstream",": WMS and AR attachments once, ops and finance on the roster, 3PL as a scoped guest, and a fail-closed release payload under ",[198,3955,972],{"href":40},[191,3957,3958,3959,411],{},"The agent drafts the checklist and quotes the write. It does not clear the hold. Shift change is a reopen of the same workstream, not a new chat. Standing hold-list jobs that should not improvise can be compiled as loops on that workstream — see ",[198,3960,3961],{"href":510},"what is a Nimbus Loop",[191,3963,3964,3965,3968,3969,3972],{},"Score any vendor, including this one, with ",[198,3966,3967],{"href":2374},"how to evaluate collaborative AI"," on a real hold reason. The ",[198,3970,3971],{"href":200},"use cases"," hub lists sibling functions if your first exception is not operational.",[985,3974,987],{},{"title":171,"searchDepth":172,"depth":172,"links":3976},[3977,3978,3979,3980,3981,3982,3983,3984,3985,3986],{"id":3397,"depth":172,"text":3398},{"id":3454,"depth":172,"text":3455},{"id":3500,"depth":172,"text":3501},{"id":3538,"depth":172,"text":3539},{"id":3696,"depth":172,"text":3697},{"id":3756,"depth":172,"text":3757},{"id":3828,"depth":172,"text":3829},{"id":3889,"depth":172,"text":3890},{"id":3933,"depth":172,"text":3934},{"id":963,"depth":172,"text":964},"Collaborative AI for operations is one shared job — exceptions, handoffs, a named closer — with WMS and finance on the same hold. Not causal replay; the live exception room.",{"eyebrow":1000,"title":3989},"Exceptions, handoffs, and the closer",[3991,3994,3997,3999],{"question":3992,"answer":3993},"Is this the same as causal AI for operations?","No. Causal ops answers why a field changed after the fact — brief, sources, signer, write, system response. Collaborative ops is the shared room while the hold is open: who sees it, who closes it, what gets signed. You need the live room to make later replay trustworthy. If the rejection lived only in a huddle, there is nothing honest to replay. Link the two ideas; do not merge the purchases. Start with the open exception, not the after-action dashboard.",{"question":3995,"answer":3996},"Should the model release holds automatically?","Not without a named closer on the roster and a payload quote finance can reject. Fail-closed until the exception type has a stored rejection test. Automatic release is how a fluent checklist becomes an unsupervised clerk. Read and list first. Store a “no” on a real proposal. Then, if the class is stable, enable one signed write with the exact order, hold code, and partial-versus-full visible to the roster. Bulk regional releases are a later question, not a week-one feature.",{"question":2478,"answer":3998},"One hold reason — credit, allocation, damaged lot — with WMS read-only, finance on the roster, and no production write until the handoff list is useful. Pick a reason that already pings three roles daily. Attach the two files people already email. Name the closer for that class. Run four cycles: list, reject, handover across a shift, then one fail-closed write. If Monday still requires Slack archaeology, do not enable execute. Expand reasons only after reopen time is boring.",{"question":4000,"answer":4001},"Is a warehouse chatbot enough if it can see WMS?","Seeing WMS is not sharing a job. A supervisor’s private thread that can query holds still dies at shift change. The night lead needs the same attachments, the same finance rejection, and the same closer — not a new summary. A chatbot with a connector is a personal assistant with a dangerous window. Put ops, finance, and the 3PL guest on one named exception. If the partner can only see their pick slice, that is a roster feature, not a prompt instruction.","\u002Fblog\u002Fcollaborative-ai-for-operations",{"title":3364,"description":3987},"blog\u002Fcollaborative-ai-for-operations",[442,4006,4007,2489],"operations","warehouse","QY62vzVMY18Xh_SNLMHhIrN6q6bgUkr7NYNLQchjxEI",{"id":4010,"title":4011,"archived":165,"authors":4012,"badge":4014,"body":4015,"date":4202,"definedTerm":166,"department":166,"description":4203,"extension":174,"eyebrow":166,"faqHeader":4204,"faqs":4206,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":4215,"relatedHeading":166,"seo":4216,"series":442,"sitemap":131,"status":166,"stem":4217,"subhead":166,"tags":4218,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":4220},"content\u002Fblog\u002Fcollaborative-ai-for-revenue-operations.md","What is collaborative AI for revenue operations?",[4013],{"name":185,"to":136},{"label":187},{"type":168,"value":4016,"toc":4195},[4017,4020,4023,4033,4036,4039,4042,4053,4056,4059,4063,4066,4069,4072,4080,4084,4087,4090,4101,4103,4120,4125,4128,4133,4137,4140,4143,4146,4149,4151,4153,4158,4162,4165,4168,4182,4185,4192],[191,4018,4019],{},"Collaborative AI for revenue operations is one shared job that RevOps, sales, and finance already run every week: clean the pipeline, then produce a forecast finance will sign and sales will use. The model sits in that room. It lists conflicts. A named person decides. It is not a copilot that writes a story from whichever export the analyst pasted.",[191,4021,4022],{},"You should care if the CRM and the sheet already disagree, and the most valuable information in the week is that disagreement. A fluent paragraph can hide it. This is a how-to for one exception type, not a claim that your CRM is the wrong system of record.",[191,4024,4025,4027,4028,4030,4031,411],{},[198,4026,205],{"href":204}," is the definition. The ",[198,4029,100],{"href":200}," hub is the parent. The job can live on a ",[198,4032,3952],{"href":32},[208,4034,4011],{"id":4035},"what-is-collaborative-ai-for-revenue-operations",[191,4037,4038],{},"Monday often starts with a hygiene list: missing close dates, stages that do not match activity, duplicates, Amounts that sales changed in a sheet because CRM “is wrong.” By Wednesday a forecast pack is due. Finance will put a number in board materials. Sales leadership will talk to the field as if that number were the pipeline.",[191,4040,4041],{},"Who already works:",[242,4043,4044,4047,4050],{},[245,4045,4046],{},"RevOps knows the CRM fields and the usual gaps in the data.",[245,4048,4049],{},"Sales knows the deals that are real this week, including the ones not yet typed in.",[245,4051,4052],{},"Finance knows which number they will sign, and which definitions — bookings versus pipeline, currencies, pulled-forward deals — are in force.",[191,4054,4055],{},"Collaborative AI puts those three on one job with the same files. The AI role is named: it may read this CRM view and this sheet; it may draft the conflict list; it may not send customer mail; it may not change Amount until a named person signs.",[191,4057,4058],{},"A Monday hygiene list nobody acts on by Friday is a report, not a job. Attach owners to the conflicts you expect the field to fix.",[208,4060,4062],{"id":4061},"why-should-revops-care","Why should RevOps care?",[191,4064,4065],{},"Because the conflict is the work, and narrative is easy to over-produce.",[191,4067,4068],{},"CRM says one Amount. The sheet sales sent at 22:00 says another. Stage in CRM is “commit.” The AE’s message says “slipped.” RevOps is asked to “make it consistent.” A personal assistant picks the fluent story. The board pack then matches neither system.",[191,4070,4071],{},"The sheet exists because a human often knows something the system does not — a verbal slip, a procurement freeze, a champion who left. Deleting the disagreement can delete that knowledge and leave a tidy field that is confidently wrong. One useful rule: the model may list conflicts and may not resolve them, because resolution has a name attached.",[191,4073,4074,4076,4077,4079],{},[198,4075,1970],{"href":480}," is the same pattern when the signed artefact is books rather than pipeline. ",[198,4078,2073],{"href":2072}," is when an AE’s private draft should stay private.",[208,4081,4083],{"id":4082},"how-do-you-get-more-from-ai-on-pipeline-and-exceptions","How do you get more from AI on pipeline and exceptions?",[191,4085,4086],{},"Ask the model for a deal-by-deal list, not a narrative.",[191,4088,4089],{},"Put both sources on the job as sources:",[242,4091,4092,4095,4098],{},[245,4093,4094],{},"The CRM connection, read-only, scoped to the pipeline this forecast covers.",[245,4096,4097],{},"The sheet, attached, with who produced it and when.",[245,4099,4100],{},"The definition finance uses.",[191,4102,2245],{},[336,4104,4105,4108,4111,4114,4117],{},[245,4106,4107],{},"Generate the conflict list. Keep both values visible.",[245,4109,4110],{},"Assign owners on the roster for the rows the field must fix.",[245,4112,4113],{},"Draft the forecast number only after finance can see the same list.",[245,4115,4116],{},"Treat a CRM edit as write-back — when AI changes a live system — with a payload: the exact records, fields, before and after.",[245,4118,4119],{},"Keep fail-closed: if nobody approves, nothing happens in CRM, and the sheet does not overwrite CRM because a prompt was confident.",[191,4121,4122,4124],{},[198,4123,665],{"href":664}," is the control on that step. Until finance has signed, CRM writes for forecast cosmetics can wait. Read and list first.",[191,4126,4127],{},"Do not start with customer emails from the forecast, or with bulk stage changes. Those are writes to a relationship or to the system of record. A prompt academy for AEs is also not a substitute for the job; prompts copy the org chart, region by region.",[191,4129,4130,4131,3277],{},"The harness — the tools, stops, and checks around the model — is what keeps “just fix stage” from becoming an unsupervised clerk. ",[198,4132,2598],{"href":352},[208,4134,4136],{"id":4135},"what-does-a-shared-revops-job-look-like","What does a shared RevOps job look like?",[191,4138,4139],{},"One room, one week.",[191,4141,4142],{},"RevOps members attach files, list conflicts, and propose field changes. They do not sign the board number unless they are also the named finance delegate. Finance rejects a definition, a pulled-in deal, or a currency treatment, and signs the artefact. Sales proposes “this deal is real” and cannot win a conflict by editing the sheet after finance has signed. A regional manager as guest sees their slice, not the whole pipeline and not the write token.",[191,4144,4145],{},"The signed forecast contains the number, the definition in force, the date and period, the named signer, the unresolved conflicts that were accepted and by whom, and the hygiene list still open. The narrative the model drafted is colour, not signature.",[191,4147,4148],{},"After signature, a new sheet that “updates” the number is a new proposal. A later prompt that rewrites the number because a deal moved is a new version with a new sign. CRM may be updated after the sign, as a write with a payload — or it may wait.",[191,4150,4145],{},[191,4152,4148],{},[191,4154,4155,4156,411],{},"RBAC — who is allowed to do what — keeps a guest from inheriting the write token. See ",[198,4157,266],{"href":265},[208,4159,4161],{"id":4160},"how-do-you-start-with-one-exception-type","How do you start with one exception type?",[191,4163,4164],{},"Pick one recurring exception: discounts outside the grid, slipped commit deals, duplicate accounts in one region, Amount mismatches above a threshold.",[191,4166,4167],{},"Four Mondays:",[336,4169,4170,4173,4176,4179],{},[245,4171,4172],{},"Read-only CRM plus the actual sheet for that slice.",[245,4174,4175],{},"A conflict list the model may not round off.",[245,4177,4178],{},"A named finance signer.",[245,4180,4181],{},"No production writes until the list is useful without them.",[191,4183,4184],{},"Count how many conflicts were still resolved in side chats. If that number does not fall, you automated a narrative rather than the room. Keep a short note: who was on the roster, which connection was read-only, how many Amount edits were proposed and rejected, whether sales used the signed number or a new sheet.",[191,4186,967,4187,4189,4190,411],{},[198,4188,395],{"href":32}," hold the weekly instance. You can start in a shared folder and a ticket. For access on the room, see ",[198,4191,266],{"href":265},[191,4193,4194],{},"The weekly ritual is not there to force agreement. It is there to make the disagreement explicit, give it a name, and end with one number somebody signed. Automate the listing. Leave the resolving to a person.",{"title":171,"searchDepth":172,"depth":172,"links":4196},[4197,4198,4199,4200,4201],{"id":4035,"depth":172,"text":4011},{"id":4061,"depth":172,"text":4062},{"id":4082,"depth":172,"text":4083},{"id":4135,"depth":172,"text":4136},{"id":4160,"depth":172,"text":4161},"2026-08-23","Collaborative AI for RevOps is one shared job — pipeline hygiene and a signed forecast — with CRM and sheet both visible. A guide to exceptions, not a narrative generator.",{"eyebrow":425,"title":4205},"Pipeline, exceptions, and the signed number",[4207,4210,4213],{"question":4208,"answer":4209},"Should AI merge the CRM and the AE’s sheet?","Not as a silent average. List both values. Name who wins each conflict this week. The sheet often holds knowledge the CRM does not — a verbal slip, a freeze, a champion who left.",{"question":4211,"answer":4212},"Can the model fix stages automatically?","Treat a stage change as a write to a live system. Show the exact records and fields. If nobody approves, nothing happens. Bulk cosmetics before a signer exists are how data goes wrong quickly.",{"question":2478,"answer":4214},"One exception type or one region. Read-only CRM plus the actual sheet, a conflict list, a named finance signer, and no production writes until the list is useful.","\u002Fblog\u002Fcollaborative-ai-for-revenue-operations",{"title":4011,"description":4203},"blog\u002Fcollaborative-ai-for-revenue-operations",[442,2039,4219,2041],"forecast","zNzuKOweHcByyAN_wTqFLe6i5fNBn48qD_z5dLgwwmw",{"id":4222,"title":4223,"archived":165,"authors":4224,"badge":4226,"body":4227,"date":4387,"definedTerm":445,"department":166,"description":4388,"extension":174,"eyebrow":166,"faqHeader":4389,"faqs":4391,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":4401,"relatedHeading":166,"seo":4402,"series":442,"sitemap":131,"status":166,"stem":4403,"subhead":166,"tags":4404,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":4405},"content\u002Fblog\u002Fwhat-is-collaborative-ai.md","What is collaborative AI, and why should you care?",[4225],{"name":185,"to":136},{"label":187},{"type":168,"value":4228,"toc":4380},[4229,4232,4238,4241,4244,4255,4258,4264,4272,4276,4279,4285,4293,4296,4300,4303,4317,4328,4335,4339,4342,4354,4360,4364,4367,4372],[191,4230,4231],{},"Collaborative AI is when several people work on one piece of work with the same context, the same tools, and a named finish line — and the AI is in that shared place, not only in each person’s private chat.",[191,4233,4234,4235,4237],{},"Personal assistants are good at drafting. Shared jobs need a shared room. The ",[198,4236,100],{"href":200}," hub is the rest of the series.",[208,4239,4240],{"id":204},"What is collaborative AI?",[191,4242,4243],{},"At minimum it has four parts:",[242,4245,4246,4249,4251,4253],{},[245,4247,4248],{},"A named job (not “the channel”).",[245,4250,250],{},[245,4252,253],{},[245,4254,256],{},[191,4256,4257],{},"That is different from giving the team one login to a chatbot. The login is still a personal product. Collaborative AI is the job as the unit.",[191,4259,310,4260,4263],{},[198,4261,315],{"href":313,"rel":4262},[225]," (2025) found that 88% of organisations use AI in at least one function, while most are still in the pilot stage. Use is common. Shared process is not.",[191,4265,4266,4268,4269,4271],{},[198,4267,273],{"href":272}," is the sibling distinction for several people in one session versus a cast of models. ",[198,4270,2073],{"href":2072}," is the comparison with copilots.",[208,4273,4275],{"id":4274},"why-should-you-care-about-collaborative-ai","Why should you care about collaborative AI?",[191,4277,4278],{},"You should care when a mistake is expensive because two teams thought they were looking at the same thing and were not.",[191,4280,3461,4281,4284],{},[198,4282,2798],{"href":2796,"rel":4283},[225]," (2022), found that firm-wide remote work made collaboration networks more static and siloed. Shared jobs already fight that pull. AI that lives only in private threads can make the silo worse: each person has a fluent answer, and nobody has the same file.",[191,4286,4287,4292],{},[198,4288,4291],{"href":4289,"rel":4290},"https:\u002F\u002Fwww.melconway.com\u002FHome\u002FCommittees_Paper.html",[225],"Melvin Conway’s 1968 paper"," noted that organisations design systems that copy their communication structure. If the structure is one person and one chat, the AI will copy that. Collaborative AI is a chance to copy the meeting you already needed, not the inbox.",[191,4294,4295],{},"If your work is mostly solo drafting, a personal assistant may be the right tool. Collaborative AI is for the jobs that already required a meeting.",[208,4297,4299],{"id":4298},"how-do-you-get-more-from-collaborative-ai","How do you get more from collaborative AI?",[191,4301,4302],{},"Treat it like a project room, not like a better chatbot.",[336,4304,4305,4308,4311,4314],{},[245,4306,4307],{},"Name the job and the finish line before you invite the model.",[245,4309,4310],{},"Put the files in the room, not in five inboxes.",[245,4312,4313],{},"Write down who can approve a change to a live system (when AI changes a customer record, a forecast, or a ticket).",[245,4315,4316],{},"Keep the debate in chat if you like; keep the outcome in the room.",[191,4318,4319,4321,4322,4324,4325,4327],{},[198,4320,2379],{"href":360}," is the container for step two. ",[198,4323,266],{"href":265}," is step three. ",[198,4326,2598],{"href":352}," is why the prompt alone is not the system.",[191,4329,4330,4331,4334],{},"If you are asking how the model is boxed in — tools, stops, checks — that is ",[198,4332,4333],{"href":352},"harness engineering",", the practice of improving the environment around the model rather than only the wording of the ask.",[208,4336,4338],{"id":4337},"what-does-this-look-like-on-a-real-job","What does this look like on a real job?",[191,4340,4341],{},"Sales wants a discount exception. Finance wants the margin intact. A personal assistant can draft the email. Collaborative AI would be a shared workstream: the CRM excerpt, the margin sheet, both teams in the same history, and a recorded approve before anything writes back to the account — write-back meaning AI changes a live system.",[191,4343,4344,4345,4347,4348,4350,4351,411],{},"Legal reviewing a clause with operations in the same place is the same pattern. So is a forecast that planning and FP&A both own. We walk those through in ",[198,4346,403],{"href":402},", ",[198,4349,3684],{"href":480},", and ",[198,4352,4353],{"href":1057},"legal and compliance review",[191,4355,4356,4357,4359],{},"If two teams still disagree after the files are in the room, that is expected. ",[198,4358,2154],{"href":1057}," is how to keep the quoted clause from pretending the argument is over.",[208,4361,4363],{"id":4362},"how-do-you-start-without-a-big-programme","How do you start without a big programme?",[191,4365,4366],{},"Pick one recurring cross-team job. Create one shared place. Add the people who already argue about it. Attach the two files they always forward. Decide who can say no. Run it for two cycles. Measure whether you still paste the same screenshot into chat.",[191,4368,4369,4370,396],{},"Nimbus’s ",[198,4371,395],{"href":32},[191,4373,4374,4375,4377,4378,411],{},"For how work should be handed between teams, see ",[198,4376,481],{"href":480},". For who is allowed to see the room, start with ",[198,4379,266],{"href":265},{"title":171,"searchDepth":172,"depth":172,"links":4381},[4382,4383,4384,4385,4386],{"id":204,"depth":172,"text":4240},{"id":4274,"depth":172,"text":4275},{"id":4298,"depth":172,"text":4299},{"id":4337,"depth":172,"text":4338},{"id":4362,"depth":172,"text":4363},"2026-08-14","Collaborative AI is several people sharing one job — context, tools, and a finish line — rather than each person using their own assistant. A guide to the definition, why it matters, and how to get more from it.",{"eyebrow":425,"title":4390},"Questions about the definition",[4392,4395,4398],{"question":4393,"answer":4394},"Is collaborative AI the same as a shared ChatGPT login?","No. A shared login is still a personal assistant used by several people. Collaborative AI is one job with shared context, shared tools, and a named person who can stop a change.",{"question":4396,"answer":4397},"Do we need it if everyone already has a copilot?","You need it when the work crosses departments or writes to a live system. A copilot helps one person draft. Collaborative AI is the place the draft becomes a shared result.",{"question":4399,"answer":4400},"Is collaborative AI the same as multiplayer AI?","They overlap. Multiplayer AI stresses several people in one session. Collaborative AI stresses the shared job — including what happens after the session ends.","\u002Fblog\u002Fwhat-is-collaborative-ai",{"title":4223,"description":4388},"blog\u002Fwhat-is-collaborative-ai",[442,445],"jcYofJLXOkObKfXxDoGZatBDFUvDuNOSaMZElf-JSlY",{"fold":4407,"id":4412,"title":4413,"archived":165,"authors":166,"badge":166,"body":4414,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":4418,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":4422,"relatedHeading":166,"seo":4423,"series":166,"sitemap":165,"status":166,"stem":4424,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":4425},{"headline":4408,"description":4409,"primaryLabel":8,"primaryTo":4410,"secondaryLabel":4411,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed agent swarms, 2,000+ integrations, and a knowledge graph that stays inside your walls. Start on Free.","\u002Fsignup?plan=free","Explore the platform","content\u002Fshared\u002Fcta.md","Site CTAs",{"type":168,"value":4415,"toc":4416},[],{"title":171,"searchDepth":172,"depth":172,"links":4417},[],{"headline":4419,"description":4420,"primaryLabel":8,"primaryTo":4410,"secondaryLabel":4421,"secondaryTo":85},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.","Talk to our team","\u002Fshared\u002Fcta",{"title":4413,"description":171},"shared\u002Fcta","PS2VPJsszmUpMBZT6nEp8cWXCdeiN6zDRl-p8d0uY2k",{"enabled":165,"message":4427,"linkLabel":79,"linkHref":80,"id":4428,"title":4429,"archived":165,"authors":166,"badge":166,"body":4430,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":4434,"relatedHeading":166,"seo":4435,"series":166,"sitemap":165,"status":166,"stem":4436,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":4437},"We're hiring! Join the team building the Sentient Enterprise.","content\u002Fshared\u002Fhiring.md","Hiring banner",{"type":168,"value":4431,"toc":4432},[],{"title":171,"searchDepth":172,"depth":172,"links":4433},[],"\u002Fshared\u002Fhiring",{"title":4429,"description":171},"shared\u002Fhiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",1790215700165]