Mandatory

Mandatory audio micro-course (transcript)

Three short podcasts about “Mandatory”. Listen with the interactive player.

Podcast 1 — Introduction & meaning

Narrator: Mandatory. A word with real authority — and a long history of making things non-negotiable.

Narrator: Mandatory — pronounced MAN-duh-tree — is an adjective meaning required by law, rule, or authority. When something is mandatory, it is compulsory. It is not optional, not suggested, not encouraged. It must be done. Full stop.

Narrator: The word derives from Late Latin mandatorius, which relates to mandatum — a command or order. That Latin root comes from mandare, meaning to order or entrust, itself a compound of manus, meaning hand, and dare, meaning to give. So at the deepest level, mandatory means something that has been placed firmly in your hands and you are required to carry it.

Narrator: Mandatory entered English in the sixteenth century in legal and ecclesiastical contexts — a mandatory was an agent who received a mandate to act on someone's behalf. The adjectival meaning — required by authority — followed naturally, as anything connected to a formal mandate carries the force of obligation.

Narrator: Over time, mandatory shed its strictly legal skin and entered everyday professional and institutional language. Mandatory training. Mandatory fields. Mandatory vaccination. Mandatory retirement age. The word became the standard signal for non-optional requirements across law, medicine, education, HR, and software.

Narrator: In register, mandatory is formal to neutral. It is at home in policy documents, legal texts, workplace guidelines, and technical specifications. In casual conversation you might say you have to or it's required — mandatory carries the tone of official authority.

Narrator: Mandatory. When the word appears, options disappear.

Speaker A: The new data protection training is mandatory for all staff by the end of the month. It came down from HR this morning.

Speaker B: Right — mandatory training always gets that slightly ominous tone in the email, doesn't it. Though I suppose that's the point. It signals you genuinely have no choice.

Speaker A: Exactly. I was going to say it's compulsory, but mandatory felt stronger somehow.

Speaker B: That instinct is correct. Compulsory and mandatory are very close synonyms — both mean required. But mandatory tends to carry more explicit legal or regulatory weight. If something is mandatory, there is usually a rule, a law, or a binding policy behind it. Compulsory is slightly softer in practice, even if technically they overlap.

Speaker A: What about obligatory? I hear that used too.

Speaker B: Obligatory is interesting — it often slides into sarcasm in British English. The obligatory team-building away day. The obligatory disclaimer at the end. It implies something that is formally required but universally dreaded or rolled at. Mandatory doesn't carry that ironic flavour — it's more straight-faced and official.

Speaker A: A common mistake I see is people writing mandatory to mean strongly recommended. Like, attendance is not technically mandatory but we really hope you'll come.

Speaker B: That's a real misuse and it dilutes the word. Mandatory means there are consequences if you don't comply. If there are no consequences, the correct word is expected, encouraged, or recommended. Using mandatory when you mean encouraged is like saying the speed limit is a strong suggestion.

Speaker A: So the word draws a hard line.

Speaker B: It does. Mandatory is the word that locks the door. Everything else leaves it ajar.

Speaker B: Today's word is mandatory. In development prompts, mandatory is one of the most precise constraint words you have. It tells the AI that certain requirements are non-negotiable — not defaults, not best practices, not suggestions. Hard requirements. Five prompts.

Speaker A: So mandatory in a prompt signals the AI that these specific things must appear in the output, no matter what?

Speaker B: Exactly — it removes AI discretion on those points. First prompt — a form with mandatory fields.

Speaker B: PROMPT: Build an HTML registration form. Mandatory fields: full name, email, password, date of birth, and country. Mark each mandatory field with a red asterisk. Block form submission if any mandatory field is empty. Show an error message under each missing field.

Speaker A: Mandatory fields here is a standard UX pattern and using the word directly tells the AI to implement both the visual marker — red asterisk — and the validation logic. The AI won't treat those fields as optional or skip the error handling because mandatory has made the requirement explicit.

Speaker B: Now a database schema with mandatory columns.

Speaker B: PROMPT: Design a PostgreSQL schema for an employee table. Mandatory columns: employee_id as primary key, full_name, email as unique, department_id as foreign key, hired_date, and status. All mandatory columns must have NOT NULL constraints.

Speaker A: Mandatory columns with NOT NULL is a clean, precise instruction. The AI applies the database constraint that mirrors the business rule. Each column listed as mandatory becomes a hard database-level requirement, not just an application-level check.

Speaker B: Now a Vue onboarding wizard where certain steps are mandatory.

Speaker B: PROMPT: Build a Vue multi-step onboarding wizard with five steps. Mandatory steps: Account Setup, Email Verification, and Terms Agreement. Optional steps: Profile Photo and Notification Preferences. Block the Next button on mandatory steps until they are completed. Show a progress bar.

Speaker A: Separating mandatory and optional steps in one prompt tells the AI exactly where to enforce blocking logic and where to allow skipping. The progress bar implies the user can see which steps are required before they start — all from two well-placed words.

Speaker B: Now a Node.js API with mandatory request body fields.

Speaker B: PROMPT: Build a Node.js Express POST endpoint for creating an invoice. Mandatory body fields: client_id, issue_date, due_date, and at least one line_item. Return 400 with a clear error message if any mandatory field is missing. Return the created invoice as JSON on success.

Speaker A: Mandatory body fields with a 400 response is the standard REST validation pattern. The AI builds the validation middleware automatically and knows the error messages need to name the specific missing mandatory field — not just say bad request generically.

Speaker B: Last one — a Next.js settings page where some settings are mandatory system configuration.

Speaker B: PROMPT: Build a Next.js admin settings page. Group settings into two sections: Mandatory System Settings and Optional Preferences. Mandatory settings include database URL, API key, and admin email. Disable the Save button unless all mandatory settings have values. Show a warning badge on the mandatory section if any field is empty.

Speaker A: Splitting the settings page into mandatory and optional sections is a real UX decision — it tells admins which gaps are blocking the system from running. The warning badge and disabled Save button are both implied by mandatory without needing to specify each individually.

Speaker B: The pattern: wherever you use mandatory in a prompt, the AI adds a gate. Validation, blocking, warnings, constraints — mandatory means the AI will enforce, not just suggest.