This guide explains how to use the Onboarding Form feature in the Template Manage page:

• /wp-admin/admin.php?page=psfw-template-manage&template_id={ID}

The Onboarding Form feature helps you collect structured customer inputs at the start of each project.

What the Onboarding Form Feature Is #

Inside Template Manage, the Onboarding Form section lets you define:

• form description shown to customers
• onboarding task due timing
• form fields customers must complete
• required vs optional questions
• options-based fields (for structured answers)

This form is then used to gather project kickoff details consistently.

Core Features and Benefits #

1) Built-In Onboarding Form Section #

Feature:

• onboarding form configuration lives directly inside the template workflow

Benefit:

• keeps setup centralized so template logic and intake logic stay aligned

2) Form Description for Customer Guidance #

Feature:

• editable description text shown above the onboarding form

Benefit:

• improves response quality by giving customers context before they answer

3) Field Builder for Structured Intake #

Feature:

• create and organize fields with labels, types, and optional descriptions

Benefit:

• transforms vague kickoff conversations into reliable, reusable data collection

4) Required Field Controls #

Feature:

• mark critical fields as required

Benefit:

• reduces missing information that normally causes delivery delays

5) Options-Based Question Support #

Feature:

• options-capable fields support predefined answer choices

Benefit:

• standardizes responses and reduces ambiguity in downstream execution

6) Onboarding Task Timing Controls #

Feature:

• set onboarding task due timing (days/hours after project creation)

Benefit:

• sets clear customer completion expectations and improves kickoff pacing

7) Pro-Aware Field Handling #

Feature:

• unsupported advanced field types are clearly marked and handled safely

Benefit:

• avoids silent misconfiguration and makes environment limits explicit

How and When to Use the Onboarding Form Feature #

Use It When #

• projects require recurring intake details before work starts
• your team loses time chasing basic client information
• scope/requirements are often unclear at kickoff
• you want consistent handoff quality across team members

Keep It Lightweight When #

• service scope is simple and fixed
• only 2–3 inputs are needed to start work

A short form is better than an overbuilt form customers abandon.

Step-by-Step: Building a Strong Onboarding Form #

Step 1: Open Template Manage #

Go to:

• /wp-admin/admin.php?page=psfw-template-manage&template_id={ID}

Find the Onboarding Form card.

Step 2: Define the Form Description #

Write a short prompt that tells customers:

• why they are filling this form
• what quality of detail you expect
• how their responses affect project start

Keep it concise and action-oriented.

Step 3: Add Core Fields First #

Start with must-have kickoff questions only.

Typical categories:

• business or brand context
• required assets/access
• key preferences/constraints
• acceptance or success criteria

Step 4: Set Required Fields Strategically #

Mark fields as required only when they truly block execution.

Use optional fields for context-enhancing information.

Step 5: Use Options for Standardization #

For repeatable answers (tiers, priorities, channels, formats), use option-based fields.

This improves reporting consistency and speeds internal decision-making.

Step 6: Set Onboarding Task Due Timing #

Configure due timing for the customer onboarding task.

Use realistic timing that balances urgency with completion likelihood.

Step 7: Save and Run a Test Submission #

After saving template changes, test the onboarding flow as if you were the customer.

Validate:

• field labels are clear
• required logic works
• options are complete and unambiguous
• description text sets proper expectations

Practical Patterns #

Pattern A: Fast-Start Intake #

• 4–6 fields
• only critical required questions
• minimal optional detail

Best for simple/fast-turnaround services.

Pattern B: Scope-Clarity Intake #

• structured scope, deliverables, and constraints fields
• mix of required and option-based questions
• explicit success criteria prompts

Best for services with frequent revision risk.

Pattern C: Team-Handoff Intake #

• questions mapped to internal delivery stages
• data designed for PM/Staff transfer clarity
• standardized option sets for repeatability

Best for multi-person delivery teams.

Best Practices #

• write fields from the customer perspective (clear, plain language)
• keep required questions limited to execution-critical inputs
• use option fields where consistency matters most
• review forms monthly using real submission quality as feedback
• remove low-value questions that do not affect delivery outcomes

Common Mistakes to Avoid #

• asking too many questions before proving value
• making non-critical questions required
• using vague field labels that invite unclear responses
• building forms without testing real customer completion flow
• failing to update fields when service process changes

Summary #

The Onboarding Form feature is your kickoff data quality engine.

When used intentionally, it improves intake clarity, reduces back-and-forth, and helps your team start projects faster with better information.