LER & TRUSTED WORKFORCE INFRASTRUCTURE WORKSHOP MODULE
Fragmented Systems & Source Responsibilities
Trace the information your exchange needs back to its sources—so partners understand who maintains it, how changes reach others, and which system connections are worth establishing.
Does this sound familiar?
The same information appears in several places
A completion, qualification, affiliation, or experience record is copied across platforms without a clear account of which source maintains the underlying information.
The most convenient copy becomes the source
Teams rely on an export, spreadsheet, or portal because it is accessible, even when another organization is responsible for confirming or updating the record.
“Ownership” means different things to different partners
The organization maintaining a claim, the team operating a platform, and the person described by the record are treated as though they have the same responsibilities.
Changes stop at the originating system
A correction or update is made locally while other systems, presented records, or receiving workflows continue using an earlier version.
Nobody knows where a correction should begin
A person or recipient identifies a problem but is passed among organizations that each control only part of the information or process.
The integration list grows faster than the use case
Partners propose connecting every available platform before establishing which information the selected exchange needs and what each connection would accomplish.
What are fragmented systems and source responsibilities?
System fragmentation occurs when relevant information is distributed across platforms, documents, exports, and organizational processes in ways that make its origin and maintenance difficult to understand.
The presence of several systems is not itself the problem. Different organizations may legitimately maintain different parts of a person’s learning and employment history.
Source responsibilities clarify which organization or process can establish a particular fact, who maintains the corresponding record, and how others should interpret and obtain updates to it.
Those responsibilities may differ by claim. A provider may confirm program completion, while an employer confirms a period of employment and an individual supplies an account of their experience.
This module traces the information needed for a selected exchange and clarifies the relationships among originating records, copies, transformations, and recipients.
A useful connection needs a clear source responsibility.
Connecting systems can make information easier to access.
It can also move uncertainty more quickly when partners have not agreed which source establishes a claim or who is responsible for maintaining it.
A copied record may be accurate at the time of export while no longer reflecting a later correction.
A combined profile may contain information from several sources with different authority and update arrangements.
The workshop makes these distinctions visible around the selected exchange.
That gives partners a clearer basis for deciding what should connect, what context must travel with the information, and who will respond when something changes.
Where source responsibilities can become unclear
Origin and authority
The selected claim or fact
Originating organization
Supporting process
Authority to confirm it
Limits of that authority
Storage and copies
Source record
Operational platforms
Exports and spreadsheets
Presented copies
Combined or derived records
Maintenance
Record steward
Update responsibility
Review frequency
Effective dates
Known currency limits
Corrections and changes
Where issues are reported
Who investigates
Who authorizes a correction
How changes reach others
Unresolved or disputed information
Useful connections
Information the exchange needs
Sending and receiving roles
Connection purpose
Required source context
Operating dependencies
The review focuses on the records and claims relevant to the selected exchange. It does not require a complete inventory of every system in the participating organizations.
How this module helps
Trace the relevant information
Follow selected claims from their originating processes through the systems and copies used in the exchange.
Clarify source responsibilities
Identify who can confirm, maintain, correct, and explain each important part of the information.
Examine update and correction routes
Determine how changes should reach the people, systems, or workflows that rely on the record.
Define useful connections
Identify the minimum source relationships and operating arrangements needed to support the selected use case.
The record people can access may not be the record someone maintains.
An agency portal may display completion information supplied by a provider.
A participant may download that information and present it elsewhere. A recipient may then retain a copy in its own process.
The workshop examines what each version represents and where a question or correction should be directed.
Example: “The portal and the provider show different completion information.”
A provider updates a participant’s completion record after resolving an administrative error.
An agency portal still displays the earlier export, and a previously downloaded document remains in circulation.
The workshop traces the record’s path and distinguishes the provider’s confirmation responsibility from the agency’s responsibility for its displayed copy.
Partners identify how the portal receives updates, what recipients need to know about the record’s date and source, and where a participant should begin a correction request. Any changes to an issued credential or its status become a separate question for the appropriate module.
Questions to review together
Which claims or facts does the selected exchange require, and which additional information is unnecessary?
Where does each claim originate, through which process, and who can confirm what it establishes?
Where does the information appear, and how do exports, transformations, or combined records relate to the originating source?
Who updates the information, what dates or conditions matter, and what can recipients reasonably assume about currency?
Where should an issue be reported, who resolves it, and how should a confirmed change reach affected copies or workflows?
Which connections are necessary for the selected exchange, and what responsibilities must accompany them?
What needs to connect?
The selected claim
The particular fact or account that the receiving workflow needs to understand.
The responsible source
The organization or process able to confirm that claim within defined limits.
The record’s path
The systems, exports, presentations, and transformations through which the information travels.
Maintenance responsibility
The people and processes responsible for keeping the relevant information current.
Correction and update routes
The arrangements for investigating problems and communicating confirmed changes.
The required exchange
The specific connections and source context needed by the selected use case.
When access substitutes for source clarity
Partners may rely on information without understanding its maintenance or limits.
- An accessible copy is treated as authoritative.
- A platform owner is assumed to own every claim it stores.
- Combined records lose their individual sources.
- Update dates are missing or ambiguous.
- Corrections remain local.
- Integrations are proposed without a defined purpose.
The exchange may reproduce conflicting or outdated information without a dependable route to resolution.
When source responsibilities are explicit
Partners can interpret the record and maintain a more useful exchange.
- Authority is defined for the selected claim.
- Storage and stewardship roles remain distinguishable.
- Copies retain their relationship to the source.
- Currency and update expectations are visible.
- Correction routes have responsible owners.
- Connections serve a defined information need.
The resulting map clarifies what others can rely on and where further confirmation is required.
A practical example: tracing completion information across three systems
A workforce agency wants participants to present preparation records to selected employers.
The provider maintains completion information in its learning system.
The agency receives a periodic export and displays selected fields in a participant portal.
Participants can download a summary that employers may retain with an application.
The workshop identifies the exact claim the employer needs: whether the person completed the selected preparation, together with enough context to understand what that means.
Partners trace where that information originates, how it is transformed, and which dates are preserved.
They identify the provider’s responsibility for confirming completion and the agency’s responsibility for representing the supplied information accurately.
They also examine what happens when the provider corrects the record after an export.
The group defines a proposed update and correction route, with questions about timing, retained copies, and credential status assigned for further review.
The result is a source-responsibility map and a prioritized connection brief. It does not assume that every copy can be remotely changed or that all systems need continuous synchronization.
Authority belongs to a claim and purpose, not simply to a platform.
A platform can contain records originating from several organizations.
Its operator may be responsible for access and availability without being able to confirm every underlying claim.
An originating organization may establish one fact while having no authority over another part of the same profile.
An individual may provide useful context about experience without presenting it as an employer-issued statement.
The workshop identifies these differences for the information within scope.
That prevents a broad label such as “system of record” from concealing the specific responsibilities the exchange needs.
An update route needs realistic limits.
Some exchanges can retrieve current information when it is needed.
Others rely on periodic exports, dated presentations, or records retained by recipients.
The appropriate arrangement depends on the use case, the consequences of stale information, and what the participating systems and organizations can support.
The workshop identifies those conditions without assuming that every source change automatically reaches every copy.
It also distinguishes correcting source information from updating an issued credential, notifying a recipient, or changing a downstream decision.
Each step needs an appropriate owner and a clear account of what remains outside its control.
WORKSHOP MODULE 2
Make the source relationships behind the exchange understandable.
This module is a focused minicourse and working session. Your team learns how to trace information across systems, applies the method to selected records, and develops a source-responsibility brief that can guide useful connections and a subsequent Gobekli configuration.
What can this module address?
The scope follows the exchange, receiving decision, and boundaries established through Workforce Infrastructure Direction.
- The claims and information the exchange requires
- Originating organizations and processes
- Authority to confirm selected facts
- Source records and operational systems
- Exports, spreadsheets, and presented copies
- Combined or transformed information
- Record maintenance and stewardship
- Update timing and currency expectations
- Correction requests and investigation routes
- Communication of confirmed changes
- Minimum useful system connections
- Operating responsibilities and dependencies
What kinds of responses might emerge?
The workshop identifies responses that clarify responsibility and reduce unnecessary complexity around the selected exchange.
Trace
Document where the selected information originates and how it reaches the receiving workflow.
Assign
Clarify responsibility for confirmation, maintenance, representation, correction, and connection operation.
Preserve
Identify the source references, dates, and transformation context that copies or combined records need to retain.
Reconcile
Define how conflicting versions or unclear responsibilities will be investigated and resolved.
Connect
Prioritize the source relationships and update routes needed for the selected use case.
Simplify
Remove unnecessary copies, requests, or proposed connections where they do not serve the exchange.
A proposed connection is useful only when its purpose, information, responsibilities, and operating conditions are understood.
What will we review?
The selected information
The facts, claims, and context required by the receiving decision.
The originating sources
The organizations, processes, and records behind that information, including their authority and limits.
The information’s path
The systems, exports, transformations, and presentations involved in the current or proposed exchange.
Maintenance arrangements
Who updates each record, how currency is represented, and which dependencies affect availability.
Correction and conflict handling
Where issues are reported, who investigates, and how confirmed changes should be communicated.
Connection requirements
The minimum useful connections, required source context, and responsibilities needing confirmation.
The working exercise
Your team traces one selected record or set of related claims through the systems and organizations involved in the exchange.
STEP 1
Select the information
Identify the claims and context the receiving decision actually needs.
STEP 2
Locate the originating sources
Name the organizations and processes able to confirm each important claim.
STEP 3
Trace systems and copies
Map where the information is stored, exported, transformed, presented, or retained.
STEP 4
Assign maintenance responsibilities
Clarify who updates the source, maintains representations, and explains currency or limitations.
STEP 5
Define correction and update routes
Identify where issues begin, who resolves them, and how changes should reach affected participants.
STEP 6
Prioritize useful connections
Specify the connections, source context, and confirmation tasks needed to support the selected exchange.
A draft Source Responsibilities & Exchange Connections Brief linking selected claims to their origins, maintenance, correction routes, and required connections.
CONNECTING THE WORK TO A POSSIBLE GOBEKLI SETUP
Keep the source context attached to the information.
The workshop can identify the source relationships and operating requirements a subsequent Gobekli configuration would need to preserve. Product availability, supported connections, and implementation scope would be confirmed separately.
A proposed setup might need to connect:
- Selected claims and receiving requirements
- Originating organizations and relevant records
- Authority and confirmation responsibilities
- Source references and record dates
- Copies, presentations, and derived information
- Transformation context and known limitations
- Maintenance and update responsibilities
- Correction contacts and resolution routes
- Connection purpose and operating ownership
- Review triggers and unresolved source questions
TalentSync could support relevant organizational and source-responsibility context. TalentPass and Passport Pages could form part of a scoped arrangement for individuals to organize or present information while retaining appropriate source distinctions.
The workshop does not assume that Gobekli replaces existing source systems. Its brief remains useful independently of a subsequent product engagement.
KEEPING THE WORK FOCUSED
What this module does—and what needs separate work
This module traces information and clarifies source responsibilities around a selected exchange.
It identifies maintenance, correction, and connection requirements that partners need to confirm.
Detailed identity matching, semantic mapping, credential status, permissions, integration design, and formal governance may require other modules or specialist work.
The module does not:
- Declare one platform authoritative for every claim
- Resolve every conflict in the underlying records
- Verify identity or match people across systems
- Establish the truth of every source statement
- Authorize access to records or create sharing permission
- Guarantee real-time updates or synchronization
- Remotely correct every retained or presented copy
- Replace detailed integration or data-governance work
The brief distinguishes confirmed responsibilities from proposed arrangements.
Source organizations and system operators retain responsibility for decisions and changes within their authority.
What should you bring?
Bring one selected exchange and examples of the information moving through it.
Redacted, synthetic, or summarized records can often support the exercise without exposing unnecessary personal information.
Useful inputs may include:
- The Workforce Infrastructure Direction Brief
- A description of the receiving decision
- Sample records or selected fields
- Relevant system and platform names
- Known originating organizations
- Export or presentation examples
- Descriptions of transformations or combined records
- Source references and available dates
- Current maintenance responsibilities
- Update schedules or known delays
- Correction procedures or examples of conflicts
- Source-owner and system-owner contacts
An incomplete map is a useful starting point. Unknown sources, unclear ownership, and missing update routes can become assigned confirmation tasks.
What can you leave with?
Source & Record Map
A view of the selected claims, originating records, systems, copies, and receiving workflow.
Responsibility & Authority Register
The organizations and roles responsible for confirmation, maintenance, representation, and correction.
Update & Correction Route
Proposed arrangements for investigating problems and communicating confirmed changes, with practical limits identified.
Connection & Configuration Priorities
The minimum useful connections, source context, operating requirements, and questions for a subsequent Gobekli setup.
These outputs begin with the information examined during the module. Final scope depends on the selected exchange, available materials, and boundaries established through Workforce Infrastructure Direction.
Where might the work lead next?
Shared Definitions & Semantic Interoperability
Clarify meaning when systems use different terms, fields, or relationships for the information being exchanged.
Record Quality, Evidence & Provenance
Examine completeness, accuracy, supporting evidence, and source history when tracing the record reveals questions about its claims.
Security, Procurement & Integration Readiness
Translate prioritized connections into technical dependencies, testing questions, review requirements, and implementation responsibilities.
Credential Issuance, Verification & Status can provide a deeper review when a source correction affects an issued credential or the way recipients check its current status.
Frequently asked questions
Questions organizations ask before beginning.
Agency and institutional technology leaders, source-system owners, record stewards, LER sponsors, and exchange partners that need clearer responsibilities across distributed information.
No. Begin with the information required by the selected exchange. A wider inventory may become useful later, but it is not the starting requirement.
It means the organization or process recognized as able to establish a particular fact within the selected arrangement. That authority should be specific to the claim and purpose, rather than assumed for every field in a platform.
No. An operator may maintain access, storage, or presentation while another organization is responsible for confirming the source information.
Yes. A combined record may contain provider-issued information, employer statements, individual accounts, and other sources. Their responsibilities and limits should remain distinguishable.
No. The workshop begins by understanding their current roles. A useful response may clarify responsibilities or improve a selected connection while existing systems remain in place.
Yes. Those are part of the information’s path and may be sufficient for some use cases. The review examines their purpose, maintenance, and limitations.
Identify the claim, source processes, dates, and responsibilities involved. The workshop can define an investigation and resolution route without assuming that the newest or most accessible copy is correct.
It can identify them and assign source responsibilities. Record Quality, Evidence & Provenance provides a deeper review of completeness, accuracy, evidence, and source history.
It identifies where matching is part of the exchange. Identity, Account Access & Record Matching examines that question in depth.
No. The appropriate timing depends on the use case and the consequences of stale information. Partners need a clear account of what the arrangement supports and what recipients should expect.
Not necessarily. Retained documents, downloaded records, and separate systems may require different responses. The workshop identifies those limits and the responsibilities for communicating changes.
This module traces source information and maintenance responsibilities. Credential Issuance, Verification & Status examines how an issued credential is checked, updated, expired, or revoked.
No. Source responsibility and access authority are separate questions. Permissions, purposes, and recipient obligations need their own review.
Begin with the receiving decision and identify what information is necessary. Prioritize connections that address a defined gap, with clear source and operating responsibilities.
The brief can define source references, organizational responsibilities, update context, and presentation requirements for a proposed configuration. Product fit and supported connections are confirmed separately.
Partners can confirm source responsibilities, resolve priority questions, test an update or correction route, and scope selected connections. Additional modules can address the deeper issues revealed by the map.
CONNECT INFORMATION TO ITS RESPONSIBLE SOURCE
Give every useful connection a clear foundation.
Clarify where information originates, who maintains it, and how questions or changes should move through the exchange.
Include Fragmented Systems & Source Responsibilities in an LER & Trusted Workforce Infrastructure Workshop built around your selected use case.