Tier 1 · Configuration
A Sharedo tenant accretes configuration faster than it sheds it. Fields are added for one matter type and never removed; the same concept ends up stored two ways; forms grow to ask for data no one supplies. This audit measures the whole configuration estate against Alterspective's Sharedo configuration standards library and returns a prioritised, rule-referenced clean-up backlog.
Every attribute field is measured for fill rate across the live matter population. Dead fields (0% populated) and sparse fields (under 5%) are identified — the tell-tale of forms asking for data no one supplies.
The same concept stored two ways at once — free-text values in one field and option-set codes in another — which quietly breaks reporting and rule logic.
One field carrying true/false in some rows and 1/0 in others. Reports built on it silently under-count.
Logical fields configured twice under keys differing only by case or punctuation (for example reserve-amount versus ReserveAmount) — data splits across both copies.
Orphaned, unused, or duplicate option-set entries; values referenced by no active field.
Configuration is measured against our standards library — 19+ active standards across work types (CFG-WT), phases (CFG-PH), key dates (CFG-KD), option sets (CFG-OS), form fields (CFG-FF / CFG-FN), participants (CFG-PT), and security roles (CFG-RS) — with every deviation cited to a specific rule identifier you can read and challenge.
Work types, aspects, and rules present in the tenant but referenced by nothing live.
Configuration is captured through the administration API. This tier consumes configuration only — no matter content and no personal data leave the tenant. Fill rates are computed over the live matter population; every standards deviation is cited to a specific rule identifier.
Across a 287-field configuration estate, 189 fields (66%) carried almost no data, 1 field's values were stored two different ways at once, and 5 logical fields were duplicated under keys differing only by case or punctuation.
A shorter, higher-signal form estate; reports you can trust; and a prioritised clean-up backlog scoped to specific rule identifiers, so remediation is defensible to your board and, increasingly, to a regulator.