7.1 Progress Bar Interpretation
The progress bar on a Productivity Board goal card shows how close the current achieved count is to the goal target for the active measurement period. The bar fills proportionally — a 50% filled bar means exactly half the goal has been achieved.
When the achieved count meets or exceeds the goal count, the progress bar reaches 100% and changes colour (typically to green). The progress bar can exceed 100% if the achieved count surpasses the goal — in these cases the percentage figure will display the actual over-achievement (e.g., 125%).
Note: The progress bar does not update in real time during the day. It reflects data calculated up to the end of the previous business day, or up to the most recent manual Generate Goal Details trigger.
7.2 Goal Achieved vs Goal Count
The goal card displays both the Achieved figure and the Goal figure as raw numbers. For count-based templates, these are plain integers — "Achieved: 14 / Goal: 20" means 14 qualifying activities have been counted against a target of 20. For monetary templates, the figures are displayed as currency amounts.
The Achieved figure is always sourced directly from the Zenople database — it counts actual records created or updated in the system that match the template criteria. It is not a manually entered figure and cannot be overridden by the user.
7.3 Revenue Period Math
The revenue period projections in the Finish Line are calculated as follows (in plain terms):
- Weekly projection — the Estimated Revenue is divided by the number of weeks in the Revenue Period to give a per-week figure.
- Quarterly projection — the Estimated Revenue is annualised and then divided by four to give a three-month figure.
- Six-Month projection — similar to quarterly but divided by two, giving the six-month equivalent.
- Yearly projection — the full estimated annual revenue, either entered directly or extended from a shorter-period estimate.
For computed opportunities, the starting point is Bill Rate × Number of Positions. The resulting amount is then extended to quarterly, six-month, and yearly figures.
7.4 Days Since Connect vs Days To Close
These two date-based columns serve distinct purposes and are often confused:
Days Since Connect answers: *How long has it been since anyone spoke to this prospective client?* It measures the gap between today and the most recent SalesConnect comment. A high value is a signal that the opportunity may need re-engagement.
Days To Close answers: *How long did it take (or how long will it take) to close this opportunity?* It measures the difference between the opportunity's creation date and its Closed Date (for closed opportunities) or its projected close date (for open ones). This metric is most useful in retrospective analysis of sales cycle length.
The two metrics are independent. A low Days Since Connect with a high Days To Close simply means the team has been in frequent contact with a client that is taking a long time to close.
7.5 Common Misinterpretations
"The progress bar hasn't moved today"
Progress bars only update after the overnight batch or a manual Generate Goal Details trigger. Activities recorded during the current business day will not appear until the batch runs overnight or you manually regenerate. This is expected behaviour.
"I can't find my Revenue Opportunity in Finish Line"
The most common reason an opportunity is missing from the grid is that the Sales Stage field was not populated when the record was created. Opportunities without a Sales Stage are excluded from the grid. Open the record from the linked organisation profile and assign a Sales Stage to make it visible.
"The Days Since Connect shows a very high number but we've been calling them"
Days Since Connect is driven by comment activity with a SalesConnect-type category. If calls and emails are being made but not logged as comments on the organisation record, the system has no way to know they happened.
"Revenue projections look inflated"
Check the Revenue Period selected and confirm whether the opportunity is in Free-form or Computed mode. In Computed mode, projections are based on Bill Rate × Positions × working periods. If the Markup was entered too high or the Pay Rate is incorrect, the resulting projections will be proportionally inflated.
"Goal count is different from what I expected"
Productivity goal counts are calculated from the Zenople database records, not from any manual entry. Confirm that the activities you expect to be counted are recorded in the correct module, against the correct person or organisation, and within the active measurement period.
7.6 Best Practices for Analysis
- Check the date range before drawing any conclusions from Insights tabs or Dashboard widgets. A wrong date range is the most common source of misleading figures.
- Use frequency filters consistently on the Productivity Board. Comparing a monthly goal count with a yearly goal count in the same view can distort the visual comparison.
- Log contact activity immediately when using the Finish Line. The Days Since Connect metric is only as accurate as the comment log. Sales teams should log every client contact as a comment within the same working day.
- Trigger Generate Goal Details at the end of the business day if you need to present the Productivity Board to management and want it to reflect today's work.
- Review Closed Date accuracy periodically. Because Discarding an opportunity does not automatically set the Closed Date, ensure your team sets it manually when discarding.
- Use Insights tabs as context, not conclusions. Insights data is aggregated. Use it to identify areas that warrant deeper investigation, and follow up with specific searches or reports before making major decisions.