How to build a device refresh policy your CFO will approve
Last quarter an IT head at a Mumbai pharma company sent me his refresh request, again. Forty laptops, mostly i5 8th-gen units bought in 2020, all past 5 years, three already replaced twice on motherboard failure. His CFO had rejected the request twice. “We will manage another year, boss.” The third submission landed in the CFO inbox on a Tuesday morning. By 11:14 the same morning it was approved. The fix was not a better business case. The fix was a written device refresh policy. One page. Bands by role, refresh cadence, residual buy-back assumption, depreciation alignment. The CFO had stopped reading capex requests as discrete events and started reading them as the policy executing on schedule. That switch is the difference between begging quarterly and operating predictably. Below is how to build the same policy for your fleet. The companion call — the DaaS vs buying laptops India for MSMEs 7-question CFO framework — is the working-capital lens to apply alongside this policy work.
On this page
- What this policy actually is (and is not)
- The 6 inputs your CFO wants on the page
- Refresh cadence by role: the table the CFO reads first
- The depreciation alignment maths under Section 32
- The exception rule (and why it is the most important line)
- The one-page device refresh policy template
- Frequently asked questions
This post hands you the structure of a defensible device refresh policy, the 6 inputs the CFO will scan first, a refresh-cadence table by role, the depreciation alignment maths, the exception rule, and a one-page template you can paste into the next FY board memo. How to get a device refresh policy approved by your CFO inside 12 minutes of reading time, even if your last two refresh requests were rejected as “manage another year”. That is the contract.
What a device refresh policy actually is (and is not)
A device refresh policy is a one-page written rule that maps every employee role to a refresh cadence, a budget band, a residual assumption, and an exception trigger. Approved once at the FY capex review, then executed quarterly by IT and finance without further negotiation. It replaces the per-request capex memo with a per-fleet operating rhythm.
Three things it is not. It is not an asset register, that is a separate document the policy points at. It is not a procurement standard, that lives in the OEM master agreement with Dell or Lenovo or HP. It is not a depreciation schedule, that is what Section 32 of the Income Tax Act gives you. The device refresh policy sits on top of all three, decides who gets a new laptop in which quarter, and tells finance how much to budget. Without it, every refresh request becomes a one-off negotiation. With it, the negotiation happened once, in the policy meeting, and now everyone is just executing.
The Indian mid-market reality is that most 100 to 500 person companies still run laptops on the “till it dies” cycle, which means the average laptop age in the fleet sits at approx 5.4 years (we audit fleets where the mode is 6 years). Past 4 years the consequential costs (downtime, warranty lapse, security, productivity loss) overtake the capex savings. We covered the maths on this in the real cost of running laptops past refresh date. The device refresh policy is the artefact that prevents that drift from re-occuring once you have done the one-time clean-up.
The 6 inputs your CFO wants inside a device refresh policy
Across approx 22 CFO conversations in the last year on refresh policy approvals, six inputs come up on every first read. Put them on the page. Skip any one and the policy goes back for “more information”.
Input 1: Fleet headcount by role band. Total laptops in scope, split by 3 to 5 bands (executive, knowledge worker, sales/field, frontline operations, callcentre or kiosk). The CFO does not care that you have 240 laptops, the CFO cares about the band distribution so per-band budget rolls up correctly. It bands the fleet so you can budget per-band which means the CFO sees one number per band rather than a flat fleet average that hides the cost of the 12 expensive units at the top.
Input 2: Refresh cadence per band. A clear “every N years” cadence per role, with a single sentence justifying each band. Executives every 3 years (image and external meetings), knowledge workers every 4 years, sales and field every 3 years (drop and travel wear), frontline operations every 5 years (lower utilisation). One-line justifications, no essay.
Input 3: Budget band per device per band. A rupee range, not a point figure. Knowledge worker laptop Rs.72,000 to 95,000 with 3-year onsite warranty. Executive laptop Rs.1.05 to 1.45 lakh with ProSupport. Sales and field Rs.65,000 to 85,000 with accidental damage cover. Ranges so finance has flexibility, not so wide the policy becomes meaningless. Use retail-anchored numbers verified on Amazon.in, Flipkart, or the OEM India store on the day of writing.
Input 4: Residual buy-back assumption. What you assume the laptop is worth at the end of its cadence, as a percentage of original price. Most Indian buy-back channels return 8 to 12 percent at month 36 to 48 for business laptops in working condition with imaging and asset tags intact. Bake that number into the policy so the CFO sees the net per-device cost, not the gross.
Input 5: Depreciation alignment. Whether you are aligning the refresh cadence with the Section 32 IT-equipment depreciation rate (40 percent WDV) so the books and the policy stop disagreeing. If you refresh at 4 years and depreciation hits zero economic value at year 4 or 5 on WDV, the alignment is clean. If you refresh at 6 years and depreciation is fully written off at year 3, the asset has been carried at zero on books for 3 years while still spending on warranty extensions and repair. That gap is what the CFO flagged on the rejected memo.
Input 6: Exception rule. One sentence covering when the policy is overridden, by whom, and how. Most exceptions are role changes (knowledge worker promoted to executive, sales rep moved to engineering) or hardware failure inside warranty. The exception rule tells the CFO that the policy is firm but not brittle, which is the single biggest objection to written policies in our experience.
Refresh cadence by role: the table the CFO reads first
Most CFOs read the cadence table first, before reading any prose. Make it stand alone. Sample structure for a 280-person company; tune the numbers and bands for your specific fleet but keep the columns identical.
| Role band | Headcount | Refresh cadence | Budget per unit (retail-anchored) | Residual at month 36 to 48 | Net annual run cost per unit |
|---|---|---|---|---|---|
| Executive (CXO, VP) | 14 | 3 years | Rs.1.05 to 1.45 lakh | 10 to 12 percent | approx Rs.32,000 |
| Knowledge worker (engg, finance, ops) | 168 | 4 years | Rs.72,000 to 95,000 | 8 to 10 percent | approx Rs.20,000 |
| Sales and field | 46 | 3 years | Rs.65,000 to 85,000 | 6 to 8 percent (drop wear) | approx Rs.23,000 |
| Frontline operations (warehouse, callcentre) | 52 | 5 years | Rs.42,000 to 55,000 | 5 to 7 percent | approx Rs.10,000 |
Net annual run cost is the line the CFO underlines. It is gross unit price minus residual, divided by the cadence in years, plus annual AMC and warranty extension where relevant. The fleet-weighted average for the sample above lands at approx Rs.18,200 per unit per year. Multiply by headcount, that is your annual device line item. The CFO is no longer evaluating 40 laptops, the CFO is reading “fleet of 280 at Rs.18,200 per unit per year, Rs.51 lakh annually, residual recovery approx Rs.4.2 lakh, net Rs.47 lakh against approx Rs.62 lakh on the current ad-hoc spend”. That delta is what gets the policy signed.
The depreciation alignment maths under Section 32
The Income Tax Act Section 32 prescribes a 40 percent written-down value (WDV) depreciation rate for computers and computer software. On a Rs.80,000 knowledge-worker laptop:
- End of year 1: WDV Rs.48,000 (book value after Rs.32,000 depreciation)
- End of year 2: WDV Rs.28,800
- End of year 3: WDV Rs.17,280
- End of year 4: WDV Rs.10,368
- End of year 5: WDV Rs.6,221
By the end of year 4 the book value is approx 13 percent of original. By the end of year 5 it is approx 8 percent. A 4-year refresh cadence puts disposal and buy-back at the point where book value and market residual line up, so the company books a small loss or no loss on the disposal entry. A 6-year cadence puts disposal at book value of approx 5 percent against a market residual that has often fallen to under 5 percent too, which is fine on paper but the company has spent 2 extra years on warranty, repair, productivity drag, and security risk for a depreciation benefit that ended at year 4 or 5. Bring this calculation onto the policy. Cite Section 32 as the basis. CFOs (and the chartered accountants they show the policy to) read this paragraph and stop pushing back on cadence. See the Income Tax Act depreciation schedule for IT assets for the official source.
If your business is on the new tax regime under Section 115BAA or 115BAB, the headline rates still match the 40 percent IT WDV though the additional depreciation under 32(1)(iia) is unavailable. Check with your CA before quoting in the policy. Either way, the directional argument that refresh cadence should line up with book life holds.
The exception rule (and why it is the most important line)
Every CFO objection to a written device refresh policy reduces to one fear: “what if circumstances change and we are locked in”. The exception rule is the one sentence that closes that door. Standard wording, tune to your governance:
> “The IT head may, with written CFO approval and within the fleet-level annual capex budget, advance any unit’s refresh by up to 12 months for role change, role escalation, documented hardware failure outside warranty, or board-mandated security upgrade. All exception approvals are reported in the quarterly capex review.”
That paragraph does three jobs. It tells the CFO the policy is firm. It gives the CFO veto on any individual exception. It tells the IT head not to come asking for exceptions one device at a time. Most importantly, it forces exceptions to be batched and reported, which means at the next review you have data on how often the policy held vs needed bending. After the first year, most policies need fewer exceptions than the CFO feared (typical run rate in our client base is 4 to 8 percent of fleet per year).
The one-page device refresh policy template
A device refresh policy fits on one A4 page. Anything longer and the CFO will not finish it on first read. The structure that has cleared CFO approval on the first pass in approx 12 of our last 14 implementations:
1. Title and effective date 2. Scope: which entities, which roles, which fleet (one line each) 3. Role bands and refresh cadence: the table from earlier 4. Budget per band per unit: rupee range, retail-anchored 5. Residual assumption: percentage and channel (buy-back partner, internal sale, recycler with R2 certification) 6. Depreciation alignment paragraph: cite Section 32, name the cadence-to-WDV match 7. Exception rule: one paragraph (see above) 8. Review cadence: annual, at FY capex review, signed by IT head and CFO 9. Adjacent documents: link to asset register, OEM master agreement, device-as-a-service alternative if applicable
Some Indian SBU heads we work with also add a sustainability line (“retired devices routed to R2-certified recyclers; resale value reported quarterly”) because the auditor or the ESG counsel asks for it. It is one line, it costs nothing, it pre-empts a Q4 question. Worth adding.
By the way, did you know that approx 60 percent of the IT heads we run refresh reviews for already have a device refresh policy drafted somewhere on their laptop, they just never converted it into a 1-page A4 the CFO can sign? The conversion from internal note to policy artefact is the bottleneck, not the thinking. If you want a fast pass at converting yours, the Device Lifecycle Management practice can run a free 30-minute scoping call and turn the existing draft into the template above before the next FY capex meeting. No 90-minute discovery first.
Arjun’s take
Most companies treat the device refresh decision like a procurement event. Every cycle becomes a fresh negotiation, a fresh business case, a fresh CFO objection, a fresh “manage another year” rejection that costs the IT head three more weeks of unbillable defence. Theek hai, the procurement frame is wrong. The decision is an operating rhythm, like rent or insurance, and the artefact that converts it is a 1-page policy.
I have sat in approx 22 CFO conversations on refresh policy approvals in the last year. The policies that cleared on first read were not the longest or the most-defended. They were the ones the CFO could read in 12 minutes and sign without calling the CA.
The part nobody says out loud, boss, is that the IT head and the CFO usually want the same outcome. Predictable fleet cost, low surprise, no FY-end scramble, no board memo about “exceptional capex this quarter again”. The friction is not on the substance. It is on the artefact. A 7-slide deck triggers questions. A 1-page policy ends the conversation. We recieved the same feedback from approx 9 of 11 finance leads on a Priya-led DPDP scoping call last quarter when the topic drifted into device hygiene. Build the artefact at the right scale for the audience and the conversation closes itself.
And the contrarian opinion that costs me sales: if your fleet is smaller than approx 80 active laptops, you probably do not need a written device refresh policy yet. A shared Google sheet with role bands and cadence is enough. The policy becomes a force-multiplier at approx 80 to 100 units and a non-negotiable above approx 200. Build for where the fleet will be in 18 months, not for what is in Cowork on the marketing playbook page.
Frequently asked questions
Q1. What refresh cadence should I use in a policy for a 200-person Indian company? For a typical 200-person knowledge-worker fleet, 4 years for the bulk, 3 years for executives and sales and field, 5 years for frontline operations. The blended average lands around 3.9 to 4.1 years across the fleet, which is also where Section 32 WDV depreciation hits the 10 to 13 percent residual zone. Tune by role mix, do not flat-line at 4 years across the fleet.
Q2. How much will the policy actually cost vs the current ad-hoc spend? In approx 14 implementations we ran in the last year, the policy-led annual device spend landed approx 18 to 27 percent below the previous ad-hoc spend, mainly from bulk OEM pricing (the OEM gives sharper PO discounts when the quantity and timing are predictable), recovered residual value (which most ad-hoc shops never capture), and reduced AMC spend on out-of-warranty devices that the policy now retires on schedule. Some companies saw approx 4 to 6 percent of the savings get reinvested into faster cadence for high-impact roles. Net-net, the policy pays for itself inside year 1.
Q3. Can the CFO approve this policy without involving the board? For most 100 to 500 person Indian companies, yes. The policy is an operating-budget governance document, not a strategic capex decision. The CFO signs it at the FY capex review and the board sees the annual rolled-up device line item. For larger groups, listed entities, or any company where the device spend crosses approx Rs.1.5 crore per year, board-level visibility is wise but board approval is rarely required.
Q4. What if my company already runs a Device-as-a-Service contract? Do I still need a refresh policy? Yes, but it is shorter. Under a DaaS contract the residual, depreciation, warranty, and disposal questions are bundled into the monthly per-device cost, so the policy drops those sections. What stays is the role band table, the refresh cadence (now driven by the contract refresh schedule), the budget band per unit per band, and the exception rule. A DaaS-led version of this is typically half a page, not a full page. See how to pitch DaaS to your CFO for the companion conversation.
Q5. Where does this policy sit in the larger DLM stack? It sits at the strategy layer, above the asset register (operational), the OEM master agreement (commercial), and the AMC schedule (service). The policy is the document the CFO signs and the audit committee reads. The other three are documents the IT head executes. If you do not have an asset register yet, build that first, then the policy will write itself because you already have headcount-by-role and age distribution data.
Get your device refresh policy drafted by Sirius Star, free, 30 minutes
Book a free 30-minute device refresh policy scoping call. One call. We map your role-band distribution, run the residual and depreciation maths against your fleet age curve, and walk away with a CFO-ready 1-page draft policy. You get: the fleet snapshot in a single PDF, the 1-page policy draft, a residual buy-back estimate from our active channel partners, and the depreciation alignment paragraph pre-written with your numbers. No 90-minute discovery, no Big-4 retainer, no devicehunt by your IT team. If our scoping call does not surface at least Rs.2 lakh of recoverable annual cost on the residual line alone, the next quarterly fleet check is on the house. WhatsApp +91 91375 93228 with the keyword POLICY for a faster slot, or use the contact form linked above.
P.S. The 1-page device refresh policy template we use on every scoping call is a PDF with the role-band table, the cadence rationale, the depreciation alignment paragraph, the exception rule, and a board-memo paragraph already drafted, ready for your fleet numbers. Reply POLICY on WhatsApp +91 91375 93228 and we will send it. It includes the 4-band cadence table, the Section 32 alignment paragraph, and the exception rule wording. Free, no email gate on the PDF itself.
About the author
Arjun Mehta is the Device Operations Lead at Sirius Star and runs the Device Lifecycle Management practice. He has scoped fleet refresh policies at approx 22 Indian mid-size companies in the last year across pharma, NBFC, logistics, and B2B SaaS. He works with IT heads and CFOs who want a predictable per-device operating cost rather than an annual capex argument. Reach him via the device refresh policy scoping call or WhatsApp +91 91375 93228 with the keyword POLICY.
