Visualising loan workload and processor performance in ClickUp dashboards

Executive overview

Managing loan pipelines across multiple brokers and offices in ClickUp is achievable, but the hierarchy limits cross-office reporting in a single widget. Assignees serve as processors; tasks serve as loans — mapping these clearly in documentation unlocks dashboard reporting. Use bar charts per office to track workload over time, and formula fields to measure early or late closings per task.

The key constraint: ClickUp cannot break out data by office and assignee simultaneously in one chart — build one widget per office instead.

Mapping the hierarchy for reporting

  • Spaces = offices; folders = brokers; lists = loan pools; tasks = individual loans
  • Assignee = processor — document this directly in the list description
  • Task name = loan ID — note this translation so the team stays consistent
  • Clear field mapping is required before dashboards can report meaningfully

Building workload distribution charts

  • Use a bar chart widget in dashboards, not a featured widget — custom gives full control
  • Set x-axis to time (day or week) to track workload changes over time
  • Set y-axis to task count, grouped by assignee to see per-processor load
  • Enable "include subtasks" if loans live at subtask level
  • Duplicate the widget once per office — ClickUp cannot split one chart by both office and processor simultaneously
  • If all offices are selected together, data merges into one view — useful for totals, not per-office breakdown

Tracking closing performance with formula fields

  • Add a formula field to calculate days between due date and close date
  • Positive result = closed early; negative result = closed late
  • Use the formula DAYS(due_date, close_date) — retype manually, clicking variables rather than copy-pasting, to avoid ClickUp parsing errors
  • Add a string suffix (e.g. "days early") for readability
  • Name the view something explicit, e.g. "Early close monitoring"
  • Sort and filter on formula fields is not available — scan the column visually for negatives

Using nested IF functions and emojis for triage

  • ClickUp supports nested IF functions inside formulas for conditional output
  • Emojis substitute for conditional formatting, which ClickUp lacks — they stand out visually in list view
  • Example logic: if days early > 20, show a celebratory emoji; if negative, show a warning emoji
  • Align thresholds with industry benchmarks (e.g. 45 days = on track, under 20 = at risk)
  • A formula gallery (available in the ProcessDriven membership) provides pre-built examples — retyping them manually avoids syntax errors

More like this — when you're ready for early access.

Join the waitlist for a personal account and content recommendations based on what you're working on.

No spam. Unsubscribe at any time.

You're on the list. We'll be in touch before launch.

Get early access to the full library.

Join the waitlist for a personal account and content recommendations based on what you're working on.

No spam. Unsubscribe at any time.

You're on the list. We'll be in touch before launch.

Be among the first to get personalised recommendations tailored to your stage in business.

No spam.

You're on the list. We'll be in touch before launch.

Be among the first to get personalised recommendations tailored to your stage in business.

No spam.

You're on the list. We'll be in touch before launch.