What changes when eight people edit the same business records at once
Concurrency strategy should follow the consequence of a lost write. Notes tolerate last-write-wins. Money, stock, and allocations do not.
Read guideBusiness Operations
Guides on business operations software, connected records, and replacing separate CRM, project, and billing tools with one record.
Connect the guide to the workflow
35 articles
Latest in Business Operations
What an operating record is — and what it is not
An operating record is not a dashboard, a module list, or a data warehouse. It is one customer identity carried across every step that references it — and the thing you can test in five minutes.
Read guideOne customer, two records: the identity problem nobody can see
Every individual record is correct and every report runs cleanly. The error only exists in the joins — outstanding split across two rows, a credit check reading a nil balance, and two calls to one customer before lunch.
Read guideWhose hour is it? Shifts and the business day
Midnight is a default that requires no decision, which is exactly why it is wrong for a business with shifts. A business day is a recorded cut-off with a named owner — and everything downstream depends on it.
Read guideWhy CRM and Billing Disagree About One Customer
A deal closed in the CRM that the billing system has never heard of is not a data-entry failure. It is an unanswered question about which record owns the customer — and a merge tool cannot decide it for you.
Read guideThe Filter That Silently Excludes Money
The report is not wrong. It is answering a different question from the one its reader assumes — and the exclusion that makes a month look worse and the one that makes it look better usually live in the same filter.
Read guideWhat a Number Needs Before Two People Compare It
Two people comparing numbers is not a disagreement about the business until the definitions are identical. Before that it is two people answering two different questions, and no tool can tell you which one you meant.
Read guideA Report That Changes When You Look Twice
A figure that was true at nine and superseded at five is not a defect. A figure that was true at nine and gives no indication that it was true only at nine is unusable — and most business meetings are arguments from a number.
Read guideThe Scope Nobody Wrote Down: When a Job Was Agreed in a Corridor
A job agreed in a corridor and never written down leaves two sincere people with two scopes and one dated document. Here is the record shape that settles it, with the arithmetic shown.
Read guideThe Approval Nobody Knew They Needed
An uninformed exception is not misconduct. It is a rule that was written and never delivered — plus one approver who is currently on a plane.
Read guideThe Permission Nobody Asked For
The cost of a broad permission is not the access. It is the question you can no longer answer: who could have done this?
Read guideThe Process Nobody Wrote Down: The First Holiday Is the Audit
A process document written by the expert is their opinion. The one somebody else has followed without them in the room is evidence.
Read guideWho Can See the Customer Record? The Shared Login Problem
One account at the counter means every record carries the same name. What a separate identity actually buys you, what it does not, and the audit question worth being able to answer.
Read guideThe Audit Trail You Cannot Produce
The records exist and the trail does not. What separates a recorded action from a reconstructable one, and why a value that changed silently is more dangerous than a value that was never captured.
Read guideWhat Happens When the Person Who Set It Up Leaves
Configuration is knowledge, and knowledge is perishable. A constructed inventory of which decisions were written down, which were tacit, and what a handover has to capture while the person is still there.
Read guideBackups Are Not the Same as an Export
A backup is continuity; an export is ownership. What the published capability inventories actually document, where they are silent, and why a report export is not an archive.
Read guideMoving From a Spreadsheet Without Losing the History
A merged cell, a row added in April, a column that means two things, a total typed by hand. Which parts of a spreadsheet are worth moving and which were never data.
Read guideThe Double-Entry Period: Surviving Six Weeks With Two Systems Live
Every transaction entered twice, the two copies disagree, and somebody has to decide which is real. What a written cutover rule has to say about the week the old system stops.
Read guideThe Data You Should Refuse to Migrate
The argument for leaving data behind, and why a migration that imports everything brings the old system's ambiguities across with it — including 48,220 of receivables that quietly lost its customer.
Read guideWhat to Do in the First Week With a New System
The first week is when people decide whether the new system is the enemy. Most week-one failures are configuration decisions that were deferred, arriving on the busiest morning of the month.
Read guideTwo Branches, Two Sets of Numbers: Why a Consolidated Total Can Be Wrong
A consolidated number is easy to produce and hard to defend. Before two branches are added, six things have to be the same at both, or the total is a sum of two different measurements wearing one label.
Read guideThe Transfer Between Branches That Never Arrived
When one site records an outward movement and the other never records a receipt, the network total is wrong by a quantity nobody has counted. The fix is a shape, not a reminder.
Read guideThe Branch That Closes Its Books Differently
A policy written for the business is a policy, not an outcome. When two sites run on different permissions and different local rules, comparing their revenue is comparing two operating decisions and calling one of them a performance result.
Read guideWhen Two Locations Are Really Two Businesses
A second location belongs in the same system when a record crosses between the two. If nothing crosses, consolidation adds a login and removes nothing, and in some cases it merges two customers who do not owe each other money.
Read guideThe Process Everyone Bypasses
A process nobody follows is not a weak process. It is a claim the records do not support, and the gap is between the process and the evidence rather than between the process and the people.
Read guideThe One Person Who Knows Where Everything Is
The map holds connections the records hold separately. The risk is not the person's leaving; it is the first routine question that arrives while they are busy.
Read guideThe Report Nobody Opened and the Record Nobody Chased
Both failures are a correct figure nobody has to act on. A report that leads with one thing that changed, and a record with a name and a date attached, is worth opening.
Read guideThe Two Sources of Truth
A spreadsheet built for presentation becomes a record the day somebody takes a decision using it. Before that it is a report requirement; after it, it is a dependency.
Read guideThe Sale That Happened Before the Record Did
A deferred record is not a late record. It is a different record, built from weaker evidence, and at a counter the errors do not cancel. A constructed sale, its arithmetic, and the 200.60 spread between the highest and lowest reconstruction.
Read guideThe Customer Who Wants Their Own Copy of Something Else
The printed bill is frozen, has no address, and cannot be corrected. The record is the only one of the four that can be, and that distinction is what tells you which document a business can reissue next month. A constructed sale with four artefacts and the arithmetic shown.
Read guideThe Discount Everybody Applies and Nobody Approves
A recorded discount with no approver reconciles perfectly, so nothing ever surfaces it. The five things that have to be true before a discount is a decision, with a constructed month of arithmetic and NoxOrigin's discount approval engine stated plainly as absent.
Read guideThe Day That Ends Early Because Something Was Wrong
A counted drawer is the only measurement in a cash business that did not come from your own system. Absorb the difference and the record becomes self-referential. A constructed close with all arithmetic shown, and shift close stated as assisted setup rather than a one-button switch.
Read guideThe Commitment Nobody Recorded
A belief is not a record. It cannot be counted, scheduled, handed over, checked at the end of a quarter, or defended to a client who asks what they were promised.
Read guideThe Deployment Nobody Billed
The work is on the project record and it is not on any invoice. A deployment entry answers whether the work happened; it does not answer what it was worth, and 321,270.00 of a constructed quarter can sit outside every report.
Read guideThe Trip That Was Never Invoiced
A visit that happened away from the business is still work, and money owed for it is still a debt. One constructed service day, worked in full, including the visit nobody could charge for and the cash that had nothing to sit against.
Read guide