Remote Team Collaboration Activity
This dataset provides granular tracking of remote team collaboration events, including communication frequency, participant engagement, and productivity bottlenecks. Managers can leverage these insights to optimize workflows, identify engagement trends, and proactively address collaboration issues. The dataset is ideal for productivity analytics, team performance monitoring, and operational improvement in distributed work environments.
Sample rows
preview · 8 of 200 rows · all 15 columns| event_idstring | event_typestring | duration_minutesinteger | bottleneck_flagboolean | team_idstring | team_namestring | event_datetimedatetime | participant_countinteger | initiator_idstring | communication_frequencyinteger | engagement_scorefloat | manager_idstring | participant_idsstring | bottleneck_descriptionstring | event_notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| EVT-0001 | meeting | 95 | false | T101 | Pacific Devs | 2024-03-05T09:15:00 | 14 | U1234 | 112 | 0.81 | M101 | U1234,U1256,U1290,U1302,U1315,U1327,U1341,U1352,U1366,U1378,U1390,U1401,U1412,U1423 | blank | General team sync; lively discussion, no major blockers. |
| EVT-0002 | code_review | 55 | false | T102 | Eastern QA | 2024-03-05T14:20:00 | 4 | U1467 | 38 | 0.62 | M102 | U1456,U1467,U1478,U1489 | blank | Reviewed bug fixes; minor comments, completed on time. |
| EVT-0003 | standup | 18 | true | T103 | UK Legal | 2024-03-06T08:30:00 | 3 | U1513 | 6 | 0.36 | M103 | U1502,U1513,U1524 | Coverage gaps due to PTO; some updates missed. | Daily standup; limited participation, follow-up required. |
| EVT-0004 | chat | 37 | false | T104 | Remote Ops | 2024-03-06T13:45:00 | 5 | U1546 | 41 | 0.54 | M104 | U1535,U1546,U1557,U1568,U1579 | blank | Issue triage chat; quick decision, resolved smoothly. |
| EVT-0005 | planning | 215 | false | T105 | Tech Support | 2024-03-07T10:00:00 | 10 | U1623 | 159 | 0.92 | M105 | U1590,U1601,U1612,U1623,U1634,U1645,U1656,U1667,U1678,U1689 | blank | Quarterly planning; high engagement, decisions made. |
| EVT-0006 | document_edit | 28 | false | T106 | Analytics Team | 2024-03-07T15:30:00 | 2 | U1700 | 8 | 0.45 | M106 | U1700,U1711 | blank | Drafting analytics report, edits completed. |
| EVT-0007 | meeting | 70 | true | T107 | R&D Europe | 2024-03-08T09:00:00 | 17 | U1722 | 135 | 0.86 | M107 | U1722,U1733,U1744,U1755,U1766,U1777,U1788,U1799,U1800,U1811,U1822,U1833,U1844,U1855,U1866,U1877,U1888 | Large group led to slow progress; recommend smaller breakout. | All-hands workshop; too many participants, consider splitting. |
| EVT-0008 | other | 0 | true | T108 | Freelance Designers | 2024-03-08T15:15:00 | 3 | U1900 | 0 | 0.11 | M108 | U1899,U1900,U1911 | Scheduled workshop canceled, no progress made. | Missed event; reschedule required. |
| EVT-0009 | chat | 32 | false | T109 | US Marketing | 2024-03-09T14:10:00 | 4 | U1933 | 36 | 0.49 | M109 | U1922,U1933,U1944,U1955 | blank | Marketing update chat; brief and focused. |
| EVT-0010 | document_edit | 73 | false | T110 | Customer Success | 2024-03-09T16:20:00 | 5 | U1977 | 13 | 0.39 | M110 | U1966,U1977,U1988,U1999,U2000 | blank | Customer feedback doc; edits and comments reviewed. |
| EVT-0011 | standup | 14 | false | T101 | Pacific Devs | 2024-03-10T08:25:00 | 3 | U1341 | 7 | 0.24 | M101 | U1234,U1327,U1341 | blank | Daily standup; routine updates, no issues. |
| EVT-0012 | code_review | 72 | false | T102 | Eastern QA | 2024-03-10T13:50:00 | 5 | U1478 | 57 | 0.73 | M102 | U1456,U1467,U1478,U1489,U1513 | blank | Reviewed new test cases; some rework needed. |
| EVT-0013 | meeting | 112 | false | T103 | UK Legal | 2024-03-11T10:10:00 | 13 | U1502 | 128 | 0.78 | M103 | U1502,U1513,U1524,U1546,U1557,U1568,U1579,U1590,U1601,U1612,U1623,U1634,U1645 | blank | Legal project kickoff; clear goals, strong engagement. |
| EVT-0014 | planning | 188 | false | T104 | Remote Ops | 2024-03-12T11:45:00 | 11 | U1557 | 133 | 0.97 | M104 | U1535,U1546,U1557,U1568,U1579,U1590,U1601,U1612,U1623,U1634,U1645 | blank | Monthly strategy session; positive outcomes. |
| EVT-0015 | document_edit | 19 | false | T105 | Tech Support | 2024-03-12T16:30:00 | 2 | U1667 | 5 | 0.29 | M105 | U1656,U1667 | blank | Quick edit for tech guide; completed as planned. |
| EVT-0016 | chat | 22 | false | T106 | Analytics Team | 2024-03-13T14:00:00 | 4 | U1711 | 33 | 0.57 | M106 | U1700,U1711,U1722,U1733 | blank | Data clarification chat; fast resolution. |
| EVT-0017 | meeting | 81 | false | T107 | R&D Europe | 2024-03-14T09:05:00 | 12 | U1755 | 99 | 0.72 | M107 | U1722,U1733,U1744,U1755,U1766,U1777,U1788,U1799,U1800,U1811,U1822,U1833 | blank | Research update; some tasks delayed, generally positive. |
| EVT-0018 | standup | 25 | true | T108 | Freelance Designers | 2024-03-15T08:40:00 | 2 | U1900 | 3 | 0.19 | M108 | U1899,U1900 | Only one update given; missed deadline. | Low attendance standup; action items pending. |
| EVT-0019 | document_edit | 109 | false | T109 | US Marketing | 2024-03-15T15:00:00 | 7 | U1922 | 16 | 0.44 | M109 | U1922,U1933,U1944,U1955,U1966,U1977,U1988 | blank | Ad campaign edits; required urgent changes. |
| EVT-0020 | planning | 203 | false | T110 | Customer Success | 2024-03-16T11:10:00 | 13 | U2011 | 151 | 0.89 | M110 | U1999,U2000,U2011,U2022,U2033,U2044,U2055,U2066,U2077,U2088,U2099,U2100,U2111 | blank | Customer journey mapping; excellent collaboration. |
What the 200 rows show
from the 200-row samplePlanning (event type) stands out: mean duration_
- 20%bottleneck_
flag = true - 50median duration_
minutes - 45team names
- 49managers
- 4median participant_
count - 33median communication_
frequency
Median 50, from 0 to 300.
- string 9
- integer 3
- float 1
- datetime 1
- boolean 1
Columns
15 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 9 columns | |||
event_id | string | Unique identifier for each collaboration eventunique | EVT-0001 |
team_id | string | Unique identifier for the remote team involved in the event | T101 |
team_name | string | Name of the remote team | Pacific Devs |
event_type | string | Type of collaborative event (e.g., meeting, chat, document_edit, code_review)7 values | meeting |
participant_ids | string | Comma-separated list of user IDs participating in the event | U1456,U1467,U1478,U1489 |
initiator_id | string | User ID of the person who initiated the event | U1234 |
bottleneck_description | string | Description of the bottleneck identified, if anyoptional | Coverage gaps due to PTO;… |
manager_id | string | User ID of the manager responsible for the team | M101 |
event_notes | string | Additional notes or comments about the eventoptional | General team sync; lively… |
| Numbers 4 columns | |||
duration_minutes | integer | Duration of the event in minutes0 or more · optional | 95 |
participant_count | integer | Number of participants involved in the event1 or more | 14 |
communication_frequency | integer | Number of communications/messages exchanged during the event0 or more · optional | 112 |
engagement_score | float | Calculated score representing participant engagement during the event (0-1 scale)0 to 1 · optional | 0.81 |
| Dates and times 1 column | |||
event_datetime | datetime | Date and time when the event occurred | 2024-03-05T09:15:00 |
| True or false 1 column | |||
bottleneck_flag | boolean | Indicates if the event surfaced a productivity bottleneckoptional | false |
Use it for
A technology dashboard
The bottleneck_
flag rate, duration_ minutes by event_ type and a breakdown of team_ id. Excel, Power BI or Tableau. Why do the 28 planning rows have a mean duration_
minutes of 217.2? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Events200EVT-000195meetingEVT-000318standupEVT-000770meeting
A software demo
Believable events with team_
id, team_ name and event_ type to fill a screen in front of a buyer.
This dataset200 rows15 columns
Yours1,000 rows15 columns
blueprint · remote-team-collaboration-activity
Behind this dataset
Same schema. As many rows as you need.
These 200 rows came out of a blueprint — 15 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- Log event type (meeting, doc edit, etc.)
- Include participant count
- Flag inactive teams
- Exclude content details
- Group activity by week
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- remote-team-collaboration-activity