All pages
Powered by GitBook
1 of 1

Loading...

Text

1. Introduction

The Text Field in Unifize allows you to enter plain text directly into a checklist record. It’s designed for simple data entry—ideal when you need to add a short explanation, title, or comment without formatting.

Depending on the setup, some text fields may appear as single-line inputs (e.g., titles or labels), while others may be configured as multiline to allow for longer responses like summaries or descriptions.


2. How Text Fields work

When completing a checklist:

  • You will see a standard input box labeled with the field name (e.g., “Action Description”).

  • The box may show placeholder text (e.g., “Enter the steps you took”) to guide your response.

  • If the field is multiline, you’ll be able to enter extended text across multiple lines (like a paragraph).

  • Simply type your input and proceed—there’s no separate formatting toolbar or “Done” button.

  • The field saves automatically as part of the record when you submit or save the checklist.

The field may appear as required, locked, or hidden based on process conditions defined by your admin.


Text Fields make it quick and easy to provide written input when formatting isn’t necessary. They’re most useful when you need to add labels, provide straightforward answers, or log context without worrying about structure or style.

  • Naming a non-conformance or action item

  • Describing what happened in a deviation

  • Logging follow-up comments

  • Entering brief root cause analysis

  • Quick to fill out and no formatting needed

  • Intuitive for short or medium-length responses

  • Multiline option lets you write in full sentences if needed

  • Reduces friction during checklist completion


  1. Open the checklist assigned to you or that you're contributing to.

  2. Locate the Text Field labeled by your admin (e.g., “Action Description” or “Justification”).

  3. Click on the “Add Text” section. You will see a text box open where you can start typing.

  4. Your entry is saved with the record as part of checklist progress.


If you cannot see or edit a text field, it’s likely controlled by admin-defined logic based on record status or role permissions.

Answering simple yes/no justifications

Suitable for both technical users and non-technical stakeholders

  • Suitable for friction based on user and non technical responses and stakeholders and non-technical situations

  • If the field is required, you must enter a response before submitting the checklist.

  • If the field is disabled, hidden, or conditionally visible, it may behave differently depending on record status, previous field entries, or your user role.

  • Role

    What You Can Do with Text Fields

    Admin

    Amins define how the field behaves via configuration

    Org Member

    Can enter/edit content in checklist text fields if visible and editable

    External Member

    3. How Text Fields help you

    Where you might use it:

    Why it helps

    4. Technical workflow

    5. Roles and permissions

    🖊️Edit this page

    Can view or edit content only if the field is explicitly made visible/editable