Compare the rule with concrete cases
Fictional frequency settings use project override first, then branch override, then organisation default. Organisation is weekly; branch is daily. P1 has no override and P2 explicitly chooses twice-weekly. Missing an override means continue up the hierarchy, not return an empty frequency.
| Project | Project override | Branch / organisation | Effective frequency |
|---|---|---|---|
| P1 | None | Daily / weekly | Daily |
| P2 | Twice-weekly | Daily / weekly | Twice-weekly |
| P3 | None | No branch override / weekly | Weekly |
Work through the distinction
Record both the effective value and which level supplied it when explaining a result. An explicit project value wins regardless of a later branch change.
P1’s branch override is removed. What frequency does P1 use?
Show the worked answer
Weekly, from the organisation default. P1 has no project override and now no branch override.
Acceptance wording to adapt
Resolve project, branch, then organisation in that order, taking the first explicit frequency. If project and branch lack overrides, return the organisation default and its source label.