Gather

Structured Submitter-Side Form Intake

Get structured data from anyone, at source.

Gives external parties — applicants, patients, vendors, citizens — a hosted form or portal to enter information directly into your process schema. Conditional flows, inline validation, save-resume, and multi-party sign-off mean data arrives complete and structured, not as a PDF you have to parse.

Shape

submitterapplicant · vendorhosted portalnametypeif commercial:ABNattachmentdrop filesubmitstructured recordaudit trail09:14 draft saved09:31 co-sign by B09:32 submitted

Operational dimensions

Human co-pilot

Person and system work side-by-side.

On demand

Fires when a user asks.

Low data gravity

Light state; replaceable any time.

Read-only inbound

Consumes external data; does not write back.

Inputs

  • Form schema defining fields, types, and conditional logic
  • Submitter identity and authentication method
  • Validation rules per field and cross-field
  • Attachment upload config and supporting document requirements

Outputs

  • Structured record matching the form schema
  • Attached supporting artefacts with file references
  • Submission audit trail (timestamps, submitter, version, sign-off chain)

Mechanism

Hosts a submitter-facing structured form / portal where a third party enters structured data directly into the org's process — with conditional fields, validation, upload handling, save-resume, multi-party signature and submission lifecycle.

Why this is a primitive

Cannot be decomposed — the submitter-side capture UI plus inline validation plus submission landing is one operation. Strip the submitter UI and you have document-intake (different channel: server-side parsing of whatever they sent); strip the validation and you have a free-text contact form (not a structured-intake primitive). Does NOT route the submitted case onward (act-on-it-together-workflow-routing), does NOT score it (make-sense-of-it).

Where it shows up

Council planning department — online development application portal with conditional sections based on application type, handles multi-party declarations and document upload
Healthcare provider — patient pre-registration and intake form capturing symptoms, history, and consent before the consult, structured and ready for the clinical workflow
Enterprise procurement — vendor onboarding portal with conditional compliance questions, banking details, and certificate uploads, replacing email back-and-forth
HR team — job application portal with conditional screening questions, structured to feed directly into the ATS without manual data entry

Related primitives

Tags

structured-dataportalthird-partyformsautomation

See where it fits.

Primitives are configured into named solution shapes for each client’s domain. The fastest next step is a conversation about which shape fits your problem.

Start a conversation