Open ICAP.
Open the demo workspace
RESEARCH BRIEF · NOVEMBER 18, 2026
Make readiness visible.
Make the evidence explainable.
Colorado ICAP compliance and administrator workflows, researched before
implementation. Research audience: district administrators, school
leaders, counselors and teachers. Only school and district administrators
sign in to this build. Staff owners can be recorded without accounts.
Students and families participate in planning and can receive
staff-prepared documents.
Product conclusion. Build a staff workspace that connects
each evidence decision to its authority, applicability, school year and
reviewer. Keep portfolio coverage, graduation demonstrations and support
delivery distinct. A completion percentage is a local management measure,
never a state certification.
1. Authority, currency and interpretation
The
Secretary of State rule index
identifies January 14, 2025 as the current effective version of 1 CCR
301-81. The supplied four-page rule was read in full and its history
matches that date. CDE's
rules page
links to the official index, a crosswalk and a document explicitly labeled
as a draft model approach. The older five-page rule at ruleVersionId=5124
is archived material and is not the implementation baseline.
Law, rule, implementation guidance and local procedures need separate
labels. The 2025 rule permits a district to use CDE's model or develop its
own approach (§4.1). Historical grade checklists and the eight quality
indicators are useful instructional references; they are not a newly
mandated statewide grade-by-grade checklist. The local District View
spreadsheet-style PDF was reviewed as an example of reporting, not as a
list of legal requirements.
2. State-rule crosswalk for a staff system
The following paraphrases the supplied current rule, pp. 2–4. Each
implemented requirement carries its citation and applicability. Grade
deadlines and evidence review standards in the application are
illustrative district choices.
| Authority |
What the record needs to establish |
Staff workflow / acceptance |
| §3.01(1) |
Career exploration, written postsecondary/workforce goal, yearly
benchmarks, interest surveys and anticipated study.
|
Review a goal and dated exploration evidence; retain annual goal
changes and benchmark outcomes.
|
| §3.01(2)–(4) |
Coursework, academic progress, remediation/credit recovery,
concurrent enrollment, arts participation and grades, and
intentional course sequencing.
|
Link SIS or paper evidence with a custodian and date. A four-year
plan alone does not establish every academic element.
|
| §3.01(5), (11) |
Relevant assessments; where district-administered placement
assessments identify risk, an intervention plan and progress with
the student/family.
|
Record applicability and assessed need. Do not mark missing optional
tests as universal failures; do not let an intervention become a
generic completion toggle.
|
| §3.01(6) |
Contextual/service-learning plans and experiences, where applicable.
|
Permit a reasoned not-applicable decision, independent of whether a
work-based course is submitted for funding.
|
| §3.01(7)–(8) |
College or alternative applications and resume as
prepared/submitted, and postsecondary study progression.
|
Track preparation stage and pathway. Military, training and
apprenticeship routes must remain usable.
|
| §3.01(9)–(10) |
Financial aid progress and understanding of postsecondary financial
consequences, plus other PWR evidence.
|
Store milestones and staff-reviewed evidence, without collecting tax
returns, SSNs, aid credentials or financial account numbers.
|
| §3.01(12) |
Assistance exploring registered apprenticeship programs with student
and parent/guardian.
|
Record exploration and participation; distinguish exploration from
verified registration or enrollment.
|
| §2.6; §3.2; §3.02(1) |
A portfolio may span paper and multiple systems; communicate access
in writing; make it accessible and transferable.
|
Evidence location/custodian index, written access instructions, and
reviewed transfer exports. A metadata export cannot replace the
actual evidence held elsewhere.
|
| §3.3–§3.5 |
FERPA protection; financial-aid awareness for students and parents
and help when requested; start by ninth grade.
|
Log awareness date, participant and requested help. Earlier grades
are an optional district expansion. Annual review remains a dated
staff workflow, informed by
CDE's current transition guidance.
|
| §3.6 |
For work-based learning funding support: name, term, created/updated date,
opportunity pursued and connection to postsecondary goals.
|
Structured term record and evidence packet; do not imply this alone
establishes funding eligibility.
|
Related statutory duties
The
2025 Title 22 compilation, §22-32-109(1)(oo)(III), specifies written parent/guardian information
and student explanation about concurrent enrollment, career pathways,
teaching careers, military opportunities and financial aid, with requested
concurrent-enrollment planning assistance. A separate source-mapped
component tracks that evidence. Verify the applicable district or
institute-charter provisions when configuring local procedures.
HB26-1357 was signed June 4, 2026
and phases out TREP; use current teaching-pathway notices rather than
copying obsolete program language. The signed-file download could not be
retrieved in this review, so its detailed transition provisions are not
encoded as an automatic check.
Work-based learning: use the current audit year
The
2026–27 Student October Count Audit Resource Guide, PDF p. 37, repeats the five ICAP documentation fields and separately
requires a course catalog, student schedule and supporting funding
documentation. It also states that the guide must be read as a whole. The
application's work-based learning record checks the ICAP fields only. Course quality,
instructional time, enrollment, attendance and the complete audit
submission remain separate responsibilities. CDE's
pupil-count page
links to the applicable guide and advises secure PII transfer.
Effective-dated change: 2027–28 financial-aid practice
Enacted HB25-1192
adds, starting in 2027–28, graduation-year exposure to federal aid
eligibility tools and net-price calculators and practice completing FAFSA
or CASFA. It permits affirmative decline by the student or parent/guardian
or a staff determination of infeasibility. This is practice, not a
requirement to submit a real aid application. Track exposure, practice or
a documented exception separately. The application effective-dates this
component to grade 12 portfolios from 2027–28 onward; it is excluded from
2026–27 coverage. The act's financial-literacy course provision is
separate from the ICAP practice workflow.
Guided-entry prompts and illustrative examples
Checked November 18, 2026. The application's field hints, questions and
draft formats are authored adaptations, not official CDE responses.
Goal and yearly-benchmark prompts draw on
CDE's ICAP rules
§3.01(1); record-location hints reflect the distributed portfolio in §2.6;
work-based learning questions reflect §3.6. Each evidence rationale also
uses the checks and authority already mapped to that component above.
Support and progress questions draw on the
current CDE ICAP model.
Student-perspective, conversation and next-step prompts draw on
CDE's Meaningful Career Conversations background resource.
Optional exploration activities also draw on CDE's prior
Scope and Sequence possible objectives.
The older document is used for activity ideas, not its superseded rule numbering.
Examples describe possible wording or records; they do not establish that
a student completed an activity or that a component does not apply.
Drafts use only staff-entered answers, require explicit insertion and
remain editable before saving. Student statements are not generated.
The drafting feature runs entirely in browser memory without an LLM or
external inference service. It does not change review statuses or
determine compliance, readiness or graduation eligibility.
3. Recommendations from CDE's current model
The
current CDE ICAP model
and
FAQ
describe universal, targeted and intensive support, readiness evidence and
continuous improvement. K–12 participation is encouraged; the stated
required grade span is 9–12. These sources support monitoring access and
scaling services, rather than treating ICAP as a one-time assignment.
The supplied 2026 model document was reviewed, including its four domains,
opportunity tables, system reflection and example measures. The product
interpretation is to record domain-specific support, owner, rationale and
review date. A student's tier is an educator decision and is not inferred
from a percentage, disability, low grades or missing evidence. Keep
universal opportunities available across tiers. Program goals and examples
in the model do not establish statewide numerical targets.
Graduation Guidelines
call for at least one demonstration in Reading, Writing and Communicating
and one in Mathematics under locally adopted options. Store the selected
option, source, date and local review; show these beside ICAP portfolio
coverage, without treating one as proof of the other. Do not hard-code
assessment cut scores from an old PDF. CDE's current secondary-transition
guidance calls for coordinating ICAP and IEP transition planning; a shared
artifact does not certify IEP compliance. The application avoids
disability records and clinical notes.
Expandable ICAP guide and Colorado government supplementary resources
Checked November 20, 2026. The four workflow expansions in
guide-details.mjs are application-authored planning steps and
optional examples. They use the existing ICAP model and rule interpretation
above, without adding assignments or changing applicability or review decisions.
The supplementary collection links only to Colorado government .gov pages;
the guide’s existing CDE authority citations remain separate.
All ten destinations were opened during research. Descriptions summarize the
resource’s purpose; time-sensitive benefit amounts, application deadlines,
test scores and program availability are not copied into the guide.
Links open only on user navigation, with no-referrer protection and fixed
URLs containing no student information. Expansions use native details and
summary controls and require no external service.
4. Competitor review: administrator and teacher workflows only
These findings are based on public first-party material, not access to a
licensed administrator tenant. “Not established” means the public material
reviewed did not demonstrate the capability; it does not mean the vendor
lacks it. No pricing, product ranking or compliance certification is
inferred.
| System |
Verified public evidence |
Implication and validation questions |
| SchooLinks |
The
Colorado page
describes ICAP indicators, course planning and local PWR/KRI
monitoring. Its
Colorado webinar description
emphasizes centralized records and reporting. The
staff overview
describes caseloads against state, district and custom graduation
requirements.
|
Strong benchmark for district visibility and unified planning. Ask
for the precise 2025 rule crosswalk, 2027–28 exception handling,
evidence-level review provenance, work-based learning audit-year fields and teacher
scope enforcement. The public pages do not establish all of these.
|
| Naviance |
Success Planner 2.0 documentation
describes task/status updates, assigned-student exports and change
history.
Reporting documentation
supports filters, selected columns, CSV and saved/shared reports.
Roles documentation
separates school and district capabilities.
2026 enhancements
mention state-aligned templates.
|
Benchmark task orchestration, reusable reports and role permissions.
Public documentation reviewed does not prove Colorado-specific
template coverage.
Login-report documentation
warns district task reports cover district tasks, not school tasks:
explicitly test denominator and school-task rollup behavior in
procurement.
|
| MaiaLearning |
The
Colorado product page
states support for ICAP, annual updates, academic plans, work-based learning,
credits, credentials and Graduation Guidelines. It describes
counselor task templates, assignments to students/grades/districts,
private/shared notes, reports and outcomes.
|
Benchmark a concise staff workflow and consolidated records. Ask how
Colorado requirements are versioned, how review decisions differ
from task completion, how teacher access is limited and how full
portfolios transfer. The page describes alignment, not an
independent determination of legal compliance.
|
Positioning inference: reporting and task management are
established expectations. The application should stand out through
transparent evidence decisions, applicability, future effective dates and
a work queue tied to responsible staff. Student college search,
personality assessments, student AI, application submission portals and
student/family accounts are outside this build.
5. Student privacy: obligations translated into architecture
Compliance depends on the school's policies, contracts, actual deployment,
access administration and operating practices. Cloudflare encryption and
an access screen do not by themselves make a system FERPA- or
Colorado-compliant. This research provides a design and implementation
baseline, not a legal certification.
| Source / obligation |
Design response |
|
FERPA school-official guidance
and 34 CFR Part 99
|
Determine the lawful disclosure basis. For the school-official
exception, support school control, educational purpose and
legitimate educational interest. Signed, verified identity maps to
an active district membership; educators see assigned students only,
school admins their school, and district admins their district.
Request-supplied role, email or tenant identifiers confer no access.
|
|
FERPA rights
and
access timing
|
Staff track identity verification, appropriate rights-holder,
access/correction request, reasonable response deadline within 45
days, decision and delivery. Rights can transfer at 18 or
postsecondary attendance. Do not destroy records under a pending
inspection request. “Staff-only” notes are not automatically exempt
from access rights.
|
|
Colorado contract-provider obligations
|
Document collected data and purpose; prohibit sale, advertising,
unrelated profiles and reuse. Require security, subcontractor
obligations and district-directed destruction terms. Track
termination and destruction, including copies. Provider and school
obligations depend on the actual service and contract, even if users
are adults.
|
|
Colorado local-provider obligations
|
Maintain district transparency materials, approved service/contract
inventory, parent complaint route and governance owner. A settings
page cannot substitute for notices, agreements or school procedures.
|
|
Colorado AG data-security and breach guidance
|
Reasonable safeguards and incident response with immediate internal
escalation. Assess applicable notice obligations, including
Colorado's 30-day outside limit and AG notice threshold. Contract
notification to the district should allow it to meet its duties; do
not delay until a vendor investigation finishes.
|
|
PPRA;
FTC COPPA guidance
|
No student accounts, embedded third-party surveys, tracking pixels
or child-directed collection. Adult operation does not erase
education-record protections. Review PPRA/consent and COPPA
applicability before adding child-facing tools, protected-topic
surveys or direct collection from children. Avoid eliciting
protected-topic or family financial details in generic notes.
|
Cloudflare deployment choices
-
Workers + D1: application data uses a private binding,
prepared SQL, district/school/assignment checks and optimistic
concurrency. Separate production, test and demo data and credentials.
Use a separate D1 database per district for a higher-isolation
production option; tenant columns and checks are still required.
-
Identity: Cloudflare Access with the district IdP and
MFA. Validate signature, issuer, audience and expiry of the
Access application JWT
at the Worker. Require explicit database membership; deny by default and
disable alternate unprotected origins.
-
Location and encryption:
D1 encrypts stored data and network transfers
using Cloudflare-managed keys.
Location hints are not jurisdiction guarantees. The
US jurisdiction announced October 2, 2026
is a relevant creation-time choice; separately review Worker processing,
logs, support access and subprocessors. US residency is an architectural
preference here, not an asserted universal FERPA requirement.
-
Minimization: retain school IDs, goals, evidence
metadata, review decisions and support records. Exclude SSNs, tax
documents, aid passwords, clinical notes, full IEPs and unnecessary
birth dates. Link to approved system custodians instead of duplicating
documents. No analytics SDK, advertising or model training.
-
Exports: single-student, approved purpose and
recipient, recorded disclosure basis, staff review and secure delivery
outside the app. No public portfolio URLs. Audit reads, changes and
exports; internal security events and FERPA disclosure records serve
different purposes.
-
Retention: district-approved schedules by record type,
legal/access holds and verified deletion of active data, exports and
backups as applicable. D1 recovery windows must be documented; reapply
deletion tombstones after restore. No universal “delete after five
years” rule is invented.
-
Files: the application stores references, not
attachments. If files are added, use private R2 behind the same
authorization, download checks, malware scanning, size/type restrictions
and lifecycle policies. Do not use a public bucket.
6. Application scope and release boundary
Implemented demonstration: school/grade/owner filtering, evidence coverage
with clear denominators, prioritized review work, student portfolio and
source mapping, reasoned review decisions, annual review, manually
assigned support tier, structured work-based learning documentation, report export,
graduation-demonstration records, student summaries, full-record review
exports, privacy-request tracking, retention holds, controlled deletion
and event history. All example people, schools and dates are fictional.
Included server implementation: Cloudflare Worker API, D1 migration,
cryptographic Access-token verification, assignment authorization,
transactional writes/audit, same-origin mutation checks, security headers,
versioned year rollover and security-focused tests. The hosting model is
monthly pricing per licensed student, with server-enforced seats, Stripe
checkout and signature-verified subscription events. Operator access is a
revocable server secret until school identity is connected. The separately
hosted interactive demo uses memory only and never connects to production
D1. Browser refresh resets demo edits.
Before real student records: execute school/provider agreements, approve
the data inventory and retention schedule, provision Access/IdP/MFA and
memberships, set D1 jurisdiction, configure logs/backups/restore and
incident procedures, implement and validate the remaining governance
workflows, and conduct independent authorization and operational review.
The application does not send messages, submit state reports, award a
graduation credential or certify funding eligibility. Research should be
rechecked when state guidance or the school year changes.