Submission Form

Data entry form · Intake form · Record creation form · Application form

Tags:dataforms

Examples

Scholarship request form: the applicant enters their personal data, accepts the instructions, and submits the form. Once submitted, the request leaves their control and enters the evaluation process; the notice says the confirmation will arrive by email (Spanish-language interface).

Description

An input component that presents a user with a set of fields for entering data and sending it to the system in a single act. It is the counterpart of Queries (input instead of output): while Queries retrieves existing information, the Submission Form adds new information. Its purpose is to capture data in a structured and validated way at a point in the process where the person entering the data is not necessarily the one who later processes, approves, or manages it. Once submitted, the data leaves the control of whoever entered it and follows its course within the system. It is very common in information systems: applications, requests, complaints, enrollments.

Mandatory capabilities

Mandatory capabilities

• Presents a defined set of fields for the user to enter data
• Indicates which fields are required, optional, or selectable from a predefined set
• Validates the inputs before submission (format, required fields, consistency), preventing invalid data from entering the system
• Adds the data to the system in a single act of submission, handing it over for later processing
• Does not offer whoever entered the data any reading, editing, or deletion of it once submitted: the interaction ends with the submission

Additional capabilities

Additional capabilities

• File or document attachments: adds files (PDFs, images, certificates) together with the form data; common in applications and requests that require supporting documents
• Save as draft: lets the user save an incomplete form and resume it later before submitting it for good
• Multi-step form (wizard): splits a long form into sequential stages, showing progress
• Conditional fields: shows or hides fields according to previous answers, adapting the form to the user's case
• Acknowledgment of receipt: after submission, gives the user a confirmation or tracking number for their submission

Boundaries

What it is not

• Is not a Data Manager. The Data Manager administers an entity over time (creating, reading, editing, and deleting the same entity, coming back to it). The Submission Form is a one-time act of entry whose data, once submitted, is no longer under the control of whoever entered it. The difference is not in the number of operations but in the relationship with the data: continuous administration of one's own entity versus handing a piece of data over to a flow
• Is not a survey. Although the capture mechanics look alike, a survey has a different intent (collecting opinions or answers for aggregate analysis, not adding a record to the operational flow of the system); it is considered different in nature
• Does not process, approve, or route what was submitted — triggering the flow, successive approvals, and later processing belong to other components (Approval Workflow, Scheduled Process, Reactive Process, Notification System)
• Does not retrieve or display existing information — that belongs to Queries, Report, or Dashboard; its direction is input only

Information flow

Input

Data entered by the user in the form fields, plus any attached files

→

Output

The submitted record, added to the system; optionally, an acknowledgment of receipt for the user

Variants

• Simple form: a single screen with the fields to fill in and a submit button; the most common case (a complaint, a short enrollment)
• Multi-step form (wizard): splits a long submission into sequential stages; typical of applications with many data fields and documents
• Form with supporting documents: data entry must be accompanied by the upload of one or more files (a scholarship application with certificates)

Typical dependencies

• Database where the submitted record is persisted
• Authentication and Authorization when submission is restricted to identified users or to users with a certain permission
• Approval Workflow, Scheduled Process, or Reactive Process when the submission triggers a later processing or approval flow
• Notification System when the user or the responsible office is notified after submission

Mapping to the Digital Board

Manual UpdateAlways

Automatic UpdateNo

Data ConceptsAlways

On-Demand OutputsNo

Automatic OutputsOptional

Autonomous ProcessesNo

Section	Relationship	Notes
Manual Update	Always	The core act of the component: the user enters and submits data that is added to the system.
Automatic Update	No	—
Data Concepts	Always	The entity or record being submitted (the application, the complaint, the request).
On-Demand Outputs	No	—
Automatic Outputs	Optional	Acknowledgment of receipt, confirmation, or notice to the responsible office, when that capability is present.
Autonomous Processes	No	Later processing belongs to a component that contains the form (Approval Workflow, Scheduled Process, Reactive Process), not to the form itself.

Digital Board example

Manual Update

Scholarship Request

Data Concepts

Application

On-Demand Outputs

—

Automatic Update

—

Autonomous Processes

—

Automatic Outputs

Submission Confirmation by Email