Describe the project and review needs. Makeform creates an editable project submission form for team details, questions, links, uploads, permissions, and routing.
Send project submissions to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the builder. The example structure is editable.
Audience
Students submitting individual or group capstone projects
Format
Course submission form with rubric-aligned questions
Prompt size
250 chars
Example form structure
Course submission form with rubric-aligned questions
Student, course section, and team members
Project title and 150-word abstract
Problem, methods, and results
Repository and working demo links
Final report and presentation
Suggested routing tags
Ready for review
Needs files
Late submission
Request a project URL and uploads so reviewers can open the build and retain the submitted files.
Step 1
Collect
team, project, links, and files
Step 2
Check
required assets and permissions are present
Step 3
Route
track, class, or reviewer gets the entry
Step 4
Review
one consistent submission per project
Why use a submission form
Email scatters files and context. A project submission form keeps each project and its evidence together.
Required questions capture the title, summary, track, links, and files. Helper text explains formats and access settings.
Consistent, rubric-aligned prompts help reviewers compare each project's problem, approach, outcome, and evidence.
Structured section, track, cohort, or category choices support sorting and reviewer notifications.
Built for different programs
Different projects need different evidence. Generate a close structure, then edit its labels and requirements.
Collect the student, section, team, reflection, report, presentation, repository, and demo.
Route by track and collect the pitch, technology, source, demo, screenshots, and setup notes.
Gather activities, outcomes, budget context, evidence, lessons, next steps, and sharing choices.
Gather descriptions, media, footprint, power, internet, accessibility, setup, and presentation times.
Submission workflow
Create the form, test it, and route complete entries to reviewers.
Describe submitters, review criteria, required artifacts, and class, category, cohort, or track routing.
Set categories, word limits, file instructions, and conditional questions for relevant submitters.
Submit realistic answers, links, and files. Check the prompts and open every asset before launch.
Share one link and route responses to Makeform, Google Sheets, Slack, or connected workflows.
Form vs email vs folder
Keep narrative answers, URLs, uploads, and team information attached to one entry.
Field guide
Six field groups cover identification, context, evidence, review, and sharing.
Submitter and team
Capture the primary contact and complete team consistently. Add course, section, cohort, or organization when relevant.
Project identity
A concise title, category, pitch, and abstract help reviewers scan and route entries.
Project narrative
Separate prompts for the problem, audience, approach, outcome, and lessons make answers easier to compare.
Links and files
Use separate URL and upload fields, with clear naming, format, access, and setup instructions.
Readiness checks
Ask participants to verify contributors, link permissions, final files, and your defined eligibility conditions.
Permissions and logistics
Offer clear sharing choices for text, names, images, and video. Add venue and accessibility questions for exhibits.
Related tools
Collect proposals, register participants, or evaluate entries around project intake.
Collect abstracts, authors, subjects, and presentation preferences.
Open toolRegister teams before project submission and judging.
Open toolCreate consistent scoring questions and reviewer comments.
Open toolCollect creative objectives, deliverables, assets, dates, and approvers.
Open toolFAQ
Practical answers for teachers, hackathon organizers, showcase teams, and program managers.
It collects a participant or team's project information and evidence in one response: identity, title, category, narrative, URLs, files, confirmations, and permissions.
Include the submitter, team, title, category, pitch, and abstract. Add rubric-aligned questions about the problem, audience, approach, outcome, and lessons. Request necessary links or files, then add access and completeness checks.
Yes. Add uploads for reports, decks, images, or archives and URL fields for repositories, demos, portfolios, or videos. Label them separately and explain formats, naming, permissions, and setup needs.
Collect the team, track, pitch, problem, solution, technologies, repository, demo, video, screenshots, and setup notes. Add confirmations based on your event rules, plus track routing and conditional questions where needed.
Mirror the rubric with separate prompts for the problem, methods, evidence, reflection, and contribution. Collect section and team as structured data, then attach the report or presentation to the same response.
Yes. Explain the planned showcase and offer separate choices for project text, creator names, screenshots, photos, and video. Review your program's wording and process before publishing.
Yes. Makeform provides unlimited free forms and responses for generating, editing, publishing, and collecting submissions. The paid option only removes the Makeform badge.
Responses reach the Makeform inbox with answers and uploads connected. You can send data to Google Sheets, notify Slack, or connect review steps through Zapier. Test the route before launch.
Replace scattered files with review-ready entries.
