Skip to main content
This page covers Data Validation check detail and history views. For dashboard-based validation widget results, see Validation Widgets in Dashboards.

What you see on the page

There are two high-level result views used for quick status checks:
  • Project page Data Validation widget: compact check cards in the project page for quick scanning.
  • Checks page cards: check cards with score, status, trend hint, and scoped model count.

Drill into a check

These high-level views are a KPI heads-up layer for rules defined by your team. Use them to spot drift quickly, then drill into a specific check for detailed analysis. When you open a check result page, you typically see:
  • a top-level check score and status (aggregate across all models in scope)
  • a per-rule list showing pass/warn/fail outcomes
  • expandable rule rows to inspect logic flow (WHERE → CHECK) and counts at each step
  • model cards for each model included in the check scope
  • latest run details (time, model/version context)
  • historical trend for previous runs
  • an object-level detail table for investigation, including passing and failing objects
Selecting View result on a model card opens that model’s detailed result, where you can inspect the rule-by-rule breakdown, the light 3D viewer, and the data table. Threshold authoring: Checks — Thresholds and status.

Investigate failing objects

Expand a rule to fill the object table with its objects, coloured by outcome. Select the rule’s pass or fail count to list one side only. The table and the 3D viewer work together: what you narrow in the table is what the viewer shows.

Group by a property

Select No grouping above the table and pick a property, such as Level or Category. Each group lists how many objects it holds and how many fail the rule. Objects without the property sit in a (no value) group. Select a group to open its rows; select All groups to go back.

Select objects

Tick rows, or tick whole groups in the grouped view. The tick box in the table header selects everything the table shows, on every page, under the current filters; untick rows to leave them out. The viewer isolates what you select. Selecting more than 50,000 objects leaves the viewer showing the whole rule.

Show context as ghosts

Select Ghost filtered-out objects (the ghost button in the viewer toolbar) to draw hidden objects as faint, colourless ghosts around the ones you selected. With a group or filter applied, the ghosts are the objects in the whole model that match it, for example everything on Level 3, not only the objects the rule checks. Ghosts don’t get in the way: clicking selects the object behind them, and clicking only ghosts clears the selection.

Export the table

Select Export view to Excel (the download button above the table) to save what it shows as an .xlsx file: the current rule, filters and open group, with the visible columns. With a rule open, the file starts with two extra columns:
  • Status: Pass or Fail against the rule
  • Reason: for failures, the value found and what the rule expected
An export holds up to 50,000 rows.

Raise issues from failures

Turn failing objects into issues so the people who fix the model can track them.
1

Select the failing objects

Expand the rule, then tick rows or whole groups. Group first when you want one issue per level, category or type.
2

Select Raise issue

The dialog opens with a title and a description that tallies the objects’ status and reasons.
3

Complete and raise

Set the priority, assignee, due date and labels, then select Raise issue. You should see the new issue in the project’s issues list.
An issue only takes the objects that fail the rule. Passing objects in your selection are left out, and the dialog says how many. Raise issue stays unavailable while your selection holds no failing objects, and one issue can reference up to 2,000 objects. Each issue keeps where it came from:
  • In the 3D viewer, it opens framed on its objects, with the rule as a filter (failures ticked and coloured) and, when you selected whole groups, the group as a second filter.
  • In check results, open the issue from the project’s Issues page and select Open in check results to return to this rule, with the grouping, filters and selection you raised it from.
  • Label: every issue gets the workspace label Data Validation. If the workspace has no such label and you can’t create labels, the issue is raised without it.
You need permission to create issues in the project.

Share results

Select Share on a check or a model result to choose who can open it:
  • Project members: everyone in the project, signed in. Copy the link to send it.
  • Anyone with the link: a read-only snapshot that opens without signing in. Choose what to share (This result only or The whole check, as it is now), optionally add a password and an expiry (24 hours, 7 days or 30 days), then select Create link.
The dialog lists what recipients will and won’t see before you create the link. They see the check’s score and every rule’s outcome, failing and passing objects in a 3D viewer, and every object and property in the shared versions. They don’t see other models, versions or checks, the project, its members or its comments.
A public link shows every object and property in the shared versions, not only what the rules check. Share it only with people who may see that model data.
A public link is a snapshot: later runs, rule edits and new versions don’t change it. Recipients can investigate the results and export BCF; they can’t export the table or raise issues. Only project contributors can create a public link. Revoke a link from the Share dialog, or from Project settings → Tokens, which lists public check links alongside other share tokens. A link also stops working when:
  • it expires
  • the person who created it leaves the project
  • the check is deleted
Recipients then see This link is no longer available. If a shared model version is deleted later, that model shows Version no longer available and its 3D preview is gone.

Export BCF

BCF export from a validation result packages failing objects into topics with viewpoints so coordinators can triage outside Speckle. Use it when your issue workflow expects BCF; it does not replace fixing property data in the authoring tool.

Result states

The top section is the aggregate result for the check across all models in scope. Only error severity rules drive the overall score; info rules still appear in the breakdown.

If a result looks unexpected

1

Open latest check result

Start with current check score and top failing rules.
2

Drill into failing rules

Expand a rule to inspect its logic flow (WHERE and CHECK) and step-by-step counts. Rule-level viewing also populates the object table with pass/fail rows so you can inspect individual objects directly.
3

Compare with history

Confirm whether failures are regressions, recurring debt, or resolved trends.
4

Hand off the failures

Raise issues from the failing objects, or share the result or export BCF for people outside the project.
Before you retune rules, confirm:
  1. The result used the model and version you expected.
  2. Predicates or thresholds have not changed since the baseline snapshot (create a new check if you need different behaviour).
  3. Failures cluster by model or timeframe (data drift) versus looking like sporadic noise.

Check the model and version

Plans cap how many models attach. Every row references explicit version ids plus trigger and timestamp—carry that context when debating trends.

FAQ

PENDING appears when evaluation is still running in the background, or when no completed evaluation exists yet for that rule/run context.
Yes. Warning and pass thresholds can be configured globally and per rule in the authoring flow. See Thresholds and status.
Issues only take objects that fail the rule. Passing objects in your selection are left out, and the dialog says how many. If objects you expected to fail pass, review the rule rather than raising an issue.
Use both. Latest helps with immediate action; history helps with governance and trend confidence.
Last modified on November 16, 2026