See the Flow.
Across Every Team.
Import sprint data from any tool, analyse workload distribution and velocity trends across team members, and produce three executive-ready report lenses — all in your browser.
FlowInSite is a fully browser-based team flow analytics tool. There is nothing to install — open the tool, import your sprint data from any supported source, and immediately see how work is flowing across your team. All data is stored in your browser and can be exported as JSON at any time.
What you get out of the box
- Five data source connectors — Jira CSV, Monday.com, Asana, ClickUp, and Manual Entry — all normalised into a single consistent model
- Dashboard view with team-level delivery metrics, workload distribution, and sprint-over-sprint tracking
- Team Members breakdown with individual velocity, trend direction, and contribution share across all sprints
- Category Mapping to group issue types into custom delivery categories meaningful to your team
- Three report lenses — Overview, Trends, and Executive — each exportable as a standalone HTML report
- Named and Anonymous mode toggle for sharing reports when team member names are sensitive
How the tool is organised
- Dashboard — Your primary analytics view. Team selector at the top lets you focus on one team or view all teams simultaneously
- Team Members — Individual contributor breakdown with trend indicators and sprint-by-sprint history
- Category Mapping — Map your issue types (Bug, Story, Task, Spike) to custom delivery categories (Value, Risk, Capability, etc.)
- Export Report — Choose a report lens (Overview / Trends / Executive), toggle Named or Anonymous, and export as standalone HTML
- Import Data — Load data from your tool of choice. Multiple sprints can be imported and accumulated
- Help — Source-specific import guides and field mapping references
FlowInSite is built for leaders who need to understand how work flows across their teams — not just whether it gets done, but who is doing what, at what pace, and how it compares to previous sprints.
Agile Coaches
Multi-team visibility across any tool stack, without requiring a unified platform
Delivery Leads
Spot contributors at risk of burnout or disengagement across multiple sprints
Engineering Managers
Produce executive-ready flow reports without exposing individual names to leadership
Portfolio Managers
Aggregate sprint analytics across multiple teams from different project tools
FlowInSite supports five data sources. Select your source from the Import Data tab — each source has its own set of instructions and field mapping requirements. Multiple sprints can be imported over time, building up your analytics as your team delivers.
Jira
Export from Jira Issue Navigator with Key, Assignee, Issue Type, Story Points, Sprint, Status columns
Monday.com
Export as .xlsx, save as CSV. Story Points, Sprint, and Type must be added as custom board columns
Asana
Export from Project view → CSV. Story Points and Sprint must be set up as custom Asana fields
ClickUp
Export from List view as CSV. Story Points, Sprint, and Task Type must be custom ClickUp fields
Manual Entry
Type stories directly into the table — Team Name, Member, Issue Type, Story Points, Status
How Jira export works — the most common source
- Open Jira → navigate to your project → use Issue Navigator (not the Sprint Report — FlowInSite reads the raw issue list, not the sprint summary view)
- Filter by your sprint name and project. Ensure these columns are visible: Key, Assignee, Issue Type, Story Points, Sprint, Status
- Export as CSV using the Export button in Issue Navigator. FlowInSite auto-detects teams from sprint names and assignee groupings
- Upload on the Import Data tab → review the preview table → click Import Stories to load the data
💡 Download the templates
For Monday.com, Asana, and ClickUp, FlowInSite provides downloadable CSV templates with the exact column names it expects. Fill in the template and upload — no guessing the column mapping.
💡 Multiple sprints accumulate
Each import adds to your dataset rather than replacing it. Import Sprint 10, then Sprint 11 — FlowInSite shows both in your trend analysis. Use JSON Backup regularly to preserve your history.
FlowInSite is flexible with column names — it matches a wide set of aliases automatically. But some fields are non-negotiable. Use this guide before you export to avoid silent skips and missing teams.
How team detection works — priority order
- 1. Jira Team Name field — most reliable. Enable the native Teams feature in your Jira project and include the "Team Name" column in your export.
- 2. Squad component — FlowInSite scans all Component columns for values named "Squad [Name]". If ≥30% of items have squad tags, squad mode activates automatically.
- 3. Sprint prefix — FlowInSite strips the team name from sprint names like "Phoenix FY27-Q1-S4" → team = Phoenix, sprint = FY27-Q1-S4. Works well when each team runs its own sprint board.
- 4. Assignee membership bridge — if an assignee appears on tagged items, their other items with inconsistent or missing squad tags inherit the same team automatically.
Recommended Jira JQL — paste this into Issue Navigator
- Replace
YOUR_PROJECTwith your Jira project key (e.g.PROJ,TEAM) - closedSprints() ensures only completed delivery sprints are included — no in-flight work, no backlog noise
- -16w limits to the last 16 weeks (~6 sprints). Use -8w for large projects to keep the file manageable
- Export from Issue Navigator → Export → CSV (all fields). FlowInSite auto-trims to the 6 most recent sprints per team at import time
💡 Large files are fine — FlowInSite trims automatically
Exporting 4,000+ rows is normal for large enterprise projects. FlowInSite skips no-sprint rows at parse time and keeps only the most recent 6 sprints per team at import, so the dataset stays manageable regardless of export size.
💡 Multi-team projects — use the Team Name field
If your Jira project spans multiple delivery squads, enable the native Teams feature and add "Team Name" to your export columns. It is far more reliable than sprint prefixes or components, especially when teams share a single board.
The Dashboard is your primary analytics view. Use the team selector at the top to focus on a specific team or view aggregate metrics across all teams simultaneously.
Reading the FlowInSite Dashboard
Select your team
Use the Team dropdown at the top to focus on a specific team, or leave it on "All Teams" to see aggregate metrics. FlowInSite detects teams automatically from your imported sprint data — each unique team name becomes its own selectable view.
Read the sprint summary metrics
The top metric cards show total story points delivered, completion rate, number of contributors, and average points per person. These update immediately when you switch teams or add new sprint data.
Check the workload distribution chart
The distribution chart shows how story points are spread across team members in the selected sprints. Look for extreme skew — one person carrying more than 40% of the load is a concentration risk that deserves a direct conversation.
Switch between Issue Types and Custom Categories
The toggle between Issue Types (Bug, Story, Task) and Custom Categories (your mapped categories) changes the breakdown dimension. Use Issue Types to spot hidden bug load; use Custom Categories to discuss strategic investment mix with stakeholders.
Compare sprints over time
If you've imported multiple sprints, the sprint selector lets you compare periods side-by-side. The Sprints Multiplier setting (in the header) controls how many past sprints feed into the trend calculations.
💡 Use Categories for strategic conversations
Stakeholders don't care whether work was a "Story" or a "Task." Map everything to categories that resonate in your context — Capability, Risk Reduction, Technical Debt, Customer Value. The dashboard immediately becomes a portfolio conversation.
💡 Skew is normal, extremes aren't
Some imbalance in workload is always expected — not all contributors work at identical velocity. The threshold to investigate is when one person consistently carries more than 2× the team average over three or more sprints.
The Team Members tab breaks down delivery at the individual contributor level — points delivered, completion rate, sprint-by-sprint history, and trend direction across all imported sprints.
Using the Team Members view effectively
Read the contributor table
Each row shows a team member's total story points delivered, number of issues completed, completion rate, and their trend direction (up, down, or stable) compared to their own historical average. The trend is calculated from the last 3 sprints vs. the 3 sprints before that.
Interpret the trend arrows
A downward trend over 2+ consecutive sprints warrants a check-in — it may signal blocked work, disengagement, context-switching, or personal circumstances. Avoid jumping to performance conclusions; start with curiosity. Ask what's changed, not what's wrong.
Use the data for 1:1 preparation
Before a 1:1 meeting, open the Team Members tab and review the relevant contributor's sprint history. You'll walk in with specific data points to anchor the conversation — not vague impressions. "Your completion rate has been strong, but I noticed you had fewer items in Sprint 12 — how are you tracking on capacity?"
Switch to Anonymous before sharing
Before showing the Team Members tab to anyone outside the immediate team (e.g. in a leadership review), toggle to Anonymous mode. Names are replaced with pseudonyms — the patterns and numbers remain, the individuals are protected.
💡 Don't show this tab in retrospectives
The Team Members view is for Scrum Master and manager use. Showing individual comparative data in a retrospective creates unhealthy competition and can damage psychological safety. Use the Dashboard's aggregate view for team discussions instead.
💡 Consistent naming matters
FlowInSite identifies contributors by name. "Alex Chen" and "A. Chen" are treated as different people. Standardise how names appear in your source tool before importing to ensure accurate trend tracking.
Full Team Members Guide Included
Unlock the complete individual analytics playbook — trend interpretation thresholds, 1:1 preparation workflow, and guidance on when and how to use individual data sensitively.
Start Free Trial — 14 Days FreeCategory Mapping lets you translate technical issue types (Bug, Story, Task, Spike, Sub-task) into delivery categories that are meaningful to your organisation — turning a developer view into a strategic view.
Setting up and using Category Mapping
Define your categories
Navigate to the Category Mapping tab. For each issue type detected in your imported data, assign it to one of your custom delivery categories. Common category sets include: Value Delivery, Risk Reduction, Technical Debt, Operational, and Capability Building.
Toggle to Custom Categories on the Dashboard
Once mapped, use the Issue Types / Custom Categories toggle on the Dashboard to switch the breakdown dimension. Your distribution charts and metrics immediately reflect the new category groupings — the same story points, seen through a strategic lens.
Use for investment mix conversations
If your team spent 60% of the sprint on Bugs and only 30% on Value Delivery, that's a conversation to have with both the team and the Product Owner. Category Mapping makes this visible without requiring custom Jira dashboards or JQL expertise.
Include in the Executive report lens
The Executive report lens (in Export Report) includes a category breakdown section. When you've set up meaningful categories, this section immediately elevates the report from a developer metric to a portfolio narrative that leadership understands.
💡 Less is more
Aim for 4–6 categories maximum. Too many categories make the chart unreadable and the conversation fragmented. If you have 10 issue types, most should map to the same 2–3 categories.
💡 Name for the audience
If your reports go to the C-suite, name categories in business terms — not technical ones. "Customer Value" lands better than "Feature Story." The mapping is yours; make it serve your stakeholder conversations.
Full Category Mapping Guide Included
Unlock the complete Category Mapping playbook — suggested category frameworks, how to align categories with your organisation's strategic themes, and how to use the investment mix view in leadership conversations.
Start Free Trial — 14 Days FreeThe Export Report tab is FlowInSite's primary analytical surface. For each team member it calculates a flow signal — a single label that summarises their delivery pattern based on velocity, category mix, and trend direction. Signals are designed to surface the right conversation, not to judge performance.
Signal Reference
Each person receives at most one signal per sprint, based on the strongest pattern detected. Hover over a signal badge in the tool for a quick reminder of what triggered it.
💡 Signals are a starting point, not a verdict
FlowInSite flags patterns — it doesn't explain them. A "No delivery" signal might mean leave, a blocked dependency, or a sprint with no closeable items. Always pair the signal with a conversation before drawing conclusions. The Recommendation column shows the default action; your judgement as a lead determines what happens next.
How to action signals in your team rituals
Using signals in Sprint Retrospectives
Export the Overview lens before your retro. Look for patterns across the team — if 4 out of 8 people are Siloed in the same category, that's a planning problem, not an individual one. Share the export anonymously using Anonymous Mode when the team hasn't seen this data before.
Using signals in 1:1s
Pull up the Trends lens for an individual before a 1:1. A Declining signal combined with a Bug-heavy pattern often means the person is being pulled into reactive work. Ask about their current experience, not their velocity number. Never lead a 1:1 with "the tool says you're declining."
Using signals in sprint planning
Concentrated signal last sprint? Deliberately spread stories across more people in the next plan. Siloed signal 2 sprints running? Assign a cross-category story as a stretch. Signals should feed forward into planning decisions — not just sit in a report.
Escalating persistent signals
A single signal in one sprint is noise. The same signal for 3 or more consecutive sprints is a pattern worth escalating. Use the Trends lens to export a multi-sprint view and share with your Engineering Manager or HR business partner as supporting context for a structured conversation.
Signal Coaching Workflows Included
Unlock the complete Export Report guide — how to action each signal in sprint retros, 1:1s, sprint planning, and leadership escalation workflows.
Start Free Trial — 14 Days FreeFlowInSite generates reports through three distinct lenses — Overview, Trends, and Executive. Each lens renders the same underlying data into a different narrative structure designed for a specific audience.
Overview
Full team and individual delivery breakdown for a selected period. Shows every contributor, their points, completion rate, and category distribution.
Audience: Team leads, Scrum MastersTrends
Sprint-over-sprint velocity and completion rate trends per contributor. Highlights who is accelerating, who is stable, and who is declining.
Audience: Agile Coaches, Engineering ManagersExecutive
High-level team health narrative with flow health score, investment mix by category, and a confidence summary across all teams.
Audience: Leadership, Portfolio ManagersWhen to use each lens
Overview — for operational sprint reviews
Use the Overview lens for your Sprint Review or team retrospective. It gives a complete picture of who delivered what, how points were distributed, and what the category breakdown looked like. Best shared internally within the delivery team and immediate management.
Trends — for coaching conversations
Use the Trends lens for Agile Coach check-ins and Engineering Manager reviews. It shows direction of travel for each contributor — not just what was delivered, but whether performance is improving, stable, or declining. Pair with Anonymous mode when sharing upward in the organisation.
Executive — for leadership presentations
Use the Executive lens for Steering Committee updates, portfolio governance reviews, and quarterly business reviews. It produces a narrative-led summary — flow health score, investment mix, and a confidence rating — without exposing granular individual data. Always use Anonymous mode for Executive reports.
Exporting as standalone HTML
All three lenses export as a fully self-contained HTML file that renders offline with no external dependencies. Share via email, attach to Confluence, or open on a shared screen. Each export is timestamped and labelled with the team name and report type.
Anonymous mode replaces all team member names with neutral pseudonyms (Person A, Person B, etc.) across every view and export — keeping the analytics intact while protecting individual identities when sharing upward or externally.
When and how to use Anonymous mode
Toggle is instant and reversible
The Named / Anonymous toggle appears on the Dashboard, Team Members, and Export Report tabs. Switching is instant — no data is changed or deleted. You can toggle freely within a session without losing any state.
Use Anonymous for all upward and external sharing
As a rule, any report that leaves the delivery team — to leadership, to HR, to external partners, or to Confluence pages accessible outside the team — should use Anonymous mode. The flow metrics retain all their analytical value; only the names are removed.
The ANON indicator confirms the mode
When Anonymous mode is active, a purple ANON badge appears next to the toggle. This acts as a visual reminder — you can see at a glance that you are in anonymous mode before taking a screenshot or exporting a report.
Always use Anonymous for the Executive lens
The Executive report lens is explicitly designed for leadership audiences. The playbook guidance is clear: always export the Executive lens in Anonymous mode. Individual performance data has no place in a portfolio-level conversation unless the individual has specifically consented to be identified.
💡 Pseudonyms are consistent within a session
Person A is always the same person within a session. If you export an Overview and a Trends report in the same session, Person A refers to the same contributor across both documents — useful for cross-referencing without naming anyone.
💡 Name-sensitive organisations
Some enterprise environments have explicit policies about sharing individual productivity data with leadership. When in doubt, use Anonymous. It is always easier to show more detail later than to retract a report that has already been seen.
Full Anonymous Mode Guide Included
Unlock the complete privacy playbook — sharing policies for each audience type, when to use named vs. anonymous mode, and how to handle requests for individual-level data.
Start Free Trial — 14 Days FreeFlowInSite exports to four formats from the Export menu in the header — each designed for a different use case from live sharing to long-term archiving.
Standalone HTML
Self-contained report from your chosen lens. Renders offline, shareable via email or Confluence
CSV Export
Raw issue-level data for further analysis in Excel, Google Sheets, or BI tools
JSON Backup
Full data backup including all teams, sprints, and category mappings — restores everything
Full Tool Export
Exports a copy of FlowInSite itself pre-loaded with your data — sharable as a live dashboard
💡 JSON Backup is your safety net
Browser local storage can be cleared by users or browser updates. Export a JSON Backup at the end of every sprint cycle and store it in a shared folder. It restores your complete dataset — all teams, all sprints, all category mappings — in one click.
💡 Full Tool Export for team leads
The Full Tool Export packages FlowInSite itself with your data embedded. Share it with a team lead who doesn't have access to the tool — they can open it in any browser and explore the dashboard themselves, with no login required.
💡 Standalone HTML for Confluence
Confluence supports HTML macro rendering. Attach your standalone HTML export to a Confluence page and embed it with the HTML Include macro — your FlowInSite report becomes a live, interactive page in your team's wiki.
💡 CSV for audit trails
If your organisation requires sprint delivery evidence for R&D tax incentive claims or project accounting, the CSV export provides issue-level granularity with assignee and story point data — exactly what finance and audit teams need.
Full Export Guide Included
Unlock the complete export and distribution playbook — format selection by audience, archiving strategy, and how to use the Full Tool Export for cross-team visibility without platform access.
Start Free Trial — 14 Days FreeUnlock the Full FlowInSite Playbook
14-day free trial included. Get the complete dashboard interpretation guide, category mapping frameworks, report lens strategy, anonymous mode policy guidance, and export workflow — everything you need to run professional team flow analytics from day one.
Already licensed? Open FlowInSite →