Component reports

Option	Description
Overwrite comparisons on component report if applicable	When saving component reports, check the comparison between the benchmark property and the analysis. If the comparison is either empty or contains one of the standard comparisons, the system will replace the comparison if it has changed.
Always use the component’s current valuer instead of last year’s when rolling forward	When rolling last year’s report information forward, uses the component’s verification valuer. Otherwise, retains last year’s verification valuer.
Which value to compare against the subject property's land value	Choose whether you want the system to compare the subject property's land value against the analysis' future land value, or the adjusted land value when coming up with comparison text.
Benchmark / analysis comparison type	When performing a bulk linking of sales to benchmarks, automatically generate one of the given types of comparisons: Don't generate comparisons A one-word comparison will be one of Superior, Comparable or Inferior where Superior and Inferior represent a +/- 3% difference in land value from the benchmark property. See Bulk linking of sales to benchmarks. A long comparison without mentioning the analysed or future land value. A long comparison which will be of the form: Size comparison sized, property size block, situated on street name in suburb. Zoned property zone. Adjusted land value of value or rate/area. Overall the sale is considered comparison text to the benchmark. A template comparison. A template comparison is generated according to the default template defined for the 'BM - analysis comparison' template type. See Comparison templates.
Redo comparisons to benchmarks when either benchmark future values or supporting adjusted LVs change	Obvious.
Regenerate BM/AID comparison during market data export	If this box is ticked, running the market data export will generate the benchmark / analysis comparison text for each pairing. If the generated comparison is different to what's stored, the comparison will be updated and saved and the system will emit a warning in the export log. The freshly generated comparison will be used in the market data file. This does not affect the Fixed comparison.
Include 6A(1) FSR and building height in benchmark commentary and comparisons	Obvious.
Include frontages in benchmark comparisons	When this box is ticked, text similar to the following will be included in comparisons: "with a [narrower|slightly narrower|similar|slightly wider|wider] [frontage length] m frontage.
Minimum comparison length (0 = check not applied)	If the comparison between a benchmark and linked analysis does not exceed the nominated length, the market data file will include an integrity check.
Lock old component reports	Tick this box to prevent people editing historical component reports.
Include supervising valuer on component report PDF	Tick this box to include the name and signature for the supervising (or assisting) valuer on the component report.
Include the valuer's supervisor as the supervising valuer on a component report by default	Tick this box to have the system automatically populate a component report's Supervising valuer field with the valuer's supervisor.
Hide the component valuer and review date on the component list	Tick this box to hide the Comp valr and Reviewed columns on the component report listing.
Store the fixed comparison on the analysis instead of the component report	Tick this box to make all instances of a particular analysis used as support for a benchmark use the same fixed comment.