Ask what the inventory is for
An inventory can support teaching, community recognition, safeguarding plans, research, funding, or a local archive. Those purposes create different expectations about what should be recorded and who may use it. Begin with a conversation about the need the inventory is meant to serve, who requested it, and what would count as a useful result. UNESCO's guidance on drawing up inventories of intangible cultural heritage places communities at the center of identifying what matters to them. That principle should shape the working process rather than appear only in the introduction. A project should not assume that a large database is valuable simply because it is technically possible. A small record designed around a community-defined need may be more useful, safer, and easier to maintain.
Identify who has authority to decide
A craft community is rarely a single voice. Makers, teachers, material gatherers, elders, apprentices, organizations, families, and local authorities may hold different knowledge or responsibilities. Ask who should guide decisions, who should be consulted, and how disagreement will be handled. Avoid treating one interviewee as a spokesperson for everyone. A project team may need to compensate contributors for their time and make participation accessible in language, location, schedule, and format. Record which decisions belong to participants and which technical tasks belong to the archive or institution. If a community group identifies a review process or representative body, document how that process works. Shared authority is more than an invitation to comment after the categories and database have already been fixed.
Agree on what can be documented
Before recording a demonstration or collecting a recipe, ask which parts of practice are appropriate to describe, photograph, name, or share. Some knowledge may be public; other material may depend on relationships, timing, gender, initiation, ownership, or local protocol. A participant should be able to decline a question or request that a detail remain unrecorded. The project can still document the existence of a boundary without exposing the protected information itself. Explain whether audio, video, transcription, translation, and derivative images may be created. Do not treat a general release form as permission for every future use. Specific and revisitable agreement helps contributors understand where their knowledge may travel.
Build the record around local categories
Start with practitioners' vocabulary for materials, tools, actions, stages, places, and relationships. If an institutional taxonomy is required for search, preserve local terms beside it and explain the mapping. Do not translate a word into a generic equivalent and delete the original because it seems easier for software. Ask contributors how names should be spelled, whether pronunciation should be recorded, and how authorship or collective knowledge should be represented. Categories should make room for change: a craft may be practiced differently across families, seasons, regions, or generations. Leave space for uncertainty and disagreement. A well-designed record does not force a living practice into a fixed checklist merely to fit a database.
Plan access before collecting media
Choose access levels for each record and each kind of media. A public description may be suitable while a close-up, location, personal name, or detailed process sequence remains restricted. Explain who can view, download, reproduce, edit, and share copies, and what happens if permission changes. Digital files can be duplicated quickly, so discuss practical limits as well as ideals. If the project uses a public platform, show contributors how the page will appear and what metadata search engines may expose. If a record must remain local or offline, plan how authorized community members can still reach it. Access design is part of documentation, not a technical detail to postpone until publication.
Keep a traceable account of each claim
For every entry, record where information came from: a named interview, a workshop observation, a community meeting, a published source, or a researcher’s inference. Attribute statements at a level agreed with contributors. Distinguish a present-day observation from a historical claim and note when dates or locations are approximate. Keep original terms alongside translations and identify who supplied each one. This makes later correction possible and prevents an individual interpretation from becoming an untraceable fact. A record should include the date it was created, who reviewed it, and which version is currently approved for the intended audience. Clear provenance gives future caretakers a path back to the source without assuming that every source may be made public.
Return useful copies and invite correction
Decide how contributors and community organizations will receive copies before collection begins. A return package might include audio or video, transcripts, photographs, metadata, and a plain-language summary, depending on permissions and technical capacity. Use formats that people can open, and agree who will maintain the files. Invite review of names, descriptions, access levels, and translations before public release. Create a way to report an error or request a change later, and explain how quickly the project can respond. Returning copies is not a substitute for ongoing relationship, but it can prevent knowledge from flowing only toward an institution. The record should be useful to the people whose practice made it possible.
Treat the inventory as a living process
Craft practices change as materials, markets, teaching opportunities, and community priorities change. Set a review date and identify who may update an entry, approve a public version, or request withdrawal. Preserve earlier versions according to agreed policy so that change is visible without leaving outdated or restricted content publicly available. An inventory can note new materials, altered workshop patterns, or loss of access without declaring the practice either unchanged or disappearing. UNESCO's community-involvement guidance emphasizes participation across safeguarding work; sustained review makes that involvement practical. A living inventory is maintained through relationships, not merely server backups.
Measure success by usefulness and trust
A community-led inventory is successful when it serves the purpose participants identified, reflects their terminology, respects access decisions, and can be corrected over time. The number of entries or photographs is not a sufficient measure. Ask whether contributors can find the record, whether it supports teaching or planning, and whether the project has honored its commitments about attribution and copies. Keep a list of decisions still unresolved. If a project discovers that a planned use exceeds the original agreement, pause and return to the people concerned before proceeding. UNESCO's inventory guidance provides a framework, but each community determines its own priorities and appropriate forms of documentation. That is what makes the inventory a tool for safeguarding rather than an extraction exercise.