Skip to content

AI briefing & assistant

STRIVN ships two team-intelligence tools: the AI briefing, which prepares your decisions for the day, and the Assistant, a chat that answers your questions about the squad.

The briefing turns the team’s data (check-ins, load, injuries, calendar) into concrete decisions for the day’s session or match.

AI briefing — daily decisions, players ranked by recommendation

At the top: the date, the check-in response rate and the day’s event. Below, the Daily decisions sort each player into a category:

CategoryMeaning
RestPlayer to spare (injury, overload)
WatchKeep an eye on during the session
FitAvailable as normal
UnknownData too old — nudge the player

For each player, shortcuts open their sheet, their injury or the assistant, and let you nudge anyone who hasn’t replied. The Staff hub / Assistant switch toggles between the steering view and the chat.

The Assistant answers in plain language about your team: squad status, injuries, load, calendar. It reads the same data you do, in real time.

Assistant — the AI's answer on the group's state before the session

Type your question, or start from a suggestion: Who’s at risk today?, Team summary, Upcoming events, List of injured players. The assistant shows the steps it consults (briefing, trends, injuries…) before answering.

When your question is about numbers — “show me the load over the last four weeks”, “compare this match to the previous one” — the assistant doesn’t just answer in text: it opens a canvas next to the conversation, with the widgets that answer it.

A canvas writes nothing. It doesn’t appear in your Dashboards, no one else sees it, and it disappears if you do nothing with it. It’s an answer, not a document.

  • Open — every reply that produced a canvas leaves a card in the conversation. Reopen it whenever you want, even after closing the canvas.
  • Save — the canvas becomes an ordinary dashboard, visible to the team and editable in the builder. You can also simply ask the assistant to save it.
  • Chain requests — while a canvas is open, “add last week too” edits it instead of opening a second one.

The assistant composes in two ways, depending on the question. A dynamic widget keeps the query: reopened later, it replays on the current data. A Snapshot widget freezes the values the assistant just read — for a question the dashboard vocabulary can’t express, like the result of a specific match. It then carries its capture date.

The canvas remains the first answer. When neither a widget nor a Free chart can draw your request — a free layout, linked views, picking a match or a player, a shot map with the pitch and the goal crossed, a mixed timeline — or when you ask for “a page”, the assistant has a made-to-measure page built, in the background, from the figures it read. It opens next to the conversation when it’s ready and can be saved to a dashboard. Pages are rolling out team by team: see Have a page built.

The assistant also knows the Analytics pages. Just ask it for:

  • a question about your data — “who played the most over the last 5 matches?”: it computes it like Explore a question and gives you a link to open it; it can then save it among your saved questions;
  • a dashboard from a template — “create an S&C Monday for me”, “a Return to play for Hugo”;
  • editing a view of an existing dashboard, setting its default filters, changing its visibility or pinning it to a colleague’s home page, scheduling its send.

Each of these writes is proposed to you and waits for your confirmation. Only the public link never goes through the assistant: it’s created in the dashboard’s Share dialog, while seeing what will be visible.

“Prepare the FC Rivals analysis for the staff”: the assistant builds a complete presentation as a private draft, with no confirmation card, and shows it as thumbnails with an Open in the editor button. You then refine it in the conversation, or write “undo”. See Build a presentation with the assistant.

If two reasonable readings of your request would give different results — which period? which player? which metric? — the assistant asks a question instead of guessing or refusing. It offers choices, but you can always answer directly, in your own words.

It can only ask two questions for a single request. Past that limit, it composes its best reading while naming the choices it made, or tells you clearly what it couldn’t resolve — never a third question.

  • New conversation (the pen button) starts a clean thread from any screen: at the top of the assistant, on the assistant bar at the bottom of the screen (mobile), in the assistant’s folded strip (computer), or from the command palette (⌘K / Ctrl+K), entry New conversation.
  • A new conversation is only created by your first question: opening one and leaving it empty leaves nothing in the list.
  • If your last conversation has been quiet for more than 30 minutes, opening the assistant starts a new one, with the screen’s suggestions. The previous one stays one tap away: the Resume row, with its title and how long ago, takes you back to it.
  • The Assistant button on a player row (in the briefing, for example) starts a new conversation about that player, unless the assistant is already talking about them.
  • Threads are filed under Active and Archived on the assistant’s full page (the All conversations button at the top of the assistant). When you already have 30 active conversations in a team, starting a new one automatically archives the least recently used; it stays readable under Archived.
  • A daily quota of messages shows at the bottom right.

If you reload the page, or switch to the full page, while the assistant is writing its reply, the page you open shows the reply is coming and displays it as soon as it’s ready; the field stays closed meanwhile. If the reply is interrupted, your question comes back to the field: press Enter to send it again.

The full page opens directly, even if you haven’t done the personalisation interview: it stays optional, offered in an empty conversation by Personalise my tone and priorities (Later hides it).

On mobile, you can dictate your question rather than type it — handy at the side of the pitch, hands full.