Proving What It Was Like Before
Somebody who was not there, and who has no reason to take your word for it, will ask what condition that machine was in beforehand. The register answers that question well. It has nothing at all to say about what the machine was insured for.
Most operational risk arrives without an appointment. You cannot schedule work for the week before a fire, because there is no week before a fire — there is only afterwards, and a set of records that either happen to be good enough or happen not to be. This is why asset condition is almost universally treated as maintenance housekeeping rather than as evidence: for most risks, evidence is something you discover you needed.
A storm season is different in a way that changes what is worth doing. It is annual, its dates are published, and everybody in the region knows them. The risk is not that something might happen; it is that a known category of event will arrive within a known window, possibly at every site you operate at once. There is a "before", it is on the calendar, and it can be staffed.
That single fact is what turns condition records from housekeeping into preparation, because it means the most valuable record you will ever hold is one you can only create while nothing is wrong.
The question you will actually be asked
After any significant event, the questions that matter are not the ones the operation asks itself. They come from outside — from an assessor, an insurer, a lender, an auditor, a donor — and they share a structure. Somebody who was not present, and who has no particular reason to accept your account, wants to establish what state a thing was in beforehand, and to distinguish damage caused by the event from wear that was already there.
Your own certainty is worth very little in that conversation. What carries weight is a record that existed before the event, at a time when nobody had an incentive, and can be shown to have existed then.
This is the thing the register does well, and it is worth knowing about before you need it rather than after. The boundary between what a register holds and what a depreciation schedule holds is set out separately in asset register versus depreciation ledger, and the routine maintenance side in asset maintenance records.
What a condition record actually is here
Condition is not just a field on the asset that gets overwritten. Movements record a condition before and a condition after, as a pair, on a timestamped event with a named person against it. Both halves are reportable, and the after-state is available as a grouping dimension, so "everything whose condition changed, when, and to what" is a report rather than an archaeology project.
Two of the twelve movement actions an asset can record are marked damaged and marked lost. They are first-class events rather than a status somebody edited, which means the moment of damage has a time, an author and a before-and-after — the three properties that make a record evidence rather than an assertion.
And because documents attach to the asset itself, photographs taken during a pre-season walk-round are retrievable against that specific machine years later, rather than living in a phone or a shared drive organised by date.
The gap, stated plainly
There is no insurance anywhere on an asset. No insured value, no policy number, no insurer, no excess, no claim, no replacement cost. The only adjacent field is a warranty expiry date, which answers a different question entirely.
The only money on an asset is what it cost when you bought it. That figure is genuinely useful — it is a report measure, so total and average cost by site, category or department are real exportable reports — but it should not be mistaken for exposure. Historic cost is precisely the number that is not what replacement costs, and the gap between them widens every year in exactly the direction that hurts.
So the honest description is a narrow one, and it is better than it sounds: this is a system that can demonstrate what you had, where it was, and what state it was in. It is not a system that knows what any of it was insured for. Those are different jobs, and knowing which one you are holding decides where the other one has to live.
The register will not tell you what you can claim. It will tell you, with a date and a name against it, exactly what you had and what condition it was in — and that is the half nobody can reconstruct afterwards.
A pre-season pass that is worth the afternoon
-
Verify, do not assume
Verification is a first-class movement action and the count of assets verified in the last thirty days is already computed. A pre-season verification pass across a site produces a dated, attributed statement that each machine existed and was where the register said it was — which is the claim most easily disputed later and the easiest to establish now.
-
Record condition honestly, including the bad ones
The temptation is to record everything as good. Resist it, because an honest pre-event condition record is what allows event damage to be separated from pre-existing wear. A machine recorded as already worn and then destroyed is a cleaner story than one recorded as pristine and visibly not.
-
Attach photographs to the asset, not to a folder
Documents attach to the asset record itself, so a photograph taken this season is retrievable against that machine in several years without anybody remembering which trip it was from. A dated folder on a drive is the same photograph with the association removed.
-
Use risk level to mark what genuinely cannot be replaced quickly
Every asset carries a risk level and it defaults to standard. Raising it on the items whose loss would actually stop the operation — rather than on the expensive ones — turns it into a prioritisation tool for both the pre-season pass and the post-event sequence.
-
Keep insured values wherever your policy lives, and tie them by asset code
Since the register holds no insured value, the schedule stays with your broker or in your own document. The thing that makes it usable is the join: reference assets by the asset code the register issues, so a schedule and a damage report can be laid side by side without anybody matching descriptions by eye.
And afterwards
The sequence after an event is the mirror of the one before it, and it benefits from being decided in advance rather than in the week when everybody is exhausted.
What the record can and cannot produce
The first four are the half that cannot be reconstructed after the fact, and they are the half the register holds. The last two can be established afterwards from documents that exist elsewhere — which is the right way round, if you have to choose.
What AWRA OpsHub does today
- Condition recorded before and after on every movement, as a timestamped, attributed pair — not a field that gets overwritten.
- Marked damaged and marked lost as first-class movement actions, so damage is an event with an author and a time rather than a status edit.
- Verification as its own action, with a count of assets verified in the last thirty days already computed.
- Documents and photographs attached to the asset record itself, retrievable against that specific machine years later.
- A risk level on every asset, available as a report column for prioritising both preparation and recovery.
- Condition-after as a report dimension, so "what changed condition, when, and to what" is a report rather than a reconstruction.
- Purchase cost totals and averages by site, category or department — a real exportable exposure figure at historic cost.
- A lost-or-damaged count surfaced without building anything.
What it does not do
- No insurance data of any kind. No insured value, policy number, insurer, excess or renewal date on an asset.
- No claims. There is no claim record, no claim status and nothing to attach a settlement to.
- No replacement or current market value. The only money on an asset is what it cost when purchased, in the currency it was bought in.
- No revaluation or impairment. Nothing writes an asset down after damage, and no charge posts anywhere.
- No pre-season checklist or campaign concept. A verification pass is a set of ordinary verification movements; nothing groups them into an exercise with a completion figure.
- No site-level risk or exposure scoring. Risk level is per asset and is not rolled up.
What is not built for Jamaica today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in Jamaica. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a tax rate that follows the class of supply, dated rate changes, a Jamaican payroll engine, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
A rate that knows what you are selling
The General Consumption Tax has a standard rate, a higher rate on telephone services and handsets, and a reduced effective rate in tourism. Our per-organization rate table can express a country, a region and a city — three columns of geography — and nothing about the class of supply, so a business outside the standard rate carries one correct default and sets the rest by hand on each line. The build is a dimension this data model does not have, and it is worth knowing it is not a Jamaican special case: the same missing column is what sub-national rates would need elsewhere, so it gets built once. Alongside it, rates that start on a date, for the tourism change announced for April 2027 and every one after it.
Banks, payments and counters that share a ledger
Statement feeds and local payment rails into the Payments Register, with retail counters, contract sales and invoicing posting to one set of books rather than three that get reconciled monthly.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
A Jamaican payroll engine with income tax tables, NIS and NHT computed on live employee records, producing the schedules in the layout the authority expects.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedThe practical summary is short and it is a scheduling point rather than a software one. The records that decide how the difficult conversation goes are the ones created while nothing is wrong, and this is one of the few risks in the world that tells you well in advance when to create them. The register is good at holding that evidence. It will not hold the insurance side, and it is better to know that in the quiet part of the year than to discover it in the loud one.
Frequently asked questions
Does the asset register hold insured values or policy details?
No. There is no insured value, policy number, insurer, excess or claim anywhere on an asset — the only adjacent field is a warranty expiry date. The only money held is the original purchase cost in the currency it was bought in. Insurance schedules need to live with your broker or in your own documents, referenced by the asset code so the two can be laid side by side.
How is damage recorded, and is it different from just editing the condition?
Yes, and the difference is the point. Marked damaged is one of the twelve movement actions, so it produces a timestamped event with a named person and a condition-before and condition-after pair. An edited field tells you the current state; a movement tells you what it was, what it became, when, and who said so.
Can we report on everything that changed condition after an event?
Yes. Condition-after is a reporting dimension on asset movements, and condition-before is a column, so damage events can be listed and grouped with both states and the date of each. That is one of the few things far easier to produce from the system than to reconstruct by hand.
Is there a pre-season checklist or campaign feature?
No. A pre-season pass is a set of ordinary verification movements, and nothing groups them into a named exercise with a completion percentage. What does exist is a count of assets verified in the last thirty days, which is a serviceable progress measure for a pass run inside that window.
Can we use purchase cost totals as our exposure figure?
Only with care. Total and average purchase cost by site or category are real report measures, so the figure is easy to produce — but it is historic cost, which is not replacement cost, and the gap between them grows every year in the direction that hurts. Treat it as a floor and a way to rank sites, not as a statement of what you would need to rebuild.
