Bring your own device: stipends, enrollment, and records risk

Reference article · 5 min read

Most agencies already have a bring your own device program. They just have not written it down. Staff answer email on personal phones, text contractors from personal numbers, and photograph field conditions with cameras the agency does not own. The question is not whether personal devices touch agency business, but whether the agency can find, preserve, and produce the resulting records.

Cost usually drives the conversation, and cost is the least interesting part of it. A phone line is a small recurring expense next to a records request the agency cannot answer, a preservation fight in litigation, or a wage claim built on off-hours work nobody tracked. Decide the records and labor questions first, then pick the funding model that fits.

The three real options

• Agency-issued device. The agency owns the hardware and the number. Full management is defensible because nothing personal is on it. Highest recurring cost, and the only option that reliably keeps agency records in agency custody. Best for roles whose messages end up in case files.
• Stipend or reimbursement with enrollment. The employee owns the phone, the agency pays a set amount or reimburses documented business use, and manages a separated work area on the device. Lower hardware cost, more policy work, and it depends on employees agreeing to enroll.
• Unmanaged personal device. No stipend, no enrollment, agency email reached through a browser or a native mail app. Cheapest on paper, and it leaves agency records somewhere the agency cannot search, preserve, or remove.

One answer for the whole agency is rarely right. Classify by role, based on how likely that role's communications are to be requested or subpoenaed.

Stipends, payroll, and wage-and-hour exposure

• Reimbursement duties vary by state. Some states require employers to reimburse necessary business expenses, and California courts have applied that to a share of personal cell phone costs. Confirm with counsel whether your state imposes a similar duty and what amount is reasonable.
• Tax treatment depends on structure. A flat allowance untied to actual business use is more likely to be treated as taxable wages than an arrangement reasonably calculated to cover documented expense. Settle that with payroll and counsel before announcing it.
• Access creates hours. A managed phone makes after-hours work easy, and work performed off the clock is generally compensable whether or not it was authorized. Set written expectations for after-hours response, and give nonexempt staff a way to report that time.
• Represented employees. Changing a stipend, or requiring enrollment as a condition of the job, is often a mandatory subject of bargaining. Raise it with labor relations before it reaches a policy draft.

What management should and should not touch

Current mobile platforms separate work data from personal data. Use that separation, and put the line in writing.

Reasonable on a personal device:

• Requiring a passcode and encryption that protect the work area
• Requiring a supported operating system version
• Blocking agency data from copying into personal apps or personal cloud backups
• Removing the work area alone, leaving personal content intact

Not reasonable, and a fast way to lose the program:

• Full device wipe authority
• Continuous location tracking
• Inventory of personal apps, photos, contacts, call logs, or browsing history
• Any collection of personal content by the agency or its vendor

Publish what the agency can and cannot see. Employees who distrust the answer forward work to personal accounts instead, which is worse for records than an unmanaged phone.

Consent, notice, and search

Enrollment on personal property should rest on a signed agreement, not a checkbox in a handbook. It should state what the software does and does not collect, that agency records on the device belong to the agency no matter who owns the hardware, that the employee will preserve and produce those records on request, the reimbursement terms, and what happens at separation.

Public employers searching employee property face constitutional limits private employers do not, and courts examine whether a search was justified at its inception and reasonable in scope. Clear advance notice narrows the privacy expectation and makes a later request easier to defend. Have counsel draft that language rather than borrowing a corporate template.

Records requests, holds, and separation

Public records laws generally turn on content, not on which device holds it. Communications about agency business can be disclosable even when they sit in a personal account, a conclusion state high courts have reached in more than one jurisdiction. Requirements differ, so confirm your state's with counsel.

• Route first, search second. The strongest control is architectural. Give staff an agency messaging and email path and archive it, so records stay searchable centrally without anyone surrendering a phone.
• Holds must name devices. A litigation hold covering email but not text messages on personal phones invites a spoliation argument. Name personal devices and personal accounts used for business, and confirm receipt in writing.
• Separation is a collection event. Build record recovery and work-area removal into offboarding before the last day, and document what was collected. If the agency pays for the number, decide in advance whether it transfers.

What to require and how to start

Ask vendors to demonstrate, on an enrolled personal device, exactly what an administrator sees. Require in the contract: work data segregated from personal data, selective removal of agency content only, exportable audit logs, written confirmation that the vendor does not access personal content, export of agency records in a usable format, and defined renewal pricing and exit terms.

Then start small. Find where agency business is actually happening, classify roles by records exposure, choose an option for each, clear the labor and tax questions, and pilot before the policy is final.

HQT works with state and local agencies on mobile device management, records architecture, and the policy and technical design that connect the two.

Frequently asked questions