# Workspace management (https://riska.io/platform/workspace-management) _Workspace management_ ## Change your underwriting rules and ship them the same day. See where loss ratio, quote time and retention are slipping, change the rules behind them, and release the change yourself. Then measure again. Each loop tells you whether the book moved. ## Every number points at a rule you can change. Loss ratio, quote time, retention and collections each trace back to configuration you own, so improving them is a change you make, not a ticket you file. - **Quote faster where it stalls**: Time in each stage shows where quotes wait. Assign that stage automatically, test it on last week's submissions and release it the same day. - **Stop referring clean accounts**: When most referrals in a score band are approved as written, raise the bar the rule refers at. Underwriters get those hours back for the accounts that need them. - **Price where the losses are**: Loss ratio by class and state shows which rates are short. Change the rate book, check it against last quarter's quotes and release it before renewal season. - **Ask brokers once**: If the same document is missing from every broker's submission, make it a requirement and let a sequence chase it the moment a submission lands short. - **Keep the accounts you want**: Retention by appetite score shows who you are losing. Start the renewal conversation earlier for your best accounts and let the rest run their course. - **Collect before it lapses**: Past-due installments by payment plan show which plans fail. Change the plan or the reminder cadence, and the next month's numbers tell you if it worked. ## One company, as many workspaces as it needs. Give each business unit or product line a workspace of its own, then see them all together when the board asks how the year is going. - **Separate where it matters.**: Each workspace keeps its own book, people, rules and releases. The specialty unit can change its appetite on a Tuesday without touching the program business. - **Share what you want.**: Start a new product line from the configuration another workspace already proved, and keep brokers, templates and teams consistent where consistency helps. - **Roll it all up.**: Premium, loss ratio and bind ratio across every workspace in one view, so the board pack does not start with five exports and a spreadsheet. - **One sign-in for every unit.**: People who work across units switch workspaces in a click, with single sign-on and the right role in each. Leave the directory and access ends everywhere. > "“A new product line used to mean months, if not a year, of work and a large capital commitment. Now the only limiter is deciding scope and strategy.”" — Head of operations, MGA · 12 programs ## Prove it before it ships. Every change is tested against real submissions in a test environment before anyone in production sees it. ### Change it in a working copy. Appetite, rate books, workflows and layouts all change in a working copy. Production keeps running on the release it is pinned to until you decide otherwise. ### Test it on the submissions that matter. Save real submissions as tests with the outcome you expect, from the appetite decision to the workflow that should fire. Run them in uat against the new release and see every pass and every miss before a broker does. ### Release it with a signature. Cut a numbered release, see exactly what changed against production, and deploy it by typing the environment and the version. Going back is the same step, pointed at the earlier number. ## Get better every week, without a services bill. You own the configuration, so improving it is an afternoon's work, not a statement of work. Small changes, shipped often, add up. - **Every number has a version**: Each release names the exact configuration behind it, so a figure in a report traces back to the rules that produced it. - **See what moved**: Compare any release with production: programs, controls and workflows added, updated or removed. - **Who, what, when**: Every change to a record lands in the audit log with the person, the time, and the before and after. - **Agents leave a trace**: When Riska or a workflow makes the change, the entry names it instead of leaving the actor blank. - **Production stays safe**: Once a workspace is live, its production data can never be reset or cleared, by anyone. - **No vendor in the loop**: The change your old vendor quoted in weeks is a working-copy edit and a release you deploy yourself. ## Describe it. Riska builds it. Say what you want in plain words. Riska drafts the configuration, and it goes through the same tests and releases as everything else. ### Automate the work nobody wants. “Research every new submission's operations and licences, and give the underwriter a task if something looks off.” Riska drafts the trigger, the research step and the task, ready to test. ### Turn a strategy into rules. “Refer property accounts within a mile of the coast.” Riska adds the rule to your appetite with its score tiers, and shows which open submissions it would have moved. ### Ask for the report, get the report. “Loss ratio by broker for property, this year against last.” Riska builds the report on your own objects and puts it on the dashboard you pick. ### Chase without writing the emails. “Ask brokers for their loss runs, and follow up until they arrive.” Riska writes the sequence and its emails in your voice, for you to review before it sends. ## Underwriting, operations and claims on one account. Notes, tasks, comments and mentions live on the record, so every desk working an account works it together, in the same place. - **Write it down together.**: Notes on any record, edited by several people at once and seen as they type. The broker call summary gets written once, by the people who were on it. - **Hand it off without a meeting.**: Assign a task to a person or a team on the record it is about. Whoever picks it up has the whole account in front of them. - **Pull someone in.**: Mention a colleague in a comment and it lands in their mentions with the record attached. Resolve the thread when the question is answered. - **Refer it to the right desk.**: When an account refers, it reaches the underwriter with the authority to decide, with the score, the notes and the history already attached. _Connected_ ## Fits the stack you run today. Email, sign-in and your data warehouse connect out of the box, and anything else can plug in, so adopting Riska doesn't mean ripping anything out. - Email (Gmail & Outlook) - Single sign-on (SAML & OIDC) - Directory sync (SCIM provisioning) - Document parsing (Any form, standard or your own) - REST API (Versioned and documented) - Webhooks (Every change, as it happens) - Search (Across the whole book) - Data export (Warehouse-ready) ## Configured, not implemented. The rest of the platform runs on the same workspaces, the same releases and the same audit trail. ## Bring the change you have been waiting on. The one sitting with your vendor, or the one nobody has had time for. We will make it in a working copy on the call, test it and release it.