Custom fields software for asset management lets enterprise teams define and capture operational data specific to their processes, industry requirements, and asset types — beyond the standard fields that every asset management platform ships with. Every enterprise has data that matters operationally but doesn't fit generic templates: internal classification codes, industry compliance identifiers, certification numbers and expiry dates, equipment-specific technical specifications, regional regulatory categories. Without custom field capability, this data lives in parallel spreadsheets maintained alongside the asset management system — creating two disconnected sources of truth that consistently diverge. Strev's custom field management software eliminates this gap by letting any administrator define any field, deploy it immediately, and use it in search, reports, mobile, and operational workflows from the moment it's created.

Strev's no-code field builder supports eight custom field types: text fields for names, identifiers, notes, and codes; number fields for quantities, measurements, and ratings; date fields for certification dates, inspection due dates, MOT expiries, and any time-sensitive operational deadline; dropdown fields for predefined category selections like compliance tier, region, or classification; multi-select fields for assets that fall into multiple categories simultaneously; checkbox fields for binary true/false data like "MDM Enrolled," "Certified," or "Cold Chain Suitable"; URL fields for linking to external documentation; and currency fields for cost and valuation data. All field types are immediately available in search, reports, mobile, and bulk import from the moment they're created.

A new custom field in Strev is live across the entire platform in under five minutes from the moment an administrator begins creating it — with no developer involvement, no support ticket, and no deployment process. The administrator names the field, selects the field type, configures scope and rules, and saves it. From that save action, the field appears on all applicable records, becomes available as a search filter and report column, appears in the mobile app, and is recognized by the bulk import field mapper. This immediate deployment is what makes Strev's configurable asset management platform fundamentally different from legacy systems where adding a field requires weeks of configuration work and a software release cycle.

Yes. Any custom date field in Strev can be linked to the operational alert system during configuration. When a custom date field like "Next Calibration Due," "MOT Expiry," "ISO Certificate Expiry," or "Software License Renewal Date" is linked to alerts, Strev monitors every record containing that field and fires an alert to the configured recipient at defined lead times before the date is reached. This means a custom date field created specifically for your operational compliance cycle works exactly like a built-in warranty expiry date field — with the same automated monitoring, the same AI-powered risk prioritization, and the same escalation chain if the alert is not acknowledged.

Custom fields in Strev are fully platform-wide — not limited to record detail pages. From the moment a custom field is saved, it appears as a filter option in the search and filter interface alongside all standard fields, as a column option in the report builder, as an export column in data exports, as a field in the mobile app record view and edit interface, and as a recognized field in the bulk import AI field mapper. Filtering your entire asset inventory by a custom "Compliance Tier" field works exactly the same as filtering by "Asset Type" — with the same performance, the same filter logic, and the same export capability. Custom fields that only exist at the individual record level — a common limitation in competing platforms — provide storage without operational utility. Strev's custom fields provide both.

Yes. Custom fields in Strev can be marked as required for specific asset types, record types, or workflow stages — and the enforcement is at the platform data layer, not through UI hints or reminder messages. A required custom field cannot be bypassed: the record cannot be saved until the field is populated. This is particularly important for compliance-critical data — a medical device classification field, a security tier designation, or a hazardous material category — where the operational and regulatory consequences of incomplete data justify forcing completion before the record is accepted. Required field enforcement can be set at the field level or conditionally — required only when a related field has a specific value, using Strev's conditional logic system.

Yes. MSPs using Strev to manage multiple client environments can define different custom field sets per client — capturing client-specific data requirements within the appropriate client workspace without those fields appearing across other clients' records. An MSP managing a healthcare client with medical device compliance fields and an IT enterprise client with security classification fields uses the same Strev platform instance for both, with custom fields scoped to the relevant client environment. For MSPs providing asset management as a service, the ability to configure custom fields per client — quickly, without developer involvement — is a direct service delivery advantage over competitors whose platforms require platform-level configuration changes to add client-specific fields.