For Actuarial Analysts ·
What you'll accomplish
Every result needs retelling several times. Underwriters want to know what it means for a book, finance wants the impact on a forecast, and executives want the decision. A saved Gemini Gem holds your instructions and a few of your own past summaries, so each retelling starts from the same setup. It keeps your figures as placeholders, adds no new conclusions and says what the result does not mean. You still compare the draft with the technical note before anything is sent.
Note on Gems. Google's help page says Gems are moving to skills in Gemini Apps, starting in November 2026 for personal Google Accounts and in 2027 for work and school accounts, and that existing Gems are recreated as skills automatically. The instructions in this guide carry over either way.
What you'll need
Data caution. Your past summaries and technical notes are company material. Whether you may paste them into Gemini or save them in a Gem depends on your company's AI policy and on whether Gemini is an approved tool for them. Check your account's settings for whether chats are used to improve Google's models and how long activity is kept, because personal and work accounts differ. If you cannot use real summaries, write two short invented ones in the style you want. No policyholder, claimant or employee details belong in a Gem, and no results tables.
This Gem is a saved setup. For a one-off explanation, a prompt in a single chat is enough.
What you should see: Short samples with placeholders where numbers were. Troubleshooting: If a sample is long, cut it to the paragraph that shows the tone you want.
What you should see: A form with fields for a name, instructions and, depending on your account, knowledge files. Google's help page confirms Gems have a Knowledge section for files. Labels may differ, so look for the name and instructions fields. Troubleshooting: If you do not see Gems, your account type or admin settings may not include them. Ask IT, or use the same instructions as a saved prompt.
Name it "Results explainer". Paste the instructions below into the instructions field, then add your samples at the end under the heading "Style samples".
You turn an actuarial analyst's technical notes into short plain-language summaries.
Ask which audience the summary is for if the chat has not said: underwriters, product, finance or executives.
Keep every figure as a [figure] placeholder, or repeat only a figure that I give you in the chat, exactly as given.
Never calculate a new number, never add a conclusion, and never recommend an assumption or method.
Use short sentences and avoid jargon. If you must use a term, explain it in a few words.
Include a section headed "What this does not mean" that lists two or three things the reader should not conclude.
End with one line headed "Decision this feeds" that names the decision when the chat states it, and otherwise says [blank].
Style samples follow. Match their tone, not their numbers.
What you should see: The instructions saved in the Gem's form. Troubleshooting: If drafts later show invented numbers, add a line: "If a figure is not in my message, write [figure]".
Start a chat with the Gem and paste this invented note.
Audience: underwriters.
Technical note: Block A actual claims for the period were 1,040 against expected claims of 1,000, an actual-to-expected ratio of 1.04. The difference is within the range the team has seen in earlier periods. Decision it feeds: whether the underwriting team reviews Block A guidelines this quarter.
What you should see: A short summary that repeats 1,040, 1,000 and 1.04 only as given, a "What this does not mean" section (for example, that one period does not show a trend) and a closing "Decision this feeds" line about the guideline review. Troubleshooting: If it says the book is "performing well" or "worsening", that is a conclusion you did not give it. Tell it to remove it, and tighten the instructions.
The reviewing actuary's normal review applies to the summary just as it applies to your other work. Send it to the audience after that, not before.
Same note, new audience
Rewrite the previous summary for executives. Keep to three sentences and the same figures.
Jargon check
List every term in my draft that a finance reader might not know, with a plain description of each.
Questions to expect
List three questions this audience is likely to ask about the summary, without answering them.
Email wrapper
Write a two-line email to go with this summary. Do not add any figures that are not in the summary.