A LEARNING VISIBILITY & CREDENTIALING WORKSHOP MODULE
Projects, Teams & Work-Based Learning: Make Real Contributions Visible
Some of the most consequential learning happens outside a conventional assignment or individual assessment.
Learners contribute to projects, collaborate with teams, complete internships, participate in labs, serve communities, solve employer problems, and practice in clinical or field settings.
Yet the evidence produced through these experiences is often scattered across platforms, reports, supervisor observations, team deliverables, and informal feedback.
The experience may be powerful while the record of what each learner actually contributed remains weak.
Workshop Module 8 — Projects, Teams & Work-Based Learning
Does this sound familiar?
The final deliverable hides individual contributions
A team produces a successful result, but instructors and employers cannot clearly see who performed which activities.
Project evidence disappears after the course
Presentations, prototypes, reports, research, and client work remain inside disconnected learning or collaboration platforms.
Supervisor feedback is difficult to reuse
Internship, clinical, field, or employer evaluations do not connect to the learner’s broader record.
Participation substitutes for evidence
Completion or attendance confirms an experience occurred without showing the responsibilities, capabilities, or outcomes involved.
Teamwork is reduced to a generic skill
Collaboration appears as a broad claim rather than evidence of communication, coordination, leadership, or shared delivery.
Learners struggle to explain what they did
People leave meaningful experiences with a course title or résumé bullet but little structured evidence they can carry forward.
What is work-based learning evidence?
Work-based learning evidence helps explain what a learner did, contributed, demonstrated, produced, or learned through authentic work or work-like experiences.
Those experiences may include individual and team projects, internships, apprenticeships, clinical and field placements, research, laboratories, capstones, service learning, employer-sponsored challenges, simulations, practicums, student employment, entrepreneurship, and community-based work.
Useful evidence goes beyond confirming that the learner participated. It connects the experience to responsibilities, activities, deliverables, capabilities, feedback, outcomes, and the conditions under which the work occurred.
The purpose is not to record every action or convert all learning into a score. It is to preserve enough reviewed context for authorized people to understand what the experience demonstrates.
The problem is not a lack of experience. It is the loss of evidence between experience and recognition.
Learning organizations already create meaningful projects and work-based opportunities. The visibility problem develops when evidence remains attached only to the event, course, platform, or team rather than becoming part of a connected learning record.
- The purpose and operating environment
- The learner’s responsibilities
- The activities the learner performed
- The people or teams involved
- The tools, systems, or methods used
- The deliverables or outcomes produced
- The capabilities demonstrated or developed
- The feedback or review completed
- The evidence supporting each claim
- The recognition that may be appropriate
Without those connections, a rich experience may be represented by little more than a title, completion date, grade, or supervisor signature.
See the complete experience—not just the final deliverable.
Purpose and Context
- Project objective
- Employer or community need
- Course or program connection
- Operating environment
- Constraints and expectations
Responsibilities and Activities
- Assigned responsibilities
- Work performed
- Decisions made
- Problems addressed
- Changes in responsibility
Team and Relationships
- Team structure
- Collaborative roles
- Supervisors and mentors
- Clients and stakeholders
- Interdependent work
Evidence and Outcomes
- Reports and presentations
- Designs and prototypes
- Research and analysis
- Feedback and observations
- Results and impact
Capabilities and Recognition
- Technical capabilities
- Human capabilities
- Knowledge applied
- Credentials or credit
- Portable evidence
A work-based experience becomes more visible when its context, responsibilities, relationships, evidence, outcomes, and recognition can be understood together.
How meaningful work becomes invisible
STAGE 1
Learners enter authentic experiences
Projects, placements, labs, clinics, and employer-connected activities create opportunities to practice and contribute.
STAGE 2
Work happens across multiple environments
Evidence accumulates in learning platforms, project systems, shared drives, evaluation forms, portfolios, and workplace tools.
STAGE 3
The experience is compressed
The organization records a grade, completion status, credit, evaluation, or participation marker.
STAGE 4
The underlying evidence is lost
Learners must later reconstruct what they did, while educators and employers cannot easily examine the original context or reviewed contribution.
Participation tells us where someone was. Evidence helps explain what they did.
Participation can confirm that a learner completed an internship, joined a project, attended a lab, or fulfilled required clinical hours. It does not by itself explain the responsibilities, contribution, evidence, or capabilities involved.
A useful work-based learning record should help answer:
Was the learner observing, assisting, coordinating, analyzing, designing, leading, presenting, or making decisions?
Which tasks, methods, tools, interactions, and problem-solving activities were actually involved?
Which parts of the deliverable, team process, client result, or organizational outcome can be connected to the learner?
Did an instructor, supervisor, mentor, client, peer, or qualified reviewer examine the work or observe the activity?
What technical, human, leadership, communication, or contextual capabilities did the experience allow the learner to demonstrate?
Which evidence is appropriate for a profile, portfolio, credential, comprehensive learner record, or future opportunity?
What makes work-based learning evidence responsible and useful?
Purposeful
Information is intentionally connected to a defined learning, recognition, or decision need.
Contextual
Evidence preserves the experience, responsibility, conditions, and relationships required to interpret it.
Reviewed
Claims distinguish learner-provided context from work examined by an appropriate instructor, supervisor, mentor, client, or reviewer.
Permission-aware
Collection, access, sharing, retention, and recognition follow a legitimate purpose and appropriate authorization.
Human-interpreted
Qualified people remain responsible for examining evidence and determining what it can support.
Portable when appropriate
Reviewed evidence can survive the course, placement, platform, or project when carrying it forward serves the learner.
The shared outcome
- Project objective
- Operating context
- Team composition
- Shared milestones
- Collective deliverables
- Stakeholder feedback
- Results or impact
- Lessons identified by the team
The team-level record preserves the context and result created together.
The learner’s contribution
- Assigned and evolving responsibilities
- Activities personally performed
- Decisions or recommendations made
- Deliverables created or supported
- Collaboration with other contributors
- Challenges addressed
- Feedback received
- Capabilities demonstrated
The individual record connects reviewed contribution to the shared work.
A shared result should not erase the people who created it.
The final result belongs to the team, but the responsibilities, activities, decisions, learning, and contributions within that result may differ significantly.
- Preserve the shared objective and outcome
- Clarify individual and interdependent responsibilities
- Connect artifacts to the work they support
- Use multiple sources when contribution is consequential
- Avoid artificial contribution percentages
- Keep interpretation with responsible human reviewers
Making work visible does not require recording everything.
Messages, document histories, platform events, task records, meeting transcripts, location data, and system usage may appear to provide an objective account of contribution. More data does not automatically create better evidence.
- Collect evidence for a defined learning or recognition purpose
- Distinguish reviewed contribution from operational exhaust
- Keep private coaching notes and draft reflections bounded
- Do not treat system activity as a complete account of work
- Apply stronger review when evidence may influence a consequential decision
- Protect confidential, proprietary, regulated, or sensitive material
Make real work count
Connect responsibilities, contributions, deliverables, feedback, capabilities, and outcomes without reducing meaningful work to attendance or activity data.
THE MATCHING WORKSHOP MODULE
Module 8: Projects, Teams & Work-Based Learning
This module helps learning organizations make responsibilities, contributions, capabilities, and outcomes visible within projects, internships, labs, clinical experiences, and employer-connected learning.
Participants examine how evidence is currently created, reviewed, stored, interpreted, and carried forward. The goal is not to capture every learner action. It is to identify the evidence that matters, preserve the context required to understand it, and create a credible path from experience to recognition.
This module helps your team:
- Map projects and work-based experiences to learning outcomes
- Clarify individual and shared responsibilities
- Identify meaningful activities and contributions
- Connect deliverables to the people and teams that produced them
- Structure supervisor, instructor, mentor, and stakeholder feedback
- Distinguish participation from demonstrated capability
- Identify evidence that should remain private or developmental
- Clarify what may support credit, credentials, or profiles
- Reduce evidence loss across platforms and transitions
- Develop a bounded work-based learning evidence model
What should happen to each source of project and work-based evidence?
Not every activity, artifact, observation, or piece of feedback should become part of a permanent learner record. The response should follow purpose, relevance, review, permission, and consequence.
Capture
Preserve meaningful evidence that is currently lost when the experience ends.
Clarify
Add missing responsibility, contribution, operating context, or connection to the outcome.
Connect
Link project, team, course, employer, feedback, capability, and learner records.
Review
Establish credible confirmation by an appropriate instructor, supervisor, mentor, client, or reviewer.
Recognize
Carry sufficiently relevant and credible evidence into an appropriate profile, portfolio, credential, or credit decision.
Protect
Keep developmental, sensitive, unrelated, or unreviewed material bounded or private.
These categories organize evidence decisions. They do not automatically determine credit, competency, credential eligibility, employment suitability, or learner potential.
What should a work-based learning review examine?
The experience
What was the purpose, setting, duration, structure, and expected outcome of the project or placement?
The responsibility
What was the learner expected to own, support, observe, decide, create, or deliver?
The contribution
What did the learner actually do, and how did that work connect to the shared result?
The evidence
Which artifacts, observations, demonstrations, feedback, or outcomes support the account?
The review
Who examined the evidence, what were they qualified to confirm, and what remains self-reported or unresolved?
The recognition
What should become visible in a profile, portfolio, credential, learner record, or future decision?
From real work to connected learning evidence
Long term, TalentSync EDU could help learning organizations structure shared context around projects, teams, courses, programs, and work-based experiences. With appropriate review and learner participation, relevant evidence could connect to a learner’s Talent Tree and support purpose-built profiles in TalentPass.
Specific workflows and available features depend on implementation stage, institutional configuration, evidence sources, permissions, Launch Partnerships, and the selected use case.
STEP 1
Clarify the experience
Define the project, placement, objective, operating context, and learning or recognition purpose.
STEP 2
Structure shared responsibilities
Connect the team, roles, expected activities, interdependencies, deliverables, and relevant courses or programs.
STEP 3
Connect work and evidence
Bring together appropriate artifacts, observations, feedback, outcomes, and learner-provided context.
STEP 4
Distinguish evidence types
Preserve differences among participation, system activity, self-report, review, verification, and formal assessment.
STEP 5
Review contribution responsibly
Use qualified human judgment to examine what the evidence supports and what remains unresolved.
STEP 6
Carry appropriate evidence forward
Connect approved evidence to profiles, portfolios, credentials, learner records, or future opportunities.
TalentSync EDU and TalentPass should help structure the transition from experience to reviewed evidence. They should not be positioned as surveillance systems or automated judges of individual contribution.
- Create shared project or experience context
- Connect responsibilities, activities, teams, and deliverables
- Preserve instructor, supervisor, mentor, or stakeholder review
- Connect approved evidence to the learner’s Talent Tree
- Support purpose-built learning, transfer, and employment profiles
- Keep learner-controlled evidence distinct from institutional access
WHY TALENTPASS MATTERS
Let meaningful experience become portable evidence.
Learners often have to translate complex projects, internships, clinical experiences, and team contributions into a résumé bullet or brief application response. TalentPass is designed to help an individual build a more connected view of experience, responsibilities, activities, skills, deliverables, credentials, accomplishment stories, and appropriate confirmation.
The learner controls their TalentPass information and chooses when it is shared. The objective is to help useful, reviewed evidence remain available after the course, project, placement, or platform ends.
PRODUCT AND DECISION BOUNDARIES
Connected evidence supports judgment. It does not replace it.
TalentSync EDU and TalentPass should not be presented as:
- Automatically determining individual contribution
- Monitoring every learner or workplace activity
- Producing definitive teamwork scores
- Calculating ownership from system activity alone
- Proving that every artifact was created independently
- Awarding credit or credentials automatically
- Predicting employment success
- Determining professional readiness without qualified review
- Replacing instructors, supervisors, assessors, or credentialing bodies
- Making legal, regulatory, accreditation, or licensing determinations
- Converting private coaching information into formal evidence
- Providing the sole basis for a consequential decision
The product connection described here includes capabilities TalentSync EDU is designed to grow into through Launch Partnerships and funded implementation work. The workshop can still clarify evidence needs, responsibilities, boundaries, and the operating model independently of future product adoption.
Privacy, accessibility, student records, cybersecurity, accreditation, labor, intellectual-property, and other questions may require qualified specialist review. TalentPass is not designed for use by minors.
What to bring into the conversation
You do not need a complete map of every project, internship, laboratory, clinic, or employer partnership. We begin with a bounded set of experiences connected to the decision established through Learning Visibility Direction.
Useful inputs may include:
- Project and capstone descriptions
- Internship or apprenticeship requirements
- Clinical, field, laboratory, or practicum structures
- Employer-sponsored challenges
- Team assignments and collaboration expectations
- Learning outcomes and competency frameworks
- Assessment rubrics and evaluation forms
- Learner reflection prompts
- Example deliverables and portfolio artifacts
- Course, program, and placement records
- Existing badges, credentials, credit, or recognition practices
- Relevant LMS, portfolio, project, or workplace systems
- Consent, privacy, access, and retention practices
- Known concerns about attribution, evidence quality, or fairness
The required Learning Visibility Direction module establishes the outcome, evidence boundary, affected experience, and decision this module should support.
What this module can help clarify
Which experiences need stronger evidence
Identify the projects, placements, teams, labs, clinics, or employer-connected activities where meaningful learning is difficult to see.
What individual contribution means
Clarify the responsibilities, activities, deliverables, decisions, and relationships that help explain a learner’s role.
Which evidence can be trusted and reused
Distinguish reviewed artifacts and observations from participation records, unverified claims, private notes, and operational data.
How evidence should be carried forward
Define appropriate connections to learner profiles, portfolios, credentials, comprehensive learner records, credit, or future opportunities.
Final outputs depend on the modules selected and the learning-visibility decision established through the workshop’s required Learning Visibility Direction module.
Where might the work lead next?
Project and work-based evidence often reveals connected problems in evidence architecture, learner profiles, institutional visibility, credentials, and employer relationships.
Connected Learning Evidence & Context
Connect activities, experiences, skills, credentials, and outcomes without stripping away the context that gives them meaning.
Course, Cohort & Program Visibility
Understand what individual learner evidence reveals about courses, cohorts, programs, and institutional outcomes.
Purpose-Built Learner Profiles
Turn one connected body of evidence into distinct profiles for prior learning, progress, projects, transfer, and employment.
Credentials & Comprehensive Learner Records
Determine when reviewed evidence should support a credential, transcript, comprehensive learner record, or another formal recognition.
Frequently asked questions
Questions learning organizations ask about project, team, and work-based learning evidence.
Work-based learning includes experiences in which learners develop or demonstrate capabilities through authentic work, workplace exposure, or work-like activities. Examples include internships, apprenticeships, clinical placements, field experiences, employer projects, service learning, practicums, simulations, student employment, research, laboratories, studios, and capstones.
Work-based learning evidence helps explain what a learner did, contributed, demonstrated, produced, or learned during an authentic work or project experience. Useful evidence preserves enough context to explain the learner’s responsibility and the conditions under which the work occurred.
Not necessarily. Completion confirms participation and may satisfy an important program requirement, but it does not automatically explain the work performed, level of responsibility, quality, or capabilities demonstrated.
Clarify the shared objective, team structure, individual responsibilities, activities performed, deliverables produced, decisions made, and evidence available. Reflections, project records, observations, feedback, and artifacts may contribute different perspectives.
Usually not. A percentage can create an appearance of precision without explaining the responsibilities, activities, decisions, or evidence involved. A structured account of contribution is often more useful.
Yes, when its purpose and limitations are clear. Peer feedback should be structured responsibly and should not automatically become a definitive judgment, public record, or high-stakes score.
Supervisor evaluations can provide valuable context about responsibilities, performance, and demonstrated capability. The organization should clarify what the supervisor observed, what they were qualified to confirm, and how the information may be used.
Reflection can help learners explain decisions, challenges, growth, contributions, and interpretation. It may remain self-reported unless connected to artifacts, observations, feedback, or reviewed evidence, and some reflection should remain private or developmental.
No. Retention should follow purpose, value, permission, sensitivity, ownership, accessibility, and institutional requirements. A representative artifact or structured description may be more appropriate than retaining the complete work.
Confidential, proprietary, regulated, or sensitive material should not be copied into a learner record without authorization. Context, responsibilities, activities, capabilities, and confirmation may sometimes be documented without exposing protected content.
Platform activity can provide supporting evidence, but it rarely explains the complete contribution. System signals should be interpreted with other evidence and responsible human judgment.
Potentially, but the evidence does not make that determination automatically. The institution or authorized credentialing body must decide whether it meets applicable standards, policies, and assessment requirements.
Long term, TalentSync EDU could help institutions structure shared profiles for projects, teams, placements, courses, programs, and employer-connected experiences. Relevant reviewed evidence could then connect to learner-controlled TalentPass records and purpose-built profiles.
No. Institutional access should follow authorized purpose, applicable policies, relevant evidence sources, learner choices, and agreed sharing conditions.
Every engagement begins with the required Learning Visibility Direction module. Projects, Teams & Work-Based Learning may then be combined with Connected Learning Evidence & Context, Course, Cohort & Program Visibility, Purpose-Built Learner Profiles, Credentials & Comprehensive Learner Records, or Learning Evidence Governance.
MAKE REAL WORK COUNT
Turn projects and work-based experiences into evidence learners can carry forward.
Connect responsibilities, contributions, deliverables, feedback, capabilities, and outcomes—without reducing meaningful work to attendance, activity data, or a generic teamwork score.
This module is part of Gobekli’s configurable Learning Visibility & Credentialing Workshop.