Bosca / Forms

Task intake

A form in front, a task behind it

Requests come in as forms; work happens as tasks. A Work Ops form connects the two — each submission opens a task, filed where you decided it should go.

Intake

From "can someone…" to on the board

Facility requests, prayer follow-ups, bug reports, event help — anything people ask for through a form arrives as a task your team already knows how to handle.

  • Every submission opens a task — filed in a project, typed, and prioritized.
  • The submission stays attached — the answers that created the task remain in the submissions queue.
  • Requesters don't need Work Ops — they see a form; your team sees a task.
Facilities request
What needs attention?Projector bulb is out in room 204
task FAC-142 · Facilities · High

Mapping

You decide what fills the task

For each task field, choose where its value comes from: a default you set on the form, or an answer the submitter gives.

  • Defaults per form — a fixed project, task type, and priority when the form shouldn't ask.
  • Or from the form — map task fields — summary, description, assignee, due date, and more — to the form's own fields.
  • Ask only what you must — a public request form can stay simple while the task still lands fully filed.
task mapping
ProjectFacilities
Priorityfrom form field
Summaryfrom form field
Due datefrom form field

Starting point

An intake form, in one click

Starting from a blank canvas? Scaffold generates a working intake form — a project selector, a task-type and priority row, a summary, and a description — and you shape it from there.

  • A working form first — scaffold, then rename, rearrange, and trim like any other form.
  • Selectors wired to Work Ops — the generated project, type, and priority fields list what your Work Ops actually has.
scaffolded layout
Project Work Ops Select
Task type
Priority
Summary
Description

Keep exploring

More on Forms