Forms Modernization

Form	Library	Submissions / yr	Rules	Repeating	Workflow steps	Score	Target	Status

Click a form to see why it was triaged that way.

The score is rules + 2 × repeating sections + workflow steps + 3 if it needs signatures. The rule, not opinion, picks the target. Owners can override with a reason, and the reason is recorded.

Vessel Boarding Reportreplaced InfoPath template VBR-7 · rev 2

Boarding

Boarding officer

Date and time

Vessel name

Vessel type

Safety items checked

Item	Result	Notes

Deficiency details (shown because an item failed)

Corrective action due

Follow-up required

Acknowledgment

I certify that this report is accurate. Signed as the signed-in identity with a timestamp and a snapshot of the submitted values; the item is read-only after sign-off. This replaces the InfoPath digital signature.

Draft · not submitted

How a form gets its target

No submissions in 24 months → retire, with the owner's signature. Nothing is rebuilt that nobody uses.
Score under 4 (a few fields, no branching, no approval) → Microsoft Lists with a customized form. Zero code, owner maintains it.
Score 4 to 11, or any repeating table, branching rule or single-path approval → canvas app over SharePoint, built from the component library, workflow rebuilt in Power Automate.
Score 12 or more, nested repeating sections, more than one related entity, role-based stages, or audit requirements → model-driven app on Dataverse with a business process flow.
Any signed form → acknowledgment block plus version lock, reviewed by counsel once and reused.

Why a rule and not a judgment call

Over a hundred forms and a dozen owners. A rule that the owners agreed to up front means every decision is explainable, the same question gets the same answer in month nine as in month one, and arguments are about the inputs, not the outcome.