RAiN Expert Foundation Course
The RAiN Expert Foundation Curriculum establishes the common operating standard required before an Expert begins package-specific training. It is deliberately limited to the knowledge and behaviours that apply across every implementation package. Technical depth belongs in the relevant package curriculum.
What you’ll learn
1Introduction to RAiN (Rivium AI Network)1 lesson
- Introduction - What is RAiNfree preview
- RAiN (Rivium AI Network) is a managed AI‑implementation service. Businesses buy implementation from RAiN; trained, verified experts deliver it, and RAiN keeps the work organised and quality‑checked from kickoff to handover.
2RAiN and the Expert Role2 lessons
- How RAiN Worksfree preview13m
- Expert Responsibilities, Conduct and Eligibilityfree preview6m
- The Expert understands the RAiN business model, the role of RAiN Experts, professional boundaries, package qualification, and project eligibility.
4The RAiN Implementation Methodology1 lesson
- Scope, Milestones, Deliverables and Acceptance Criteria
- Every package has a defined scope, and working outside it creates risk for time, quality, and cost. Projects are divided into milestones, each with deliverables and measurable acceptance criteria. A milestone is complete only when every deliverable is submitted, every criterion is tested, evidence is attached, known issues are documented, and any business approval is recorded. Scope changes must go through the RAiN platform, never an informal request.
5Business Discovery and Requirements Analysis1 lesson
- Data Privacy, Security and Responsible AI
- AI implementation gives Experts access to business documents, customer conversations, and personal information, and that access brings responsibility. Experts follow data minimisation and least-privilege access, protect credentials, use test data where possible, and never reuse business information for personal purposes. Because AI can produce incorrect or fabricated answers, high-risk responses need approved knowledge sources, clear restrictions, safeguards against prompt injection, and human escalation, with stronger controls in sensitive areas like medical, financial, legal, and personal records. Before handover, unnecessary Expert access is removed, and any security incident is reported immediately, never hidden.
6Package Scope and Delivery Control1 lesson
- Client Communication and Documentation
- Projects often fail because of unclear communication, not technical weakness. Experts ask specific, grouped questions, and keep questions, recommendations, risks, and decisions separate. Decisions are recorded, progress updates are concrete, and blockers are reported early with evidence. All communication stays inside RAiN, and documentation must let another qualified person understand what was built.
7Data Privacy, Security and Responsible AI1 lesson
- Testing, Quality Assurance and Issue Resolution
- Working once is not enough for handover. Each acceptance criterion gets test cases covering positive, negative, edge, integration, and AI response testing. Failed tests are logged as defects with severity levels, fixed, and retested, and critical issues must be resolved before handover. Evidence must never be manipulated, because QA exists to catch problems before they reach the business.
8Client Communication and Project Documentation1 lesson
- Business Training and Solution Handover
- Handover moves a tested solution into the business’s control. Training is role-specific and covers normal operation and common problems. The business takes ownership of all production assets, credentials are transferred securely, and unnecessary Expert access is removed. A final checklist confirms QA, documentation, training, ownership, accepted limitations, and clear support responsibilities.
9Testing, Quality Assurance and Issue Resolution1 lesson
- Using the RAiN Expert Workspace
- The workspace is the official record for every project. Experts review the full assignment before accepting, record questions, decisions, and blockers there, and submit evidence that proves each acceptance criterion. Blockers are reported with what, why, who, and timeline impact, and revisions are handled with corrected evidence and a clear explanation. Selecting a skill does not qualify an Expert for a package, since eligibility depends on training, assessments, labs, and quality history.
10Business Training, Handover and the Expert Workspace1 lesson
- Foundation Curriculum Closing Video
- Learners have completed the Foundation Curriculum, covering the path from intake to final acceptance. Next is the Foundation Assessment and Readiness Lab, after which they can begin package-specific training. The key message is that the Expert’s role is to deliver a reliable business outcome within an approved scope, quality standard, and process, not just to install tools.
11Course Assessment and Labs3 lessons · quiz
- How the Foundation Assessment works
- Requirements Analysis Exercise — instructions
- Submitting your lab evidence
- Knowledge assessment (30 questions, pass mark 80%), requirements analysis exercise, and readiness lab. Critical security questions must be answered correctly.
Your capstone
Requirements Analysis Exercise
In this section, you will review a short business request and convert it into structured implementation information.
Do not add capabilities simply because they appear useful.
Use only the information provided in the scenario.
Where information is missing, record it as an assumption or clarification question.
Your submission must contain seven sections:
The business problem.
The desired outcome.
Confirmed requirements.
Assumptions.
Dependencies.
Out-of-scope requests.
And clarification questions.
The purpose of this exercise is to test whether you can distinguish facts from assumptions and prevent uncontrolled project expansion.
Remember
- Use only confirmed information
- Do not invent requirements
- Record missing information
- Separate scope from preferences
- Ask testable clarification questions
Business scenario
BrightPath Academy is a private nursery, primary, and secondary school.
The school currently prepares student academic reports using spreadsheets. Teachers enter scores into separate files and send them to the school administrator.
The administrator manually combines the information and prepares report cards.
The process takes several days and errors are common.
The school wants an AI-powered academic reporting system that allows teachers to submit scores, automatically calculate totals and grades, generate student report cards, and notify parents when reports are ready.
The school has approximately 650 students and 45 teachers.
The school currently uses Google Workspace but does not have a school management system.
The school director also asks whether the system can collect school fees, manage admissions, track school buses, record student medical information, and automatically recommend whether a student should be promoted.
The school wants the first version ready before the end of the current academic term.
Expected Submission
1. Business Problem
The current academic-reporting process depends on separate spreadsheets and manual consolidation, resulting in delays and frequent errors.
2. Desired Outcome
Teachers should be able to submit student scores through a controlled process, after which the system calculates approved results, generates report cards, and notifies parents when reports are available.
3. Confirmed Requirements
- Support academic reporting for approximately 650 students
- Support approximately 45 teachers
- Allow authorised teachers to submit scores
- Calculate totals and grades using approved rules
- Generate student report cards
- Notify parents when reports are ready
- Work with the school's existing Google Workspace environment where appropriate
- Complete the approved first version before the end of the current academic term
4. Assumptions
- The school has documented grading rules
- The school maintains an accurate student and parent database
- Teachers have individual Google Workspace accounts
- Parent contact details are available
- The school has approved report-card templates
- Internet access is sufficient for daily use
5. Dependencies
- Access to the school's Google Workspace environment
- Approved grading structure
- Student, subject, class, teacher, and parent data
- Report-card design or template
- Approved notification channel
- Academic calendar and deadline
- Business approval of user roles and permissions
6. Out-of-Scope Requests
Unless included in a separate approved package:
- School-fee collection
- Admissions management
- School-bus tracking
- Student medical-record management
- Automated promotion decisions
7. Clarification Questions
- What grading scales and calculation rules does the school use?
- Are grading rules different across nursery, primary, and secondary levels?
- Who may enter, review, approve, and publish results?
- Can teachers edit results after submission?
- What report-card format is currently used?
- How should parents be notified?
- Should parents view reports online or receive downloadable files?
- What is the exact academic-term deadline?
- What historical student data must be imported?
- What approval is required before a report is released?
- How should missing scores, absent students, and incomplete subjects be handled?
- Are teacher comments required?
- Does the school require separate access controls for class teachers, subject teachers, and administrators?
Learner reviews
No reviews yet.