Skip to content

Projects

How to write a student project brief

Write a student project brief with a clear outcome, defined roles, realistic availability, and a finish line. Use the fictional example to plan your own post.

By UniSphere Connect

Explain what the team will make

A student project brief gives someone enough information to decide whether to join. Start with a specific outcome and audience, then explain what already exists and what is still undecided. A smaller finishable project is easier to assign than an open-ended ambition.

In UniSphere, use the title and summary for the main idea, and the fuller description for the plan. The summary allows up to 200 characters. State what is outside the scope: for example, a clickable prototype does not mean launching a live service.

Define roles and the time the work needs

Each role should name a contribution rather than just a subject someone likes. Include responsibilities, relevant skills, and the number of available spots. Say what experience is needed and what guidance a beginner can realistically expect.

Choose the expected commitment and use the description to explain your own estimate of hours, meeting arrangements, and any important dates. Do not assume a commitment label guarantees the same schedule for every team. Leave room to agree on availability before work begins.

Fictional example: Campus Reuse project brief

This invented brief illustrates the Campus Reuse Demo. It is not an active recruitment post, a completed student project, or a university initiative. The times and roles below are an example plan.

Title: Campus Reuse — a student exchange prototype

Summary: Design and test a simple way for students to offer reusable supplies to one another.

Goal and scope: Explore a clearer listing and collection flow. Finish with a clickable prototype, a short usability research summary, and a handoff document. Building a live marketplace, handling payments, and storing real listings are outside this project.

Starting point: An idea and a rough description of the flow. The team still needs to agree on research questions, create the prototype, and decide how to collect voluntary feedback.

Availability: Example estimate of 3–5 hours per week, with remote document reviews and one weekly planning meeting. Agree on the meeting time and milestone dates together before starting.

Product designer — one example spot: Sketch the listing flow, build the clickable prototype, and revise it after testing. Relevant skills: interaction design and prototyping.

Student researcher — one example spot: Prepare questions, organize voluntary feedback, and summarize usability findings. Relevant skills: interviewing and research synthesis. A beginner could help organize notes if the team agrees who will guide and review that work.

First milestone: Agree on the listing flow and research questions, then assign the first prototype and feedback tasks to named teammates.

Check the brief before publishing

Save a draft while you work through the details. UniSphere publishing requires a summary and at least one role; meeting that minimum does not replace a clear plan.

  1. Read the summary without the description. It should say what the project will produce.
  2. Check that every role has a distinct responsibility, realistic skill expectations, and an accurate number of spots.
  3. Make the expected effort, meeting needs, and known dates easy to find. Identify what the team still has to decide.
  4. Remove private student information and material you do not have permission to share. Use only claims about the project that you can support.
  5. Review the post, publish when ready, and read incoming role requests before accepting teammates.

Plan for a truthful final project record

Use the brief as a starting agreement, then record changes and milestones in project updates. At the end, explain what the team actually completed, including any part of the original plan that changed or remains unfinished.

Before marking the project completed, the owner should check the team roster and recorded roles. Completion freezes the roster and preserves the project on member profiles in the student community. UniSphere does not independently verify contributions, certify skills, or turn the record into a public portfolio. For an incorrect frozen record or a contribution dispute, contact Student support.

Put the guide into practice.

Explore real projects or contact support if you still need help.