Reviewing reports while using Rico can be a little different to what you’re used to. This post outlines the options for reviewing reports while using Rico and things to be conscious of with each approach.
Reviewing reports on Rico
Rico accommodates a relatively simple review process. We suggest the following if you’re reviewing reports in Rico:
All changes made in Rico are automatically saved as you go. This is something to be conscious of as you won't be asked to save at the end of a session like when using some other software (e.g. MS Word). You also aren't able to revert back to before your changes are made. We suggest you make any suggested changes in highlighted text and add a ‘TODO’ to the section to flag where changes have been made. This clearly identifies any changes you've made and flags this for others to see so these changes can then be incorporated into a report by the author.
Use an in-browser spell check such as Grammarly to detect spelling and grammar mistakes. We also recommend this is used by those writing reports. We’ve made a post for setting this up here.
Use the Output Preview to read through reports and click the link icons to jump into a given section and make any corrections to text.
Reviewing reports off Rico
If you prefer to review reports off Rico (such as in MS Word), we suggest the following:
It’s fine to output as many reports from Rico as you like for a given project.
Changes made off Rico obviously won’t update in Rico. We suggest that you update any text changes made to reports in Rico as you may need to output another report in the future and any changes not carried over will be out of date. In general, it’s strongly recommended that the only changes made between Rico and the report you submit to Council are those which can’t be made in Rico, such as presentation changes like adding your own pictures or minor formatting changes.