Career → brief → submit with evidence — finished with proof on your trail.
Do work, prove skills — briefs that protect your work and your words.
Project Briefs gives you structured opportunities to practise by producing work that demonstrates relevant skills. A strong brief defines a realistic problem, deliverables, constraints and evaluation criteria — while protecting intellectual property, privacy and your right to describe your contribution accurately.
Choose a purposeful project
Briefs are organised by career, skill, difficulty, domain, estimated effort and expected output — each explaining which capability it practises and what prior knowledge may help. Different project scales let you begin with a small exercise and progress to more complex, integrated work; the rubric-generated briefs here come from the career's own skill record, labelled as such.
Understand the brief
Context, problem, audience, objective, deliverables, constraints, assumptions, resources and completion criteria are stated up front. A brief is identified as fictional, educational, open-data based, community supplied or employer sponsored — simulated business data and fictional stakeholders are never presented as real, and any external assets, licences or permissions you must respect are named.
Plan and execute
Break the work into discovery, planning, production, testing, review and presentation — with optional checkpoints and suggested tools, and no single correct solution prescribed where multiple approaches are valid. Document decisions, trade-offs, sources, limitations and individual contributions, especially in team projects.
Evaluate against a rubric
Assessment criteria are published before work begins — problem framing, method, technical quality, usability, communication, responsible practice and reflection as the brief requires. Feedback refers to observable evidence and offers next steps; AI-generated evaluation is labelled, explainable and treated as practice feedback, never formal accreditation.
Publish evidence safely
Create a project summary, selected artefacts, skills demonstrated, tools used and lessons learned — redacting personal, confidential or licensed material. Public sharing stays optional, with ownership and permissions confirmed; individual versus team contributions are labelled and completed work is distinguished from prototypes.
Connect to career pathways
Project outputs map to skills, career plans, resume evidence and interview preparation where you consent — helping you explain the problem, process, result and limitations in your own words. Completing a brief establishes neither professional proficiency nor guaranteed employer recognition.
The workspace
The brief catalogue, the brief detail with its rubric, your submission with an evidence link, and the portfolio handoff — accessible, mobile-friendly, with privacy and error states handled. Select a project brief, produce a meaningful artefact and document the skills your work demonstrates.
How this works.
Pick the career you're aiming at — briefs are generated from that career's own skill rubric, with the provenance stated on every card.
Do the work outside DISHA — code, deck, demo, essay — wherever you keep your workspace.
Submit the title and an evidence link. It joins your evidence trail and becomes portfolio material in the Resume Studio.
Stated plainly — what this doesn't do
- — Briefs are generated from the career's own rubric, not set by employers — treat them as serious practice, not a pipeline.
- — DISHA does not verify evidence links; reviewers and mentors judge the work itself.
- — There is no marketplace payment or bidding — this is a brief-and-evidence exchange, not gig work.
Questions people ask.
Who wrote these briefs?
They're generated from the career's skill rubric — the same rubric that powers the Practice Lab — and every card says so. Nothing pretends to be an employer brief.
Where do my submissions go?
Into your own evidence trail, listed on this page. From there they feed the Resume & Evidence studio when you build it.
Can I submit the same brief twice?
Yes — revisions are part of real work. Submit again with the improved title and evidence link.
Skills you can't prove are rumours.
Pick a brief, do the work, keep the evidence link. A month of that beats a month of browsing.
Briefs that read like real work
Every project brief mirrors an actual task a practitioner handed over — scoped, honest, and assessable.
