Make Woodsystems speak the language of your shop

Track species, finish, rooms, site conditions, selections, and checklists as usable job data.

Custom fields and a working form on a Woodsystems job

Notes can hold information; they cannot reliably run a process

For experienced shops with a proven process that generic job records cannot hold.

1

Repeated values are entered with inconsistent spelling.

2

Important facts cannot be filtered or reported.

3

Printed job forms go stale.

4

Checklist fields lack an owner and due date.

Use facts for facts and process for process

Define typed fields

Use text, number, percentage, date, yes/no, and controlled choice fields for data the company wants to filter.

Build the form

Create reusable sections, fields, checkboxes, and repeating groups for the working job document.

Assign responsibility

Give form work an owner, due date, completion state, or supported status.

Use the data

Bring structured custom values into sheets and reports instead of retyping them.

Questions shops ask us

What is the difference between a custom field and a job form?+

A custom field stores one reportable fact about the job, such as species or finish. A job form is a working document with sections, checkboxes and repeating groups, such as a room-by-room site survey.

Can custom values appear in reports and sheets?+

Yes. Custom fields are columns in sheets and filters and groupings in the report builder.

Can form items be assigned?+

Yes. A form field can carry an owner, a due date and a completion state, so a form runs a process rather than recording one.

Can a form repeat a section?+

Yes. Repeating groups let one form cover every room, every elevation or every cabinet run.

Can automations use custom fields?+

Yes. A rule's conditions can read them.

See it on your own jobs.