Model Role SOP / Operating Playbook: Investor Relations

Model Role SOP / Operating Playbook: Investor Relations

Role: Investor Relations practitioner working under the issuer's assigned owners
Evidence date: 8 October 2026
Evidence scope: Selected issuer-side IR roles current on 8 October 2026 in the United States, Canada, Australia and Singapore; UK context comes from the separate current-change study.
Use: Evidence-derived model for adaptation by an issuer team

Purpose and scope

This playbook helps an Investor Relations (IR) team turn approved company information and market observations into accurate, traceable investor materials, inquiries, meetings and management feedback. It covers preparation, internal review, release coordination, post-release checking and recordkeeping. It applies to a supervised analyst or intern as well as more senior IR staff, with different authority at each level. A beginner may gather sources, prepare comparisons, check versions and route questions; the issuer's authorized owners decide materiality, disclosure content, timing and external release.

The model is informed by issuer-side IR role research and current-change research for the UK, Canada, Australia and Singapore. US-specific research provides separate context. Apply each item only to the relevant issuer population, effective date and local approval route.

Selected employer sources: In the United States, Hasbro's IR role describes earnings scripts, investor materials, Q&A and recurring inquiries. In Australia, Symal's IR analyst role describes preparing presentations, ASX announcements, reporting materials and executive briefings. In Singapore, Keppel's IR and sustainability internship describes supervised results-content preparation and investor-event coordination. These support the preparation and handoff tasks in this model; local approval authority remains employer-controlled.

Inputs, people and systems

Inputs may include approved financial results and filings; draft presentation, release, script, Q&A or fact sheet; the latest published company disclosures; consensus and peer information where licensed; shareholder or unitholder data; an investor question; an event brief; a source document and approval history. Treat an unattributed number, a stale deck and a market rumor as unresolved inputs, not approved facts.

Working roles and handoffs

• IR preparer: assembles the source pack, drafts or updates materials, logs questions, checks consistency and routes work. A supervised learner performs these tasks only within assigned access and review limits.
• IR lead: sets priorities and messaging, assigns reviewers, resolves ordinary editorial issues and confirms the handoff to authorized decision owners.
• Finance or Accounting owner: validates reported numbers, definitions, period comparisons and financial explanations.
• Legal, Company Secretariat or disclosure owner: applies the issuer's approval route for disclosure questions, market-sensitive information, filings and announcements.
• Executive spokesperson: uses the approved brief and speaks only within the issuer's delegated authority.
• Communications, Sustainability or other subject owner: validates content in that function when the role has a mixed remit. A listed-unit IR and sustainability assignment illustrates such a remit; it does not make sustainability a duty of every IR role.
• Distribution or platform operator: releases approved material through the issuer's authorized channel and returns a publication receipt or link.

Employer-controlled fields to fill before use: issuer and legal entity; listed venue and relevant issuer population; disclosure decision owners and alternates; approval matrix; escalation channels; approved source repository; document naming and version rules; licensed market-data and contact systems; restricted-list and access rules; market-calendar cutoffs; release channels; retention period; response-time targets; incident route; accessibility and translation requirements. Vendor names observed in individual vacancies are examples, not mandatory systems.

Trigger-to-close workflow

Use one case ID for each results cycle, announcement, investor event or material inquiry. The IR lead assigns an owner and due time before drafting begins.

1. Open and classify the case. Record the trigger, jurisdiction, issuer entity, audience, deadline, requested output and source location. Identify whether it is a scheduled cycle, routine inquiry, proposed external statement or unexpected market event. If classification is unclear, stop external response and ask the IR lead and authorized disclosure owner.
2. Build a controlled source pack. Link current approved filings, releases, financial tables, policies and relevant prior messaging. Record owner, date and version for each source. Mark external research, analyst models and market commentary separately from issuer-approved facts. Ask Finance or the subject owner to resolve discrepancies rather than silently choosing a number.
3. Draft a purpose-specific work product. Prepare the requested deck, script, Q&A, fact sheet, website update, briefing or response log from the controlled pack. Show period, unit, currency, scope and source for each quantitative claim. Write for the audience without turning interpretation into an unapproved company statement. Create a version number and change log.
4. Run the preparer check. Compare figures and wording across the candidate materials, latest public disclosure and source pack. Check links, dates, entity names, titles, charts, accessibility, embargo labels and any approved translation. Flag forward-looking, non-GAAP or alternative performance wording for the appropriate owner; the preparer does not decide its acceptability.
5. Route decisions and approvals. Send the draft and an issue list through the employer's approval matrix. Obtain recorded Finance, Legal/disclosure, executive and functional reviews as required. Resolve every open comment or assign an explicit decision owner. A silence, informal chat or old approval is not approval of a changed version.
6. Prepare and execute the handoff. For external release, give the authorized operator the approved version, exact destination, scheduled time, accessibility assets and named final approver. For meetings, provide the approved spokesperson brief, attendee list and question-routing route. If timing or content changes, return to the relevant approver before release.
7. Read back and monitor. Check the live release, filing, website, webcast or sent response against the approved version, including links, figures, timestamp and venue. Save the public URL or delivery receipt. Monitor incoming questions and market/holder feedback within the assigned scope; do not improvise an answer to an unresolved disclosure question.
8. Close and learn. Log the final approved version, approvals, distribution proof, corrections, inquiry outcomes and remaining actions. Send management a concise feedback note that distinguishes observed analyst/investor questions from IR interpretation. Close the case only when the owner confirms all handoffs and exceptions are resolved.

Working cadence

The timing below is a model; the employer's reporting calendar and coverage determine actual frequency.

Work may include quarterly results, proxy or annual meeting seasons, roadshows, site visits, daily inquiries or a fixed assignment term. Use the issuer's own calendar and role assignment rather than treating every example as a universal cadence.

Decisions, escalation and exceptions

The IR preparer can propose edits, identify a mismatch, log an inquiry and recommend a route. The IR lead can assign work and approve ordinary internal preparation within delegated authority. Materiality, selective-disclosure concerns, reporting obligations, public wording and release timing belong to the issuer's authorized decision owners under its local approval matrix. Where a vacancy says an IR leader “owns” a process, do not infer final legal approval unless that authority is explicit.

Escalate promptly through [employer-controlled escalation channel] when any of these occur:

• A number or statement differs between approved sources, or a source has no owner or date.
• An investor asks for information that is not already approved for release, including a forecast, transaction, financing, operational event or nonpublic metric.
• A rumor, unusual market movement, leaked document or erroneous publication appears.
• A deadline, approval or distribution channel changes after signoff.
• The wrong version goes live, a link fails, a venue rejects a submission, or a webcast/translation differs from the approved copy.
• An inquiry involves personal information, a restricted contact, a security issue or a complaint requiring a separate team.

For an unresolved case, pause the affected external communication, preserve the source and draft, log who was notified and when, and follow the owner's decision. Do not delete a mistaken public version or issue a correction on personal initiative. The issuer's incident and disclosure owners decide the correction route and timing; IR then checks the actual public outcome and updates the record.

Jurisdictions differ. A UK listed-issuer update, a Canadian issuer filing, an Australian ASX announcement and a Singapore listed-unit communication can involve different participants, dates and systems. Regulatory consultations and future-effective requirements in the trend study are context for the relevant issuer population, not instructions to activate a new step everywhere. Set [employer-controlled jurisdiction and effective-date check] for each case and refer it to the appropriate local owner.

Records and quality measures

Keep the following in [employer-controlled approved repository] with access and retention set by the employer:

• Case register: trigger, entity, jurisdiction, audience, owner, due time, status and escalation route.
• Source index: source link, owner, publication date, version, approval status and data provenance.
• Draft and decision trail: versioned work product, changes, comments, open issues and named approvals.
• Distribution proof: final file hash or version, release receipt, live URL, channel and timestamp.
• Inquiry and feedback log: question, public/approved source used, assigned response owner, response date, follow-up and management insight.
• Exception log: discrepancy, impact, pause, decision, correction route, readback and closure.

Useful team measures are the proportion of cases with complete source and approval trails; proportion of live items matching the approved version at readback; count and age of unresolved exceptions; correction frequency; response timeliness against [employer-controlled target]; and completion of post-event feedback notes. Use these to find workflow weaknesses, not to reward quick unreviewed release. The IR lead sets thresholds and investigates exceptions. A beginner can collect the data but does not certify a disclosure control.

Reusable SOP model

Copy this model into the employer's approved workspace and fill every bracketed field before using it.

Apply the trigger-to-close sequence above. Keep each approval tied to the exact version; after a substantive revision, ask the assigned owner whether approval must be repeated.

Quick reference

• Start with the trigger, case owner, jurisdiction and approved source pack.
• Keep figures, wording and versions traceable to named owners.
• Route materiality, disclosure and timing decisions to the issuer's authorized owners.
• Release only the approved version through the approved channel, then read back the live result.
• Preserve approvals, receipts, inquiries and exceptions until the case owner closes them.