The student still does the thinking.
- Orient to the lecture before expanding notes
- Retrieve an idea before seeing the answer
- Return to the source and write a personal explanation
Institutional readiness
Education leaders can examine how Synlecto turns lecture material into active study, then review source grounding, accessibility, privacy, governance, current controls, known limits, and the next accountable decision.
Current public gate: ready for a first conversation. A pilot offer and formal procurement response remain controlled review stages.
Review what the learner sees, where active effort happens, and how the lecture remains the reference throughout.
Review flow
Education leaders can start with the learning case, then see the assurance evidence expected by learning technology, accessibility, privacy, procurement, and student-support teams.
Students move from lecture source into guide, recall, application, and revisit actions rather than finished answers.
Source boundaries, quality labels, review state, and course-rule reminders make limits visible to students and staff.
Accessibility, privacy, procurement, integration, and support questions sit beside the learning case, not after it.
A bounded pilot tests benefit, risk, support load, and expansion criteria before any wider institutional decision.
Positioning
The product is positioned as a lecture-first study route for higher education, with careful claims and a clear university pilot path.
Synlecto is a lecture-learning system for higher education. It turns lecture material into structured study support, active recall, and next-step revision, with academic quality controls, accessibility-first design, and institution-ready deployment.
Synlecto is not a generic AI summary app. It is a quality-gated lecture-learning layer designed for university teaching, accessibility, and term-long revision.
Institutional adoption is framed as managed deployment for cohorts, schools, or support services.
Current confirmed state: what Synlecto can support from current code, tests, and public documentation.
Controlled deployment position: the deployment framing used for university review and contract discussion where it does not overstate current implementation.
Roadmap or bespoke work: later work that is scoped openly with the university and not presented here as current implementation.
Assurance evidence
Each lane gives a reviewer the current public position first, then keeps limits, evidence, and roadmap items close to the relevant question.
Guide first, recall next, revisit later
Synlecto is moving from one-off guide generation toward source-grounded study routes: a lecture-first route through recap, active recall, revisit points, and later review.
Assurance is shown in the product through guide quality labels, source coverage checks, publication states, and review prompts.
For universities, the practical pilot question is constructive learning value: whether students can use existing lecture material more confidently while course materials, lecturer judgement, and academic standards remain central.
Current public position
Synlecto has a documented security baseline and a roadmap toward stronger formal assurance suitable for institutional review.
Synlecto uses authenticated access controls, server-side verification, rate limiting, security headers, and privacy-aware observability.
Sensitive content is not sent into analytics by default.
Core application data is hosted in European infrastructure.
If any third-party processing falls outside that core hosting footprint, it is disclosed in sub-processor and contract materials.
Inclusive study support
Synlecto is designed with accessibility-first principles and aims toward WCAG 2.2 AA-aligned delivery, supported by automated checks, manual assistive-technology testing, and a published accessibility statement with known limitations and ongoing improvements.
Synlecto supports accessibility-first study through keyboard-oriented controls, reading preferences, transcript-linked study support, automated checks, and manual assistive-technology testing evidence.
Known limitations and ongoing improvements are stated openly rather than being hidden behind a blanket conformance claim.
Compatibility context
Current state: browser-surface compatibility with Panopto, Canvas, Moodle, Blackboard, Brightspace, YouTube, Vimeo, SharePoint, OneDrive, and Microsoft Stream, plus Google and Microsoft sign-in.
Microsoft sign-in is described as Microsoft sign-in, not as enterprise SSO.
Roadmap or bespoke institutional work only: SAML, Shibboleth, Entra enterprise SSO, LTI 1.3, Canvas-native LMS integration.
Review evidence
Each row connects a university question to current product behaviour, the evidence route, and the boundary that still needs specialist review. This is a decision aid, not a substitute for legal, security, accessibility, academic, or procurement judgement.
The study route starts with structure, then asks students to recall, compare, apply, and revisit the source. It is positioned as study support, not assessment automation, answer production, or a shortcut around course rules.
Guide quality labels, source coverage checks, provenance language, and honest downgrading help reviewers see when an output is checked, partial, limited-source, or source-text only.
Public wording keeps Synlecto out of assessment automation and reminds students that module, assessment, and academic integrity rules remain authoritative. The product is designed for lecture study, not for producing submissions or judging misconduct.
Synlecto is framed as transcript-aware study support with keyboard-oriented controls, reading preferences, known limitations, and manual testing evidence. It does not claim to replace disability support or formal accommodation processes.
The pilot focuses on repeat study, recall activity, revisit behaviour, student confidence, support load, and quality feedback rather than vanity usage alone.
The page separates current confirmed state, controlled deployment position, and roadmap or bespoke institutional work. Student-facing product language can explain capabilities, limits, source dependence, and responsible use without implying that AI output is authoritative.
Public wording explains the retained guide and cleaned source snapshot model while privacy, DPA, subprocessor, retention, IP, and contract-end details remain in the controlled university review route.
A credible pilot should track support load, student confidence, objections, and guide quality feedback alongside usage. Synlecto is positioned as study support and does not replace professional services, lecturer judgement, or student-support routes.
Readiness stages, document control, review cadence, named pilot ownership, and explicit support-route caveats help the university decide what can be discussed now and what needs controlled review before wider rollout.
Pilot model
This is an illustrative evaluation model, not a current public pilot offer. It becomes viable only when one cohort, a named institutional owner, an agreed support route, response commitments, and closeout criteria are confirmed.
Review the evaluation pathwayA future evaluation would need enough time to observe lecture-to-study behaviour without drifting into an unreviewed rollout.
Typically one module, school, support route, or lecture-heavy cohort, with scale only if support remains controlled.
The pilot has explicit checks before launch, during use, and before any expansion recommendation.
The review tests whether students study more actively while academic and operational risk stays visible.
Review the evaluation pathwayA credible pilot has a named owner, local academic context, a support route, and an expansion gate before broader review.
One education, digital learning, student-success, or school owner holds the pilot question and closeout decision.
Module, programme, school, or support-service context shapes permitted source use and student guidance.
Kickoff, mid-point review, final report, and agreed escalation path keep student and staff issues visible.
No wider recommendation is made without evidence on learning behaviour, quality, inclusion, support load, and risk.
Best starting bundle for first institutional conversations: overview, academic assurance, and current integration boundary.
Use this stage to decide whether Synlecto can send pilot-facing materials rather than only discuss a pilot conceptually.
Formal procurement response is ready only when the formal bundle is safe, required founder values are supplied, and the contract-facing draft materials are no longer blocked by unresolved founder inputs.
Local adaptation
Synlecto can meet the university context with a focused pilot first, then a clearer roadmap conversation around the institution’s learning design, support model, and technology estate.
Pilot one lecture-heavy discipline with examples tuned to its assessment style, terminology, and revision rhythm.
Shape student instructions around Canvas, Moodle, Blackboard, Brightspace, Panopto, or Microsoft Stream usage patterns.
Prepare transcript-aware guidance for accessibility, disability support, learning development, or inclusive education teams.
Agree a compact pilot report showing student route usage, qualitative feedback, assurance boundaries, and next decisions.
Examples include discipline-specific study-route guidance, transcript-aware accessibility review, Canvas/Moodle/Blackboard/Brightspace launch instructions, a leadership-ready pilot report, and stable reviewer-share bundles for security, privacy, accessibility, procurement, and academic assurance.
Deeper LMS-native integration, enterprise SSO, LTI 1.3, formal certifications, and institution-specific data workflows are treated as roadmap or bespoke institutional work unless separately agreed.
Review status
The public pack supports a first education and learning-technology review. More detailed privacy, legal, security, and contract material is completed through the appropriate university review route once scope and contacts are agreed.
Review cadence: Quarterly and before any external circulation after a material readiness change.
Shareable now.
First conversation materials are ready. Pilot review is completed through controlled review once named support handling and contractual response expectations are confirmed. Formal procurement response is completed through controlled review once contract-facing entity, contact, and deletion details are confirmed.
Synlecto retains the generated guide and a cleaned source snapshot used to support source moments, evidence, quality checks, and guide continuity.
Current capability, deployment assumptions, and future integration work are kept separate so a university can distinguish what is available today from what would need scoped review.
Evidence pack
Materials are grouped by review area so education leaders can see the evidence available for an initial conversation, what can be shared with a named specialist reviewer, and what remains incomplete until institution-specific inputs are agreed.
Learning model, guide quality, public trust and accessibility position, current integration boundaries, privacy summary, terms, and review status.
Detailed privacy, security, lifecycle, DPA, subprocessor, accessibility, and implementation material is shared only with an agreed scope and reviewer.
Support ownership, response targets, contracting entity, named contacts, and final retention and contract-end wording must be resolved first.
Public summaries are shown here with their sharing status. Detailed privacy, legal, DPA, subprocessor, and contract-end materials are prepared through the appropriate university review route rather than published as blanket public commitments.
Best starting point: First conversation bundle. Later bundles are stage-gated; their presence in the register does not mean they are complete, publicly shareable, or ready to support a commitment.
Choose the bundle that matches the conversation stage.
Best starting bundle for first institutional conversations: overview, academic assurance, and current integration boundary.
Included public materials: D1. Institutional overview, D7. Guide quality and academic assurance, D8. Integration note: Canvas, LTI, and SSO.
Best bundle for pilot review: overview, accessibility, academic assurance, integration boundary, pilot model, and procurement summary.
Included public materials: D1. Institutional overview, D6. Accessibility statement and testing summary, D7. Guide quality and academic assurance, D8. Integration note: Canvas, LTI, and SSO, D9. Pilot proposal template, D10. Procurement summary sheet.
Best external-safe bundle for structured institutional review: current baseline across procurement, security, accessibility, academic assurance, integration, and pilot framing.
Included public materials: D1. Institutional overview, D2. Security overview, D6. Accessibility statement and testing summary, D7. Guide quality and academic assurance, D8. Integration note: Canvas, LTI, and SSO, D9. Pilot proposal template, D10. Procurement summary sheet.
Start here for first conversations, pilot scoping, and procurement triage.
Plain-language overview of what Synlecto is, where it fits first, and how it should be read institutionally.
Reusable institutional pilot shape covering duration, cohort size, owners, and review cadence.
Single-sheet procurement summary covering product type, hosting, privacy posture, assurance, integration state, and support handling.
Evaluation framework separating product-native metrics, manual review evidence, and pilot risk tracking.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Evidence-backed pilot metrics dictionary tied to existing dashboard and feedback signals, plus manual review measures.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Template for a realistic post-pilot institutional outcomes report without fabricated numbers.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Use these materials for current controls, accessibility position, and evidence boundaries.
Current security baseline wording for institutional review, kept separate from formal assurance claims.
Accessibility-first position, current testing evidence, known limitations, and ongoing improvement note.
Use these materials for privacy triage, DPIA support, subprocessor review, retention, deletion, and contract-end discussion.
Institution-facing privacy summary with the cleaned source snapshot model and controller or processor split.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Operational sub-processor baseline covering current vendors, current role, and transfer-note handling.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Internal scope matrix separating user-scoped, lecture-scoped, institution-scoped, and browser-local data for deletion and contract-end review.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Operational schedule for retention, deletion, export, and contract-end handling across the main university data categories.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Internal note clarifying what is currently deletable, what remains lecture-scoped, and what still depends on deployment scoping or future purge tooling.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Use these materials for guide assurance, current interoperability, and academic trust questions.
Academic assurance explanation describing source provenance, publication states, and honest downgrading.
Strict current-state integration note separating browser-surface compatibility from roadmap-only identity and LMS work.
Plain institutional transparency record describing inputs, outputs, quality gates, publication states, and system limitations.
This material is available for the relevant university review route once scope, contacts, and review responsibilities are agreed.
Deeper security, privacy, procurement, accessibility, and academic review packs are available during university review and are shared through the appropriate review route.
Scope clarity
The following remain roadmap or bespoke institutional work and are scoped as part of a university-specific review: SAML, Shibboleth, Entra enterprise SSO, LTI 1.3, Canvas-native LMS integration, ISO 27001, SOC 2, formal framework or reseller route if not yet secured, campus-wide rollout automation.
FAQ
Synlecto is a lecture-learning system for higher education. It turns lecture material into structured study support, active recall, and next-step revision with academic quality controls and accessibility-aware design.
There is no public pilot offer at the current readiness gate. Once support ownership, response commitments, scope, and contractual inputs are agreed, the intended evaluation shape is 8 to 12 weeks around one bounded learning context. The current route is an evidence-led first conversation.
Synlecto currently describes browser-surface compatibility with lecture and source workflows such as Panopto, Canvas, Moodle, Blackboard, Brightspace, YouTube, Vimeo, SharePoint, OneDrive, and Microsoft Stream. SAML, Shibboleth, Entra enterprise SSO, LTI 1.3, and Canvas-native LMS integration are roadmap or bespoke institutional work unless separately agreed.
A future controlled evaluation could be scoped around a university’s VLE context, lecture-heavy disciplines, accessibility priorities, student-success services, reporting needs, and support model. Deeper LMS-native integration, enterprise SSO, certifications, and institutional data-sharing workflows remain roadmap or separately scoped institutional work.
Synlecto keeps assurance visible through source provenance, guide quality labels, source coverage checks, publication states, and review prompts. The product avoids presenting every generated guide as equally complete.
Universities can use the first-party university review form to start a readiness conversation. That route gathers the decision context without presenting a pilot or procurement commitment before the relevant evidence gate is complete.
Next step
Use the institutional review form to share the decision context for an initial education, learning-technology, accessibility, privacy, or procurement conversation. General questions can also be sent to hello@synlecto.com.
Start an institutional conversationDeployment-specific legal contacts, contract schedules, and detailed support targets are handled during university review rather than published as blanket public commitments.
Public-safe review bundles can be prepared on request for first conversation, specialist review, or a later stage-gated evaluation without exposing internal-draft material.