One list
Codes defined in a single place
Disciplines, tag types, areas, systems, companies and roles live as controlled reference lists rather than as free text typed differently by each team.
Master Data
Every report is only as good as the list behind it.
Master data is the set of controlled reference lists that Deskely uses everywhere — disciplines, tag types, areas, systems, companies. Get it right at project setup and scoping, filtering and progress reporting stay reliable for the life of the project.
No credit card required · 14-day free trial
Everywhere
Consumed by every module
Tags, templates, scoping rules, filters, dashboards and certificates all read the same values, so what you select in one place means the same thing in the next.
Governed
Changed by people who should
Managing master data is a permission. Edits and deletes are treated as controlled actions because they reach every record that references the value.
The problem
Five spellings of one discipline is five different projects.
Reference data usually starts as free text. One engineer types MEC, another types Mechanical, a third imports a vendor list that says MECH. Nobody notices, because each entry looks correct on the record it was typed into.
It surfaces later, and always at the worst moment. A template scoped to a discipline applies to a third of the tags it should. A filter for an area returns a clean list that quietly excludes two hundred items. A weekly progress figure moves because someone corrected a spelling, not because any work was done.
Fixing it late means touching tags, templates and issued records at once, on a live project, while people are still using them. The cost is not the typing — it is the week spent reconciling numbers nobody trusts and the credibility lost with the client in the meantime.
How it works
Set up once at the start, relied on for the whole project.
Master data is a short piece of work at project setup that quietly determines whether every filter, template and progress report behaves for the next two years.
CARD
Agree the categories
Decide which lists the project runs on — disciplines, tag types, areas, systems, companies, roles — before the first tag is created.
CARD
Set the unique codes
Each entry gets a unique code and a description. The code is what the system reasons with; the description is what people read in dropdowns and reports.
CARD
Build the tag register on it
Tags select from the lists rather than accepting free text, so the register is consistent from the first import onwards — including when AI Population creates it from EPC documents.
CARD
Scope templates by the same values
ITR, preservation and procedure templates apply to tag types and disciplines, so scoping rules match the register exactly instead of approximately.
CARD
Maintain it as a controlled change
Editing or removing a value reaches every record that references it, so changes are made deliberately by someone with the permission to make them.
RESULT
One vocabulary, end to end
A discipline means the same thing in a template, a filter, a dashboard and a certificate — because there is only one of it.
Project control
Values are picked from a list, never typed into a box.
Anywhere a discipline, tag type, area, system or company is needed, Deskely presents the project's controlled list. There is no free-text alternative to fall back on, which is what keeps the register clean without anyone policing it.
Because the same codes run through the whole platform, a filter behaves the way you expect it to. Scope an ITR template to a tag type and it applies to every tag of that type. Filter the punch register by discipline and you get all of it, not the portion that happened to be spelled your way.
Before changing an entry, you can see what depends on it — how many tags, templates and open records reference the value — so maintenance on a live project is a considered decision rather than a discovery made a week later in a progress meeting.
Assurance
Reference data is infrastructure, so it is treated like infrastructure.
A single careless edit to a shared list can move every number on the project. These rules hold on every entry, on every project, from setup through handover.
Managing master data is a role permission — users without it can select values but cannot change the lists
Every entry carries a unique code and a description, so the machine-readable key stays stable when wording changes
Values are selected from controlled lists wherever they are used, so free-text near-duplicates never enter the register
Usage is visible before an edit: how many tags, templates and open records reference the value
Changes to reference data are attributed to a user with a date and time
The same codes flow into tags, templates, punches, certificates and exports, so external reports match the system
When a progress figure is challenged, the discussion is about the work, not about whether two spellings of the same discipline have been counted twice.
Business outcomes
What this changes for your project.
Progress numbers that hold up
Totals by discipline, area and system are complete by construction, so the weekly report does not move because someone corrected a spelling.
Filters you can rely on
A filtered list is the whole list. Scoping, issuing and close-out all work against the same values, so nothing is quietly excluded.
Faster project setup
With the lists agreed first, the tag register, templates and scoping rules fall into place instead of being reworked once inconsistencies surface.
No late data clean-up
The reconciliation exercise that usually lands weeks before handover simply does not happen, because duplicates were never able to enter.
FAQ
Frequently asked questions.
Related Modules
Works seamlessly with other modules.
ITR Checksheets
Build templates with sections and steps, issue checksheets, and execute on tablet with evidence capture.
Preservation
Manage Preservation Work Lists with interval tracking, due-date management, and field evidence capture.
Access Control
Configure custom roles, module-level permissions, and signing rights across web and tablet.
