What Is a Digital Truffle Inventory?

A digital truffle inventory is a maintainable system of verified find records, candidate habitat notes, and field metadata (coordinates, dates, species, methods, photos) across a woodland or estate—a habitat suitability map alone is not inventory.

Discovery maps are not inventory

Most confusion starts here:

• Discovery / screening: Models suggest candidate corridors; suitability scores are not probabilities.
• Inventory: Rows that say “on this date we hold this evidence,” backed by dog or expert verification, vouchers, or institutional protocols.

TruffleMaps products define the path from discovery to inventory through field discipline, not automatic promotion.

Why digital inventory in forests?

On large public and private woodlands, truffles intersect stewardship and harvest governance:

• Where permits and quotas apply.
• Revisit cycles and sustainable collection.
• Habitat change after fire, drought, or road cuts.
• Stakeholder reporting (local authorities, partners, research).

Digital records enable geographic queries and detailed report archives beyond paper notebooks.

Recommended minimum fields

| Field | Notes | |-------|--------| | Coordinate + precision | GPS / RTK comment | | Date and season | Ripening window | | Species (target / verified) | aestivum, magnatum, etc. | | Method | Dog, voucher, observation | | Habitat note | Trees, litter, slope | | Evidence | Photo, voucher code | | Suitability score (if any) | Planning context, not prediction |

Score fields must not imply “model % correct”—only why you visited.

Habitat discovery phase

1. Clarify boundary and legal status (contact for institutional processes). 2. Generate TruffleMaps habitat scores (how it works). 3. Execute corridor plans and checklists. 4. Enter rows as “candidate” or “unverified.”

VOC or sensor pilots do not create inventory lines by themselves; patent-pending integration remains decision support (technology).

Field verification phase

Institutions set the bar: dog teams, mycologist sign-off, lab vouchers. Digital inventory accepts records that meet the bar. Rejected dog alerts should not become inventory; log them as cancelled alerts.

Model feedback and data quality

Clean labels improve map feedback; dirty labels harm models. TruffleMaps feedback loops never market fake accuracy rates—data quality is an operational duty.

Institutional governance

• Role-based access: field entry vs executive reports.
• Change history: who edited what.
• External sharing: preserve “candidate habitat” vs “verified find” language.

TruffleMaps institutional scenarios support that separation.

Legal caution

Inventory does not grant picking rights or ownership. Even recording in protected areas may face restrictions—local law prevails.

Claims to avoid

• “The map is the whole inventory.”
• “High score = open an inventory row.”
• “Sensors auto-generate inventory.”
• “Guaranteed X% accuracy.”

Audit and external reporting

When auditors or municipalities ask for “truffle inventory,” submit verified rows only; attach candidate habitat separately. Label score fields as planning rationale—not prediction or probability. Change history (who deleted, who approved) underpins institutional trust.

Research collaboration

Partners may want anonymized coordinates and voucher codes. Contracts should define GPS sharing up front. Discovery maps generate hypotheses; publication claims still need field proof.

Short FAQ

Is a screening map inventory? No. Is a dog alert enough? Depends on institutional standard—often vouchers required.

Inventory maturity steps

Step 1 — Candidate: Map score + checklist; no verification. Step 2 — Observed: Crew notes, photos, negative or uncertain. Step 3 — Verified: Dog/voucher + approved label. Step 4 — Operational: Harvest plan, quota, permit-linked record. Skipping from 1 to 4 creates audit risk. Suitability scores justify Step 1 only.

Data lifecycle

Raw GPS → validated coordinate → linked photos → species label → approver → archive. Prefer “cancelled” rows with rationale over silent deletes. Score fields remain “planning rationale” to answer “why this corridor that year?” later—no probability or harvest forecast columns. Backups and role access should match institutional IT policy; clarify hosting during request-access.

Forest enterprise scenario

Annual plan: refresh screening maps, merge Steps 1–2, schedule dog week for Step 3, open Step 4 only on permitted ground. After fire, Step 3 rows become “historical”; new screening is mandatory. TruffleMaps archives show transitions with role access—no probability or guarantee language.

Sample inventory row (fictional)

Date: 2026-09-12. Coordinate: XX.XXXX, YY.YYYY (±5 m). Species: Tuber aestivum (verified). Method: Dog alert + voucher TM-2026-014. Habitat note: Oak, 3 cm litter, gentle slope. Planning score (reference): 68—not probability, visit rationale. Approver: Field lead A. Sharing: Internal. This is Step 3; it did not auto-generate from a map PDF. A separate negative visit row exists for a high-score empty corridor—not inventory.

Inventory reading habit

Ten weekly minutes: count candidate rows, verified rows, cancelled alerts. Ratios are internal QA—not marketing. Stakeholders get verified summaries only. Map scores must never become “find counts.” That habit keeps inventory and discovery maps apart for years.

Sources

• Forest inventory standards: national forestry inventory manuals (general).
• Fungal record protocols: regional scientific society guides.
• GIS data quality: general metadata standards.

Next step

Start habitat discovery and verifiable digital inventory on your woodland: request access or review institutional options on packages.