Welcome to Ascend, Lebra's professional development and employee evaluation management system. Whether you're setting up evaluations for the first time or looking to understand how all the pieces fit together, this guide will walk you through everything you need to know.
What is Ascend?
Ascend is Lebra's solution for managing employee evaluations and professional growth in K-12 school districts. It brings together everything you need to:
Conduct classroom observations — formal observations scored against your framework, informal observations, and quick walkthroughs
Create professional development plans — help staff set and track growth goals
Generate summative reports — synthesize a year's worth of evidence into a final evaluation
Enable self-reflection — let employees assess their own performance against standards
Track evaluation timelines — make sure every required evaluation happens on schedule
Think of Ascend as your evaluation command center. Instead of juggling spreadsheets, paper forms, and email chains, everything lives in one connected system — and staff complete their part in the Staff Portal.
Understanding the Building Blocks
Before diving into setup, let's make sure we're speaking the same language. Ascend has several interconnected concepts, and understanding how they relate to each other is key to using the system effectively.
Roles: The Foundation of Everything
What are roles? Roles represent the different job positions in your district — Teacher, Principal, Counselor, Instructional Coach, Custodian, and so on. In Ascend, roles are the foundation because different positions require completely different evaluation criteria.
Why does this matter? The indicators you'd use to evaluate a 3rd-grade teacher are very different from those you'd use for a school counselor or building principal. A teacher might be evaluated on classroom management and student engagement, while a counselor is evaluated on crisis intervention and student support services.
The key insight: Each role gets its own complete evaluation framework — its own domains, its own standards, and its own scoring weights. Every person needs a framework role before evaluation documents can be created for them.
One person, up to two roles: Some staff genuinely do two jobs — a teacher who also coaches, a counselor who teaches a class. A person can hold a primary framework role and an optional secondary one, and each role runs its own complete evaluation cycle: its own pathway, its own evaluator, and its own evaluation documents, each against that role's framework. See Staff Who Hold Two Framework Roles for the full model.
Domains: Organizing Your Evaluation Areas
What are domains? Domains are the major categories that group your evaluation criteria. Think of them as the "chapters" in your evaluation framework.
Example for a Teacher role:
Domain 1: Planning and Preparation
Domain 2: Classroom Environment
Domain 3: Instruction
Domain 4: Professional Responsibilities
Example for a Counselor role:
Domain 1: Student Support Services
Domain 2: Crisis Prevention and Intervention
Domain 3: Academic and Career Planning
Domain 4: Collaboration and Advocacy
The relationship: Each domain belongs to ONE specific role. When you create domains, you're building out the evaluation framework for that particular position.
Components: The Specific "What" You're Evaluating
What are components? Components are similar to what you may call "standards" or "indicators"; these are the specific competencies, skills, or behaviors you're evaluating within each domain.
How they're numbered: Components follow a numbering system that connects them to their parent domain:
Component 1.1, 1.2, 1.3 belong to Domain 1
Component 2.1, 2.2 belong to Domain 2
And so on...
Example for Domain 1 (Planning and Preparation):
Component 1.1: Knowledge of Content and Pedagogy
Component 1.2: Knowledge of Students
Component 1.3: Setting Instructional Outcomes
Component 1.4: Designing Coherent Instruction
Component 1.5: Designing Student Assessments
Rating Scale and Rubric Descriptions: How You Score Performance
The rating scale defines your levels of performance — for example, Ineffective, Developing, Effective, and Highly Effective. It's shared by every role in your district, and it's where score ranges are set.
Rubric descriptions are the words for each level on each component — what "Effective" looks like for Component 1.2, for example. They're written per component, so the chain is:
Role → Domains → Components → Rubric descriptions for each rating level
Evaluators and staff see these descriptions in the Select Rating window whenever they score a component. How scores roll up into an overall rating is covered in Setting Up Scoring in Ascend.
The Evaluation Documents
Now that you understand the building blocks, let's look at the actual evaluation documents you'll create and manage in Ascend. Each one has a row of status steps on the employee's page, so you can see where it stands.
Note: Every evaluation document is recorded under a specific framework role and uses that role's framework. For staff who hold two roles, each role's documents are separate — and each document permanently keeps the role it was conducted under, even if the person's role changes later.
Observations: Capturing What You See
Formal Observations:
Full, structured evaluation against the role's domains and components
Can include scoring (if enabled for your organization)
The employee reflects and signs (or just signs, if your district doesn't require a reflection)
Workflow: Draft → Staff Feedback Requested → Signed by Employee → Completed
Informal Observations:
Quick feedback or check-in notes
No signature required; you choose whether to email it to the employee
Workflow: Draft → Completed → Shared with Employee
What's captured in a formal observation: general feedback, comments and scores per component, action steps for growth, optional transcription of the staff member's own words, and file attachments.
Observation Assignments: Who Evaluates Whom
Before you can create observations, you define who is assigned to evaluate whom. On the Evaluator Dashboard these are called observation assignments.
Observer: The administrator or evaluator conducting observations
Observed Person: The employee being evaluated
Framework Role: Which of the person's framework roles this evaluator covers. Evaluators are assigned per role — for staff with one role this is automatic; for staff with two roles, you pick the role each evaluator is responsible for
Multiple evaluators: A person can have more than one evaluator in two ways:
Per role — a person who holds two framework roles has one evaluator per role, and they can be different people
Reviewers — beyond the evaluator, any number of additional reviewers can support the process (for example, an assistant principal doing informal check-ins). Reviewers are per person, not per role
To set how many observations each person needs and by when, use Pathways (below).
Summative Reports: The Big Picture Evaluation
What are summative reports? Summative reports are comprehensive, typically annual evaluations that bring all the evidence together into a final assessment.
What's included:
Key strengths demonstrated over the evaluation period
Areas of growth identified
Component-by-component scores with comments, and an Evaluation Score Summary
Linked evidence: observations, notes, in-person meetings, and recognitions
The workflow: Draft → Feedback Requested → Signed by Employee → Completed
AI assistance: Ascend can help draft summative content from the linked evidence. Evaluators review and edit everything before it's shared.
Self-Evaluations: Employee Self-Reflection
What are self-evaluations? Self-evaluations give employees the opportunity to assess their own performance against the standards. They encourage reflection, surface the employee's perspective, and set up growth conversations.
What employees provide:
Comments per domain and standard reflecting on their practice
Self-assigned ratings per standard
Artifacts and evidence (lesson plans, student work, certificates, etc.), with optional AI summaries
The workflow: Requested → Draft → Submitted. If the employee needs to change a submitted self-evaluation, they can request an edit and you can reopen it.
Self-evaluations are turned on for your district by Lebra.
PDPs (Professional Development Plans): Looking Forward
What are PDPs? PDPs are forward-looking documents where employees identify areas for growth and create action plans. While observations and summatives look at past performance, PDPs focus on future improvement.
What's included in a PDP:
Selected components: which standards they're targeting for growth
Professional growth goal and the action steps to reach it
Student achievement goal and its action steps (required in some districts)
Progress updates during the year, with artifacts tagged to the components they support
The workflow: Requested → Signed → Completed, then Requested Progress → Progress Submitted (and year-end steps in Idaho)
Customizing the name: If your district doesn't call it a "PDP," you can rename it under Settings → Ascend → General in the PDP naming convention section. Some districts call it:
Professional Growth Plan (PGP)
Individual Professional Learning Plan (IPLP)
Professional Learning Plan (PLP)
More Tools in Ascend
Depending on what your district uses, you'll also find:
Pathways — each role's milestones and due dates for the year, with automatic requests and reminders. See Pathways.
Walkthroughs — quick classroom visits against short look-for checklists your district writes, plus Walkthrough Analytics. See Walkthroughs.
In-Person Meetings — documented conversations you can attach to a summative. See Recording an In-Person Meeting.
Pre- and post-observation forms — your district's own forms, completed by staff around a visit. See Pre- and Post-Observation Forms.
Evaluator Dashboard and Analytics — progress by evaluator, building, and rating. See Tracking Evaluation Progress.
State Reporting — export your evaluation results in your state's format. See State Reporting.
Ready to set it up? Start with Setting Up Ascend: A Step-by-Step Guide.
