The short answer: Business MacBook and iPad servicing starts not with a screwdriver, but with proper records. For every device, you need to know its owner, exact model, criticality, backup status, cost approver, and the acceptance test to be performed. A consistent process reduces the time devices spend sitting idle while awaiting a decision and prevents password sharing. ITHOPE in Brno accepts out-of-warranty hardware repairs after individually verifying the model and scope; we are not an Apple Authorized Service Provider.
One device, one traceable record
Accepting devices through email without an asset number quickly creates chaos. The record should link the device to its user and company without unnecessarily copying sensitive content. An internal identifier, device type, model, serial number stored in a protected system, fault description, condition upon receipt, and contact details for the person authorized to approve the quote are sufficient.
The model must be exact. „MacBook Pro„ and „iPad Air" cover multiple generations. Apple explains how to identify a Mac in the operating system or by its serial number, and an iPad by its model number. Include only the information needed for initial assessment in ordinary email threads; complete identifiers belong in a controlled system.
What the records should actually contain
| Field | Purpose |
|---|---|
| internal asset number | unambiguous identification without sending the serial number by email |
| exact model and year | „MacBook Air M1 2020,„ not „silver MacBook" |
| model number in the A… format | the only reliable way to identify an iPad generation |
| role and criticality | determines priority and eligibility for a loaner device |
| user and cost center | who has the device and who pays for the repair |
| approver and approval limit | who may approve the quote and up to what amount |
| management status (MDM) | whether the device is enrolled and who can remove it |
| date of the last verified backup | not „backup is enabled," but when it last completed |
| service history | how many times the device has been serviced and for what issues |
Even a spreadsheet can handle these nine fields. Without them, every service request starts from scratch: finding out who has the device, who can approve the repair, and whether it has been backed up.
Model records: why „iPad" is not enough
Accurately identifying the generation is even more important for iPads than for Macs because Apple reuses product names for years. You can find the model number in the A… format under Settings → General → About. Tap the part number to switch to the model number; Apple also provides an iPad model identification guide. Typical business fleets include the 9th-generation iPad (2021, A2602/A2604), 10th-generation iPad (2022, A2696/A2757), 2022 iPad Air with the M1 chip, and 11″ and 12.9″ iPad Pro models from 2018–2022.
For MacBooks, record at least the product line, screen size, year, and chip type: MacBook Air M1 2020, 13″ MacBook Pro M1 2020, 14″ and 16″ MacBook Pro models from 2021 with M1 Pro or M1 Max, and MacBook Air M2 2022. Keep Intel-based models from 2016–2020 separate, as both parts availability and residual value differ significantly. This single spreadsheet column will eliminate half the questions that otherwise arise when submitting a service request.
Recommended service workflow
| Step | Output |
|---|---|
| report | device, user, symptom, priority |
| intake | condition photographs, accessories, internal ID |
| diagnostics | findings and solution options |
| approval | a named person confirms the scope and price |
| repair | work performed and part used |
| handover | joint functional test and updated records |
Unclear decision-making authority delays a service request more than the repair itself. A company should therefore define an amount or type of work that the IT administrator may approve, along with a clear escalation path for everything else. This does not replace diagnostics with a fixed price; it simply determines who makes the decision and how quickly.
Approval: who, how much, and how quickly
Business service requests are most often delayed by approval, not by parts. Set the process out in writing before the first failure occurs:
- IT administrator’s limit. Up to an agreed amount, the administrator approves the repair without consulting anyone else. Below this threshold, there should be no wait for a meeting.
- Second level. Above the limit, a manager or company director approves the repair, with a specified response deadline. Without a deadline, escalation merely becomes another delay.
- Delegate. Every approver must have a designated substitute. A holiday should not bring servicing to a halt.
- Rule for additional findings. Decide in advance what happens if diagnostics uncover a second fault: whether new approval is required or the original spending cap still applies.
- Form of consent. Use email or a ticket, not a verbal agreement in the hallway. Every repair should leave a traceable record of who authorized it and to what extent.
We do not promise a price or completion date without diagnostics. The designated approver always receives the quote, and no paid repair begins without their confirmation.
MDM and Activation Lock: resolve them before handover, not after repair
If devices are managed, preparation should cover several questions that the service provider should not have to resolve:
- Is the device enrolled in MDM, and who operates the management system? For an externally managed fleet, identify who has administrator access and how quickly they can respond.
- Who can remove and re-enroll the device, and how long does that take? Include this figure in the downtime plan.
- Which account is Activation Lock tied to? An administrator handles a business account. If it is linked to a user’s personal account, you need that specific person’s cooperation—and they may be on holiday or no longer work for the company.
- Does the procedure require Find My to be turned off? If so, the administrator or user should do it, not the service provider, and they should be told why.
We do not bypass Activation Lock or attempt to do so. We do not accept a device for repair if the company cannot prove ownership and has no access to its management system.
Loaner devices and business continuity
Prepare a loaner MacBook or iPad for a critical user before the original device is sent away. It must have the necessary updates, management, encryption, and valid licenses. Migration should not rely on improvised sharing of personal accounts. For roles dependent on certificates, VPN access, or multi-factor authentication, verify the recovery process in advance.
A fleet without a spare device pays for every repair through unnecessary downtime. The loaner does not always need to be the same model; it needs to provide the functionality required for that role. A practical minimum is usually one loaner MacBook for every ten to fifteen users and one loaner iPad for each location where customer service depends on an iPad. For roles that use a mobile app as a second authentication factor, verify access on the loaner before the original device is sent away. Otherwise, you may lock the user out of company email at the very moment you are trying to help them.
Handover report: what it must contain
The report is not a formality; it is the only record of the device’s condition at handover. It should include:
- the date, name of the person handing over the device, and its internal ID,
- the exact model and year, plus the model number for an iPad,
- the fault as reported by the user,
- visible damage, including photographs of the frame, corners, display, and ports,
- accessories handed over, such as the power adapter, cable, case, stylus, or keyboard,
- the approver and their approval limit,
- confirmation that a verified backup has been created and when,
- the agreed method and date for returning the device.
When returning the device, work through the same information in reverse: recorded findings, work performed, type of part used, tests completed, and the recipient’s signature. Testing the device on site takes a few minutes; disputing the result two weeks later takes days.
Passwords do not belong in a handover report
A service provider does not need passwords for email, online banking, password managers, or the company’s Apple account. Tests that require the device to be unlocked can be scheduled with an authorized user during handover. If a specific procedure requires a change to Find My or another setting, the administrator or user should make the change after receiving an explanation of why it is necessary.
Before servicing, Apple recommends creating a backup and describes the configuration steps needed for diagnostics. This is not an instruction to disclose permanent passwords to a third party. Company policy should specify who creates the backup, who unlocks the device, and how the test result is recorded.
There is one more boundary that should be stated clearly in advance: we do not offer data recovery from mobile devices, including iPads, even as an add-on to a repair. Data must be backed up before handover. If you send an unbacked-up device for service, you must accept that its contents may be lost.
What to measure for recurring service
Track the number of faults by model, repeat repairs of the same device, time spent waiting for approval, the type of part used, and when the device returned to operation. The data will show whether it makes sense to keep loaner devices, standardize configurations, or replace a particular part of the fleet. Do not, however, mistake internal service history for a technical diagnosis of the device’s current condition.
The simplest metric is also the most useful: how many days the device was out of service, and how many of those days it spent waiting for a decision rather than for work to be completed. In most companies, the second figure is higher than the first—and fixing that costs nothing in replacement parts.
The wider device lifecycle is covered by ongoing business IT management. The basics of protecting information before handover are summarized by the 3-2-1 backup rule.
Out-of-warranty business intake in Brno
Use the Apple device service in Brno page to send us the number of devices, exact models, fault descriptions, and your required approval process. Before accepting a larger batch, we will confirm capacity, scope, and the handover process. We do not promise a price or turnaround time without inspecting the specific devices.
Frequently asked questions
Should a company send all its devices at once?
Only after agreeing on capacity and priority. A smaller pilot batch verifies the record-keeping, handover, and approval process without causing a fleet-wide outage.
Can you repair the 9th-generation iPads we use as point-of-sale devices?
Send us the number of devices, model numbers, and fault descriptions. We confirm the scope individually after verifying each model. We do not promise parts availability, price, or turnaround time in advance. For operationally critical devices, we recommend starting with a smaller batch so the store is not left without a functioning point of sale.
Does the service provider need company passwords?
Not for standard hardware intake. Tests requiring an unlocked device are arranged with an authorized person; permanent passwords are not shared.
What belongs in the service history?
The date, device, findings, approved scope, part used, tests performed, and result. It should not contain the contents of user files.
Who should approve a repair if the device is leased or supplied by a mobile operator?
Verify the owner first. For leased devices or equipment supplied under a mobile operator’s contract, the service channel and approver may be different from the user—and work performed without the owner’s consent could cost the company more than the repair itself.