Change Activity Insight (Beta)

This feature is currently in beta. Please share your feedback using the in-app feedback form.

Overview

The Change Activity insight helps you visualize how your organization’s flows are being updated over time, which users are submitting the most change requests and their approval rate, as well as a detailed log of change request activity. It highlights the volume and type of change management activity taking place in Procedureflow, giving you a high-level view of how knowledge is evolving across your workspace.

What this report shows

Changes over time graph

This report displays a stacked bar chart of change activity events for a selected time range and entry point. Every change activity event is included in the chart regardless of the current status of the change request.

Each bar represents the total number of change events per day (or per month, depending on your selected interval).

The following event types are currently included:

  • Created – New change requests created during the selected period.
  • Submitted for Approval – Change requests submitted for approval.
  • Approved – Change requests approved and published.
  • Cancelled Approval – Approvals that were withdrawn by the submitter.
  • Declined – Change requests that were rejected by the approver.
  • Requested Changes – Change requests returned to the submitter with feedback requesting additional edits before resubmitting.

You can adjust the date range and granularity (e.g., daily, monthly) to explore different activity windows.

Change requests submitted leaderboard

Below the bar chart is a leaderboard tracking the top 20 contributing users' change requests submitted and their approval rate within the selected date range.

Note   Approval rate is the percentage of unique change requests a member submitted during the selected date range that have been approved to date. Approval may occur outside the selected period.

Change activity log

At the bottom of the page is a detailed log of change activity for full audit visibility. It includes the user, the action they took, and the flow affected (where applicable). These include links to view the changes.

Exporting the activity data

You can export the data shown in the log. The export includes the total number of results stated at the bottom, even if they're on multiple pages—however, the maximum export size is 100,000 rows, so you should apply or change the filters to focus the results within that limit.

Click Export CSV. Since exports may be large, you will receive an email with a link to download a zipped CSV.  

The columns in the Change Activity CSV export include:

Column What it is Example Data Point Notes
At_UTC Timestamp at which the event occurred, in Coordinated Universal Time (UTC). 2025-11-27 19:10:56 UTC can be converted to local time by adding or subtracting the time zone offset in hours divided by 24 (e.g., =C2+(5/24) for UTC+5)
Entry_Point_Id Unique identifier for the entry point in which the event occurred. 1234
Entry_Point_Name The name of the entry point in which the event occurred. Training
Change_Request_Id Unique identifier for the change request in which the event occurred. 456789
Change_Request_Title The title of the Change Request in which the event occurred. Onboarding edits
Activity_Id Unique identifier for the event. 0123456
Type Type of event that occurred. flowModified
User_Id Unique identifier for the user that triggered the event. 67890
User_Name Name of the user that triggered the event. Jane Smith
Flow_Id Unique identifier for the flow that was connected to the event. 901234

The only event types that will have Flow data populated are events where a flow is directly impacted – e.g. Flow Added, Flow Modified etc..

Other event types apply to a change request rather than a flow (e.g. Created, Published, Submitted for Approval etc.)

Flow_Name Name of the flow that was connected to the event. New Hire: Week 1 Checklist

Why it’s important

Change activity provides a quick pulse on how actively your knowledge base is being maintained. Monitoring these trends helps you:

  • Understand whether process documentation is being kept up to date.
  • Identify periods of high or low update activity.
  • Spot potential bottlenecks in the approval workflow.
  • Meet audit and compliance requirements without manual tracking.
  • Recognize and reward contributors that are submitting quality change requests, keeping your process content up-to-date.

By visualizing this information, teams can better plan their updates, ensure content remains relevant, and maintain overall knowledge health.

Insights you can draw from this report

  • Consistency of updates:  Regular activity suggests healthy engagement with your content.
  • Spikes in “Submitted for Approval” or “Declined” events:  May indicate review bottlenecks or quality issues.
  • Low overall activity:  Could signal that process documentation isn’t being maintained as frequently as expected.
  • Who is contributing, and how:  Drives ownership, improves content quality, and boosts platform adoption.

Dive deeper with these 5 key questions to ask yourself when analyzing change activity.


Accédez à cet article en français