How do you build a better form over a SharePoint list?

What the default form does and doesn’t do

A SharePoint list form is generated from the columns. It shows all of them, in column order, with the validation the column type happens to provide.

That’s adequate for a list three people maintain. It fails the moment the form is filled in by someone who doesn’t know the list, because everything that makes a form usable is missing:

• No conditional fields, so a person answering “no” still sees the eight questions that only matter if they said yes
• No cross-field rules, so “end date before start date” saves happily
• Attachments land on the item but with no indication of what was expected
• No guidance text beyond a column description nobody reads

The result isn’t that people can’t use it. It’s that the data arrives wrong, and somebody spends their week correcting it.

Clean at capture beats clean-up later

This is the whole argument. A correction made after the fact costs more than the field would have cost to get right, and it never catches everything.

It’s also the difference between a list an assistant can answer questions from and one it can’t. A date column containing “ASAP” isn’t a date, and no amount of grounding fixes it.

Three ways up, in order of effort

1. Column formatting and list validation. JSON in the column settings, plus a list-level validation formula. Free, immediate, and enough for cross-field rules like “end after start”. It can’t hide a field.

2. Conditional field logic in the form. SharePoint supports show-and-hide formulas per field on the default form. Under-used, and it solves the largest single complaint — eight irrelevant questions — without leaving the list.

3. A purpose-built form. Needed when the form has to be mobile-first, multilingual, or has to write to more than one place. This is where a guided wizard earns its keep: EPP Law’s claims intake replaced a paper form with one, and it runs in three languages.

When Power Apps is the wrong answer

Power Apps is the default recommendation and it’s often too much. It’s right when the form is an application — offline capture, complex logic, a different interface per role. It’s wrong when you needed to hide four fields and add a date rule, because you have now taken on a second thing to maintain and licence.

Ask what the form has to do that a formatted list form can’t. If the answer is a sentence, you don’t need Power Apps.

Where to start

Forms is the narrow version: conditional fields, validation and attachments over a SharePoint list, writing straight to it. It is ready — ask for it on the page and we’ll send the package and the setup notes.

If the form is one step in a process with owners, states and reminders, the form isn’t the project — the register behind it is, and that’s Custom Operational Apps.