Turn scattered comments like ‘please make a tutorial about this’ into useful, comparable briefs. Describe your audience and publishing workflow, and Makeform generates a tutorial request form for collecting the exact topic, learner goal, current skill level, format preference, reference material, and deadline your team needs to decide what to create next.
Route tutorial ideas to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose the scenario closest to your request queue, adjust its details, or send the prompt to the Makeform builder. Each structure is a practical starting point, not a live AI result.
Audience
Customers requesting product how-to content
Format
Prioritized product tutorial brief
Prompt size
464 chars
Example form structure
Prioritized product tutorial brief
Which product area or feature is this about?
What are you trying to accomplish?
Where did you get stuck?
Add a screenshot or example
How soon would this help?
Suggested routing tags
New request
Needs clarification
Planned tutorial
Ask what the requester wants to accomplish, not only what topic they want covered. ‘Build a pivot table from sales exports’ gives a creator a testable finish line; ‘spreadsheets’ does not.
Step 1
Request
topic, obstacle, audience, and outcome
Step 2
Clarify
references, skill level, and missing context
Step 3
Prioritize
reach, urgency, effort, and content fit
Step 4
Close the loop
publish, share, and update the requester
Better requests
A chat message may name a broad subject, but it rarely explains the learner’s starting point, failed attempt, or desired result. A structured tutorial request form captures those signals consistently, so a training team or creator can compare ideas without another long clarification thread.
Pair a topic field with ‘What are you trying to do?’ and ‘Where are you stuck?’ The answers separate a request for a basic overview from a narrow troubleshooting walkthrough, even when both requesters choose the same subject.
Use consistent choices for audience, skill level, format, affected group, and urgency. Your backlog becomes sortable instead of a collection of differently phrased comments that cannot be assessed side by side.
A long-answer field records the words learners use for their problem. Those phrases can shape the tutorial title, examples, chapter labels, and follow-up material without pretending the request alone proves overall demand.
Four request queues
Keep the request experience short for learners while gathering the operational context your team actually uses. Choose a starting pattern, then rename topic lists, formats, owners, and priority choices for your publishing process.
Connect feature selection, user goal, friction point, account context, and a screenshot. Product educators get a reproducible scenario instead of a vague request for ‘more documentation.’
Capture department, job task, learner level, number of people affected, process owner, and desired completion date for internal software or procedure tutorials.
Let subscribers suggest a question, choose a content series and format, share a reference, and optionally leave an email. The result is an idea inbox with enough detail to script from.
Tie requests to a course, module, and lesson, then ask for the attempted method and confusing step. Instructors can spot repeated gaps and create a supplemental explanation for the relevant cohort.
Request workflow
Generate the intake form, tailor it to your curriculum or channel, and establish a simple review rhythm. The form creates a shared starting point; your team still decides what fits the roadmap and when to produce it.
Tell Makeform who submits ideas, what you teach, which formats you produce, and how requests are reviewed. Mention the categories you want as dropdowns and the open questions that should capture nuance.
Remove questions you will not use, add brief helper text, and put the essential topic and outcome fields first. Use conditional follow-ups when a choice changes the brief, such as asking for a file only when the requester has an example.
Link the form from your course, help center, team portal, community profile, or video description. A single destination keeps new ideas in the same format while still allowing requests from several audiences.
Group submissions by topic and learner goal, flag those needing clarification, and record the chosen status. When a tutorial is published, share it with the requester and look for related submissions that the same resource may answer.
Request channels compared
Every channel can surface an idea. The difference is whether it gives the content owner enough consistent detail to understand the learner’s problem, compare it with other needs, and return to the original requester.
Field guide
Six field groups turn an idea into a content brief without asking the requester to write the brief for you. Keep the required path focused, make supporting evidence optional, and explain how each answer will help your review.
Topic and scope
Start with a category or product area and a plain-language topic. Then ask for the smallest question the tutorial should answer. This combination gives you a sortable label and the requester’s own framing without forcing them to know your taxonomy.
Goal and obstacle
A useful tutorial moves someone from an obstacle to an outcome. Ask what they need to accomplish, what they tried, and the exact step that stopped them. This reveals whether the right response is a quick demonstration, a full lesson, or clarification of an existing resource.
Audience context
Beginner, intermediate, and advanced labels help, but they mean different things in different fields. Add a short question about prior knowledge, role, or setup so the creator knows what can be assumed and what must be introduced before the main task.
Format and access
Someone following along in software may prefer a screen recording, while a repeatable workplace procedure may need written steps and a checklist. Collect preferences as guidance, not a promise, and include caption, transcript, or presentation needs relevant to your production process.
Evidence and references
An optional screenshot, sample file, timestamp, or reference link can expose the missing step faster than a paragraph. Tell requesters to remove passwords, private customer information, graded work, and other sensitive content before uploading anything.
Priority and follow-up
Ask when the information would be useful, what work is blocked, and whether the team may contact the requester. Avoid presenting an urgency choice as a guaranteed production date. Add status language explaining that submissions inform planning and may be combined with related ideas.
Related tools
A request form captures what people want next. Pair it with needs analysis, course evaluation, and learning feedback forms to understand where instruction is missing and how completed material lands with its audience.
Gather broader role, task, and capability needs before defining a training program or tutorial series.
Open toolCompare current knowledge, desired performance, barriers, and priorities across a team or learner group.
Open toolCollect reactions and improvement suggestions after employees complete a workshop or internal tutorial.
Open toolReview course structure, teaching clarity, pace, materials, and areas needing supplemental explanation.
Open toolAsk remote learners about content access, instruction, engagement, and support gaps in an online setting.
Open toolTurn internal content ideas into briefs with audience, search intent, references, owner, and requested timing.
Open toolFAQ
Practical answers for content creators, enablement leads, instructors, and training teams building a repeatable tutorial intake process.
A tutorial request form is a structured way for learners, customers, employees, students, or subscribers to suggest instructional content. Instead of collecting only a broad topic, it asks about the task they want to complete, their starting knowledge, what they tried, where they became stuck, and which format may help. The content owner receives a comparable brief for each idea and can request clarification before deciding whether it belongs in the publishing or training plan.
Require only what you need to understand the problem: topic or category, desired outcome, point of confusion, and current skill level are a strong core. Make contact details required only if follow-up is essential and explain how they will be used. References, screenshots, deadlines, format preferences, and estimates of people affected can usually stay optional. A shorter required path encourages useful submissions, while optional evidence lets motivated requesters provide a deeper brief.
Follow the topic field with concrete prompts: ‘What should someone be able to do after this tutorial?’, ‘What have you tried?’, and ‘At which step did you get stuck?’ Offer an example beneath the question, such as ‘Connect a data source and build a weekly conversion chart.’ Category and skill-level choices also narrow the scope. You may still receive broad ideas, but the form makes the missing context visible so you know exactly what to clarify.
Yes, if the core questions are shared and you give each audience an appropriate path. Start with an audience or request-type choice, then show relevant follow-ups: product area and account context for customers, department and work process for employees, course and lesson for students, or series and preferred medium for subscribers. Keep privacy expectations clear and do not ask one audience for internal information meant for another. Separate forms may still be simpler when owners and workflows are completely different.
Use the form to collect consistent signals such as the learner outcome, number or type of people affected, current workaround, urgency event, fit with your curriculum, and whether an existing resource partly answers the question. Review those alongside production effort and your editorial or training goals. Treat requester urgency as context rather than a promised deadline. Similar submissions can be grouped under one problem statement, then linked to one tutorial or a small series if that best addresses the need.
Yes. Add a file upload for screenshots, sample documents, or a short recording, and a website field for an existing lesson or reference. Include helper text asking people to remove passwords, access tokens, private customer records, confidential company material, graded submissions, and other sensitive details. Also keep a long-answer field available: some requesters cannot share the original screen or document but can still describe the relevant step and expected result.
Yes. Makeform is unlimited free for creating, editing, publishing, and collecting responses with your tutorial request form. The paid tier removes the Makeform badge. You can begin with a generated structure, revise the wording and choices for your audience, and share the finished request link without inventing a response cap or waiting for a trial period.
Confirm that the request was received, then route it to the person who owns the relevant course, product area, or content series. During review, mark whether it needs clarification, duplicates an existing idea, can be answered by current material, or is a candidate for planning. If you collect contact permission, update the requester when you ask a follow-up or publish something relevant. Do not promise that every submission will become a tutorial; explain that requests inform prioritization and may be combined.
Turn questions into teachable briefs.
