The first problem that needs fixing is that you have the calculate fields running off fields that have relevant conditions.
For example, your calculation for row 57 (clustered_monarchs) is: ${cluster_1_monarchs_in_cluster}+${cluster_2_monarchs_in_cluster}+${cluster_3_monarchs_in_cluster}.
But ${cluster_2_monarchs_in_cluster} and ${cluster_3_monarchs_in_cluster} both have relevant conditions.
When the relevant conditions for a field are not met, the value of the field is set to null. What that means for your form is that when an observer only records a single cluster, the calculation for (clustered_monarchs) is:
${cluster_1_monarchs_in_cluster}+null+null.
because both the latter two values are set to null due to being not relevant.
Of course ${cluster_1_monarchs_in_cluster}+null+null can't yield a valid integer result, so it returns a null - the empty field that you are seeing.
So the first thing to do is change the fields from being relevant under those condition to being visible under those conditions. In connect you just need to move all of those [relevant] calculations to the [bind::esri:fieldType] column. That way the fields are hidden under the same conditions, but not set to null.
Not sure how to do this is the web designer.
Once you have made that change, let us know how it goes. That will probably solve the problem.
FWIW, there are quite a few other things that have been done in this survey that I wouldn't recommend.
The three cascading relevant/visible fields for the various observations seems to be essentially a way to avoid using a repeat. But unless there is a good reason not to use the repeat function, that would be far neater and less error prone. It would also allow any number of observations, rather than being restricted to three.
I'm also not a big fan of assigning "question" field types like 'integer' and then setting them to 'read only' as you have done for your Grand Total fields. Since they are effectively just notes, you're usually better off assigning them as the 'note' type notes, and then setting the [bind::esri:fieldType] or [bind::type] to whatever format you want.
