Field glossary
Field provenance: rows 1–36 describe captured context and human decision fields used in the historical reconstruction. Rows 37–44 are a proposed future AI-assisted triage extension and must not be read as evidence that an AI workflow existed historically.
| # | Fields (44) | Format / selectable options | Source | Description | Why it matters |
|---|---|---|---|---|---|
| 1 | Touchpoint name | Short text | Entered / confirmed | The named product surface, such as Careers website: External. | Keeps decisions at the surface users actually experience. |
| 2 | Touchpoint ID | Auto number or formula | System-generated | Stable identifier for one touchpoint record. | Lets the portfolio link context and history without duplicate rows. |
| 3 | Created | Created time | System-generated | Date the touchpoint record was first saved. | Preserves inventory history without making a new record look like a historical claim. |
| 4 | Intake status | Single select: Draft Ready for triage Active Archived | Entered / confirmed | State of the inventory record before and after triage. | Allows a touchpoint to be saved without prematurely assigning a support lane. |
| 5 | Touchpoint type | Single select: Website App Dashboard Platform Kiosk Other | Entered / confirmed | The kind of user-facing surface. | Distinguishes web, app, kiosk, and system-level needs. |
| 6 | Short description | Long text | Entered / confirmed | Brief description of what the touchpoint helps someone do. | Provides useful context before the essential journey is known. |
| 7 | Initiative | Linked records; optional: Associate Experience | Entered / confirmed | Top-level portfolio links. A touchpoint can have none, one, or several. | Allows a strategic theme to span multiple domains without forcing a match. |
| 8 | Domain | Linked records; optional: Careers Global Time & Attendance Pay & Benefits Learning & Development Field Operations Corporate Communications | Entered / confirmed | Organizational grouping links. A touchpoint can have none, one, or several. | Supports portfolio filtering and ownership context when it is useful. |
| 9 | Workstream | Linked records; optional: External Careers | Entered / confirmed | Organizational grouping links below Domain. A touchpoint can span several. | Preserves the portfolio hierarchy without treating Workstream as remediation work. |
| 10 | Project | Linked records; optional: Candidate Web | Entered / confirmed | Delivery-context links below Workstream. A touchpoint can have none, one, or several. | Connects a surface to relevant work without making a project required for inventory. |
| 11 | Audience | Multiple select: Public Internal Vendor | Entered / confirmed | Audience scopes that may apply to the same touchpoint. | Makes consequence and access context visible in prioritization. |
| 12 | URL or location | Short text; optional | Entered / confirmed | A direct URL, physical location, or other way to find the touchpoint. | Lets a reviewer locate the actual surface without treating a URL as a portfolio link. |
| 13 | Reach | Single select: High Moderate Targeted | Entered / confirmed | Relative audience scale. | Makes the scope of potential impact visible. |
| 14 | Lifecycle | Single select: Live In build Proposed Sunset | Entered / confirmed | Current state of the touchpoint. | Separates a live risk from a timely delivery window. |
| 15 | A11y maturity | Single select: Identify Build Embed Fix | Entered / confirmed | The accessibility maturity stage that best describes the touchpoint’s current need. | Clarifies whether to discover, design in, scale, or remediate accessibility work. |
| 16 | Sunset status | Single select: Not planned Sunset proposed Sunset in progress Sunset complete | Entered / confirmed | Whether linked project work is being reduced or sunset. Shown only when Lifecycle is Sunset. | Keeps an upcoming sunset visible without overloading lifecycle or support lane. |
| 17 | Essential journey | Long text | Entered / confirmed | The task the audience must be able to complete. | Protects consequential journeys from being lost in ranking. |
| 18 | Essential required journey | Checkbox | Entered / confirmed | Whether completion of the journey is required rather than discretionary. | Provides a clear protection input without turning the journey description into a tag field. |
| 19 | Alternate path available? | Single select: Yes Limited No | Entered / confirmed | Whether a meaningful route exists if the main journey fails. | No-alternate-path journeys receive explicit protection. |
| 20 | Signals | Multiple select: Historical risk Delivery timing High reach / no alt Shared-system impact Reusable pattern Cross-team dependency Inventory gap | Entered / confirmed | Observed evidence that may change the risk-and-impact decision. | Creates a visible, explainable basis for human review and prioritization. |
| 21 | Portfolio coverage | Single select: Baseline Funded | Entered / confirmed | The current support lane for the touchpoint. | Shows where deeper capacity is intentionally allocated while retaining a baseline floor. |
| 22 | Linked intervention | Linked records; optional | Entered / confirmed | Bounded audit, remediation, feature, ownership decision, or other intervention associated with the touchpoint. | Allows a touchpoint to remain one record while relevant work is connected to it. |
| 23 | Active intervention | Lookup text; optional | System-generated from linked intervention | Current audit, remediation, feature, ownership decision, or other bounded activity attached to a touchpoint. | Tracks active work without creating a duplicate touchpoint or repurposing Workstream. The view displays its title as text, not as a tag. |
| 24 | Linked epics | Linked records: ENG-129 | Entered / confirmed | Relevant delivery epics attached to the touchpoint. | Connects surface-level context to delivery evidence. |
| 25 | A11y support decision | Long text | Entered / confirmed | Agreed support scope and boundaries. | Makes allocation accountable rather than treating the risk category as an automatic decision. |
| 26 | Funding rationale | Long text | Entered / confirmed | Reason a portfolio lead chose or retained the Funded lane, such as strategic priority, regulatory commitment, or a leadership decision. | Lets a leadership priority be visible without changing the risk evidence. |
| 27 | Decision owner | Collaborator | Entered / confirmed | Person accountable for a funding or override decision. | Creates a clear approval trail. |
| 28 | Baseline support available | Long text | Entered / confirmed | The enablement, office-hours, standards, or escalation route available to all touchpoints. | Defines the floor for work that is not funded. |
| 29 | Targeted help path | Long text | Entered / confirmed | Potential escalation route, including office hours, lightweight review, planned assessment, or funded-capacity review. | Makes the move out of baseline legible and bounded. |
| 30 | Delivery window | Date range | Entered / confirmed | Planned delivery or review window. | Turns priority into a realistic roadmap choice. |
| 31 | Capacity notes | Long text | Entered / confirmed | Available support capacity and constraints. | Lets a proposed action be matched to actual bandwidth. |
| 32 | Next checkpoint | Long text | Entered / confirmed | Next decision or review moment. | Prevents funded support from becoming an indefinite promise. |
| 33 | Owner follow-up | Collaborator | Entered / confirmed | Accountable partner for the next step. | Ensures an intervention has a route to action. |
| 34 | Connected surfaces | Linked touchpoint records: Careers website: External | Entered / confirmed | Other touchpoints affected by the same system or pattern. | Helps route systemic issues once and avoid repeated local escalations. |
| 35 | Evidence to collect | Long text | Entered / confirmed | Specific context needed before changing a support lane. | Prevents a thin signal from being presented as certainty. |
| 36 | Comments | Long text | Entered / confirmed | Decision, review, or follow-up context attached to the touchpoint record. | Preserves the context behind a record without overloading the A11y support decision or risk rationale. |
| 37 | Future AI risk-and-impact result | Generated category: Critical High Managed Monitor | ✦ Proposed future extension | Categorical summary that could be derived from entered signals, journey protection, and current context. | Supports consistent triage in a future operating system without presenting a numeric score as precision. |
| 38 | Future risk override | Editable single select: blank, Critical High Managed Monitor | Proposed future extension | Optional leadership or portfolio-lead adjustment to a generated category. | Allows a justified exception while preserving the underlying recommendation. |
| 39 | Future override rationale | Long text; required when overridden | Proposed future extension | Reason for the change, with approver and decision date. | Makes future exceptions auditable and discussable. |
| 40 | Future final risk assessment | Formula / automation output: Critical High Managed Monitor | Proposed future extension | Would display an explicit override when present; otherwise the generated category. | Provides one consistent category without losing the underlying recommendation. |
| 41 | Future risk rationale | Generated text | ✦ Proposed future extension | Possible short explanation of the factors behind the risk-and-impact result. | Makes a future recommendation inspectable in a leadership or team conversation. |
| 42 | Future next action / assessment | Generated text | ✦ Proposed future extension | Possible smallest useful move, such as maintain baseline, office hours, lightweight review, or funded-capacity review. | Turns signals into a proportionate future proposal, subject to confirmation. |
| 43 | Future leverage result | Generated text | ✦ Proposed future extension | Possible shared-system or reusable-pattern opportunity. | Helps identify where one future intervention could improve several surfaces. |
| 44 | Future timing check | Generated text | ✦ Proposed future extension | Possible flag for a conflict between risk, active intervention, and roadmap timing. | Helps ensure a future plan does not defer an urgent critical-path need. |
Reading the provenance: the future-extension rows describe a possible assistive layer, not an automatic decision and not a historical capability. Funding remains a separate portfolio decision with its own rationale and owner.