Business areas 21
Every Sense screen and every backend call sits in exactly one business area, in the product's own vocabulary — the dimension the Users, Orgs and Journey pages group by. This is the taxonomy, with test27's traffic over the last 1h against it.
?Names come from Linear's product-area labels first (EDC, TMF, EDL, Work Orders, Work Plans), then the sidebar the product ships. Each screen also carries a scope — where in the entity tree it sits — because URLs are organised by entity while areas are capabilities. Nine hand-picked keywords used to classify 17% of the declared routes; these rules place all 206, and a route they do not know lands in Unmapped, shown below, never in a grey Other.
| Area | Group | What it is | Share | Requests | Errors | Users | Orgs | Screens | Last |
|---|---|---|---|---|---|---|---|---|---|
| EDC | EDC | Data capture and review: subjects, visits, activities, queries, sign-offs, adverse events, protocol deviations, the adopted protocol, printed forms. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| TMF | TMF & EDL | Files: documents, staging, collections, TMF templates and their metadata, AI document processing and findings. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| EDL | TMF & EDL | Events: the Expected Document List — events, placeholders, event templates, and the study Audit tab that lists them. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Work Orders | AI Teammates | AI Teammates: work orders, their configs and templates, the AI-teammate inbox settings. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Work Plans | AI Teammates | AI Teammates: work-plan configs, instances and plan types, at org and study level. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Studio | EDC | Study build: study configuration, forms, questions, response sets, workflow, controls, triggers, training content. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Tasks | Tasks | The Tasks app and the task tabs on a study, site, subject or patient. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Studies | Studies & Sites | The study list, a study's overview, team and settings, its Sites tab and study-site pages. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Sites | Studies & Sites | The Sites app: site list, site detail, staff and credentials, site settings. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Trainings | EDC | Protocol training for staff and its log; the study's training settings. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Patients | Patients & Outreach | The Patients app: patients, leads, the subjects list, patient profiles, pre-screening and Chart Review. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Advocacy | Patients & Outreach | Both Advocates apps: campaigns, advocates, organisations, rates, screeners, payouts; the patient-portal preview. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Calendar | Patients & Outreach | Scheduling: the Calendar app and a site's calendar. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Insights | Insights & Finance | The Insights app (dashboards) and a study's Reports tab. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Monitoring | Insights & Finance | The study Compliance tab — CRA monitoring tasks and controls by category. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| AI Chat | AI Teammates | Chat threads and memory (chat-agent); the documents AI-chat pane. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Finance | Insights & Finance | Budgets and their activities, site cards, Tilda Pay. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Messenger | Patients & Outreach | The Messenger app. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Partners | Patients & Outreach | The Partners app. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Home | Platform | The org home screen. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Account & Org Settings | Platform | Sign-in, sign-up, 2FA, onboarding, Account Settings, Organization Settings. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Internal | Platform | Design system and thread-debug panes — not a business area. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Not Found | Platform | The /:orgId/* fallback. A broken link is a finding, so it is its own bucket. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
| Unmapped | Platform | A screen these rules do not recognise yet. It is counted here so the mapping can be fixed, never hidden. | 0.0% | 0 | 0.0% | 0 | 0 | 0 | — |
Where the work happens — the second dimension: scope, as a share of requests
The review that produced this taxonomy, with the nine boundary decisions and the data behind them: docs/taxonomy/business-areas-review.html. Query alerts can use it: area_rollup carries area and scope per five-minute row — "org X inactive in EDC for 6 h" is one SELECT.