Builder

The Builder is the central configuration module in Cinqd used to create, manage, and standardise forms, emails, and reusable templates across the platform. Any structured data collection, onboarding flow, or automated communication used in Cinqd is created and controlled from the Builder. 

Where to Find the Builder?

From the left sidebar, click Builder. 

–

Within the Builder module, you will see the following sections:  

• CRM – Client and supplier forms, onboarding forms, reference forms 

• HR – Employee onboarding and internal HR forms 

• Proposals Emails – Proposal-related email templates 

• Dropdowns – Global option lists used across forms and fields 

This structure allows you to manage all form and email logic in one place while deploying it across multiple modules. 

What the Builder Is Used For

The Builder allows you to: 

• Create custom forms for clients, suppliers, employees, and internal teams 

• Build master forms that act as reusable templates across departments 

• Configure automated email templates for onboarding, notifications, and proposals 

• Standardise how data is collected, validated, and reused across workflows 

Master forms act as global templates. They can be copied and adapted across teams, services, and departments, ensuring consistency while still allowing flexibility where required. 

How the Builder Powers Other Modules?

Forms and templates created in the Builder are used throughout Cinqd, including: 

• CRM – Client onboarding, supplier setup, reference data collection 

• HR – Employee onboarding and information management 

• Task Manager – Assign form-based tasks and trigger workflow steps when a form is submitted 

• Proposals – Send structured proposal and communication emails 

What Are Forms Used For?

Forms built in the Builder can be used in multiple ways across your business. They can be completed by internal teams, clients, suppliers, or partners, depending on the workflow. 

Client Onboarding 

Collect client details, documents, KYC information, and service selections in a structured, repeatable way. 

Supplier/Partner Onboarding 

Capture supplier or partner compliance information, including Company Registration Number (CRN), VAT details, and contractual documents. 

HR 

Collect employee data such as personal details, identification documents, role information, and training requirements using standardised HR forms. 

Client Portal 

Clients can securely complete onboarding forms, submit documents, and provide required information through the Client Portal, with full visibility and tracking. 

Internal Forms 

Use internal forms to request project requirements, access approvals, technical specifications, asset requests, or internal information,  all without relying on email or spreadsheets. 

Top Tabs in Forms 

• Info → Form name, description 

• Elements → Add form fields (Input, Dropdown, Upload, etc.) 

• Refs → Connect form fields to CRM or HR system fields 

These three tabs define the structure of every form. 

Master Forms vs Custom Forms

Master Form 

• A global template that defines the default data structure 

• Used as the standard structure for: 

1. 1. CRM → Customer records 
   2. CRM → Supplier records 
   3. HR → Employee records 

• Ensures employee information is standardised in the same way as client and supplier data 

• Maintains consistent fields across the entire platform 
• Updating a master form applies changes to all future records using that form 

Custom Form 

• A form created for a specific workflow, service, or department 

• Commonly used for: 

1. 1. Client onboarding 
   2. Questionnaires 
   3. Project briefs 
   4. Tax or compliance information 

• Does not affect the global structure 

• Only applies when the form is: 

1. 1. Explicitly attached to a record, or 
   2. Triggered within a task or workflow 

Where Forms Are Used in Cinqd?

Forms created in the Builder are available across multiple modules: 

Module	Use Case
CRM	Client onboarding forms, supplier forms, information updates
Task Manager	Activity checklists, data collection inside workflows
HR	Employee details, onboarding forms, certifications and records

Creating & Editing a Form

This section explains how to create, structure, and publish forms in Cinqd using the Builder. 

Step 1: Open Builder → Forms 

Navigate to Builder from the left-hand menu.
Select the relevant section (CRM, HR, etc.), then click + Form to create a new form. 

This determines where the form will be available across the platform. 

Step 2: Info Tab 

Use the Info tab to define the identity and placement of the form. 

Here you set: 

• Form name 

• Description (optional, but recommended for clarity) 

• Whether the form should be pinned as a tab in: 

• Customer profiles 

• Supplier profiles 

This helps users understand when and where the form should be used. 

Step 3: Elements Tab 

This is where you build the structure of the form. 

Add and configure fields such as: 

• Text inputs 

• Dropdowns 

• Upload fields 

• Mandatory/optional settings 

• Accepted file types (where applicable) 

This tab defines what data is collected and how users interact with the form. 

Step 4: Refs Tab 

The Refs tab is used to manage shared data and references. 

Used for: 

• Viewing shared field references 

• Mapping form fields to core system data 

• Reusing fields across multiple forms without duplication 

• Auto-populating fields in emails or templates using reference tags 

This ensures consistency and avoids data fragmentation across the system. 

Step 5: Save & Preview 

Before publishing: 

• Use Preview to test the form layout and behaviour 

• Click Save to make the form available for use 

Once saved, the form can be attached to records, workflows, or profiles based on its configuration. 

Elements Library 

The Elements Library contains all the building blocks used to construct forms in Cinqd. Each element serves a specific purpose and can be added, configured, and reused across different forms. 

Input 

A basic free-text input field used for capturing short pieces of information. 

Use for: 

• Names 

• Short answers 

• Company details 

• ID or reference numbers 

• Custom text input 

Divider 

Adds a visual separator to structure the form and improve readability. 

Use for: 

• Grouping related fields 

• Separating form sections 

• Organising long or complex forms 

 Checkbox 

A yes/no or confirmation selector. 

Use for: 

• Declarations 

• Confirmations 

• Agreement statements 

• Optional selections 

Date Picker 

Allows users to select a date from a calendar. 

Use for: 

• Deadlines 

• Birthdates 

• Document expiry dates 

• Project milestones 

• Filing or submission dates 

Text 

A static, non-editable text block displayed to the user. 

Use for: 

• Instructions 

• Explanatory notes 

• Section headers 

• Guidance within a form 

Dropdown 

A list of selectable options. 

Use for:
• Status
• Service type
• Country selector
• Yes/No lists
• Any controlled input requiring consistency 

User Field 

Allows selection of an internal Cinqd user. 

Use for: 

• Assigning managers 

• Selecting responsible staff 

• Approval ownership 

Link 

Adds a clickable hyperlink. 

Use for: 

• Terms & Conditions 

• Instructions 

• External resources 

• Documentation links 

Number 

A numeric-only input field designed to capture structured quantitative data accurately. 

Use for: 

• Quantities (e.g. item counts, hours, units) 

• Budget and cost values 

• Employee headcount 

• Financial figures and metrics 

• Any data that must be stored and validated as a number 

Why use this field: 

• Prevents invalid (non-numeric) entries 

• Ensures consistent data for reporting and analytics 

• Supports calculations, totals, and comparisons across records 

• Ideal for CRM, HR, and operational workflows where accuracy matters 

Phone Number 

Structured phone input with country code support. 

Use for: 

• Contact numbers 

• International client or supplier details 

Image 

Displays a static image in the form. 

Use for: 

• Branding 

• Visual guidance 

• Reference images 

Upload 

Allows users to upload files. 

Use for: 

• ID documents 

• Proof of address 

• Contracts 

• Supporting documentation 

Email 

An email-specific input field with built-in validation to ensure accurate and properly formatted email addresses. 

Use for: 

• Client and contact email addresses 

• System notifications and alerts 

• Account, onboarding, and service-related communication 

Why it matters: 

Using the Email field ensures clean, valid email data across CRM, HR, and workflows, reducing bounce-backs, missed notifications, and data errors. 

Text Area 

A multi-line input field designed for capturing longer, more detailed responses. 

Use for: 

• Detailed answers and explanations 

• Internal or client notes 

• Service descriptions or requirements 

• Any additional context that doesn’t fit short text fields 

Why it matters:
The Text Area field allows users to provide full context without constraints, making it ideal for briefs, onboarding details, and qualitative information. 

Radio 

Allows users to select one option from a set. 

Use for: 

• Mutually exclusive choices 

• Single-selection questions 

Reference Fields (Refs Tab)

The Refs tab is used for: 

• Viewing shared fields 

• Ensuring consistent data across forms 

• Avoiding duplication 

• Mapping fields to CRM entities like:
  • Customer
  • Supplier
  • Contact
  • Company 

Emails (CRM Email Templates)

Builder also manages all CRM emails. 

Emails include: 

• Variants 

• Subject line 

• Body content 

• Placeholders (e.g., {customer.name}) 

• Attachments 

Used for: 

• Onboarding emails 

• Request emails 

• Notifications 

• Compliance reminders 

• Invoice reminders 

 

How Forms Are Used Across Modules?

Cinqd forms are deeply integrated throughout the ERP. Here’s how each module uses Builder-driven forms: 

CRM 

Forms created in the CRM → Builder section are used to collect and update client and supplier information. 

Examples: 

• New Client Onboarding Form 

• Supplier General Form 

• Tax Questionnaire 

• KYC/AML Verification Form 

What happens when CRM forms are submitted? 

• CRM records are updated 

• Workflows may be triggered 

• Files are stored under the client 

• Approvals are timestamped 

• Assigned users get notified 

HR 

Forms may be used for: 

• Employee onboarding 

• Leave requests 

• New starter documents 

• Internal approvals 

HR forms help maintain structured employee data feeding into calendars, availability, and permissions. 

Proposals emails 

Builder is used to manage: 

• Proposal email templates 

• Proposal acceptance emails 

• Payment reminder emails 

• Monthly bookkeeping engagement emails 

Every proposal communication is controlled via Builder → Proposals Emails. 

Dropdowns  

Dropdowns (Builder → Dropdowns) define options used across all forms. 

Examples: 

• Industry Type 

• Supplier Status 

• Payroll Frequency 

• VAT Scheme 

• Employee Role 

• Client Service Type 

How Form Submission Works?

When any form is submitted, Cinqd follows a consistent system-wide logic: 

Step 1 – Validate Required Fields 

Form cannot be submitted unless mandatory fields are completed. 

Step 2 – Update CRM/HR/Workflow Records 

Mapped fields update automatically using Ref mappings. 

Step 3 – Save Files & Attachments 

Any uploaded file is: 

• Stored under the client/supplier/employee record 

• Timestamped 

• Categorised under the form name 

• Available for audits 

Step 4 – Trigger Assigned Actions 

Depending on configuration: 

• Tasks may be created 

• Workflows may start 

• Emails may be sent 

• Internal approvals may be requested 

Step 5 – Log Activity 

Each submission is recorded with: 

• Who submitted 

• When 

• What changed 

• What was attached 

This supports audits, compliance, and client transparency. 

Using Builder for Client Portal

Forms created in Builder can be shared with your clients via the Client Portal. 

Clients can: 

• Complete onboarding forms 

• Update their company information 

• Upload required documents 

• Approve drafts 

• Respond to compliance requests 

• Fill service questionnaires 

When a client submits a form: 

• CRM data updates 

• Files are categorised and stored 

• Portal logs a timestamped approval 

• Accountants/Consultants receive notifications 

• Pending compliance tasks are marked complete 

This eliminates email threads and manual follow-ups. 

Builder Emails – How They Work

Inside Builder → Emails, you can create templates for: 

• Client onboarding 

• Document requests 

• Regulatory updates 

• Invoice reminders 

• Workflow notifications 

• Proposal emails 

• Approval requests 

Each email includes: 

• Template name 

• Subject 

• Body text 

• Merge fields (dynamic variables) 

• Variants (A/B templates) 

• Attachments 

• References to workflows or modules 

These templates are used in: 

• Workflows 

• CRM 

• Proposals 

• Client Portal 

Using Ref Fields (Reference Mapping)

Ref fields determine how form fields connect to system data. 

Form Field	Ref Mapping	Result
Business Email	CRM.Email	Updates CRM Email
Director UTR	CRM.Director.UTR	Updates director data
Payroll Frequency	Accounting.Payroll.Frequency	Feeds payroll workflow
Assigned Accountant	CRM.OwnerUser	Links staff member

Why ref fields matter: 

• Prevent duplicate data 

• Ensure accuracy in workflows 

• Sync client/supplier/employee info 

• Feed analytics with consistent structure 

• Support automations 

Without ref mapping, the form acts like a stand-alone document  no automation or CRM update. 

 Benefits of central dropdown management: 

• Keeps data consistent 

• Allows updates in one place 

• Improves filtering & reporting 

• Avoids typos or inconsistent naming 

Updating a dropdown updates ALL forms using it. 

Best Practices for Builder Forms

Keep forms short 

Avoid overwhelming clients or staff members. 

Group related fields using sections 

Makes forms easier to navigate. 

Make required fields meaningful 

Only require fields essential to onboarding or workflow logic. 

Use dropdowns, not free text 

Supports better reporting and fewer errors. 

Map every important field 

Ensures workflows, CRM, and automations receive clean data. 

Use attachments only when needed 

Request essential documents only. 

Test forms through “Preview” 

Always review how clients or staff will experience the form.