Faith Forge LabsChile
EnglishEspañol

Dashboards that show the work still requiring a decision

The field calendar can show completed visits while the office still has reports to assess and customers to update. Combining those events into a single “finished” total hides the reason work remains.

We build operational views around the decisions a team needs to make, with inspectable records and agreed definitions behind the summary.

Define the queue before drawing the chart

Start with the person using the view. An office reviewer may need reports ready for assessment. A coordinator may need assignments lacking an accepted instruction. A customer-service colleague may need approved results that have not yet been communicated.

Each queue needs a source, an eligibility rule and an action. The organization approves those meanings. A field colleague’s report may be evidence for review without being the office’s final approval.

The dispatched-versus-finished article shows how to test those distinctions with a small workload.

Preserve the boundary between a job and a visit

One job can involve more than one visit or attempt. Joining every start and end by job number can invent an interval that no person actually worked. A dashboard should retain the identifiers needed to understand which events belong together.

Time displays also need a stated purpose. An event’s occurrence time, its receipt time and the office review time answer different questions. A delayed update should not quietly rewrite the apparent order of the work.

The time and handoff guide provides a worked review of mismatched visit records. Such a review establishes the meaning of the display; it is not a staff-performance conclusion.

Show missing information honestly

A source that has not been checked is different from a checked source with no matching records. The view can show when information was last confirmed and what remains unknown. That helps staff decide whether to wait, investigate or contact the responsible colleague.

Access also applies to summary views. A broad total should not expose customer details that the viewer cannot otherwise open. The scope should explain the permitted aggregate and the drill-down behavior.

Let a reviewer challenge the result

Acceptance uses a known set of fictional records: a job assigned but not visited, a completed visit without a report, a report awaiting review and an approved result awaiting customer communication. The reviewer should be able to account for each record.

A corrected state must affect the appropriate queue while retaining the reason for correction. Another customer or job acts as an unchanged control. The view is useful when staff can identify the next action and explain why a record appears there.

Bring a safe version of the report your team currently assembles and the person who approves its definitions. We can scope the initial queues, supported data sources and maintenance of those rules.

Discuss an operational view · Review solution choices