How to Decide Which Fields Should Be Required

Deciding which fields should be required is a balance. Too few and records arrive incomplete; too many and people enter something arbitrary just to proceed.

What over-requiring produces

A mandatory field someone cannot answer honestly will be answered dishonestly.

Placeholder values entered to get past a form
Guessed data that looks real and is not
Abandoned submissions when nothing fits
Data quality worse than if the field had been optional

A rule for each case

Field type	Require it when
Routing field	Always — the cost centre determines who approves
ERP-mandated field	Always — the entry cannot post without it
Status	Always — a record without one has no state
Generated identifier	Never — it fills itself
Context field	Only when the process genuinely cannot proceed

How to configure it in Jestor

Mark as required in Jestor every field your ERP needs for the entry to post.
Make the cost center required, since it determines routing.
Leave sequential IDs unmarked — they generate automatically on creation.
Use conditionals so a field is required only in the cases where it applies.
Review blank columns in the table view to find fields nobody is filling.

Why choose Jestor for data discipline?

Jestor lets conditionals control when a field appears at all, which is usually better than making something mandatory for everyone — the question simply does not exist for people it does not apply to.

Scanning the table view for consistently blank columns is the fastest way to find fields that should either be removed or made conditional.

Frequently Asked Questions

Should a sequential ID be required?

No, it generates automatically. See jestor.com.

Can a field be required only sometimes?

Yes, using conditionals tied to another answer.

How do I find useless fields?

Look for columns that are consistently blank.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,