ProfilEd for programme leaders

Run one pilot before you scale the workflow.

Programme leaders use ProfilEd to run a bounded pilot: one capability, one practice mode, one reviewer, then keep, change, or stop.

Built for: Programme leaders

Evidence links

Claim boundaries

  • Programme leaders use ProfilEd for a bounded pilot: one capability, one practice mode, one reviewer. They inspect fit, then keep, change, or stop. The product does not certify programme competence.
  • A first ProfilEd implementation is one course or cohort, not a platform-wide rollout.
  • Programme leaders inspect attempts, reviewer load, and workflow fit.
  • The record is practice evidence, not certified competence.

Common questions

How large should a first pilot be?

One course, cohort, or module. One capability. One reviewer. Expand only after you inspect the record.

Does a successful pilot prove the programme?

No. It shows whether the workflow fits. Competence claims stay with your assessment process.

Do we need every ProfilEd capability?

No. Start with the smallest mode that matches the moment.

Who designs the activity?

Faculty and learning designers. This page is the operating decision around that design.

Does ProfilEd replace the LMS?

No. Delivery and records stay where they are.

The job

You need to know whether the workflow fits before you expand it.

Programme leaders decide whether a new practice layer belongs in a course, capstone, or cohort. Curriculum Graph names the capability. Faculty attach Story Quests, AI Case Lab, or Socratic AI Interviews. You inspect operating fit: did learners attempt it, is the record usable, can reviewers stand the load.

Faculty and Learning Designers own the activity design. This page is the keep, change, or stop decision. The record is practice evidence. It is not certified competence.

What a pilot must make visible

Four questions the first cohort should answer.

  • One capability

    Write the decision or explanation the cohort currently cannot defend.

  • One practice surface

    Do not attach every product in week one.

  • Named person

    Who reads attempts, and what they are allowed to conclude.

  • Keep, change, or stop

    Judge evidence quality and reviewer effort, not attendance alone.

Pilot path

Select, define, run, decide.

  • Select

    Choose one course, cohort, capstone, or module.

  • Define

    Agree the capability, mode, reviewer, and evidence rule.

  • Run

    Learners practise. Reviewers inspect a sample.

  • Decide

    Keep the workflow, change the mode, or stop.

What you inspect

Operating evidence, not a competence score.

  • Did they do the work?

    Participation in the chosen practice mode.

  • Can a reviewer use them?

    Recommendations, follow-ups, and revisions that are actually readable.

  • Can faculty stand it?

    Reviewer time against the value of the sample.

  • Does it sit beside delivery?

    LMS, timetable, and assessment stay in place.

What it leaves

A programme decision with inspectable inputs.

  • Pilot record

    What learners attempted and what reviewers could use.

  • Boundary

    Who saw the evidence, and for what purpose.

  • Next call

    Expand, redesign, or stop.

  • A pilot is not proof of programme competence.

    ProfilEd records practice in a bounded scope. It does not certify competence, replace institutional assessment, or treat the record as recruiter-auditable proof.

Continue

See the path product, the designer view, and the method.

  • Curriculum Graph

    Map a goal into capabilities and the next practice action.

  • Faculty and Learning Designers

    How an activity is attached to a practice mode.

  • ProfilEd methodology

    Practice, challenge, revision, and human review.

Questions

Short answers before a first cohort.

Next step

Bring the course where judgement currently disappears.

Plan a focused pilot