The Modeling Room: (M1) Discover one event - (A2) Find the event
Series: The Modeling Room, module 1, article 2 of 26. Separate the actions around one repair job, then choose the action that supplies actual labor hours. You leave with an event clause carrying candidate actions, included and excluded stories, and a named source check.
Who should read it?
Students learning modelstorming, analysts, report builders, data modelers working with business experts
Prerequisite
A reporting question that names its quantity, groupings, and date meaning, as in article 1.
Learning objective
Discover the measurable business event behind a reporting question.
Artifact
An event clause with candidate actions, inclusion tests, and a named source check.
Why this matters
Alex Morgan calls everything from drop-off to payment "a repair”. A report built on that word can count arrivals, estimates, and payments as if they were work. The totals still add up and the answer is wrong.
This lesson finds the one action your report must describe.
What you'll learn
- How to separate the actions around one repair job and choose the action that supplies the quantity the report asks for.
- How to defend that choice with included and excluded example stories and a named source check.
Your output: an event clause with candidate actions, inclusion tests, and a named source check.
New terms: business event, main clause, data story.
The one idea
A report question hides one action. A business process connects work over time, such as handling a repair job from arrival to collection. Within it, a business event is an activity or observation worth analyzing.
Name it with a main clause, a short subject-verb-object sentence: in "mechanic performs service”, the mechanic acts, performs says what happens, and service names what it concerns.
The verb decides which evidence the report needs.
A clause in present tense is a pattern.
A concrete occurrence with actual values is a data story.
A report sentence hides one action; the main clause names what happened.