Best Practices

1. Naming Conventions & Data Quality

Consistent naming is the foundation of good asset management. Inconsistent names — like "Dell laptop", "DELL Laptop", and "laptop - dell" — make searching, filtering, and reporting unreliable.

Recommended Asset Naming Pattern

[Category] - [Manufacturer] [Model] #[ID]

✅ Good Examples

• Laptop - Dell XPS 15 #042
• Forklift - Toyota 8FGU25 #03
• HVAC - Carrier 50XC #Unit-A2
• Generator - CAT XQ230 #GEN-01

❌ Avoid

• dell laptop
• forklift 3
• air conditioner unit A
• Generator (backup)

check_circle Decide on a naming convention before you start and document it. Share it with your team so everyone follows the same format.
check_circle Use AI Normalization to audit and clean up existing assets. It detects typos, inconsistent capitalization, and suggests standardized names in bulk.
check_circle Always fill in the serial number field for equipment. It's the most reliable way to identify an asset and is required for API sync operations.
check_circle Keep custom field names consistent. If you call it "Engine Hours" in one template, don't call it "Hrs on Engine" in another.

2. Asset Management

How you structure your assets from the start determines how easy they are to manage at scale.

check_circle Use Asset Templates for all repeating asset types. Create a "Fleet Vehicle" template with standard fields (VIN, Year, Make, Model, Odometer) rather than adding those fields manually to each asset.
check_circle Use the Location field consistently. Establish a standard list of locations (e.g., "Site A - Warehouse 2", "Head Office - Level 3") and pick from them — don't type free text every time.
check_circle Attach documents at creation time. Upload warranties, manuals, and purchase records when you first create the asset. Retroactively finding documents later is time-consuming.
check_circle Use bulk import for large inventories. If you have 50+ assets, use the Excel bulk import rather than creating them one by one. Download the template, fill in your data, and upload.
check_circle Mark assets as inactive rather than deleting them. Deleted assets lose their history. Marking as inactive preserves the full audit trail while keeping your active list clean.
check_circle Set an expiration date for assets with a finite operational lifespan (fire extinguishers, certifications, leased equipment). You'll get automatic reminders before expiry.

📋 Asset Lifecycle Tip: For assets that go through different statuses (Active → Under Repair → Disposed), update the asset status field at each transition. This keeps your dashboard counts accurate and your team informed.

3. Maintenance Scheduling

Preventive maintenance is only as good as its scheduling. Inconsistent or missed schedules lead to breakdowns and compliance failures.

check_circle Create Task Templates for every maintenance type. An "Oil Change" task template with a pre-built checklist and parts list saves time and ensures nothing is missed.
check_circle Link Task Templates to Asset Templates. When a new asset of a certain type is created, its recurring maintenance tasks are generated automatically.
check_circle Set realistic due dates. A task that is always overdue is demoralizing. If a quarterly task keeps slipping, consider whether the interval is too aggressive for your team's capacity.
check_circle Always add completion notes. Require technicians to write what was done, what parts were used, and any anomalies observed. This builds a valuable maintenance history.
check_circle Review overdue tasks weekly. Schedule a standing weekly review of all overdue tasks in your dashboard. Unaddressed overdue tasks are a liability risk.
check_circle Assign every task to a specific person. Unassigned tasks have no owner and tend to fall through the cracks. Even if anyone can do it, nominating a primary responsible person creates accountability.

4. Team Collaboration

Taagger works best when your whole team is engaged. Here's how to drive adoption and accountability.

check_circle Assign roles carefully. Give Managers the ability to assign work but restrict admin-level settings to Owners and Admins. Use the Member role for read-only field staff who only need to scan and view.
check_circle Use comments to communicate in context. Instead of emailing about an asset issue, leave a comment directly on the asset or task. This keeps the full conversation in one place.
check_circle Train field staff before rollout. A 15-minute demo showing how to scan a QR code, update a task, and add a note is all most field workers need. Focus on mobile scanning.
check_circle Nominate a Taagger champion per team. Designate one person in each team or department as the go-to for Taagger questions. This reduces support load and accelerates adoption.
check_circle Use multiple companies for separate divisions. If you have distinct business units (e.g., "Construction Division" and "Plant Hire"), create separate companies to keep their assets, tasks, and teams independent while sharing one account.

5. Compliance & Documentation

For regulated industries, compliance documentation is critical. Taagger's compliance features are only useful if they're used consistently.

check_circle Attach compliance documents to the relevant Asset Template. This ensures every new asset of that type automatically has the right documents (e.g., a pre-start checklist on every vehicle).
check_circle Enable signature requirements for safety-critical documents. If someone must physically sign off on a pre-start inspection, set the document to require a digital signature before access is granted.
check_circle Review audit reports monthly. The audit trail shows every change made to every asset. A regular review catches data entry errors and unauthorized changes early.
check_circle Export audit reports before major events. Before a regulatory audit, a site handover, or an asset sale, export and archive the full audit report for that asset as a PDF.
check_circle Store certificates with their expiry dates as custom fields. Add a "Certificate Expiry" custom field to your templates and set asset expiration dates accordingly to get automated reminders.

6. Tagging Strategy

Physical tags are the bridge between your digital records and your physical world. Poor tagging defeats the purpose of the system.

Label Materials

• Indoor/office: standard paper or vinyl labels
• Outdoor/construction: UV-resistant polyester labels
• High-heat: metal or aluminium-backed labels
• Harsh chemicals: BOPP or polypropylene labels

Tag Placement

• Place at a consistent height and position on all assets of the same type
• Avoid hinges, moving parts, and high-wear surfaces
• Keep away from heat sources and direct sunlight
• Ensure the tag is visible without moving the asset

check_circle Use NFC for high-frequency scan points. If an asset is scanned multiple times per day (e.g., a toolbox or a piece of shared equipment), NFC tags are faster and more durable than QR codes.
check_circle Print tags at a minimum size of 2cm × 2cm. Smaller QR codes are harder to scan reliably, especially in low light.
check_circle Use ZPL format for label printers. If you have a Zebra or compatible label printer, download tags in ZPL format for direct, high-volume printing without a PC.

7. Security & Access Control

Protecting your asset data is as important as collecting it. Follow these practices to keep your company data secure.

check_circle Use the principle of least privilege. Assign team members the minimum role they need. Most field workers need only Member access; very few need Owner or Admin.
check_circle Rotate API keys periodically. If you use the REST API, regenerate keys every 90 days and immediately revoke any key associated with a team member who has left.
check_circle Use private tags for sensitive assets. Private tags require the user to be logged in before viewing asset details. Use these for assets with confidential information (valuations, sensitive serials).
check_circle Enable claim passwords (unlock codes) for shipped assets. When sending assets to recipients, use unlock codes (format: XXX-XXX) to ensure only the intended recipient can claim them.
check_circle Remove departed team members immediately. When someone leaves the organization, remove them from all companies in Taagger right away to prevent unauthorized access.

8. Integrations & Automation

Taagger's real power comes from connecting it to the rest of your operational stack.

check_circle Use webhooks for real-time notifications. Set up a webhook to post to Slack whenever a task is overdue or an asset status changes. This keeps your team informed without polling the app.
check_circle Use the sync API instead of create/update separately. The POST /api/assets/sync endpoint is idempotent — it creates assets that don't exist and updates ones that do, using serial number as the key. This is safer for ERP integrations.
check_circle Test webhooks with ngrok during development. Before deploying a webhook receiver, use ngrok to expose your local server and use the "Test Webhook" button in Taagger to verify payloads are received correctly.
check_circle Verify webhook signatures in production. Always validate the X-Taagger-Signature HMAC-SHA256 header on incoming webhook payloads to prevent spoofed requests.
check_circle Handle webhook retries idempotently. Taagger retries failed webhooks up to 10 times with exponential backoff. Ensure your receiver handles duplicate deliveries gracefully (check for duplicate event IDs).

tips_and_updates

Start simple, then automate. Get your team using Taagger manually for the first month before adding integrations. Once you understand your data flows, you'll know exactly what to automate.

Menu

In this guide: