If your team collects information regularly, you may spend as much time preparing it as using it. Survey responses need to be matched with earlier records. Documents need to be read. Different teams use different definitions. Each report brings another round of checking.
This course explains how to organize that work as a continuing process. You will follow one example from collection to a reviewed finding, using Sopact Sense to make the approach concrete. You can also use what you learn to assess your existing tools.
Start with the introduction to Connected Data Intelligence.
Who the course is for
Foundations is for growing organizations where a small team manages recurring data collection and insight. You might run training, support participants, review applications, work with partners, manage a membership network, or bring results together across programs.
You do not need to be a data engineer. You do need a question worth answering and someone who can make decisions about the collection process.
The course introduces the concepts before asking you to build a detailed plan. You can read it to understand Sopact, or work through the practical steps using your own example.
Three minutes on why connected data matters before you add AI, and how to work through this course. Watch on YouTube ↗
One example through six lessons
A fictional training team wants to know: “Who is using what they learned, and who needs more support?”
Its information includes registration, attendance, assessments, mentor notes, and follow-up. The lessons show how to connect and interpret that evidence while keeping appropriate control over it.
| Lesson | What you will understand | What you can add to your plan |
|---|---|---|
| 1. Understand the approach | What Sopact does and when connected data becomes useful | One recurring question and its sources |
| 2. Understand AI approaches | How evidence reaches AI, how findings are reviewed, and how to compare setups | Requirements to test with your own records |
| 3. Build context | Five categories of context, from identity and history to interpretation, access, and purpose | A scoped context brief for one workflow |
| 4. Govern the work | Who owns collection, access, review, and follow-up | Responsibilities and permitted uses |
| 5. Measure change | How to interpret an outcome with its coverage and limitations | One clearly defined measure |
| 6. Report and choose a workflow | How to share a checked finding and plan the next cycle | A report brief and a first pilot |
The sequence moves from understanding the approach to applying it. The working evidence plan is available when you want to record your decisions.
Each lesson links to optional deeper readings. Open them when the question is relevant to your work; you do not need to read every supporting article.
What you should be able to do afterward
You should be able to explain what information your team needs, how it should stay connected, what AI may use, and who will review the results.
You should also be able to test a proposed setup with your own records. Ask it to handle the next update, a changed question, a missing response, and an access restriction. Those tests help reveal whether your team can keep the work running.
Choose one workflow next
After Foundations, choose the workflow closest to your immediate need. You do not need to complete every course.
- Training and programs: understand learning, practice, and follow-up.
- Participant and case support: connect support and progress over time.
- Applications, awards, and grants: organize evidence for review and later follow-up.
- Membership and networks: connect members, activities, chapters, and feedback.
- Partners and suppliers: follow commitments and supporting evidence.
- Portfolios: bring organization-level results together.
- All workflow paths: find the relevant customer or employee feedback path.
Use Measurement and Reporting when you need to agree on outcomes, define measures, or communicate results. If reporting requirements are driving the work, use that course alongside your chosen workflow so those requirements shape collection early.