Working Out What the Device Is Worth per Month

Most BYOD allowances are a round number somebody chose. Deriving one is straightforward, defensible, and produces a figure you can explain to a finance director and to the person receiving it.

The commercial question in “Working Out What the Device Is Worth per Month” needs a record that both sides can read. An organisation considering Monitask pricing and plans for monitask pricing can connect time and project evidence with the cost model, provided reimbursements, corrections and non-billable work remain visible.

The components

Start with what the organisation would otherwise spend. If you equip somebody, what does the device cost and over how many years do you replace it? A machine at a given price on a three-year cycle has a monthly equivalent that is simple division.

For an independent reference relevant to “Working Out What the Device Is Worth per Month”, consult the CISA mobile-device security guidance; compare its principles with the proposed ownership model, access rules and real support process.

Then the work share. A phone used for work and personal life is not entirely a work expense, and a laptop used mostly for work is mostly one. A stated percentage — half, two thirds, whatever reflects the role honestly — is cruder than reality and defensible, which is the standard any allowance has to meet.

Then the running costs attributable to work: the portion of a data plan, if the work consumes meaningful data, and a provision for repairs, which the breakage note treats separately.

Multiply the monthly device cost by the work share, add the running portion, and you have a figure with a derivation behind it.

Why derivation matters more than the amount

An allowance of a given size arrived at by calculation is explicable: here is the device cost, here is the share, here is the arithmetic. A person who thinks it is too low can argue with a component rather than with a feeling, which is a far better conversation.

A round number chosen by somebody in a meeting has no such defence, and when it is questioned the only available responses are to change it arbitrarily or to refuse arbitrarily.

It also protects the employer. Where a jurisdiction requires reasonable reimbursement of necessary expenses, a documented derivation is evidence that the figure was reasonable. A round number is not.

Varying it by role

Where device requirements differ substantially, one figure will be wrong for somebody. A role needing a capable laptop and a role needing only a phone are not the same expense.

Two or three bands, derived the same way, handle this without creating an administrative burden. More than three bands is usually a sign that the organisation should be buying the hardware for the demanding roles, which the alternatives section covers.

Reviewing it

Device prices move, replacement cycles shift, and an allowance set five years ago is describing a different market. An annual check against current prices takes minutes and keeps the derivation honest.

An allowance that has not changed in several years while hardware prices have is quietly becoming a smaller contribution, which the people receiving it notice before the people paying it do.

Explaining the figure to the recipient

An allowance arrives in a payslip with no explanation and is read as a small gesture. The same amount accompanied by its derivation — this is the device cost, this is the share, this is why — is read as a calculation somebody did carefully. The money is identical and the reception is not, which makes publishing the method the cheapest improvement available to an existing allowance.

When the derived figure is awkwardly large

Occasionally the arithmetic produces a number the organisation does not want to pay, particularly for roles needing capable hardware. That is information rather than an error. It usually means the role belongs in the equipped category, which the alternatives section covers, and discovering that through the costing is better than discovering it through somebody working on an inadequate machine for two years.

Publishing the method

The derivation can be published in four lines: device cost, replacement period, work share, running costs. Doing so pre-empts most challenges, makes the annual review mechanical, and means the next person to hold the arrangement inherits a method rather than a number nobody can explain.

Worked example: a laptop at a typical business price, replaced every three years, is a modest monthly equivalent. At a two-thirds work share, plus a small provision for a data plan, the derived allowance comes out well below what most people assume and well above what most organisations pay.