"If assumptions are inadequate or absent, then these uncertainties often persist and can drastically impact the analysis outputs" - should also add that if assumptions are inadequate, may impact users' interpretation.
There is no description of the columns related to value of estimated mean or distribution, so this should be added for clarity.
Need to create a html, completable version of the assumptions and decisions log. This will create consistency between all the forms in this documentation repo.
When merging, differences caused by rendering the quarto files create unnecessary merge conflicts which do not need to be reviewed.
Can we put all the files that regenerate each time there is a render into a .gitignore to avoid this happening?
This may be better separated into 2 questions to reduce the risk of any one of these important questions being missed. Under importance, we should also add that analysts should not assume datasets are high quality and should conduct your own quality assurance on the data.
Sample assumptions on quality questions currently not in table format. Needs a table created so these are structured in the same way as the template assumptions log.
Currently documented as a Yes/No response for each question. Suggestion to change this to initials to clarify who has signed it off (particularly if SRO changes during lifecycle of a project)
Additionally, suggestion of some kind of line for commissioner, SRO, and analytical assurer to all confirm they have read this document and agree with the responses.