RealAdvice

WarpCore

WorkFlow PM

/

Track record

Screen

Track record

How a client organization’s engagements went, as an index out of 100, with its reasons and its stages.

What you need to know

The track record shows how a client organization's engagements with us went, as an index out of 100. Higher is better. It counts only what the client did and the parties it chose, never the other side, the assessor or our own work. It shows from the first engaged engagement, always with its count of engagements and its reasons. It records what happened. It does not predict.

How to get here

  • On an organization, select Insights. At the top of At a glance, the Track record group shows the line. Select Reasons and stages.
  • On an engagement's Overview, under the key of Progress, select Track record. It opens the report of the engagement's client.

The group and the line show only for a client organization with an engaged engagement.

What is on this screen

The line at the top gives the index, the client's place among every client organization with an engaged engagement, and its count of engagements. Top means at or above the middle; Bottom means below it. The question mark beside the line says what the index is.

Track record

Example · sample data

84 of 100 · Top 38% · 12 engagements
  1. The index. How its engagements went, out of 100. Higher is better.
  2. Place and count. Its place at the last dated update, and the engaged engagements the index rests on.

Below the line, from the top: Reasons, Payments, By stage, From FileMaker and History.

Section
What it shows
Reasons
At most three: the problems where the client is furthest above typical. Client counts its engagements with the problem, of those that reached it. Typical is the typical count on the same engagements, so it can have a decimal. Next step is what we can do about it. When no problem is above typical, the section does not show.
Payments
Closing invoice and True-up: whether the client pays late. Each reads Not measured yet until WarpCore reads payments. The Amounts row shows only to the people who see money, and also reads Not measured yet for now.
By stage
The twelve stages of the route. The figure under a stage counts the engagements without a problem there, of those that reached it.
From FileMaker
The engagements loaded from FileMaker. They count only by how they ended, because FileMaker recorded nothing else the index reads.
History
Closed until you open it. Each dated update of the typical figure and the places, oldest first.
No records

Own side pushed back counts the post-closing survey answers of the client's own side only: its own row, its lender when it is the buyer, the title company it introduced, and its own attorney and JV partner. The other side never counts.

By stage

Example · sample data

  1. A stage reached. A filled circle. Bold: fewer without a problem than typical. Its name opens its page.
  2. A stage not reached. An open circle: the client had nothing to do there.

A stage's page lists its tasks by their names in the workflow, each with its problem, its count Without a problem and Typical. A task's page lists the engagements behind it, each with Problem as yes or no, and the engagements from FileMaker under their own heading.

What you can do here

  • Read what the index means: point at the question mark beside the line.
  • Open a stage: select its name under By stage, or a reason under Reasons.
  • Open a task: select its name on its stage's page.
  • Open an engagement: select the circle beside its name.
  • Read the dated updates: select History.
  • Go back: select the link above the title.

Who can do what here

  • Everyone who can open an organization reads its track record, with the payment lines.
  • The Amounts row shows only to company administrators, the Accounting manager and executives.
  • A person whose only role is Executive observer reads the index and its reasons, and no payment line.

See Who can see and do what.

Things to know

  • The index sets no term and blocks no task. What to do about a reason is a person's choice.
  • The typical figure and the places change only at a dated update, each a line of History. Another client's day never moves this client's place.
  • Until the first dated update is over, the line shows no place and there is no history.
  • An engagement counts once it engaged: once the client decided to go ahead, or, for one from FileMaker, once it had Tax Advisory work.
  • The report names no person: engagements by their own names, tasks by theirs.
  • The track record never ranks clients against each other on a list.

Good to know

The payments count once WarpCore reads them from QuickBooks. Until then, the index rests on the other problems only.