Chapter 38 — Capstone implementation
Lesson map
Lesson 38 published. Map, example, EX112.
flowchart TD
N0["Learning outcomes"]
N1["38.1 Building"]
N2["38.2 Linking parents"]
N3["38.3 Staged rollout"]
N4["38.4 Expanding"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5
N5 --> EX["Worked example"]
EX --> Q["Exercise EX112"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["38.1 Building"]
N2["38.2 Linking parents"]
N3["38.3 Staged rollout"]
N4["38.4 Expanding"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX112"]
[Learning outcomes]
|
v
[38.1 Building]
|
v
[38.2 Linking parents]
|
v
[38.3 Staged rollout]
|
v
[38.4 Expanding]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX112]
Learning outcomes
You will (1) implement the parent portal with privacy controls; (2) roll out in stages; (3) handle problems during rollout.
38.1 Building
Elena works with the trust's IT manager and a vendor to configure the parent portal. Parents authenticate with an account linked to their child; reports are uploaded by staff and visible only to linked parents. Access is logged. Documents expire after the school year. She configures the system with synthetic families first and tests each role. The DPIA is approved before any real data are used. Each role is tested first. Staff accounts use single sign-on. Roles mirror school staff structures.
38.2 Linking parents
Linking parents to children is the hardest part. Errors could show one family's report to another. Elena designs a process: the school office verifies identity and sends a one-time code by post to the address on record. Separated parents are linked according to the legal information held by the school. She tests the process with synthetic cases including complex family situations, which reveal two edge cases she fixes. Each link is checked against school records. Separated parents are handled carefully. Errors are rare.
38.3 Staged rollout
Elena rolls out to two schools first. In the first month 78% of parents activate accounts. Staff report that uploading is faster than emailing. Three parents without internet receive printed copies. One linking error is caught before any report is shared because the parent notices an unfamiliar child name and reports it. Elena traces the error to a typing mistake and adds a confirmation step for office staff. One school starts first. Feedback shapes the next school. One error is caught early.
38.4 Expanding
After fixes, the portal rolls out to all twelve schools. Elena monitors activation, support requests and any emails of reports still being sent. She finds a few staff still emailing reports and contacts them to understand why: they did not know how to upload large files. She arranges help. She learns that implementation is mostly about people and processes, with technology as the easier part. Staff guides help the most. Help desks run at drop-off times. Staff ask good questions.
Worked example
Elena configures the portal, designs postal-code linking for parents, rolls out to two schools (78% activation, one linking error caught and fixed) and expands to all twelve schools.
Synthetic case. The portal and rollout are synthetic.
Errors and limits
Postal codes delay activation; balance security with convenience.
Exercises
- EX112 — Linking process. How are parents linked to children? Rubric: 3 = office identity check and a one-time code posted to the recorded address;; 2 = one part;; 1 = self-registration;; 0 = none.
- EX113 — Linking error. How was the linking error caught and fixed? Rubric: 3 = a parent saw an unfamiliar name; a confirmation step was added;; 2 = one part;; 1 = vague;; 0 = none.
- EX114 — Remaining emails. Why did some staff still email reports? Rubric: 3 = they did not know how to upload large files;; 2 = mentions training;; 1 = refused;; 0 = none.
Synthesis
Chapter 38 implements the portal. Chapter 39 evaluates it.
Continue studying — chapter 38 of 40
← Chapter 37 (draft) · Course chapter index · Chapter 39 (draft) →