Overview
Your organization structure in UniAsset - how you set up categories, locations, departments, and custom fields - determines how effectively you can manage, search, and report on assets. A well-designed structure:
- Scales with growth from 100 to 10,000+ assets
- Supports your workflows rather than fighting them
- Makes data entry easy with logical groupings
- Enables powerful reporting across meaningful dimensions
- Adapts to change as your organization evolves
This guide helps you design a structure that works for your specific needs.
Key Structural Elements
Categories (Asset Types)
Group assets by what they are:
- Computers & Laptops
- Mobile Devices
- Network Equipment
- Office Furniture
- Vehicles
- Manufacturing Equipment
Purpose: Different asset types have different tracking needs, lifecycles, and maintenance requirements.
Locations (Physical Spaces)
Group assets by where they are:
- Buildings
- Floors
- Rooms
- Storage areas
- Field sites
Purpose: Physical location tracking for audits, relocations, and facility management.
See Hierarchical Location Structure for details.
Departments (Organizational Units)
Group assets by who owns them:
- IT Department
- Human Resources
- Finance
- Operations
- Sales
Purpose: Cost allocation, budget tracking, and organizational accountability.
Assignments (Individual Responsibility)
Track who's responsible for each asset:
- Individual employees
- Role-based assignment
- Shared/pool assignments
Purpose: Individual accountability and day-to-day asset management.
Planning Your Category Structure
Functional Categories vs. Technical Categories
Functional Approach (Recommended for Most):
Computers & Laptops
Mobile Devices
Printers & Scanners
Network Equipment
Office Furniture
Audio/Visual Equipment
Groups by how assets are used.
Technical Approach:
IT Hardware
- Endpoints
- Infrastructure
- Peripherals
Facilities
- Furniture
- Climate Control
- Security Systems
Groups by technical domain.
Choose based on: How your team talks about assets and who manages them.
Category Depth: Flat vs. Hierarchical
Flat Structure (Recommended for < 500 assets):
Laptops
Desktops
Monitors
Printers
Chairs
Desks
Pros: Simple, easy to understand Cons: Many categories as you grow
Hierarchical Structure (For larger inventories):
Computers
├─ Laptops
└─ Desktops
Peripherals
├─ Monitors
└─ Printers
Furniture
├─ Seating
└─ Desks & Tables
Pros: Organized, scales well Cons: More complex setup
Common Category Patterns
Small Office (< 100 assets):
- Computers
- Office Equipment
- Furniture
- Other
Keep it simple with 4-6 broad categories.
IT Department:
- Laptops & Tablets
- Desktops & Workstations
- Servers & Storage
- Network Equipment
- Peripherals
- Mobile Devices
- Software Licenses
Manufacturing Facility:
- Production Equipment
- Quality Control Instruments
- Material Handling
- Safety Equipment
- Office Equipment
- Vehicles & Fleet
- Tools & Consumables
Healthcare Organization:
- Medical Devices - Diagnostic
- Medical Devices - Treatment
- Patient Monitoring
- IT Equipment
- Furniture - Patient Care
- Furniture - Office
- Facilities Equipment
Education Institution:
- Classroom Technology
- Lab Equipment
- Library Resources
- Sports Equipment
- Facilities & Maintenance
- Administrative Equipment
- Vehicles
Designing Location Hierarchies
Match Your Physical Reality
Single Building:
Main Building
├─ Ground Floor
│ ├─ Reception
│ └─ Mailroom
├─ Floor 1
│ ├─ Sales Department
│ └─ Marketing Department
└─ Floor 2
├─ IT Department
└─ Server Room
Multi-Site Organization:
North Region
├─ Seattle Office
│ ├─ Floor 1
│ └─ Floor 2
└─ Portland Office
└─ Main Floor
South Region
├─ Los Angeles Office
└─ San Diego Office
Depth Guidelines
Recommended Depth: 3-5 levels maximum
Level 1: Region/Campus/Building Level 2: Building/Floor Level 3: Room/Area Level 4: Zone/Section (optional) Level 5: Specific rack/cabinet (optional)
Avoid excessive depth: ❌ Too deep: Country > Region > City > Campus > Building > Wing > Floor > Zone > Room > Sub-area > Rack ✅ Better: Campus > Building > Floor > Room
Department Structure
Align with Organizational Chart
Match your company's actual structure:
Functional Departments:
Executive
Human Resources
Finance & Accounting
Sales
Marketing
Product Development
Operations
IT
Customer Support
Matrix Organization:
Departments (Cost Centers):
- Engineering
- Sales
- Operations
Projects (Alternative grouping):
- Project Alpha
- Project Beta
- Ongoing Operations
Use departments for primary organization, custom fields for project tracking.
When to Create Sub-Departments
Create sub-departments if:
- Department has 50+ assets
- Clear sub-teams with different budgets
- Need separate reporting for sub-units
Example:
IT Department
├─ Infrastructure Team
├─ Application Development
├─ Help Desk
└─ Security Team
Keep flat if:
- Small organization
- Departments change frequently
- Simple cost allocation needs
Custom Fields Strategy
When to Use Custom Fields
Add custom fields for:
- Industry-specific data (e.g., patient ID for medical equipment)
- Regulatory tracking (e.g., calibration dates, certifications)
- Cost center codes if different from departments
- Project tracking across departments
- Vendor-specific details not in standard fields
Common Custom Field Sets
IT Assets:
- Operating System
- IP Address
- MAC Address
- Employee ID (assigned user)
- License Key
- Last Patched Date
Manufacturing Equipment:
- Machine ID
- Production Line
- Rated Capacity
- Calibration Due Date
- Safety Inspection Date
- OEE Target %
Vehicles:
- License Plate
- VIN
- Mileage
- Fuel Type
- Insurance Expiry
- Next Service Due
Medical Devices:
- FDA Classification
- Biomedical ID
- Clinical Department
- Calibration Interval
- Service Provider
- Preventive Maintenance Due
Field Type Guidelines
Text Fields: Names, IDs, descriptions Number Fields: Quantities, capacities, measurements Date Fields: Expirations, due dates, inspections Dropdown Lists: Standardized values (status, type) Checkboxes: Yes/no values (warranty active, certified)
Status and Lifecycle Tracking
Standard Status Values
Define clear statuses for your asset lifecycle:
Minimal Set:
- Active
- Inactive
- Disposed
Expanded Set:
- Ordered (procurement stage)
- In Stock (received, not deployed)
- Active (in use)
- In Repair (temporarily out of service)
- Stored (long-term storage)
- Retired (no longer used, pending disposal)
- Disposed (removed from inventory)
Customize for your workflow: Add statuses that match real stages in your asset lifecycle.
Structure Examples by Organization Size
Startup (10-50 assets)
Categories:
- Computers
- Office Equipment
- Furniture
Locations:
- Office
- Storage
- Remote Workers
Departments:
- Engineering
- Sales
- Admin
Custom Fields: Minimal - use standard fields
Rationale: Keep it simple, easy to manage without dedicated staff.
Small Business (50-500 assets)
Categories:
- Laptops & Tablets
- Desktops
- Monitors & Peripherals
- Network Equipment
- Printers
- Office Furniture
- Other Equipment
Locations:
- Main Office
- Floor 1
- Floor 2
- Warehouse
- Field Equipment
Departments:
- Executive
- Sales & Marketing
- Operations
- Finance
- IT
Custom Fields:
- Warranty Expiration
- Vendor Name
- Purchase Order #
Rationale: Structured enough for growth, not overly complex.
Mid-Size Company (500-5000 assets)
Categories (Hierarchical):
IT Equipment
├─ Endpoints (Laptops, Desktops, Tablets)
├─ Infrastructure (Servers, Network)
└─ Peripherals
Facilities
├─ Furniture
├─ HVAC
└─ Security Systems
Vehicles & Fleet
Locations (Multi-Site):
Headquarters
├─ Building A (Floors 1-5)
└─ Building B (Floors 1-3)
Regional Offices
├─ Boston Office
├─ Chicago Office
└─ San Francisco Office
Warehouse & Distribution
Departments:
- C-Level
- Finance
- HR
- IT (sub: Infrastructure, Apps, Support)
- Sales (sub: East, West, Central)
- Marketing
- Operations (sub: Production, QA, Logistics)
- R&D
Custom Fields:
- Cost Center Code
- GL Account
- Vendor Contract #
- Criticality Level (High/Medium/Low)
- Lease vs Purchase
- End of Life Date
Rationale: Detailed structure supports complex reporting and compliance needs.
Enterprise (5000+ assets)
Categories: Standardized taxonomy with 3-4 hierarchy levels Locations: Full geographic + building + floor + room hierarchy Departments: Mirrors organizational chart with business units Custom Fields: Extensive, integrated with ERP/CMMS systems Asset Codes: Standardized naming + barcode/RFID tracking Workflows: Approval processes for acquisitions, transfers, disposals
Rationale: Mature, governance-focused structure for large-scale management.
Implementation Best Practices
Start Simple, Add Complexity as Needed
- Begin with basic categories, locations, departments
- Add assets and use the system for 30-60 days
- Identify gaps or pain points
- Add custom fields or sub-categories as justified
Don't over-engineer upfront. Let real usage drive complexity.
Plan for Change
Your structure will evolve:
- Office moves/expansions
- Departmental reorganizations
- New asset types acquired
- Changing business needs
Choose flexible structures that can adapt:
- Use "Other" or "Misc" categories sparingly but have them available
- Create "TBD" or "Pending Classification" temporary locations
- Plan for asset re-categorization over time
Document Your Structure
Create a reference guide:
Category Definitions:
Laptops & Tablets:
- Portable computers under 15" screen
- Includes 2-in-1 convertibles
- Tablets with keyboards
Desktops:
- Tower and small form factor PCs
- All-in-one computers
- Fixed workstations
Location Naming Standards:
Format: Building - Floor - Room Number
Example: HQ-F2-R205 (Headquarters, Floor 2, Room 205)
Department Codes:
FIN = Finance
IT = Information Technology
HR = Human Resources
...
Share this with all team members adding assets.
Train Users on Structure
Ensure everyone understands:
- Which category to use for each asset type
- How to select correct location
- Department assignment rules
- Required vs. optional custom fields
Consistent data entry maintains structure integrity.
Testing Your Structure
Create Sample Assets
Before full deployment:
- Create 20-30 sample assets representing your inventory
- Assign them to categories, locations, departments
- Run reports to see if structure makes sense
- Try searching and filtering
- Generate an audit report for a location
Ask Key Questions
Can I easily answer:
- How many laptops does the Sales department have?
- What's the total value of assets in Building A?
- Which assets are assigned to John Doe?
- What equipment is due for replacement this year?
- How many printers do we have on Floor 2?
If reports or searches are difficult, revise the structure.
Get Stakeholder Feedback
Show the structure to:
- Department heads (do departments make sense?)
- Facility managers (do locations work for audits?)
- Finance team (does it support cost allocation?)
- End users (is data entry straightforward?)
Adjust based on feedback before rolling out widely.
Common Pitfalls to Avoid
Too Many Categories
❌ Bad: 50+ categories for 200 assets
✅ Better: 8-12 broad categories with subcategories if needed
More categories = more complexity without benefit.
Location Overkill
❌ Bad: Individual desk locations for every employee
✅ Better: Room or department-level locations
Track assignment to users separately from physical location.
Inconsistent Naming
❌ Bad Mix:
- Categories: "Laptops", "Desktop Computer", "Printers/Scanners"
- Locations: "Bldg A", "Building B", "HQ-Building-C"
✅ Consistent:
- Categories: "Laptops", "Desktops", "Printers"
- Locations: "Building A", "Building B", "Building C"
Using Custom Fields for Standard Data
❌ Bad: Custom field for "Purchase Date" (already a standard field)
✅ Better: Use built-in fields first, custom fields for truly unique data
Custom fields are for special needs, not duplicating standard features.
No "Other" or "Uncategorized" Option
Problem: Unusual assets don't fit any category, data entry stalls.
Solution: Have catch-all options:
- "Other Equipment" category
- "Miscellaneous" location
- "General" department
Re-categorize later when you understand the asset better.
Migrating or Restructuring
When to Restructure
Consider major changes if:
- Current structure prevents useful reporting
- Growth outpaced original design
- Merger/acquisition brings new asset types
- Compliance requirements change
Restructuring Process
- Document current state - Export all assets
- Design new structure - Categories, locations, departments
- Map old to new - Create crosswalk spreadsheet
- Update in bulk - CSV export, modify, re-import
- Validate - Check sample assets, run reports
- Communicate changes - Train team on new structure
Timeline: Plan 2-4 weeks for organizations with 500+ assets.
Quick Tips
Think Long-Term
Design for where you'll be in 3-5 years, not just today.
Limit Hierarchy Depth
3 levels is sweet spot. 5 levels is maximum before usability suffers.
Mirror Existing Systems
Align with your accounting system, org chart, or ERP for easier integration.
Use Naming Standards
Consistent names for categories, locations, departments improve reporting.
Review Quarterly
Check if structure still serves your needs. Adjust as organization changes.
Next Steps
- Asset Naming Conventions - Name individual assets consistently
- Hierarchical Location Structure - Set up location trees
- Managing Categories - Create and organize categories
- Managing Departments - Set up department structure
- Scaling Strategies - Grow your asset management effectively
Common Questions
Should I set up the entire structure before adding assets?
Set up major categories and locations, but don't over-plan. Add detail as you go based on real needs.
Can I change the structure later without losing data?
Yes. Assets can be re-categorized, moved to new locations, or reassigned to different departments. History is preserved.
How detailed should categories be?
Detailed enough to support useful reporting, but not so granular that data entry becomes burdensome. Start broad, subdivide if needed.
Should departments match cost centers?
Ideally yes, for easier financial reporting. If they differ, use custom fields for cost center codes.
What if my organization structure changes frequently?
Keep structure simple and flexible. Use custom fields or tags for temporary organizational needs.
Need Help?
If you have questions not covered in this article, our support team is here to help.
Contact Support