Launch via a kick-off form

What prerequisites are needed for kick-off form setup?

• Permission to edit Tallyfy® templates for configuration access.
• A process template where you want to add a starting form for workflow initiation.
• Clear understanding of what information you need to collect before the process starts.

These requirements ensure proper form setup and effective data collection for workflow automation.

How do Tallyfy kick-off forms enable process launching and data collection?

Kick-off forms attach to the beginning of Tallyfy® templates, ensuring comprehensive information collection before main workflow tasks commence.

These forms accommodate both internal team usage and public access - enabling external stakeholders including customers or partners to initiate processes through form submission. Unlike standalone online forms, Tallyfy® kick-off forms integrate directly with subsequent workflow steps for seamless automation.

Upon form submission, processes launch immediately with complete progress tracking capabilities across all participants and stakeholders, creating a smooth transition from data collection to workflow execution.

How can I create an effective kick-off form?

1. Go to the Templates library.
2. Open the template you want to add the form to in Edit mode.
3. In the left sidebar of the editor, click Triggers.
4. Select Kick-off Form.
5. Click + Add Field to add your questions (form fields).
6. Set up each field (name, type, required?, help text, options, and default content if needed).
7. Save your changes to the template.

What field types are available for comprehensive data collection?

You can use various field types to capture different types of information:

• Short Text (for names, IDs, brief responses)
• Long Text (for descriptions, detailed explanations)
• Dropdown List (pick one from a predefined list)
• Checklist (pick multiple from a list for comprehensive selection)
• Radio Buttons (pick only one option from exclusive choices)
• Date (for scheduling and timeline information)
• File Upload (for documents, images, and attachments)

Mark fields as Required if the process cannot start without that information. Note: Having required fields limits how the process can be started automatically (e.g., cannot be started by email or some API calls without providing the required data).

How do users complete kick-off forms during process launch?

When someone launches a process that has a kick-off form:

1. They click Launch Process on the template.
2. The kick-off form appears immediately.
3. They fill out the fields (required fields are marked with *).
4. They click Submit.
5. The process then starts, using the information entered.

How can I access kick-off form answers during process execution?

Anyone working on the process can see the information submitted in the kick-off form:

1. Open any task within the running process.
2. Click the Info tab in the task details.
3. Expand the Kick-off Fields section.

This helps provide context for later tasks.

Filling forms automatically

You can pre-fill kick-off forms automatically using data from other systems, often via web form links or middleware.

How do public kick-off forms enable external collaboration?

You can share a kick-off form publicly so anyone (even non-Tallyfy users) can fill it out to start a process.

Why should I use public forms for external engagement?

• Starts workflow automatically: No delay between form submission and process start for immediate action.
• Submitter tracking link: The person who submits gets a unique, permanent link to track the progress (if they verify their email).
• Email verification: Helps prevent fake submissions and allows Tallyfy to send updates to the submitter.
• Save and return: Submitters can save partly filled forms and come back later using their link for convenience.
• No extra tools needed: Directly integrates form submission with your Tallyfy process for seamless automation.

Public forms bridge the gap between external stakeholders and internal workflows.

Important note on deactivated members and public forms

If the Tallyfy member associated with setting up the public form gets deactivated, it can affect the public link. Always check and potentially reassign public forms before deactivating members to avoid issues. (See Removing Members for details).

Magic Links limitation with kick-off forms

Magic Links cannot be used to pre-fill kick-off form data when the form has required fields. This is because Magic Links work only for logged-in users and process directly without displaying the kick-off form interface. For external users or when you need to pre-fill forms with required fields, use:

• Public kick-off form links for external users
• Web form redirects with query parameters
• API calls with proper field data
• Middleware integrations that can programmatically provide required field values

How can I make a kick-off form available to external users?

1. Open the template in Edit mode.
2. Go to Triggers > Kick-off Form.
3. In the panel on the right, find Public Sharing and switch it ON.
4. Click Get Public Link.
5. A box will appear with the shareable link. Copy this link.
6. Share this link with people outside your organization.

How does the public form submission process work?

When someone clicks the public link:

1. They are asked to enter their email address (for verification).
2. They receive an email with a private access link.
3. Clicking that link takes them to the form.
4. They fill out and submit the form.
5. The process launches in Tallyfy.
6. They can use their private access link later to check the process status.

This is great for forms that might take time to fill out.

What’s the difference between public forms and internal process steps?

Understanding this distinction is crucial for designing effective workflows:

Public Kick-off Forms:

• Who sees them: External users (customers, vendors, partners) without Tallyfy accounts
• Purpose: Collect initial information to start a workflow
• Access: Via public link shared through email, website, or other channels
• User experience: Simple form interface with your company branding
• What happens next: Form submission automatically creates a process inside Tallyfy

Internal Process Steps:

• Who sees them: Your team members and assigned guests
• Purpose: Execute the actual workflow tasks after the process starts
• Access: Through Tallyfy dashboard with login credentials
• User experience: Full task management interface with comments, attachments, and tracking
• Visibility: External submitters can track overall progress but cannot see internal task details

Common Use Case: Purchase Requisitions

A vendor submits a purchase order through your public form. This automatically creates an internal approval workflow where your finance team reviews, approves, and processes the order - all invisible to the vendor except for status updates.

What are best practices for creating effective kick-off forms?

Progressive Information Gathering Strategy

The most effective kick-off forms follow a “minimal upfront, progressive collection” approach:

• Only include guaranteed available information: Ask only for data you know the person launching will definitely have at the start
• Avoid complex conditional questions: Save detailed branching questions for later workflow steps where context has been established
• Keep initial forms lightweight: Don’t overwhelm users with extensive forms that might discourage process initiation
• Plan for just-in-time data collection: Design subsequent workflow steps to gather additional information precisely when it’s needed

Equipment Insurance Example

Instead of asking “List all equipment details, specifications, and carrier requirements” in the kickoff form, start with just “Is this endorsement for equipment or facilities?” and “What’s the client ID?” Then use conditional automations to reveal appropriate detailed collection steps based on those initial answers.

Form Design Best Practices

• Use clear field names that users can easily understand without technical jargon
• Arrange fields logically to create a smooth, intuitive user experience
• Mark fields as required sparingly: Only make fields required if the process absolutely cannot proceed without that information
• Provide helpful guidance text for fields that need extra explanation or context
• Test thoroughly before sharing widely to ensure proper functionality across different user scenarios

Advanced Progressive Collection Techniques

• Conditional step revelation: Use automations to show additional data collection steps based on kickoff form responses
• Role-based information requests: Collect different information based on who is launching the process (department, expertise level, etc.)
• Just-in-time validation: Verify and expand initial information at appropriate workflow milestones rather than upfront
• Exception path planning: Design clear procedures for handling unusual situations that don’t fit standard information collection patterns

Common Mistakes to Avoid

• Front-loading complex questionnaires: Asking for detailed information that may not be available until later in the process
• Branching in kickoff forms: Complex conditional logic belongs in workflow steps, not initial forms
• Requiring uncertain information: Making fields mandatory when the person launching may not have that data readily available
• One-size-fits-all approaches: Not considering that different types of users may have different information available at launch time

These practices ensure high completion rates, quality data collection, and smooth workflow initiation while supporting sophisticated information gathering throughout the process lifecycle.

Related articles

Launching > Launch a process from a web form

External web forms can be configured to automatically start Tallyfy processes upon submission by redirecting users to a special launch URL with form data appended as query parameters that match the exact field names in the Tallyfy template’s kick-off form.

How To > Build effective forms

Tallyfy’s integrated approach to form building connects form submissions directly to trackable workflows while offering features like email verification conditional branching field validation and document generation to create seamless end-to-end processes rather than isolated data collection.

Launching > Triggers

Tallyfy process launch triggers offer multiple methods including manual buttons API calls email addresses magic links scheduled automation task completion events and kick-off forms to initiate workflows automatically or manually while enabling data pre-population and integration with external systems.

Triggers > Launch via a magic link

Magic links are special URLs that automatically perform Tallyfy actions like creating tasks launching processes or completing workflows when clicked by logged-in users enabling seamless automation across emails websites and other tools.