nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Time to redline metrics

Peter_Berkowitz

Hi community 👋

We'd like to granularly track how long it's taking us to review + redline our MSAs, ideally tracking each individual turn (i.e. if in the midst of negotiating a single MSA we go through four different versions of our MSA, we'd like to record how long it took us to review each version).

In Ironclad, I think we'd be looking for the time between the two events in this screenshot:

Has anyone had luck tracking this kind of metric? I'm planning to look into using (1) the workflow updated webhook to trigger a (2) "Look up a specific workflow" as a way of getting at this information. Welcome any input, and thanks!

Find more posts tagged with

Live Training

Insights & Analytics

Status: None

Comments

Mel_Scott

My first thought here is that the data is absolutely in the report you can run from the dashboard - it does show how many 'pivots' between workflows I believe.... but I haven't gone deep into this yet.

Manuel_Martinez

I'm also very interested on this!

Peter_Berkowitz

Thanks, Mel!

I'm checking up with my team to make sure I fully understand that data, but I'm not actually seeing that information (🤔).

From the Workflow Actions table I can see the date of each approval, but I'd like to see each time a new version of a document is uploaded (and by whom), which doesn't appear to be the same thing as approvals.
Even if I have (1) total # of turns per workflow and (2) total workflow duration, that wouldn't be adequate. Analogizing to a restaurant, if I wanted to know how fast a restaurant's kitchen was, I wouldn't look at (1) how many times a party ordered and (2) how long a party stayed at a restaurant (i.e. I'd just be interested in how long it took the food to come out, each time a party ordered).

Would love to know if I'm missing something, thank you!

Peter_Berkowitz

I've done a bit more digging here – I think what we're really looking for is to record each time a new document version is uploaded on a workflow. So, this information, but in a structured format (i.e. csv).

With this information, we can then start to calculate how long it takes us to respond to each new document version (indicated by us uploading a new doc version).

Image 2021-08-06 at 4.54.56 PM.jpg

Jessica_Patel

I am interested in tracking more granular review times as well. We currently have anywhere between 3 and 7 approvers per workflow so I want to be better understand the SLAs for each approver. This data would allow us to better manage workloads and address requests out of SLA. Since the timestamp of the data points we're looking for live in the activity, maybe they just need to be unlocked or surfaced through the existing Workflow Metrics Report?

David_Bushby

Super keen for a solution to this as experiencing the same desire for this level of data visibility.

The other metric issue I've noticed is time in Review ends once it goes to Sign step, but if a party sends it back for one last change before signing, we go back to Review but this additional time starts accumulating in Sign step, not in Review.

Peter_Berkowitz

Okay, I've been looking into this more – so, with the Google Data Studio Time Between Versions Page that Ironclad provides, there's almost enough information to get exactly this metric in a structured format.

Currently, the Time Between Versions Page lets you export a CSV that has a row per document upload per workflow (so, workflow URL, time of upload, time since last upload, etc). However, the CSV doesn't provide information about who is uploading the document (!).

As a legal team trying to report out on our responsiveness / speed, we pretty much only care about the time it takes for us to upload a new document version, in response to a CFX colleague uploading a redlined document. We don't at all (!) care about how long after we return a document that a CFX colleague returns with more redlines. But the CSV / doesn't provide any distinction between these two figures, even though they are night and day for us.

I've asked Ironclad if they can simply add a column for document uploader – with that information, we'd then be able to reliably and quickly calculate average turnaround time for legal. Happy to keep this thread posted on what I hear back from Ironclad, and to also then share how I calculate legal's average turnaround time, assuming Ironclad is able to provide the document uploader informaion.

Fingers are crossed!

Mary_OCarroll

I dont want to spill any beans, but I think this feature is coming soon... 😉

Peter_Berkowitz

😮

Angela_Mendenha

@Peter_Berkowitz I manually calculated this early this year for my team, and then also pulled a couple complex workflows to highlight how long it was "really" in our hands. I think you could use info on who uploads the new version and focus the filter on just your Legal people. But it sounds like @Mary_OCarroll has the inside track on some info that is going to solve this for us. Woohoo!

James_Noake

It sounds like it's coming from the message above but there is a way to use Microsoft Automate to analyse this type of data

Allison_Schoening

I am really happy to have joined the community and see like-minded people wanting similar things 😁 We find it interesting that vendor turn tracking is coming soon, but the internal team turn tracking is not yet available. This is one of the primary reports (like top 2) that our executives want to see. Please Ironclad get this one out soon! 🤞