STEP 01
Define typed fields
Use text, number, percentage, date, yes/no, and controlled choice fields for data the company wants to filter.
Make Woodsystems speak the language of your shop
Track species, finish, rooms, site conditions, selections, and checklists as usable job data.
Why it matters
Notes can hold information; they cannot reliably run a process
For experienced shops with a proven process that generic job records cannot hold.
01
Repeated values are entered with inconsistent spelling.
02
Important facts cannot be filtered or reported.
03
Printed job forms go stale.
04
Checklist fields lack an owner and due date.
How it works
Use facts for facts and process for process
STEP 02
Build the form
Create reusable sections, fields, checkboxes, and repeating groups for the working job document.
STEP 03
Assign responsibility
Give form work an owner, due date, completion state, or supported status.
STEP 04
Use the data
Bring structured custom values into sheets and reports instead of retyping them.
Questions buyers ask
Straight answers, before the demo.
What is the difference between a custom field and a job form?+
A custom field stores a reportable fact about the job. A job form is a working document with sections and process-oriented fields.
Can custom values appear in reports?+
Yes. Supported custom fields can be used in sheets and reporting.
Can form items be assigned?+
Yes. Supported job-form fields can carry responsibility, due dates, and completion state.
See it in action