Describe the role, review perspective, competencies, and rating anchors you need. Makeform drafts an editable skills assessment form that you can customize, publish or share, and use to collect structured responses for a review conversation.
Draft the form, check every field, then publish or share it with the intended respondents.
Practical skills assessment form prompts
Choose a review format, inspect the example questions, and edit the prompt before sending it to the Makeform builder.
Respondents
An employee and reviewer assessing one role
Review format
Role-based form with anchored ratings and evidence
Prompt length
402 characters
Example question structure
Role-based form with anchored ratings and evidence
Respondent name, reviewer context, role, team, and time in role
Which competency area are you reviewing?
Which observable behavior have you seen?
Select a proficiency level: Learning, Applying, Independent, or Coaching others
Give a recent example or evidence for this rating
What development priority, support need, owner, and follow-up date should be recorded?
Suggested review stages
Draft
Ready to discuss
Follow-up set
Define each proficiency anchor in observable terms and discuss responses with the person; a form records judgments but does not verify skill.
Step 1
Define
role, purpose, reviewer perspective, and competency areas
Step 2
Anchor
observable behaviors and clearly defined proficiency levels
Step 3
Collect
ratings, examples, confidence, and development needs
Step 4
Discuss
responses in context, then record owners and follow-up dates
What the form is for
A useful skills assessment form makes the role, evidence, rating anchors, and review perspective explicit. It supports a discussion; it is not proof that someone can perform a skill.
Identify the respondent, reviewer relationship, role, team, review period, and purpose so each answer can be interpreted in context.
Group questions by competency area and describe behaviors that a respondent or reviewer could reasonably observe in real work.
Use defined proficiency anchors alongside examples, confidence, development priorities, support needs, and follow-up notes.
Use with care
Keep ratings tied to evidence, allow context, and use the completed form as an input to a human conversation. Makeform does not verify skills or make employment decisions.
Ask what proficiency anchor fits, then ask how confident the respondent or reviewer is. Uncertain ratings should invite more context, not a forced conclusion.
Prompt for a recent behavior, work example, or other evidence. Avoid vague traits and questions unrelated to the role or purpose.
Review differences between self and reviewer responses together. Record what was clarified rather than treating one response as automatically correct.
Decide who needs to see submissions, how long the records should be kept, and when notes should be removed. Test the form on mobile before sharing it.
Four-step workflow
Start with the job and purpose, then customize the draft before anyone responds. Review completed forms with the person and document agreed next steps.
State who will respond, who will review, what decision or conversation the form supports, which competency areas matter, and what each proficiency anchor means in observable terms.
Edit the draft for the actual role. Add behavior prompts, evidence and confidence fields, development and support questions, then complete a test response on mobile to catch unclear labels or missing context.
Publish or share the form with the intended people. Before collection begins, set who may access submissions, communicate the purpose, and define how long responses and notes will be retained.
Read ratings alongside examples and reviewer context. Discuss results with the person, agree on development priorities and support or training needs, then record a follow-up owner, date, and notes.
Choose the right instrument
These tools answer different questions. Use the form to collect structured judgments and evidence, and use qualified methods when validation or high-stakes decisions are required.
Field guide
Use these field groups as a practical checklist. Keep only what serves the stated review purpose, and write anchors that a respondent can distinguish without guessing.
Context
Responses need enough context to interpret them without turning the form into a personnel dossier. Make the perspective and scope clear at the start.
Competencies
A competency label such as communication is too broad on its own. Pair each area with behavior prompts that fit the role and can be supported with examples.
Ratings and evidence
Use a proficiency scale only when each point has a distinct meaning. Ask for evidence and confidence separately so the discussion can distinguish observed performance from uncertainty.
Development and follow-up
The form becomes useful when the people involved can turn the discussion into a specific action without treating the rating as an automatic verdict.
Related tools
Use a separate form when the purpose shifts away from skills assessment. The related tools remain in the existing page order.
Draft an administration application form for its own intake workflow.
Open toolCollect structured questions and context from prospective students.
Open toolPrepare a focused interview questionnaire and collect responses.
Open toolGather event feedback separately from a role or team skills review.
Open toolCollect complaint details through a dedicated issue-reporting form.
Open toolCreate a lead intake form for contact and qualification details.
Open toolFAQ
Practical answers about drafting, reviewing, and using a skills assessment form responsibly.
A skills assessment form collects structured self, manager, reviewer, or team observations about role-related competencies. It can record defined proficiency ratings, observable behaviors, examples or evidence, confidence, development priorities, support needs, and follow-up notes for a discussion.
No. A form records responses to the questions you choose; it does not establish psychometric validity, verify that a person has a skill, or turn a rating into a test result. Use an appropriately validated instrument and qualified process when the purpose requires testing.
Start with respondent and reviewer context, role, team, review purpose, and competency areas. For each area, ask about observable behaviors, a proficiency level with defined anchors, supporting examples or evidence, and confidence. Finish with development priorities, support or training needs, a follow-up owner and date, and notes.
You can draft one editable structure, but label the response perspective clearly and customize prompts for each audience. Self-ratings, manager observations, and team-level input are different kinds of evidence and should be reviewed in context rather than merged into an automatic ranking.
Yes. The prompt seeds a first draft in the builder. Review every competency, anchor, field label, and required question, remove anything unrelated to the purpose, and test the completed path on mobile before publishing or sharing it.
No. Makeform drafts an editable form and collects responses; it does not provide validated psychometric testing, automatically score or verify skills, make hiring or promotion decisions, or issue credentials.
Give every level a distinct, observable definition. For example: Learning means performs with close guidance; Applying means handles familiar tasks with some support; Independent means handles the expected work without routine support; Coaching others means guides others in that same work. Adapt the language to the actual role.
Read ratings together with examples, confidence, role expectations, and reviewer context. Discuss differences with the person, document what was clarified, agree on development and support needs, and assign a follow-up owner and date. Do not treat the form alone as an employment decision.
Confirm the purpose and audience, remove unnecessary personal information, decide who may access submissions, set a retention period for responses and notes, and submit a test response on a mobile device. Also tell respondents how the information will be used and what happens next.
Start with the role, not a generic score.
