Hello @cuprico,
I’m pleasantly surprised by the quick and detailed response. I didn’t expect that at all.
I feel a bit bad for being silent for a week. I hope the following can be accepted as an apology: our newborn’s sleeping rhythm is very incompatible with our daily routine. Our first child was just the opposite, but fingers crossed this one will decide to sleep all night soon! 
In addition, the days at work have been quite long this week. 
Anyway, let’s get into the discussion.
I noted that some of my initial questions weren’t as clear as they should have been.
I cannot turn the post into a wiki otherwise I would improve the description and noted what I changed.
I meant QWC - QGIS Webclient (or Lizmap / OpenLayers / MapLibre)
A dedicated discussion is started here: Web portal for sharing survey results with third parties - Ask the Community - QField community
Here is some feedback based on what you wrote.
As soon as the first post is converted into a wiki, I will merge it with the others.
- I detailed what I meant by ‘script templates’, see:
PyQGIS-driven form generation — modular script approach - Advanced Use & Customization - QField community - I took a deep dive into the layer principle of QGIS. That was a bit of a mind blocker. I created a new topic to work through this with a commonly understandable project example, to avoid blowing this discussion with the basics of QGIS.
An attempt at a ‘principle description’ of how to structure a multi-user, callable, collaborative site inspection survey - Ask the Community - QField community - Thers is wish to introduce a multi-user workflow (creation, editing, extension, approval and handling by different roles).
Multi-user workflow for collaborative site surveys with live feedback from the office - Advanced Use & Customization - QField community