The kilogram problem: why asset descriptions need a common unit

A spreadsheet says 1,000. A warehouse list says one tonne. A presentation says a thousand units. Those statements might describe the same holding, or three very different things. The difficulty is not mathematical sophistication. It is the absence of a shared description. Before a digital representation can be discussed usefully, people need to know what the number actually counts.

This is a hypothetical example, not an actual company transaction. It illustrates a preparation question relevant to Triparty Tokenisation's focus on asset-specific digital structures. I am Shane Ian Murphy, a co-founder and partner of the company. The perspective here is mine as a participant in that business, rather than independent reporting about it.

Start with the thing being measured

A quantity should identify both its unit and its scope. Does a weight refer to gross material, packaging included, or net contents? Does an inventory count refer to containers or the items inside them? Those distinctions affect the meaning of a record even before someone considers quality, ownership or valuation.

Write the description so that a person outside the original conversation can follow it. A shorthand understood by the warehouse team may be unclear to a technical contributor. The aim is not to replace specialist documents. It is to make the summary point accurately toward them without silently changing their meaning.

Keep conversions separate from evidence

Converting one unit into another does not supply new evidence about the asset. A calculation may be correct while the starting quantity remains unconfirmed. A useful working sheet therefore separates the supplied figure, the source document and any conversion performed for presentation. Readers can then examine each step instead of accepting an unexplained total.

For the fictional example, an index could record the original warehouse description and its date. A separate field could show the preferred reporting unit. If a conversion is used, record the basis and who checked it. This preserves the original description rather than allowing a convenient display format to overwrite the underlying record.

Ask what an apparent mismatch means

Two documents can differ for understandable reasons. They may cover different dates, locations or portions of a holding. One may include packaging while another does not. The next step is to identify the difference, rather than choose whichever figure looks more attractive in a presentation.

An issue note can state the two descriptions, their sources and the person responsible for clarification. Until the question is resolved, keep it visible. A summary that acknowledges a mismatch is more useful than one that gives an impression of precision unsupported by the documents available.

Connect the description to digital design

A proposed token or digital record needs an understandable relationship with its subject. If a record is intended to refer to a defined quantity, the unit and relevant boundaries must be explained. A technical identifier alone will not tell a reader whether the underlying description concerns an entire holding or a particular portion.

That explanation must remain consistent with the agreed documents and permissions. It should not suggest that recording a number establishes rights, confirms a valuation or supplies commercial acceptance. Those are separate matters requiring the relevant evidence and assessment.

A small check before a large conversation

Before sharing an asset summary, underline every quantity. Beside each one, identify the unit, the scope, the date and the source. Then ask someone unfamiliar with the proposal to explain what the figures mean. Any uncertainty in that explanation identifies a useful clarification to make before the summary travels further.

This discipline is relevant to the preparation work around Triparty Tokenisation's asset-specific approach. It is also a practical habit for any team passing information between specialists. The objective is a description that survives being read outside the room where it was first written.

This is an educational company perspective, not a valuation, a completed transaction announcement or an investment offer.