CISI Global Operations Management Case Study: How to Structure Written Answers

Table of Contents

• • Start with the requirement, not the story
• • Build an issue-and-evidence map
• • Develop every point from risk to action
• • Worked example: turn an observation into management analysis
• • Use a reusable report or memorandum skeleton
• • Write for the requested professional audience
• • Manage time across Sections B and C
• • Self-review a written answer without inventing a pass mark
• • Keep current without losing syllabus control
• • Final takeaway

The CISI Global Operations Management case study tests whether you can turn a dense operational scenario into clear management analysis. Section B is worth 35% of the three-hour paper, while Section C can require reports, memoranda or letters. In both, technical knowledge becomes useful only when it is connected to the evidence, consequence and decision.

Quick answer: structure each developed point as issue, evidence, operational or regulatory consequence, control assessment, recommendation and follow-up. Group related points under issue-led headings and prioritise them using the requirement and available marks.

Start with the requirement, not the story

Read the question before annotating the scenario. Identify the action verb—explain, assess, evaluate, recommend—and the intended audience. A request to identify regulatory weaknesses is different from a request to decide whether a service provider should be approved.

Convert each requirement into a working question. What is wrong? Why does it matter? Which control failed? What should management do, and how will it know the action worked? This creates a usable answer plan and stops you from copying interesting facts that do not answer the question.

Use the marks to set depth. If a subpart carries 15 marks, a small number of fully developed points is usually more defensible than an indiscriminate list. Leave room for distinctions the question makes, such as regulatory concerns versus wider operational concerns.

Build an issue-and-evidence map

For each material fact, record the issue it supports. A trader able to execute and settle the same transaction suggests weak segregation of duties. Confidential material left on desks suggests information-security and conduct exposure. A recovery site close to the primary office raises correlated-location risk even when the technology looks impressive.

Then connect the issue to the relevant GOM areas. One fact may touch Trading, Settlement and Clearing, Regulation and Compliance, and Risk Governance. This cross-syllabus reasoning is more valuable than labelling the fact with one chapter title.

Distinguish evidence from assumption. If the scenario proves an access-right conflict, say so. If the information merely suggests weak governance, identify what further evidence is needed. Professional judgement includes knowing when not to claim certainty.

The scenarios above are answer-planning exercises. They are not official CISI questions, a predicted GOM paper or an automated grade for narrative writing.

Develop every point from risk to action

A complete analytical point can follow six steps:

1. identify the issue precisely;
2. cite the relevant scenario evidence;
3. explain operational, client, financial or regulatory consequences;
4. assess the existing or missing control;
5. recommend a proportionate action;
6. state ownership, priority, evidence or monitoring where the facts support it.

Avoid recommendations such as “improve controls.” Specify the action: remove incompatible access, introduce independent approval, reconcile positions daily, test recovery capacity under a relevant scenario, strengthen contractual oversight or obtain independently selected due-diligence evidence.

Prioritise immediate containment before long-term redesign when an exposure is live. A reconciliation break may require investigation and escalation now, followed by process remediation, automation and trend monitoring. This sequence demonstrates operational practicality.

Worked example: turn an observation into management analysis

Assume a scenario says: aged settlement breaks are reviewed weekly, the queue has no named owner and management information reports only the total number of breaks.

Weak response: “The firm should improve its settlement controls and review breaks more often.”

That response notices a problem but does not show why the evidence matters or what management should implement.

Stronger response plan:

• Issue and evidence: weekly review, aged items and no named owner indicate weak exception governance and delayed escalation.
• Consequences: unresolved breaks can create failed settlement, liquidity and counterparty exposure, client detriment, inaccurate records, costs and potential reporting or control breaches.
• Immediate action: reconcile the population, prioritise high-value and time-critical breaks, assign accountable owners and escalate material exposure.
• Control redesign: introduce daily age-and-value reporting, reason codes, service thresholds and documented escalation routes, supported by independent review.
• Evidence and monitoring: management information should show value, age, market, cause, owner, expected resolution and recurrence trend; management should test whether aged breaks fall after remediation.

The stronger plan is not better because it is longer. It earns its length by connecting the fact to consequence, action, ownership and evidence.

Use a reusable report or memorandum skeleton

Adapt the structure to the actual requirement rather than reproducing it mechanically:

1. To, from, date and subject where a memorandum is requested.
2. Purpose and scope stating the decision or problem addressed.
3. Executive conclusion summarising the most material finding and recommended direction.
4. Issue-led findings linking evidence to operational and regulatory consequences.
5. Prioritised recommendations separating immediate containment from longer-term remediation.
6. Ownership and timetable identifying responsible functions, dependencies and escalation.
7. Monitoring and follow-up stating the evidence or metrics needed to confirm effectiveness.

Do not spend disproportionate time decorating the format. The skeleton should make the analysis easier to follow, not replace technical content.

Write for the requested professional audience

If the question asks for a memorandum, report or letter, use that form. A report to an operations committee can use a concise purpose, executive conclusion, issue-led findings, recommendations and next steps. A memorandum should orient the recipient quickly and make the requested decision visible.

Headings should reflect decisions: access and segregation risk, settlement-control failure, third-party assurance, resilience exposure or required remediation. Do not use workbook chapter names unless they genuinely help the reader.

Make conclusions distinct from recommendations. A conclusion explains what the evidence means; a recommendation states what management should do. Conditional recommendations are appropriate when approval depends on remediation, evidence or a defined threshold.

Manage time across Sections B and C

The official weightings imply a first-pass time budget of roughly 63 minutes for Section B and 72 minutes for Section C across both selected answers, before a review margin and adjustment to the actual marks. Spend part of that time planning; a clear structure reduces repetition and omitted requirements.

For Section C, select questions by your ability to answer every part, not by one familiar keyword. Sketch headings and supporting points for more than one option before committing. If a topical issue appears, apply it to operational decisions, controls, costs and risks rather than describing the news generally.

Reserve review time to check that every subpart is answered, the professional format is visible and recommendations follow from the analysis. Remove unsupported absolutes and add missing consequences or actions where time permits.

Self-review a written answer without inventing a pass mark

CISI does not publish an explicit GOM pass mark, so a private rubric should diagnose answer quality rather than claim to predict the result. Score each dimension 0, 1 or 2:

Dimension	0	1	2
Requirement	Misread or omitted	Partly addressed	Every command and subpart addressed
Evidence	Scenario copied or ignored	Some relevant facts cited	Material evidence selected and used precisely
Consequences	Assertion only	One consequence explained	Operational, client, financial or regulatory impact developed proportionately
Controls	Generic control named	Relevant control described	Preventive/detective/corrective role and limitations evaluated
Recommendation	Vague or unsupported	Practical action proposed	Action, owner, priority, evidence and monitoring stated
Communication	Unstructured or wrong format	Generally clear	Audience, headings, conclusions and requested format handled consistently

The total is not a CISI grade. Look at the pattern. Repeated zeros for evidence mean you need case annotation practice; repeated ones for recommendations mean you need greater specificity; weak requirement scores mean more writing will not solve the problem until question analysis improves.

Keep current without losing syllabus control

GOM expects awareness of current developments, but the latest official syllabus remains the scope anchor. Maintain a short update file for regulation, settlement cycles, operational resilience, outsourcing, cyber risk and market infrastructure. For each development, record the operational change, affected stakeholders, control implication and possible management response.

This guide was reviewed against the latest official syllabus located in 2026, Version 10, and the current CISI withdrawal notice. The final GOM sitting is 26 November 2026, and CISI strongly recommends it for resit candidates only. Always check the Diploma in Investment Operations page, CISI Candidate Update page and latest syllabus for your sitting.

The CISI Global Operations Management preparation page maps all six elements and the written assessment. The completed learning hub adds 12 detailed chapter summaries, 140 flashcards, 152 rapid-reference and exam-trap entries, five written-answer planning sets and a syllabus-grounded AI tutor.

Final takeaway

Strong GOM answers are not long lists of operational facts. They are structured management advice: requirement first, evidence second, consequences and controls next, then a practical recommendation. Practise that chain under time pressure and your technical knowledge becomes much easier for an examiner—and a senior manager—to follow.