Make requests arrive with an owner
In this guide, I focus on getting a project request to a reviewable decision and a named owner. In monday work management, plan the questions, board fields and review responsibilities together. The example below shows the design and checks to apply to a small project-intake workflow.
Use a board for Onboarding Refresh requests. Define a small process before configuring it: Received, Needs detail, Accepted, In progress, Review and Closed. The delivery lead owns triage; the requester supplies the desired outcome; the approver accepts a specific version. Keep CRM sales pipelines outside this exercise.
Map each question deliberately
The supplier’s WorkForms instructions say form questions are managed separately from board columns. Add questions in the editor and check their destination fields. Use request reference and requested outcome as required inputs; add a needed-by date and the reason it matters. Verify mappings by reading the resulting board item.
Keep assignment and approval under team control. Avoid exposing a People question publicly just to let a requester choose an internal employee. Supplier documentation describes an account-data setting for that question type; changing it needs a deliberate access decision. Do not enable it as an incidental tutorial step.
Run three distinct submissions
Illustrative valid input: DEMO-001, Update the onboarding checklist to include a named delivery owner, requested by the fictional Client A coordinator. Expected result: one item with the reference and outcome intact, waiting for triage.
Illustrative invalid input: omit the requested outcome. Expected result: a useful correction path and no misleading accepted status. Record whether a submission is created and which fields are empty. Then correct the input and observe the result.
Illustrative duplicate: submit DEMO-001 again. Do not assume WorkForms deduplicates it. The delivery lead should identify repeated references and decide which item is authoritative. Keep a pointer and explanation on the duplicate rather than silently treating two submissions as two commitments.
Separate intake from approval and access
Acceptance is a team decision, not a consequence of successful submission. Record the approver, accepted version, decision date and reason for rework. Try a correction after approval and agree whether it reopens review. Start with manual triage; automate only a stable rule with a recovery owner.
Check four roles separately: submitter, form editor, board owner and external reviewer. With synthetic Client A and Client B requests, attempt prohibited direct access as well as normal work. A form’s visibility and its connected board’s visibility are different questions. Record the purchased work-management and WorkForms capabilities before treating a trial feature as included.
Keep an exportable handoff
Use the software pilot plan to record the actual plan, tester, timestamps and observed results. Verify a record outside monday that retains the request, owner, approval and any correction. Document exclusions and how the operational owner would recover the missing information.
Keep evidence of all three submissions, permissions, mappings and approval handling. If an unexpected item appears or a required question does not behave as intended, pause the handoff and investigate the mapping. Use manual review until the team can explain the result and recover a failed or duplicated request.
Explore the options
Sources and scope
The sources below support the feature, price and plan details in this guide. Prices and limits may change; check the actual order and plan.