Describe your program, eligibility rules, and evidence list. Makeform creates a structured application for company credentials, declarations, and supporting files.
Route applications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a brief, tailor the criteria, or send it to the builder. Each example is editable.
Audience
Companies applying to an industry accreditation program
Format
Multi-section application with evidence uploads
Prompt size
328 chars
Example form structure
Multi-section application with evidence uploads
Legal identity and registration details
Which services are included?
Insurance and credential expiry dates
Upload supporting documents
Authorized representative declaration
Suggested routing tags
Ready for review
Evidence missing
Renewal applications
Ask for expiry dates and document types separately so reviewers can spot missing or outdated evidence without opening every attachment.
Step 1
Identify
company, contacts, services, and locations
Step 2
Evidence
credentials, policies, insurance, and references
Step 3
Review
completeness checks and assessor routing
Step 4
Decide
record the program team's outcome and follow-up
Built for evidence-heavy applications
Connect each requirement to a field, expiry date, or file so reviewers receive every company's information in the same order.
Show trade, region, service, or risk questions only when relevant.
Place each upload beside the license, policy, insurance, or reference it supports.
Required fields and controlled choices create comparable records, with explanations where needed.
Adapt the same foundation
Tailor the applicant, evidence, criteria, and routing to the organization making the decision.
Collect scope, staff competence, procedures, references, and required evidence.
Screen vendors by category, geography, capacity, disclosures, and insurance.
Request licenses, safety practices, responsible personnel, incident explanations, and trade-specific documents.
Focus returning applicants on changed details, expiring documents, unresolved actions, and updated declarations.
Application workflow
Define required evidence and route submissions to the responsible reviewers.
Name applicant types, services, eligibility gates, evidence, declarations, and reviewers.
Separate identity from capability and reveal details according to category and answers.
Send a receipt and notify reviewers by category, region, or pathway.
Use submissions for follow-up, reviewer notes, expiry tracking, and renewals.
Choose the intake method
Guide applicants through detailed criteria while giving reviewers structured answers.
Field guide
Use these six sections, then apply your program's criteria, definitions, retention language, and decision process.
Company identity
Separate the legal entity from trading names and branches. A registration identifier and correspondence address help distinguish related applications.
Contacts and authority
Separate the application contact from the representative authorized to make declarations so questions reach the right person.
Scope and eligibility
Use controlled lists for services, locations, and pathways, then branch to applicable eligibility and capability questions.
Credentials and evidence
Capture credential type, issuer, number, holder, and expiry as fields before requesting the file.
Experience and disclosures
Request projects, references, procedures, and explanations for relevant incidents or conflicts.
Declaration and review
Place your declaration before acknowledgment and signature fields. Explain review without promising approval or a fixed result.
Related tools
Add vendor registration, evaluation, onboarding, and general application forms.
Collect vendor identity, categories, capabilities, references, and supporting files for an initial review.
Open toolCapture the structured company and contact data needed to create or update a vendor record.
Open toolGive reviewers a consistent scorecard for supplier performance, capability, and follow-up notes.
Open toolTurn an accepted vendor's setup tasks, owners, evidence, and dependencies into a trackable checklist.
Open toolCreate a supplier intake alternative for business details, categories, documentation, and key contacts.
Open toolStart a broader application workflow when the intake does not require accreditation-specific evidence.
Open toolFAQ
Practical answers for accrediting bodies, procurement teams, and program administrators designing company intake.
It collects a company's identity, requested scope, credentials, declarations, and evidence for review. The form organizes the submission; the responsible body applies its criteria and decides the outcome.
Include legal identity, registration, ownership, addresses, contacts, requested scope, credentials, required evidence, references, disclosures, uploads, and an authorized declaration. Capture expiry dates as fields rather than burying them in files.
Yes. Branch after service, discipline, region, or risk selections. Contractors can see trade and safety questions while professional suppliers see qualification and reference questions. Keep identity and declarations shared.
Yes. Put uploads beside each requirement and state accepted formats. Capture document type, issuer, number, holder, and expiry in fields so reviewers need not rely on filenames.
No. Submission only sends an application. Accreditation, qualification, renewal, or rejection depends on the responsible body's criteria and decision process. A receipt is not an approval.
Ask for the existing reference, changed details, new services, updated credentials, expiry dates, relevant incidents, and replacement evidence. Use confirmation instead of re-entering unchanged data where appropriate.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge.
Mark essential questions required and use completeness fields or routing tags. Keep the submission reference when requesting missing evidence. Completeness supports review but is not the accreditation decision.
Make every credential easier to review.
