THE KEY POINTS
What to take with you.
- Keep a separate reference for every phone, even when one custodian has several devices.
- Confirm scope, practical readiness and communication responsibilities before invitations go out.
- Track collection and delivery separately, then reconcile the results against the device roster.
Start with a roster that accounts for every phone
A matter involving several custodians needs a way to answer a simple question: what is happening with each phone? Start with one shared roster in the workspace agreed with the collection team. Give each device its own reference, linked to the custodian and matter. One person may have a current phone and an older phone; treating that as a single assignment can hide an unfinished collection.
For each device, record the reachable contact, phone platform, agreed scope, next action and person responsible for it. Keep sensitive details in the agreed workspace. A short coordination list should help people find the assignment without becoming another copy of the evidence.
Accurate device identification also supports the collection record. SWGDE’s mobile-device best practices, version 2.0, dated August 21, 2025, address device identification in section 4.1.1. The roster suggested here is a practical coordination aid; it does not replace the examiner’s records.
Confirm the differences before sending instructions
Agree which phones and supported data categories are in scope before asking custodians to begin. Identify relevant sources such as texts, WhatsApp or Signal and make sure the assignment refers to the phone holding that material. If a custodian has replaced a device, resolve that change with the collection team before starting.
Readiness will vary. Ask about availability, time zone and any restrictions on the setup. An employer-managed computer may need IT assistance before software can be installed. Managed phones can also have restrictions: section 5.3.3.1 of the same SWGDE guidance, version 2.0, discusses mobile-device management and administrator involvement. Raise restrictions early rather than asking the custodian to bypass them.
In MARA’s remote iPhone workflow, the custodian uses a supported Windows computer or Mac, depending on the assigned collection, and connects the phone by cable. MARA’s Android phone app supports collection directly on the handset without a computer connection. Send each person the instructions for their assigned collection, rather than one generic setup message for everyone. The preparation guide explains these paths.
Give communication a clear owner
Decide who coordinates the matter, who can answer scope questions and where a custodian gets collection help. These may be different people. A custodian who cannot install software should have a clear contact and next step, without having to copy the whole legal team into troubleshooting messages.
For MARA-managed collections, your team submits the request through the portal and MARA coordinates with the custodian. Enterprise teams manage their collection work through their own MARA workspace. In either case, check the assignment and contact details before an invitation is sent. The custodian’s collection invitation and the legal team’s portal access serve different purposes.
Schedule around readiness and support needs
For a larger matter, consider starting with a small group whose scope and setup are ready. Confirm that instructions reach the right people and that support arrangements work before inviting the next group. Grouping by availability or time zone can make coordination easier; the right order depends on the matter’s priorities.
Allow for setup and delivery as well as collection. For iPhone, the custodian needs to be available for prompts on the phone. Apple’s guidance on trusting a computer, published December 4, 2025, describes unlocking the device and confirming access. A scheduled start should account for that interaction. Collection and transfer times vary, so avoid promising that every device will finish in the same window.
Track collection and delivery as separate milestones
A single “done” column can conceal what still needs attention. Use milestones that answer different questions: has the invitation reached the custodian, is the setup ready, is collection underway, is delivery underway, and are the completed deliverables available to the authorized receiving team? These are planning milestones, not prescribed names for portal statuses.
For MARA’s remote iPhone workflow, successful collection starts secure upload from the computer to the portal automatically. The custodian does not need to click a separate upload button. Keep collection progress and delivery progress distinct when checking the roster. Follow the instructions and status for the assigned path, then confirm availability to the receiving team.
Give exceptions an owner and a next action
When work pauses, record what is needed to move it forward. “Waiting for IT to approve software on the collection computer” is more useful than “custodian delayed.” Assign a contact and next action. If the phone, scope or schedule changes, keep the assignment and collection team aligned before proceeding.
Coordinate with the collection team before repeating an interrupted workflow. Keep relevant changes and outcomes connected to the eventual handoff. SWGDE’s Requirements for Report Writing, version 1.0, November 20, 2018, addresses request scope, item identification, results and applicable procedural deviations in sections 5.2 through 5.4. A project tracker supports coordination; the examination report documents the examination.
Close the matter against the agreed roster
Before marking the collection work complete, account for every assigned phone. Match each device to its outcome, deliverables and any unresolved issue or agreed change. Confirm who receives the material and what happens next. A completed device should not hide another device that still needs attention.
Use the collection report and handoff checklist to plan the receiving team’s review. MARA Analyzer can help review supported artifacts and prepare reports or exports for downstream work. The aim is a clear outcome for each phone and a handoff the next team can use.