Stood Flows · field usages · new

Which fields a process can see, and which it never fills

A field costs nothing to create and something forever: a layout slot, a permission to maintain, a column in every export, a question in every training. Field usages measures fill per record type, so the unused ones can leave the layout or the org.

statusbuilt after 1.3.2 · no release note yetfield schemas as a refresh step · 1.3.2docsKPI Table (Fields columns)Capability atlas

Three numbers, one funnel

For each process row, three amber columns read as a funnel. Allowed is what the profiles that see this record type may read, from field-level security. Visible is what the record type's layouts actually show. Unused is what is visible and filled on fewer than 5% of the records created in the window.

Field usages · Marina Concierge BookingSTOOD
Opportunity · Marina Concierge Booking 64,953 records · 4,811 created in the 12-month window AllowedFLS read, via the profiles and permission sets that see this record type 380 Visibleon the record type's page layouts 62 Unusedvisible, yet filled on under 5% of records created in the window 12 of which 8 deletable 318 allowed fields never reach a screen for this process: they are FLS maintenance only. Of the 62 on the layout, 12 are filled on almost no record: a question every concierge skips. The master row shows the intersection across record types that show the field. One cell, one windowed count per field read-only SOQL · anchored on CreatedDate · grouped by RecordTypeId COUNT(field) per record type one query per field, window 12 months, narrowed automatically on timeout: 12 → 6 → 3 months, never a full scan Newest-record sample 2,000 most recent records, for booleans, long text and record types with an empty window, where COUNT cannot answer Fill share filled ÷ created, per field, per RT compared with the folder threshold default 5% · editable per customer three outcomes, never conflated Unused measured, below threshold. A real finding. Counts toward the cell. Unmeasurable no FLS for the connected user, an unsupported type, or a query that timed out. Shown, not counted. No records nothing was created in the window, so fill cannot be judged. Cell reads —. The honest limit: with a Read-Only connected user, roughly one field in five is measurable. A broader read-only permission set on the audit user, still with no write, is what makes the column complete. Nothing in the engine can write. What 12 (8) means cell format in the matrix · click opens the field panel 12 (8) 12 unused fields visible on this record type, under 5% fill 8 deletable the org's own custom fields: can leave the org 4 standard or managed (NS__x__c) can only leave the layout; the package owns them the field panel, per field fieldfill %sampleon layoutskindverdict Charter_Deposit_Waived__c0.4%4,8112 of 6custom, owndeletable Guest_Loyalty_Tier__c2.1%4,8116 of 6custom, owndeletable · check reports loyaltyplus__Points_Hold__c0.0%4,8111 of 6managed packagelayout only
Illustrative — Meridian Hospitality Group. Threshold slider in the panel re-filters locally; the measurement itself is not re-run. Fields on no layout at all are listed by a separate metadata-only action.
What this means on Monday. Open the Unused cell of your busiest record type. Every own custom field under 1% fill with no report dependency is a removal candidate, not a debate.

Why per record type, again

A field that is empty on one process can be the whole point of another. Measured on the object, Charter_Deposit_Waived__c reads as "used"; measured per record type, it is filled on 0.4% of Marina Concierge Bookings and on 61% of Yacht Charters. The master row keeps the intersection (unused on every record type that shows it), so the org-wide verdict is conservative and the per-process verdict is actionable.

What the engine never does

Field usages runs read-only SOQL from the user's own Salesforce CLI session, grouped by record type and bounded by a window. It stores counts, never values. It cannot write, deploy or delete; the removal itself goes through your own release process; Stood Flows never executes a change.

In the app

Captured from the application itself, built from the current source tree and opened read-only on the Meridian demonstration workspace.

Fields → Allowed / Visible / Unused on the Meridian flagship org. Cells read unused (deletable); the master row shows the intersection.
Fields → Allowed / Visible / Unused on the Meridian flagship org. Cells read unused (deletable); the master row shows the intersection.