Undertaking

Podcast 2 — In conversation

Speaker A: The legal sense of undertaking is worth understanding precisely because it has specific consequences that the everyday sense does not. In English law, an undertaking given to a court — a formal promise made by a party to proceedings — is binding and enforceable. Breach of a court undertaking can be treated as contempt of court and may result in a fine or imprisonment. Solicitors routinely give undertakings on behalf of their clients, and the undertaking is considered personally binding on the solicitor giving it. The word undertaking in a legal context is not just strong language — it is a technical term with specific legal force that distinguishes it from ordinary promises.

Speaker B: The use of major undertaking and daunting undertaking in everyday speech is interesting because it reflects the word's implicit scale. When someone describes something as a major undertaking, they are signalling that it requires significant time, effort, resources, and commitment — and often that there is some doubt about whether it will be successfully completed. Moving house is always described as a major undertaking; so is writing a thesis, starting a business, or raising a child. The word carries a slight sense of the heroic — the person who has taken this on has accepted a serious challenge — which is perhaps why it is so frequently paired with major, significant, or daunting.

Speaker A: Undertaking versus enterprise — what is the distinction?

Speaker B: Both describe a significant project or venture, but enterprise carries more energy and commercial ambition. An enterprise implies bold action, commercial initiative, and often the creation of something new — a business enterprise, a spirit of enterprise. An undertaking emphasises the commitment and responsibility dimension more than the boldness — it is about the pledge made as much as the activity itself. A commercial undertaking can sound like a business, while a commercial enterprise sounds like an adventure. Undertaking is more sober and duty-bound; enterprise is more adventurous and energetic. In project language, undertaking is the more formal and procedural word.

Speaker A: What is a common mistake about undertaking in the legal sense?

Speaker B: Treating it as an ordinary promise or statement of intent rather than as a formal binding obligation. In non-legal conversation, I give you my undertaking that this will be done sounds emphatic but not technically distinct from a strong promise. In a legal context — particularly in writing, in correspondence between solicitors, or in court proceedings — the word undertaking signals a specific type of binding commitment with legal consequences for breach. Using undertaking casually in a legal context, or failing to appreciate the binding nature of an undertaking given in correspondence, is a mistake with potentially serious consequences. In legal writing, if you do not mean to be bound, do not use the word undertaking.

Speaker A: Any close synonyms?

Speaker B: For the task or project sense — enterprise, venture, project, endeavour, and initiative are all close. Endeavour emphasises the effort and determination involved. Venture implies risk and boldness. Initiative emphasises the originating action. For the formal promise sense — pledge, commitment, guarantee, and assurance are close, but all are less legally specific than undertaking. Covenant is a more elevated, often religious or contractual term for a binding commitment. For the funeral business sense — funeral service, funeral direction. Undertaking is the most formal of the project-sense synonyms and the most legally specific of the promise-sense synonyms.

Podcast 3 — Prompt engineering

Speaker B: Welcome to the workshop. Today we prompt AI using the word undertaking — building the project scoping and commitment systems, formal obligation managers, enterprise initiative trackers, large-scale work planning tools, and binding agreement platforms that handle everything from the first formal commitment to the final delivery of a significant piece of work.

Speaker A: So undertaking tells the AI to build the formal-commitment and large-project management systems — the initiative trackers that manage company-wide undertakings from proposal through delivery, the legal obligation platforms that store and monitor formal undertakings made to courts or regulators, and the project scoping tools that define and document exactly what has been committed to?

Speaker B: Exactly. It signals significant enterprise management, formal obligation tracking, and large-scope project governance. Let me start with an initiative scope and commitment platform.

Build a strategic initiative scoping and commitment platform: allow executives to define strategic undertakings with a formal scope statement, success criteria, resource requirements, key milestones, and the sponsoring executive. Require a formal approval step before an undertaking is activated. Track each undertaking through initiation, planning, execution, and closure phases. Compute a health score for each active undertaking based on milestone completion rate, budget consumption relative to progress, and risk count. Generate a quarterly executive report showing the health and progress of all active strategic undertakings.

Speaker B: Initiative platform defines undertakings with scope-success-criteria-resources-milestones-sponsor, requires formal approval before activation, tracks through initiation-planning-execution-closure phases, computes a health score from milestone rate-budget-risk count, and generates quarterly executive reports — the AI builds the scope definer, the approval gate, the phase tracker, the health scorer, and the executive reporter.

Speaker A: Computing a health score from multiple dimensions — milestone completion rate, budget consumption relative to progress, and risk count — rather than using a single metric is the multi-signal undertaking health assessment: a project on schedule but severely over budget, or on budget but with a high open-risk count, is not healthy despite performing well on one dimension; the composite score surfaces undertakings that are struggling on any of the key dimensions.

Speaker B: Multi-dimension health score as the single-metric gaming prevention and comprehensive undertaking health surface tool. Now the formal obligation schema.

Design a formal legal undertaking and obligation management schema: an undertakings table recording each formal undertaking with an ID, the giving party, the receiving party, the undertaking text, the date given, the jurisdiction, the source as court order, regulator, or contract, the expiry date if applicable, and the current compliance status as active, complied, breached, or expired. A compliance_evidence table recording each piece of evidence of compliance with the undertaking ID, the evidence type, a description, the submitted by user ID, and the submission timestamp. An undertaking_reviews table recording each periodic review of an undertaking with the status at review, any actions required, the reviewer, and the review date. A compliance_status_view showing per-undertaking the latest compliance evidence date, the latest review date, and whether any review is overdue.

Speaker B: Legal undertaking schema stores formal undertakings with jurisdiction and source and compliance status, compliance evidence records, periodic review records with actions required, and a status view with latest evidence and review dates and overdue review flags — the AI builds the four-table schema.

Speaker A: Recording the source of each undertaking — whether it originated from a court order, a regulator, or a contract — is the consequence-calibration context that shapes how breaches are managed: a breach of a regulatory undertaking may trigger supervisory action; a breach of a court undertaking may constitute contempt; a breach of a contractual undertaking may trigger a damages claim; the source field ensures the appropriate escalation path is followed.

Speaker B: Undertaking source as the breach-consequence escalation-path selection context field. Next, the large project planning interface.

Design a large-scale project planning and decomposition interface: allow project managers to define a major undertaking at the top level and then break it down into phases, workstreams, and individual work packages. Display the full work breakdown structure as an expandable tree. Allow assigning owners, effort estimates, and dependencies to each work package. Visualise the critical path through the project. Show a progress rollup from work packages up through workstreams to the overall undertaking. Allow the project manager to flag any work package as at risk with a reason.

Speaker B: Large project planning interface shows an expandable work breakdown structure tree, assignment of owners-effort-dependencies per work package, critical path visualisation, bottom-up progress rollup to the undertaking level, and at-risk flagging with reasons — the AI builds the tree viewer, the work package editor, the critical path renderer, the progress rollup, and the risk flag.

Speaker A: The progress rollup from work packages through workstreams to the overall undertaking — aggregating completion status bottom-up through the hierarchy — is the accurate top-level status mechanism: reporting the overall undertaking as forty percent complete should reflect the actual completion of the component work packages, not a subjective impression; the bottom-up rollup ensures that the top-level status is derived from ground-truth progress rather than from optimistic estimates.

Speaker B: Bottom-up work-package rollup as the ground-truth-derived rather than optimistic-impression top-level status mechanism. On to vendor commitment management.

Create a vendor and supplier commitment tracking system: record the formal undertakings made by each supplier in their contracts — delivery dates, quality standards, service levels, and compliance obligations. Monitor each supplier's performance against their undertaken commitments. Alert procurement teams when a supplier misses a commitment or is at risk of doing so. Track the history of each supplier's commitment fulfilment rate over time. Generate a supplier scorecard showing commitment fulfilment rates, breach counts, and overall reliability rating for use in contract renewals.

Speaker B: Supplier commitment tracker records contracted undertakings by type, monitors performance against them, alerts on misses and at-risk commitments, tracks fulfilment rate history, and generates scorecards with breach counts and reliability ratings for renewals — the AI builds the commitment recorder, the performance monitor, the at-risk alert, the history tracker, and the scorecard generator.

Speaker A: Tracking the history of each supplier's commitment fulfilment rate over time — not just their current performance — is the contract renewal intelligence tool: a supplier who has fulfilled ninety-five percent of their commitments over three years is a very different proposition from one who has fulfilled ninety-five percent in the last quarter after two years of poor performance; the historical trend reveals the pattern, not just the snapshot.

Speaker B: Historical fulfilment rate trend as the contract-renewal trend-versus-snapshot intelligence mechanism. Now something whole.

Build a transformation programme management platform: manage a company-wide digital transformation as a portfolio of undertakings — each with a business case, sponsoring executive, cross-functional team, budget, and timeline. Support benefits realisation tracking — measuring whether the promised benefits of each undertaking are being achieved post-delivery. Generate a monthly transformation board report. Track interdependencies across the undertakings. Provide a benefits realisation scorecard showing planned versus actual benefits for completed undertakings.

Speaker B: Transformation programme platform manages business-case-sponsored-budget undertakings, tracks benefits realisation post-delivery, generates monthly board reports, manages cross-undertaking interdependencies, and provides planned-versus-actual benefits scorecards — the AI builds the full transformation programme management system.

Speaker A: Benefits realisation tracking — measuring whether the promised benefits of each undertaking are actually achieved after delivery — closes the accountability loop that most project management systems leave open: projects are typically measured on delivery of outputs — features, systems, processes — but the original business case was justified by outcomes — cost savings, revenue growth, efficiency gains; benefits realisation tracking holds the undertaking accountable to the outcome promise, not just the output.

Speaker B: Benefits realisation as the output-delivery-to-outcome-accountability loop closure mechanism. Last one — work breakdown API.

Write a project work breakdown and estimation API: accept a plain-text description of a significant undertaking. Use AI to decompose the undertaking into phases and work packages, estimating the effort in days for each work package and identifying key dependencies between them. Return a structured work breakdown with effort estimates, a suggested timeline based on a configurable team size, and the critical path. Flag high-uncertainty work packages — those where the estimate range is large — for special planning attention.

Speaker B: Work breakdown API accepts undertaking descriptions, decomposes into phases and work packages with effort estimates and dependency identification, returns structured breakdowns with timelines for configurable team sizes, critical path analysis, and high-uncertainty work package flags — the AI builds the decomposer, the estimator, the dependency mapper, the timeline calculator, the critical path finder, and the uncertainty flagger.

Speaker A: Flagging high-uncertainty work packages — those where the estimate range is large relative to the point estimate — is the planning risk surface tool: a work package estimated at anywhere from two days to three weeks is not the same as one estimated consistently at four days; the high uncertainty flag tells the planning team where to invest additional discovery effort before committing to a fixed timeline.

Speaker B: That is the goal — one committed word, better-managed formal undertakings and project governance systems. Keep it in your kit.