Describe the credentials your team handles. Makeform creates a certification request form for requester details, request type, supporting files, authorization, delivery, and review routing.
Route requests with Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, adjust the prompt, or send it to the builder. Each example is editable.
Audience
Employees requesting a training certificate
Format
Internal request with course and delivery details
Prompt size
314 chars
Example form structure
Internal request with course and delivery details
Employee name, email, and department
Course title and completion date
What are you requesting?
Supporting record
Delivery preference
Suggested routing tags
New credential
Copy requested
Verification review
Ask for request type first because copies, renewals, and third-party checks need different follow-up fields.
Step 1
Request
requester, credential, and purpose
Step 2
Match
staff locate the relevant record
Step 3
Review
details and attachments are checked
Step 4
Respond
status or copy follows your process
Why structured intake helps
Collect identifiers, dates, authorization, and delivery details in one intake. Your team still decides what can be issued or confirmed.
Let people choose a credential, copy, renewal, or verification path, then reveal only relevant questions.
Former names, program dates, and credential numbers help reviewers locate the right record.
Explain review ownership and the response channel without implying that submission grants a credential.
Four request paths
Choose the closest workflow, then tailor evidence, routing, and response instructions.
Capture completion details and requested format after staff confirm the record.
Ask for former names, dates, and known identifiers to help search archives.
Collect the third party, credential holder, inquiry scope, and authorization.
Gather credential dates, activities, and documents while keeping decisions in review.
Request workflow
Turn your description into an editable form for consistent submissions.
Describe what you record and whether you handle copies, checks, or renewals.
Show mailing, authorization, or activity fields only on relevant paths.
Notify the right reviewer based on program and request type.
Review the intake, request missing details, and communicate status through your chosen channel.
Form vs inbox vs static file
An online form adapts questions and routes consistent submissions while leaving decisions with your team.
Field guide
Capture enough context to find the record and review the request without presenting the form as proof of status.
Requester
Collect current contact details and the requester's relationship to the credential holder so the request reaches the right path.
Record matching
Ask for exact identifiers when available, with approximate-date and former-name fields for older records.
Request type
Use the first choice to branch copy, renewal, and verification questions instead of asking everyone for every detail.
Authorization
Your team defines required permission evidence and who reviews it; the upload field only collects the file.
Supporting material
Keep relevant records and prior copies attached to the request, with plain labels for each upload.
Review and delivery
Name the reviewing team and response channel without promising an outcome.
Related tools
Connect intake with records, training, transcripts, and verification workflows.
Collect the student, record type, dates, delivery details, and recipient for an academic records request.
Open toolGather applicant goals, prerequisites, scheduling information, and approvals before a training program begins.
Open toolRecord a participant's completion details and the internal reviewer responsible for signoff.
Open toolRoute requests for course history or transcripts with recipient and delivery preferences included.
Open toolCollect an employment-related inquiry, subject details, requester contact, and supporting authorization.
Open toolStructure requests that ask an organization to check a membership record and respond through its own process.
Open toolFAQ
Answers for teams setting up request intake.
It is intake for a certificate, replacement, renewal review, or status check. It collects requester details, record identifiers, purpose, files, authorization, and delivery preference. Submission starts review; the form does not issue or confirm a credential.
Include requester contact, relationship, request type, credential title and number, relevant dates, reason, uploads, and response preference. Add former-name, approximate-date, and conditional mailing fields when useful.
Yes. Use request type and conditional logic. The copy path can ask for format and address; a third-party path can ask for organization details, inquiry scope, and authorization. Route each to the appropriate reviewer.
No. A submission is only a request record. Your team must review the source record before deciding what it can provide. State this clearly for third-party inquiries and renewals.
Collect the organization, contact, credential holder, credential details, inquiry scope, and required authorization. Route it to a designated reviewer and keep record information out of automatic confirmations.
Yes. Add uploads for a prior certificate, completion record, authorization, or activity summary. Label each field by purpose and request only material needed for that path.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect certification requests without a response cap. The paid tier removes the Makeform badge.
Responses arrive in your Makeform inbox. Notifications can alert HR, learning, records, or credential teams, while Google Sheets, Slack, and Zapier integrations can support tracking.
Make every request easier to review.
