Who This Is For
One platform. Three conversations.
Stackle serves learning designers, educational managers, and institutional leaders - each with a different question, each finding a different answer on this page.
How do I build evidence collection into courses I'm already running?
Stackle activities embed directly into existing Canvas and Brightspace pages. There is nothing to rebuild and no parallel system to maintain. The Activity Builder gives educators a flexible set of evidence collection types - from a single locked response to a semester-long journal - that sit inline within course content from day one.
For Learning Designers & Educators
How do I get consistent evidence collection across a department - without rebuilding every course?
Stackle's template system and institutional-level configuration mean evidence collection can be standardised across programs and disciplines without removing educator autonomy. Activity types can be renamed, restyled, and configured once at the institutional level - and that configuration propagates across every course automatically.
For Managers & Directors of Learning
What does evidence infrastructure actually look like at institutional scale?
The architecture that supports a single-course pilot is the same architecture that supports institution-wide deployment. Cohort management, Canvas Sections integration, role-based access, and Excel evidence reporting are available from day one - not as an enterprise upgrade. The University of Newcastle expanded from three courses to sixteen across six departments in under two months, with no additional systems for students to navigate.
For Institutional & Executive Leaders
Evidence Integrity
The version trail doesn't detect fabrication. It makes authentic engagement visible by design.
Every time a student saves a response, Stackle creates a new timestamped version. Not an overwrite - a new record. The complete history of every revision is stored, accessible, and comparable across the full length of a course.
A coherent development arc across multiple versions, captured over weeks, is extremely difficult to generate artificially. A polished submission with no revision history is a signal worth examining. The trail doesn't catch dishonesty - it makes authentic engagement structurally visible.
Evidence Captured Across
Analytics
The right level of detail,
for the question you're asking.
From a course-wide engagement overview to a single student's revision history - Stackle gives educators and institutional leaders visibility at every level, without opening individual records.
Enterprise
Built for the institution,
not just the course.
Stackle is designed to be deployed once and managed by the people already responsible for Canvas - without a dedicated support team, without a parallel system, and without rebuilding anything that already works.
Running the same course across multiple semesters - without losing what came before.
When a new semester begins, historical evidence from previous cohorts stays intact. Educators switch between offerings to compare engagement across semesters, and previous cohorts are archived with their complete evidence records preserved. One course structure, many offerings, nothing lost.
3 cohorts · 1 active
Every educator sees their students. Nobody sees more than they should.
In a large deployment, appropriate access isn't a preference - it's the condition under which teaching staff will actually use the system. Canvas Sections integration means every evidence view filters automatically to the students each educator is responsible for. Tutorial groups, campuses, and cohort subsets are all managed through the Canvas infrastructure already in place - no separate configuration required in Stackle.
ACTIVE SECTION FILTER
16 students in view
A new staff member added to Canvas is ready in Stackle immediately. Someone who leaves takes nothing with them.
Access roles sync directly from Canvas. When an educator is added to a course, their Stackle access is ready without a separate provisioning step. When they leave, access is revoked automatically. Because Stackle activities belong to the course rather than the individual who created them, there is no content ownership problem when staff change - no stranded activities, no access requests, no support burden for IT.
Synced from Canvas · Updated 2 min ago
Audit-ready evidence exports at any level, at any point in the semester.
Evidence can be exported at course level, section level, individual activity, single student, or individual response - as a complete Excel export containing raw response data, not summaries. Because exports can be generated at any point across the semester, institutions build a longitudinal compliance record progressively rather than compiling evidence retrospectively before a review. Every export is stored for historical access and can be regenerated at any time.
EXPORT LEVEL
Delivered by email · Stored for historical access
Customisation
Stackle doesn't impose a framework. It implements yours.
Every institution has its own language for learning. What Stackle calls a “Quick Reflect” might be a “Clinical Observation” in a nursing program, a “Knowledge Check” in law, or a “Module Journal” in psychology. That name - the one students see when they engage and educators see when they build - is entirely within the institution's control. The evidence infrastructure underneath stays consistent. The framing is always yours.
The same applies to the visual experience. Colours, icons, borders, spacing, and activity styling are all configurable at the institutional level. A configuration change propagates across every activity, every course, and every student view institution-wide - immediately, without rebuilding anything.
The result is that students don't experience Stackle as a separate system. They experience a coherent learning environment - one that looks, feels, and responds like the Canvas environment their institution has built. The infrastructure stays invisible. The learning stays central.
Same infrastructure. Different institutions.
See what institutional-scale evidence looks like in practice.
Thirty minutes with Sean. He will show you the analytics hierarchy, the version comparison system, the enterprise configuration options, and how institutions like Newcastle and Melbourne have deployed Stackle across departments - tailored to your programs, your disciplines, and your compliance context.
Book a DemoRead the Newcastle case study →