Chapter 23 — Regulatory returns
Lesson map
Lesson 23 published. Map, example, EX067.
flowchart TD
N0["Learning outcomes"]
N1["23.1 The return"]
N2["23.2 Documenting calculations"]
N3["23.3 Checks"]
N4["23.4 Sign-off"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX067"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["23.1 The return"]
N2["23.2 Documenting calculations"]
N3["23.3 Checks"]
N4["23.4 Sign-off"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX067"]
[Learning outcomes]
|
v
[23.1 The return]
|
v
[23.2 Documenting calculations]
|
v
[23.3 Checks]
|
v
[23.4 Sign-off]
|
v
[Worked example] --> [Exercise EX067]
Learning outcomes
You will (1) prepare data for regulatory returns; (2) document calculations and checks; (3) support sign-off by owners.
23.1 The return
Calder Valley submits an annual return to its regulator including repair performance, safety compliance and tenant satisfaction. Ravi helps prepare the repair figures. He reads the regulator's definitions carefully and compares them with Calder Valley's own measures. He finds that the regulator counts repairs by the date of completion within the year, while Calder Valley's internal reports count by the date raised. He adjusts the calculation for the return to match the regulator's definition. He records the reason for the difference in the calculation note.
23.2 Documenting calculations
Ravi writes a calculation note for each figure in the return: the definition, the source tables, filters, the script used, the result and the checks performed. He saves the script version used in the repository with a tag for the return year. He explains that documentation lets the owner and auditors verify the figures, and allows next year's preparer to repeat the method consistently even if Ravi has moved on. The owner reads every note before the return is prepared, and asks two questions that lead to clearer wording.
23.3 Checks
Before sign-off, Ravi runs checks: totals reconcile with monthly reports adjusted for the definition difference, no jobs are counted twice and figures are within expected ranges compared with last year. One figure differs substantially from last year. Investigation shows that a contractor's jobs were missing from last year's return because of a loading failure. The owner decides to note the error in this year's return rather than ignore it. The regulator's guidance allows corrections of this kind, and the owner explains the cause and the fix in a short covering note.
23.4 Sign-off
The head of repairs, as owner, signs off the figures after reviewing the calculation notes and check results. Ravi prepares a short summary of any judgements made, such as how unknown completion times were treated. Ms. Moreau notes that the owner signs because they are accountable, and that technologists support sign-off by making evidence clear rather than asking owners simply to trust the numbers they are given. The owner signs the return after a meeting in which Ravi walks through each note, and the signed copy is filed with the evidence for future reference.
Worked example
Ravi aligns the return with the regulator's completion-date definition, documents calculations with tagged scripts, finds last year's missing contractor jobs during checks and supports owner sign-off with clear evidence.
Synthetic case. The return is synthetic.
Errors and limits
Using internal definitions for regulatory figures misreports performance.
Exercises
- EX067 — Definition difference. How did definitions differ? Rubric: 3 = completion date versus date raised;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX068 — Year difference cause. What explained the change from last year? Rubric: 3 = a contractor's jobs missing from last year;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX069 — Signing owner. Who signs off the repair figures? Rubric: 3 = the head of repairs;; 2 = partly correct;; 1 = other;; 0 = none.
Continue studying — lesson 23 (chapter 23 of 30)
← Chapter 22 · Course chapter index · Chapter 24 →
Continue to the next authored lesson.