Every split dispute starts the same way: everyone in the room agreed. The percentages were said out loud, someone wrote them on a split sheet, a screenshot went into the group chat, and the session moved on.
Then the record does well, and the paper has to become money. That is where split sheets fail, quietly and months later.
The three quiet failures
The numbers drift. The split sheet says 25 for the producer. The email thread from two weeks later says 20. The version in the manager’s spreadsheet says something else again. Nobody lied. There were just three copies of the truth, and they stopped agreeing the moment one of them changed.
The total is not 100. Handwritten percentages have a habit of adding up to 95, or 105, once a late collaborator gets penciled in. Nothing catches it, because paper does not do arithmetic. The error surfaces at distribution time, which is the most expensive possible moment to discover it.
Someone re-keys everything. Whatever the paper says, a person eventually types those numbers into a royalty system by hand. Every re-keying is a fresh chance to transpose digits, skip a row, or work from the stale copy.
What a live split changes
In FlowRights, the split schedule is not an appendix to the contract. It is structured data: each party has a percentage and a revenue type, held as fields, not prose.
That single change removes each failure in turn:
- One copy of the truth. The splits live inside the same contract everyone negotiated and signed. When a percentage changes during negotiation, it changes in the split table, the schedule, and the clause text at once.
- The arithmetic is enforced. Percentages must total exactly 100 before the contract can go active. Not roughly 100. Exactly.
- Nobody re-keys. When the contract goes active, the split terms push to Royalti.io on their own. The push is recorded, failures are retryable, and a hiccup in the sync never blocks the contract itself.
Sealed with the signature
There is one more difference worth naming. When the contract is signed, the exact terms, splits included, are sealed with a tamper-evident SHA-256 fingerprint. If a single character of the agreement changes afterwards, the fingerprint no longer matches and the change is detectable.
A split sheet asks you to trust everyone’s memory. A live split asks the numbers to prove themselves, once, before anything depends on them.
See how the whole lifecycle fits together on the product tour, or start your first contract.