Four overlapping iMessage screenshots show a contact named Kaylee arranging two rides with the device owner. The contact card's Siri suggestion reads “Kaylee Uber” and identifies home as 1122 King Road. At 8:40 p.m. Saturday, Kaylee asks whether the recipient is driving. At 10:02 p.m., she asks for pickup at 1122 King Road and a ride to “the club”; the driver says they have just dropped people in Pullman, estimates 15 minutes, and reports arrival at 10:15. At 1:45 a.m. under “Yesterday,” Kaylee asks for pickup from the Grub Truck. The driver says they will arrive shortly, reports being parked at 1:49, and Kaylee replies that “They are at 75 and we are 78.” At 1:05 p.m., the driver sends “You all ok?” and the screenshot shows Delivered. The screenshots do not display absolute dates, device metadata, phone numbers, export provenance, or a forensic authentication report.
A large collection of Idaho State Police investigative supplements for case D22000030. The searchable extraction includes the November 13, 2022 initial call-out, witness and roommate interviews, crime-scene work on multiple dates, photographic and SUAS documentation, evidence transport, phone and video inquiries, search-warrant activity, receipts, hospital checks, WSU and Moscow reports, vehicle and Hyundai Elantra processing, defense evidence processing, and later witness-list follow-up. At least 117 unique supplement identifiers and 35 report-title labels are visible in the extraction, with reports attributed to numerous ISP investigators. The collection records officer narratives, witness recollections, investigative leads and later follow-up; those categories are not interchangeable with independently proven fact.
A verified connected-Drive PDF titled “26. Uber Driver Information ,” filed under MPD Investigative Docs. The authorized folder context identifies it as part of Moscow Police investigative reports, interviews, warrants, evidence handling, and follow-up. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
A verified connected-Drive PDF titled “68. Uber Location Request,” filed under MPD Investigative Docs. The authorized folder context identifies it as part of Moscow Police investigative reports, interviews, warrants, evidence handling, and follow-up. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
The fourth installment compiles WSU safety concerns, institutional communications, media-related correspondence, public-records handling, and investigative support. Visible examples include a parent’s November 22, 2022 questions about campus safety and academic options, a January 2023 message circulating a Kohberger internship-related video, and a January 2024 request concerning memorial coins for WSU Police staff who worked the Idaho Four response. The large production also references parking, LPR, warrant, and administrative records; each thread must be read with its own date and sender context.
The eighth and largest text installment compiles media requests, interview invitations, press releases, campus-safety communications, public-records correspondence, parking/LPR references, warrant-related material, and institutional messaging. Examples include a December 27, 2022 podcast invitation to WSU Police leadership, January 3 Moscow releases on extradition and nondissemination, and WSU communications describing increased patrols, safe-ride and escort resources, academic flexibility, and employee/student support after the homicides and arrest. Repetition and forwarded chains are substantial; each item’s sender, date, attachment, and status should be verified in the original.
This record indexes “social_media_results_2.pdf,” a PDF stored under “Pullman Social Media Records.” Connected extraction recovered 34,965 searchable characters. A sanitized full-text extraction is included for research and must be checked against the original layout.
This record indexes “social_media_results_3.pdf,” a PDF stored under “Pullman Social Media Records.” Connected extraction recovered 27,724 searchable characters. A sanitized full-text extraction is included for research and must be checked against the original layout.