## TechReady.io · For Academic Technology Leaders ### What Your LMS Assumes. What TechReady Verifies. ### The Assumption Every LMS Makes Your LMS assumes the student's device is ready. Browser compatible. OS current. Bandwidth sufficient. Webcam present. It has to — it has no way to check. That assumption fails quietly. A student with an outdated browser can't run certain LMS features. A student with an aging OS hits compatibility errors. The LMS records no activity. The student disengages. The first signal is a missed assignment — days or weeks after the problem first appeared. # 4 in 10 students still arrive at sign-on with outdated browsers — unchanged for nearly a decade despite improvements in hardware and connectivity ### What Eight and a Half Years of Scans Show Across 131,418 student device scans at 19 institutions since 2017, two patterns are now structural: - Bandwidth is solved. The share of students arriving below 25 Mbps — the FCC's pre-2024 broadband floor, since raised to 100/20 Mbps — dropped from 47% pre-pandemic to 13% in 2026. Median download speed: 146 Mbps. - Browser hygiene and OS currency have not improved. Four in ten students arrive with outdated browsers. One in three with outdated operating systems. These are the failure modes your LMS can't see. The fixable problems that produce first-week ticket surges and early disengagement are not infrastructure problems. They are device-hygiene problems that arrive with the student — and are catchable before the first course session. ### Architecture: Fits Your Stack Without Touching It TechReady is browser-based. No software is installed on student devices. No student PII is collected or stored. FERPA review — which can take quarters for software-based tools — is largely sidestepped for TechReady: with no PII and no software, there is little to evaluate. The scan runs at sign-on, tests devices against your institution's own documented technical requirements (not a vendor benchmark), and surfaces a knowledge-base recommendation to students with fixable issues. The institution gets a dated, student-level record. You get no new software to manage, no API surface to secure, and no data-sharing agreement to negotiate. *"TechReady doesn't define readiness. Your institution does. The scan tests devices against your own documented technical standard."* ### What You Can Show Your Stakeholders At sign-on, before day one, with a dated and exportable record: how many students in this cohort had fixable technical issues, which issues, and which received knowledge-base guidance. That is the operational evidence layer your student success and IE colleagues need — and the one most LMS stacks cannot produce. ### LTI and API Integration — Included at No Upcharge TechReady connects to Blackboard Learn and Ultra via LTI — included in every subscription at no additional charge. The scan deploys as a required activity inside any course or orientation workflow without a separate student login. An API feed is also included, pushing flagged student data into your student success or early-alert platform at the moment of scan. No integration project, no separate licensing conversation, no upcharge for either. ### The Orientation Course Implementation Model The highest-coverage deployment pattern is a required LMS orientation course that every incoming student must complete before accessing live coursework. The TechReady scan runs as one required step in that orientation — alongside syllabus review, LMS navigation, and account setup. Because completion is required, the institution approaches 100% scan coverage of the incoming cohort rather than relying on voluntary student behavior. Every student who completes orientation has a scan record. Flagged students can be triaged immediately. The institution has a dated, student-level intervention record for the full entering class before day one — not just for the online population, but for every student using a personal device to access institutional systems. ### 30-Day Readiness Audit — No Cost 500 scans on one incoming cohort. No install, no PII, no FERPA burden. You see exactly what your students are arriving with — browser versions, OS currency, connectivity — before the first course session.