Home/Products/Operating Model Design
Live

Your operating model is a living record.
Stop keeping it as a drawing.

Who does what, in which system, by when, and how each step hands off to the next — kept as one structured model, drawn as an interactive board, and published as a web page, Word and Excel that always agree.

Request a demo → See the board
Dealing and NAV — swimlane board
Teams as rows, phases as columns, hand-offs coloured by channel · step numbers computed, never typed
Illustrative
1. Dealing 09:00–12:00 2. Matching 12:00–14:00 3. Valuation 14:00–17:30 4. Settlement T+2 Investment Manager External Transfer Agent Internal Fund Administrator Internal Custodian External 12:00 cut-off 1 Submit orders Order portal 2 Validate orders TA system 3 Send dealing totals TA system 4 Price portfolio Accounting system 5 Release NAV Accounting system 6 Issue instructions TA system 7 Settle cash Custody platform 8 Receive NAV Mailbox
APISFTPSWIFTEmailInternalDeadlineDashed card = external party

Illustrative recreation of a fictitious operating model, in Veracis styling — not a client model and not a screenshot of the application.

The gap it closes

Accurate on the day
it was finished.

Ask an operations team for their operating model and you usually get a drawing, built for a project. Then the drawing has to be kept up.

The picture and the documents drift
Step numbers are typed by hand. The step table in the Word document was copied from the drawing once. Move a box and nothing else knows.
The arrows are where it goes wrong
Box text is easy to get right. Which team a hand-off actually goes to, in which direction and over which channel, is where errors hide — and it is what the model is for.
Nobody knows what changed
No history of the model, no record of who changed a hand-off or why — and working questions end up on the board the client receives.
What it does

One model.
Every output drawn from it.

Start from what you have
Import a Visio .vsdx or a PDF of a swimlane diagram. Every step and hand-off is read into a draft, with a named question wherever a judgement was needed. Nothing changes until a person accepts it.
  • Rules-based import, reviewed before acceptance
  • Password-protected files accepted
  • The original file kept with the import
See it as a board
Teams as rows, phases as columns, a timeline with deadlines, hand-offs coloured by channel and routed cleanly. Hover any step to trace what comes in and what goes out.
  • System-level detail behind each step
  • Straight-through steps marked as such
  • Edit on the board or in tables
Publish in one click
A self-contained interactive web page, a Word document and an Excel workbook — the same content and the same step numbers, in one standard structure readers learn once.
  • Printable to PDF
  • Your brand colours
  • Nothing internal ever reaches an output
The registers, not just the flows
The published model carries the deadline schedule, the reporting matrix, a manual-process register, roles and responsibilities, a risk analysis and a RASCI matrix — each built from the model. The manual steps standing between you and straight-through processing are named, not guessed.
Questions kept apart
Open questions live on an issues list beside the model, linked to the steps they concern — never on the board you send. A possible gap becomes an issue, not content.
Every version kept
Every save is a version, with who saved it and why. Restore any of them without losing anything; a save never silently overwrites a colleague's work.
Redesign, never invent

The model contains what you told it. Nothing more.

A model contains only what its owner or a supplied document provided. Challenges, manual processes, deadlines and risks stay empty until someone supplies them, and empty sections are left out of every output.

Vera, Veracis's AI, sits in a panel beside every project, to discuss the model, work through the issues and propose changes. A proposal arrives as a list of changes against your draft; it reaches the model only when a person applies and saves it. In development

See Vera review a step →

Published model — standard structure
Overview · key risks and challenges1
Operating model flows2
Deadlines and cut-offs3
Reporting matrix4
Manual process register5
Roles and responsibilities6
Risk analysis7
RASCI8
Sections with nothing in them are left out of every output.
Who it's for

For the people who own
how the work gets done.

  • Operating-model owners — a model you maintain, not a drawing you redraw.
  • Change teams — versions, a history of who changed what, and an issues list to work a design to sign-off.
  • Client service and oversight — a board you can send with confidence, and Word and Excel that match it.
  • Confidential by design — each client organisation's models sit in their own database, behind single sign-on with multi-factor authentication.
Live
Fund Master
One governed record for every fund and class — and a view of where your book stands in the market.
Live
Fund Calendars
The dealing and settlement dates your model's deadlines depend on, generated and watched for change.
Live
Change Delivery
The change that lands a new model — items, gates, decisions and actions in one governed portfolio.
Talk to us

A model,
not a drawing.

Operating Model Design is live. If your operating models live in drawings nobody can keep current, we'd like to show you the alternative.

Request a demo

Tell us a little about your organisation and we'll be in touch within one business day.

By submitting, you agree to our Terms of Use and Privacy Policy.

No commitment required Responses within one business day Design-partner conversations welcome