[{"data":1,"prerenderedAt":1372},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/loops-for-finance-and-planning":179,"blog-index-copy":773,"blog:/blog/loops-for-finance-and-planning:surround":794,"hiring-banner-content":1341,"site-cta-content":1353},{"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","/overview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","/product/conflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","/product/agent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","/product/lifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","/product/wiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","/product/workstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","/product/perception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","/product/governance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","/models",{"label":47,"to":48},"Pricing","/pricing",{"label":50,"to":51},"Integrations","/integrations",{"label":53,"to":54},"Security","/security",{"label":56,"to":57},"Partners","/partners",{"label":59,"to":60},"Insights","/blog",{"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://docs.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","/careers",{"label":82,"to":83},"System status","/status",{"label":7,"to":85},"/contact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","/glossary",{"label":91,"to":92},"Compare","/compare",{"label":94,"to":95},"Evaluate","/evaluate",{"label":97,"to":98},"Problems","/problems",{"label":100,"to":101},"Use cases","/use-cases",[103,106],{"label":104,"to":105},"Terms of Service","/terms",{"label":107,"to":108},"Privacy Policy","/privacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https://www.linkedin.com/company/gonimbusai/",{"label":114,"href":115},"X","https://x.com/gonimbusai",{"label":117,"href":118},"Instagram","https://www.instagram.com/gonimbus_ai/",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","/compliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","/llms.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://gonimbus.ai",[138,143,148,153,158],{"name":139,"label":140,"icon":141,"hrefPrefix":142},"chatgpt","ChatGPT","simple-icons:openai","https://chatgpt.com/?prompt=",{"name":144,"label":145,"icon":146,"hrefPrefix":147},"perplexity","Perplexity","mdi:magnify","https://www.perplexity.ai/search/new?q=",{"name":149,"label":150,"icon":151,"hrefPrefix":152},"grok","Grok","simple-icons:x","https://x.com/i/grok?text=",{"name":154,"label":155,"icon":156,"hrefPrefix":157},"claude","Claude","simple-icons:anthropic","https://claude.ai/new?q=",{"name":159,"label":160,"icon":161,"hrefPrefix":162},"google-ai","Google AI","simple-icons:google","https://www.google.com/search?udm=50&aep=11&q=","content/shared/nav.md","Site navigation",false,null,{"type":168,"value":169,"toc":170},"minimark",[],{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[],"md","/shared/nav",{"title":164,"description":171},"shared/nav","1dD7ahDRl0SQ4hz53-kKo0tEFrGaLuaztZ3PPfp6a9k",{"id":180,"title":181,"archived":165,"authors":182,"badge":185,"body":187,"date":745,"definedTerm":166,"department":166,"description":746,"extension":174,"eyebrow":166,"faqHeader":747,"faqs":750,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":763,"relatedHeading":166,"seo":764,"series":765,"sitemap":131,"status":166,"stem":766,"subhead":166,"tags":767,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":772},"content/blog/loops-for-finance-and-planning.md","Loops for Finance and Planning",[183],{"name":184,"to":136},"Nimbus Research",{"label":186},"Use case",{"type":168,"value":188,"toc":736},[189,201,218,221,261,283,288,296,317,333,345,349,359,362,372,386,389,403,415,419,463,471,475,478,484,494,500,505,532,538,545,552,604,616,620,623,637,645,648,652,662,665,682,685,705,708,712,722,732],[190,191,192,193,200],"p",{},"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. ",[194,195,199],"a",{"href":196,"rel":197},"https://www.govinfo.gov/content/pkg/PLAW-107publ204/html/PLAW-107publ204.htm",[198],"nofollow","Sarbanes-Oxley"," (US Congress, 2002) does not mention standing orders; it still asks issuers for a trail showing how a number became the number.",[190,202,203,204,208,209,212,213,217],{},"This page is ",[205,206,207],"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 ",[205,210,211],{},"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 ",[194,214,216],{"href":215},"collaborative-ai-for-finance-and-planning","collaborative AI for finance and planning",".",[190,219,220],{},"Three nouns, as vocabulary:",[222,223,224,235,251],"ul",{},[225,226,227,230,231,217],"li",{},[205,228,229],{},"Eval loop"," — a completion sensor. After a signed journal, read-back accounts and amounts. See ",[194,232,234],{"href":233},"eval-loops-for-enterprise-agent-harnesses","eval loops for enterprise agent harnesses",[225,236,237,240,241,245,246,250],{},[205,238,239],{},"Standing-order loop"," — a compiled recipe that admits a run when a trigger fires. See ",[194,242,244],{"href":243},"what-is-loop-engineering","what is loop engineering"," and the ",[194,247,249],{"href":248},"what-is-a-nimbus-loop","standing-order loop"," definition.",[225,252,253,256,257,217],{},[205,254,255],{},"Agentic workflow"," — open-ended replan, such as “close the books” with no saved recipe. See ",[194,258,260],{"href":259},"what-is-an-agentic-workflow","what is an agentic workflow",[190,262,263,266,267,272,273,278,279,282],{},[194,264,199],{"href":196,"rel":265},[198]," (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. ",[194,268,271],{"href":269,"rel":270},"https://www.law.cornell.edu/uscode/text/15/7262",[198],"Section 404",", as implemented in the ",[194,274,277],{"href":275,"rel":276},"https://www.sec.gov/files/rules/interp/2007/33-8810.pdf",[198],"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, ",[205,280,281],{},"SOX reconstruction still matters for what the loop produced",": which extract, which period, which recipe version, who was notified, what was skipped.",[284,285,287],"h2",{"id":286},"what-a-finance-standing-order-loop-is","What a finance standing-order loop is",[190,289,290,291,295],{},"Three common starts, from ",[194,292,294],{"href":293},"six-things-that-start-a-loop","six things that start a loop",":",[297,298,299,305,311],"ol",{},[225,300,301,304],{},[205,302,303],{},"When the calendar says Monday"," — the recurring pack: actuals vs plan, exception list, driver tab refresh.",[225,306,307,310],{},[205,308,309],{},"When the numbers moved"," — ledger extract updated, cube refreshed, material variance against threshold.",[225,312,313,316],{},[205,314,315],{},"When the file lands"," — business partner uploads the operational file that explains the line.",[190,318,319,320,323,324,327,328,332],{},"The job is narrow: detect the start, pull the ",[205,321,322],{},"same scoped reads"," every time, produce the pack or exception list, and ",[205,325,326],{},"skip"," when the extract hash matches last run. It does not post journals. Posting belongs on the collaborative job with a named controller sign. ",[194,329,331],{"href":330},"a-loop-is-not-an-agent","A loop is not an agent",": the standing order does not sign the pack.",[190,334,335,336,340,341,344],{},"Pin the plan version and the definitions — currency, BU map, bookings versus pipeline — on the job ",[337,338,339],"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 ",[205,342,343],{},"locked"," plan version, not against whichever file arrived last.",[284,346,348],{"id":347},"why-fpa-or-the-controller-should-care","Why FP&A or the controller should care",[190,350,351,352,355,356,217],{},"Because speed is the usual failure mode, and unattended ",[205,353,354],{},"drafting"," is safer than unattended ",[205,357,358],{},"posting",[190,360,361],{},"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.",[190,363,364,365,368,369],{},"The common belief is that controls live at the ERP write. The plan and the commentary often become management truth ",[205,366,367],{},"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: ",[205,370,371],{},"the standing order produces the draft pack; the collaborative job signs what people act on.",[190,373,374,375,380,381,385],{},"McKinsey’s ",[194,376,379],{"href":377,"rel":378},"https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai",[198],"State of AI"," (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. ",[194,382,384],{"href":383},"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.",[190,387,388],{},"You should care if:",[222,390,391,394,397,400],{},[225,392,393],{},"the “Monday pack” is already a chain of exports nobody can replay",[225,395,396],{},"a commentary cited August actuals and nobody can find that extract",[225,398,399],{},"journals still post from a confirm box the analyst clicks through",[225,401,402],{},"the line received a “new target” from an automation that nobody signed",[190,404,405,409,410,414],{},[194,406,408],{"href":407},"what-is-write-back-governance","Write-back governance"," stays on the journal path. ",[194,411,413],{"href":412},"collaborative-ai-for-revenue-operations","Collaborative AI for revenue operations"," is the sibling when the moving number is pipeline, not books.",[284,416,418],{"id":417},"words-you-will-hear","Words you will hear",[222,420,421,427,433,439,445,451,457],{},[225,422,423,426],{},[205,424,425],{},"Extract hash."," A fingerprint of the actuals file or ERP pull. Unchanged hash → skip.",[225,428,429,432],{},[205,430,431],{},"Locked plan version."," The plan the recipe rebuilds against. Not “latest.”",[225,434,435,438],{},[205,436,437],{},"Exception list."," Rows that crossed a threshold, with sources cited.",[225,440,441,444],{},[205,442,443],{},"Commentary skeleton."," Draft language that points at attached sources — not a private rewrite.",[225,446,447,450],{},[205,448,449],{},"SOX reconstruction."," An independent reader can chain extract → inputs → signed pack.",[225,452,453,456],{},[205,454,455],{},"Eval loop."," After a signed journal, read-back matches payload.",[225,458,459,462],{},[205,460,461],{},"Agentic workflow."," “Explain variance” with no saved recipe — expensive, uneven.",[190,464,465,470],{},[194,466,469],{"href":467,"rel":468},"https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/artificial-intelligence/",[198],"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.",[284,472,474],{"id":473},"how-to-compile-one-finance-standing-order","How to compile one finance standing order",[190,476,477],{},"Start from a close ritual someone already runs.",[190,479,480,481],{},"Example: ",[205,482,483],{},"Weekly variance when actuals refresh",[190,485,486,489,490,493],{},[205,487,488],{},"Trigger:"," file lands in the controlled folder ",[205,491,492],{},"or"," ERP actuals extract event.",[190,495,496,499],{},[205,497,498],{},"Preconditions:"," read-only ERP or warehouse connection; pinned definitions; last extract hash stored.",[190,501,502],{},[205,503,504],{},"Steps:",[297,506,507,510,516,523,529],{},[225,508,509],{},"Pull actuals for the agreed period and scope.",[225,511,512,513,515],{},"Compare hash to last run. If unchanged, ",[205,514,326],{}," and log.",[225,517,518,519,522],{},"Rebuild variance against the ",[205,520,521],{},"locked plan version"," — not “latest workbook in email.”",[225,524,525,526,217],{},"Draft exception list and commentary skeleton that ",[205,527,528],{},"cites attached sources",[225,530,531],{},"Land outputs on the run record; notify FP&A and controller roster.",[190,533,534,537],{},[205,535,536],{},"Explicit non-goals:"," no journal post; no planning-cube write that behaves like books; no email to the line with “your new target.”",[190,539,540,541,544],{},"When commentary must commit the business, open the ",[205,542,543],{},"collaborative"," planning job. Partner rejects there. Controller signs there. The standing order may attach the run record as input.",[190,546,547,548,551],{},"A second common compile: ",[205,549,550],{},"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.",[553,554,558],"pre",{"className":555,"code":556,"language":557,"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",[559,560,561,569,574,580,586,592,598],"code",{"__ignoreMap":171},[562,563,566],"span",{"class":564,"line":565},"line",1,[562,567,568],{},"flowchart LR\n",[562,570,571],{"class":564,"line":172},[562,572,573],{},"  actuals[\"Actuals file lands\"] --> hashCheck{\"Same file as last week?\"}\n",[562,575,577],{"class":564,"line":576},3,[562,578,579],{},"  hashCheck -->|yes| skipNode[\"Skip, logged\"]\n",[562,581,583],{"class":564,"line":582},4,[562,584,585],{},"  hashCheck -->|no| compilePack[\"Compile the Monday pack\"]\n",[562,587,589],{"class":564,"line":588},5,[562,590,591],{},"  compilePack --> runPage[\"Outputs on the run page\"]\n",[562,593,595],{"class":564,"line":594},6,[562,596,597],{},"  runPage --> notifyFpna[\"Notify the roster\"]\n",[562,599,601],{"class":564,"line":600},7,[562,602,603],{},"  runPage --> signOffRoom[\"Sign-off room\"]\n",[190,605,606,607,610,611,615],{},"Eval loops still matter on the ",[205,608,609],{},"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.” ",[194,612,614],{"href":613},"how-to-evaluate-loop-engineering","How to evaluate loop engineering"," asks whether you can replay triggers and skips — the finance equivalent of audit reconstruction.",[284,617,619],{"id":618},"what-done-looks-like","What “done” looks like",[190,621,622],{},"A good finance standing-order week:",[222,624,625,628,631,634],{},[225,626,627],{},"The run record shows extract period, hash, recipe version, skip or delta.",[225,629,630],{},"The exception list points at sources on the job, not at a private chat rewrite.",[225,632,633],{},"No ERP post from the standing order.",[225,635,636],{},"An independent reader can open the collaborative signed pack and trace inputs to the loop run without the authors’ memory.",[190,638,639,640,644],{},"Retention on run logs should match how long you must explain the number — not how long chat keeps threads. ",[194,641,643],{"href":642},"rbac-for-enterprise-ai","RBAC for enterprise AI"," applies: the standing order uses read grants. Posting tokens stay on human signers.",[190,646,647],{},"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.",[284,649,651],{"id":650},"how-to-start-with-one-trigger","How to start with one trigger",[190,653,654,655,658,659,661],{},"Pick ",[205,656,657],{},"when the file lands"," if actuals already arrive in a folder — or ",[205,660,550],{}," if timing is fixed.",[190,663,664],{},"This cycle:",[297,666,667,670,673,676,679],{},[225,668,669],{},"Name the artefact the standing order may produce: exception list, variance tab — not the signed board number.",[225,671,672],{},"Pin definitions and plan version on the job.",[225,674,675],{},"Add controller or deputy and FP&A to the roster for notifications.",[225,677,678],{},"Require skip logs when hash unchanged.",[225,680,681],{},"After four runs, ask an independent reader to reconstruct the pack from the run record alone.",[190,683,684],{},"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.",[190,686,687,691,692,696,697,691,699,701,702,704],{},[194,688,690],{"href":689},"loops-for-revenue-operations","Loops for revenue operations"," and ",[194,693,695],{"href":694},"loops-for-legal-and-compliance","loops for legal and compliance"," cover pipeline and policy triggers. If the pack is still a chat ritual, read ",[194,698,244],{"href":243},[194,700,294],{"href":293}," before you pick a trigger. ",[194,703,331],{"href":330}," is why the Monday compile should not invent a journal.",[190,706,707],{},"Automate the pack compile. Leave the signature on the artefact people act on — and keep journals off the unattended path entirely.",[284,709,711],{"id":710},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[190,713,714,715,691,718,721],{},"Nimbus ",[194,716,717],{"href":32},"workstreams",[194,719,720],{"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.",[190,723,724,727,728,731],{},[194,725,726],{"href":248},"What is a Nimbus Loop"," is the product noun for the standing order. Score skip logs and recipe version with ",[194,729,730],{"href":613},"how to evaluate loop engineering"," before you let a Monday compile look like a close.",[733,734,735],"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":737},[738,739,740,741,742,743,744],{"id":286,"depth":172,"text":287},{"id":347,"depth":172,"text":348},{"id":417,"depth":172,"text":418},{"id":473,"depth":172,"text":474},{"id":618,"depth":172,"text":619},{"id":650,"depth":172,"text":651},{"id":710,"depth":172,"text":711},"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":748,"title":749},"Common questions","Monday packs vs the sign-off room",[751,754,757,760],{"question":752,"answer":753},"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":755,"answer":756},"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":758,"answer":759},"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":761,"answer":762},"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.","/blog/loops-for-finance-and-planning",{"title":181,"description":746},"use-case","blog/loops-for-finance-and-planning",[765,768,769,770,771],"finance","FP&A","loops","planning","aZM01FaAac4-SKaA6xSdi1RT5SUa3dldoE6yjJM4uRA",{"hero":774,"id":776,"title":777,"archived":165,"authors":166,"badge":166,"body":778,"date":166,"definedTerm":166,"department":166,"description":782,"extension":174,"eyebrow":783,"faqHeader":166,"faqs":166,"footerBand":784,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":60,"relatedHeading":790,"seo":791,"series":166,"sitemap":131,"status":166,"stem":792,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":793},{"filename":775},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content/blog/index.md","Exploring the future of intelligence.",{"type":168,"value":779,"toc":780},[],{"title":171,"searchDepth":172,"depth":172,"links":781},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":785,"description":786,"primaryLabel":787,"primaryTo":788,"secondaryLabel":789,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":777,"description":782},"blog/index","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[795,166],{"id":796,"title":797,"archived":165,"authors":798,"badge":800,"body":801,"date":745,"definedTerm":166,"department":166,"description":1318,"extension":174,"eyebrow":166,"faqHeader":1319,"faqs":1321,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1333,"relatedHeading":166,"seo":1334,"series":765,"sitemap":131,"status":166,"stem":1335,"subhead":166,"tags":1336,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1340},"content/blog/loops-for-legal-and-compliance.md","Loops for Legal and Compliance",[799],{"name":184,"to":136},{"label":186},{"type":168,"value":802,"toc":1309},[803,816,829,831,856,859,863,867,886,900,912,915,919,929,932,947,966,968,982,993,995,1037,1040,1044,1047,1052,1057,1062,1066,1097,1102,1105,1110,1115,1121,1173,1178,1180,1183,1201,1204,1209,1229,1233,1243,1246,1264,1267,1286,1289,1291,1299,1307],[190,804,805,806,809,810,815],{},"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 ",[205,807,808],{},"guesses"," which version applies instead of escalating. The ",[194,811,814],{"href":812,"rel":813},"https://eur-lex.europa.eu/eli/reg/2024/1689/oj",[198],"EU Artificial Intelligence Act"," (Regulation (EU) 2024/1689, 2024) is not a clause playbook; it is a reminder that automated systems carry duties chat etiquette does not satisfy.",[190,817,203,818,820,821,824,825,217],{},[205,819,207],{},", 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 ",[205,822,823],{},"escalates",". It does not approve send. It does not paraphrase the clause into “legal OK.” For that room, read ",[194,826,828],{"href":827},"collaborative-ai-for-legal-and-compliance-review","collaborative AI for legal and compliance review",[190,830,220],{},[222,832,833,840,849],{},[225,834,835,837,838,217],{},[205,836,229],{}," — a completion sensor. Did the sent message match the signed payload hash? See ",[194,839,234],{"href":233},[225,841,842,844,845,245,847,250],{},[205,843,239],{}," — a compiled watch that admits a run when a trigger fires. See ",[194,846,244],{"href":243},[194,848,249],{"href":248},[225,850,851,853,854,217],{},[205,852,255],{}," — open-ended replan, such as “review this contract” with no quote, version, or rejector. See ",[194,855,260],{"href":259},[190,857,858],{},"A watch that logs what it saw is more useful than a bot that guesses comfort. Escalate. Do not guess.",[284,860,862],{"id":861},"what-a-legal-and-compliance-standing-order-loop-is","What a legal and compliance standing-order loop is",[190,864,290,865,295],{},[194,866,294],{"href":293},[297,868,869,875,880],{},[225,870,871,874],{},[205,872,873],{},"When the policy changes"," — playbook PDF updated, wiki revision, grid effective date crossed.",[225,876,877,879],{},[205,878,315],{}," — customer paper in the intake folder, vendor MSA upload, RFP attachment.",[225,881,882,885],{},[205,883,884],{},"When the clause source moves"," — standard terms URL changed, registry filing published, regulator update feed.",[190,887,888,889,892,893,896,897,899],{},"The job is narrow: detect the start, ",[205,890,891],{},"quote or hash"," what changed, compare to the version pinned on the job, and ",[205,894,895],{},"escalate"," — open a collaborative matter or notify the named lawyer roster. It does not approve send. ",[194,898,331],{"href":330},": the standing order does not bind the company.",[190,901,902,903,906,907,911],{},"Do not let the watch ",[205,904,905],{},"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. ",[194,908,910],{"href":909},"what-is-harness-engineering","What is harness engineering"," covers pinning versions on the job.",[190,913,914],{},"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.",[284,916,918],{"id":917},"why-legal-should-care","Why legal should care",[190,920,921,922,925,926,217],{},"Because fluency is not review, and ",[205,923,924],{},"watching"," is not ",[205,927,928],{},"signing",[190,930,931],{},"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.",[190,933,934,935,940,941,946],{},"In February 2024 Air Canada was held to chatbot-invented fare terms — ",[194,936,939],{"href":937,"rel":938},"https://www.cbc.ca/news/canada/british-columbia/air-canada-chatbot-lawsuit-1.7116416",[198],"CBC News",", decision ",[194,942,945],{"href":943,"rel":944},"https://decisions.civilresolutionbc.ca/crt/crtd/en/525448/1/document.do",[198],"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.",[190,948,949,950,955,956,959,960,965],{},"NIST’s ",[194,951,954],{"href":952,"rel":953},"https://www.nist.gov/itl/ai-risk-management-framework",[198],"AI Risk Management Framework"," (2023) maps govern-measure-manage for AI systems. A watch that logs triggers and skips is a ",[205,957,958],{},"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 ",[194,961,964],{"href":962,"rel":963},"https://www.reuters.com/legal/new-york-lawyers-sanctioned-using-fake-chatgpt-cases-legal-brief-2023-06-22/",[198],"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.",[190,967,388],{},[222,969,970,973,976,979],{},[225,971,972],{},"policy changes already arrive as email attachments and sales learns from a snippet",[225,974,975],{},"incoming MSAs sit in a folder until someone remembers",[225,977,978],{},"three playbook PDFs share a title and retrieval picks the obsolete one",[225,980,981],{},"customer-facing claims leave the building without a send gate",[190,983,984,987,988,992],{},[194,985,986],{"href":407},"What is write-back governance"," stays on customer messages, contract repositories, and CRM terms fields. ",[194,989,991],{"href":990},"what-is-ai-governance","What is AI governance"," is the wider map.",[284,994,418],{"id":417},[222,996,997,1003,1009,1015,1021,1027,1032],{},[225,998,999,1002],{},[205,1000,1001],{},"Quote."," The clause as written, extracted — not a paraphrase.",[225,1004,1005,1008],{},[205,1006,1007],{},"Pinned playbook version."," The version the watch diffs against. Not “the legal PDF.”",[225,1010,1011,1014],{},[205,1012,1013],{},"Diff."," What changed between pinned version and new source, as an artefact.",[225,1016,1017,1020],{},[205,1018,1019],{},"Escalate."," Open a collaborative matter or notify the named roster. Do not guess.",[225,1022,1023,1026],{},[205,1024,1025],{},"Skip."," Duplicate hash or empty diff, recorded with a reason.",[225,1028,1029,1031],{},[205,1030,455],{}," After send, did the message match the signed payload?",[225,1033,1034,1036],{},[205,1035,461],{}," “Handle contracts” with no saved escalation path.",[190,1038,1039],{},"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.",[284,1041,1043],{"id":1042},"how-to-compile-one-legal-standing-order","How to compile one legal standing order",[190,1045,1046],{},"Start from intake people already perform badly when busy.",[190,1048,480,1049],{},[205,1050,1051],{},"Incoming customer paper",[190,1053,1054,1056],{},[205,1055,488],{}," file lands in the legal-intake folder with extension pdf or docx.",[190,1058,1059,1061],{},[205,1060,498],{}," job pinned to current playbook version; roster includes the duty lawyer.",[190,1063,1064],{},[205,1065,504],{},[297,1067,1068,1073,1080,1087,1090],{},[225,1069,1070,1071,515],{},"Hash file; if duplicate of open matter, ",[205,1072,326],{},[225,1074,1075,1076,1079],{},"Extract ",[205,1077,1078],{},"quoted"," limitation-of-liability and data-processing sections — not summary-only.",[225,1081,1082,1083,1086],{},"Compare keywords against pinned playbook sections; flag deltas as ",[205,1084,1085],{},"questions",", not approvals.",[225,1088,1089],{},"Open a collaborative matter with quote, file, playbook version, and flag list.",[225,1091,1092,1093,1096],{},"Notify the named roster. ",[205,1094,1095],{},"Disable send"," on any draft until a lawyer joins the matter.",[190,1098,1099,1101],{},[205,1100,536],{}," no customer email; no CRM “legal approved” field; no auto-redline send.",[190,1103,1104],{},"When policy changes:",[190,1106,1107,1109],{},[205,1108,488],{}," playbook repository commit or effective date.",[190,1111,1112,1114],{},[205,1113,504],{}," diff old vs new pinned version; list clauses affected; open matters for templates that reference changed sections; skip if diff empty.",[190,1116,1117,1118,217],{},"Write-back — customer messages, contract repositories, CRM terms fields — stays on the collaborative path with ",[194,1119,1120],{"href":407},"write-back governance",[553,1122,1124],{"className":555,"code":1123,"language":557,"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",[559,1125,1126,1131,1136,1141,1146,1151,1156,1161,1167],{"__ignoreMap":171},[562,1127,1128],{"class":564,"line":565},[562,1129,1130],{},"flowchart TD\n",[562,1132,1133],{"class":564,"line":172},[562,1134,1135],{},"  watchTrigger[\"Policy changes or a file lands\"] --> seen{\"Already seen this file?\"}\n",[562,1137,1138],{"class":564,"line":576},[562,1139,1140],{},"  seen -->|yes| skipLegal[\"Skip, logged\"]\n",[562,1142,1143],{"class":564,"line":582},[562,1144,1145],{},"  seen -->|no| quoteExtract[\"Quote the key clauses\"]\n",[562,1147,1148],{"class":564,"line":588},[562,1149,1150],{},"  quoteExtract --> diffPlaybook[\"Compare to the pinned playbook\"]\n",[562,1152,1153],{"class":564,"line":594},[562,1154,1155],{},"  diffPlaybook --> escalate[\"Open a review matter\"]\n",[562,1157,1158],{"class":564,"line":600},[562,1159,1160],{},"  escalate --> notifyLawyer[\"Notify the named lawyer\"]\n",[562,1162,1164],{"class":564,"line":1163},8,[562,1165,1166],{},"  escalate --> reviewRoom[\"Collaborative review\"]\n",[562,1168,1170],{"class":564,"line":1169},9,[562,1171,1172],{},"  reviewRoom -->|signed| sendGate[\"Send or write\"]\n",[190,1174,1175,1177],{},[194,1176,614],{"href":613}," applies to watch loops too: can you replay why a matter opened, or why it skipped?",[284,1179,619],{"id":618},[190,1181,1182],{},"A good legal standing-order week:",[222,1184,1185,1192,1195,1198],{},[225,1186,1187,1188,1191],{},"Every new file either opened a matter with ",[205,1189,1190],{},"quotes"," or logged a skip with reason.",[225,1193,1194],{},"Policy-change runs produced a diff artefact, not a chat summary.",[225,1196,1197],{},"No customer send from the standing-order path.",[225,1199,1200],{},"A later reader can reconstruct intake without asking who “checked the bot.”",[190,1202,1203],{},"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.",[190,1205,1206,1208],{},[194,1207,643],{"href":642}," applies: outside counsel may see the matter, not every connector. Retention should match how long you must explain the language.",[190,1210,1211,1212,1215,1216,1219,1220,1224,1225,1228],{},"Website and support bots need the same escalation split: a watch may ",[205,1213,1214],{},"detect"," that public terms changed; the ",[205,1217,1218],{},"send"," of customer-facing language still routes to ",[194,1221,1223],{"href":1222},"collaborative-ai-for-customer-support","collaborative AI for customer support"," or the legal review room with a signer class. ",[194,1226,945],{"href":943,"rel":1227},[198]," is the reminder that the message can be the write.",[284,1230,1232],{"id":1231},"how-to-start-with-one-watch","How to start with one watch",[190,1234,654,1235,1238,1239,1242],{},[205,1236,1237],{},"file lands"," for one intake folder you already have — or ",[205,1240,1241],{},"policy change"," if version chaos is the pain.",[190,1244,1245],{},"Four weeks:",[297,1247,1248,1251,1258,1261],{},[225,1249,1250],{},"One folder or one playbook repo path.",[225,1252,1253,1254,1257],{},"Quote extraction plus diff against a ",[205,1255,1256],{},"pinned"," version — no approval language.",[225,1259,1260],{},"Automatic open of a collaborative matter with sources attached.",[225,1262,1263],{},"Zero sends from the standing order.",[190,1265,1266],{},"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.",[190,1268,1269,691,1273,1276,1277,1279,1280,1282,1283,1285],{},[194,1270,1272],{"href":1271},"loops-for-finance-and-planning","Loops for finance and planning",[194,1274,1275],{"href":689},"loops for revenue operations"," cover packs and pipeline triggers. If you are still choosing the discipline, start with ",[194,1278,244],{"href":243}," and score a vendor with ",[194,1281,730],{"href":613}," before you let a watch open matters on its own. ",[194,1284,331],{"href":330}," is the rule that keeps the watch from drafting a customer email at 3am.",[190,1287,1288],{},"Watch faithfully. Escalate honestly. Leave the signature to the room where a lawyer can refuse.",[284,1290,711],{"id":710},[190,1292,714,1293,1295,1296,1298],{},[194,1294,717],{"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. ",[194,1297,39],{"href":40}," is the send gate — not a prompt that says “ask legal.”",[190,1300,1301,1303,1304,1306],{},[194,1302,726],{"href":248}," is the product noun for the standing order. Score it with ",[194,1305,730],{"href":613}," before you let a watch look like review.",[733,1308,735],{},{"title":171,"searchDepth":172,"depth":172,"links":1310},[1311,1312,1313,1314,1315,1316,1317],{"id":861,"depth":172,"text":862},{"id":917,"depth":172,"text":918},{"id":417,"depth":172,"text":418},{"id":1042,"depth":172,"text":1043},{"id":618,"depth":172,"text":619},{"id":1231,"depth":172,"text":1232},{"id":710,"depth":172,"text":711},"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":748,"title":1320},"Watchers vs the review room",[1322,1325,1328,1330],{"question":1323,"answer":1324},"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":1326,"answer":1327},"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":758,"answer":1329},"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":1331,"answer":1332},"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.","/blog/loops-for-legal-and-compliance",{"title":797,"description":1318},"blog/loops-for-legal-and-compliance",[765,1337,1338,770,1339],"legal","compliance","policy","HuWs_EuMXxdW-9WB8YQhVQTlC0KN4Zl-NUriFdPYzCk",{"enabled":165,"message":1342,"linkLabel":79,"linkHref":80,"id":1343,"title":1344,"archived":165,"authors":166,"badge":166,"body":1345,"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":1349,"relatedHeading":166,"seo":1350,"series":166,"sitemap":165,"status":166,"stem":1351,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1352},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":168,"value":1346,"toc":1347},[],{"title":171,"searchDepth":172,"depth":172,"links":1348},[],"/shared/hiring",{"title":1344,"description":171},"shared/hiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"fold":1354,"id":1358,"title":1359,"archived":165,"authors":166,"badge":166,"body":1360,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":1364,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1368,"relatedHeading":166,"seo":1369,"series":166,"sitemap":165,"status":166,"stem":1370,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1371},{"headline":1355,"description":1356,"primaryLabel":8,"primaryTo":1357,"secondaryLabel":789,"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.","/signup?plan=free","content/shared/cta.md","Site CTAs",{"type":168,"value":1361,"toc":1362},[],{"title":171,"searchDepth":172,"depth":172,"links":1363},[],{"headline":1365,"description":1366,"primaryLabel":8,"primaryTo":1357,"secondaryLabel":1367,"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","/shared/cta",{"title":1359,"description":171},"shared/cta","PS2VPJsszmUpMBZT6nEp8cWXCdeiN6zDRl-p8d0uY2k",1789797894467]