Application to Registration - EnglishConnect (EC App)
Application to Registration - EnglishConnect (EC App)
Overview
Application to Registration – EnglishConnect (EC App) is an EnglishConnect-led initiative in which Digital Operations provides the technical implementation required to move learners and institutions from application to registration and payment for EnglishConnect courses. The project connects the EnglishConnect program, existing Church identity systems, Anthology, and the EnglishConnect learning platform through a set of coordinated digital workflows.
From a Digital Ops perspective, EC App has two main delivery channels: a student-facing experience inside Companion Native (B2C) and an institution-facing web portal (B2B). Digital Ops is responsible for designing and implementing these flows, integrating them with existing systems, and ensuring that learners and institutional partners can progress smoothly from initial application to full registration and readiness to participate in EnglishConnect. This page focuses specifically on the scope, responsibilities, and current work of Digital Operations within this EnglishConnect project.
Main Objective & Expected Outcomes (Digital Ops Perspective)
From a Digital Operations perspective, the main objective of Application to Registration – EnglishConnect (EC App) is to design and implement the technical flows, integrations, and user interfaces that move EnglishConnect learners and institutions from application to registration and payment, both in Companion Native (B2C) and in the institution portal (B2B), in alignment with EnglishConnect strategy.
Expected Outcomes
Reliable end-to-end flows: Learners (EC3 and above) can apply, select a gathering, and be registered in Anthology through Companion, while institutions can register and pay for groups through the portal without manual workarounds.
Reduced operational friction: EnglishConnect staff and partner institutions spend less time on manual registration, tracking, and follow-up thanks to the digital flows implemented by Digital Ops.
Consistent data across systems: Application and registration data flows cleanly between Companion, the B2B portal, Anthology, and the EnglishConnect learning platform, improving reporting and decision-making.
Scalable foundation for program growth: The Digital Ops components (Companion feature and portal) provide a reusable, extensible foundation that can support additional EnglishConnect levels, markets, and partners as EnglishConnect expands.
How It Works (Digital Ops Perspective)
How EC App Fits Within Companion (Project, App, and Feature)
Within Digital Ops, “Application to Registration – EnglishConnect (EC App)” refers to the technical workstream owned by Digital Operations in support of an EnglishConnect project. This workstream includes:
A B2C feature inside the Companion Native app, built and maintained by Digital Ops, that guides eligible learners through the EnglishConnect application and registration process.
A B2B web portal that Digital Ops will implement for institutions and organizations to register and manage groups of EnglishConnect learners.
In other words, EC App is one project for EnglishConnect, but two surfaces for Digital Ops to deliver:
Inside Companion, EC App appears as a feature or feature flow that is part of the broader Companion ecosystem.
Outside Companion, EC App is a standalone web application that institutions access through a browser.
Digital Ops does not define EnglishConnect curriculum, policies, or program strategy. Instead, Digital Ops implements the technical flows, integrations, and user interfaces that support the application, registration, and payment steps agreed with EnglishConnect, and then hands learners off to the existing EnglishConnect learning platform where teaching and coursework occur.
B2C: Student Experience in Companion Native (Digital Ops Work)
On the student-facing side, Digital Ops is responsible for building a feature inside Companion Native that supports EnglishConnect application and registration for eligible learners. According to current alignment with the development team and EnglishConnect, this Companion experience is not intended for EnglishConnect 1 or 2; it is scoped from EnglishConnect 3 upward, with future higher-level EnglishConnect offerings added as EnglishConnect defines them.
From a Digital Ops standpoint, the B2C flow inside Companion includes:
Authentication via Church Account
Digital Ops integrates Companion Native with Church Account for sign-in, including support for non–Latter-day Saint learners who also create a Church Account managed by the Church. Identity management and account policies remain under Church and EnglishConnect ownership; Digital Ops is responsible for using those accounts correctly within Companion.
Application workflow for EnglishConnect
Digital Ops implements the UI and backend integrations that allow eligible learners to apply for an EnglishConnect course (starting from EC3 and higher levels). The exact questions, requirements, and rules for this application are defined with EnglishConnect; Digital Ops is responsible for making the process work reliably in the app.
Entry into the EnglishConnect area in Companion
Once signed in, learners access a designated EnglishConnect section inside Companion. Digital Ops designs and implements the navigation and screens that expose the EnglishConnect application and registration flow, following product direction from EnglishConnect.
Creation of registration in Anthology
After the application and gathering are confirmed, Digital Ops handles the integration with Anthology so that the appropriate course registration is created. This step is critical because it is where the system recognizes the learner as enrolled in the corresponding EnglishConnect course. Business rules and data mappings are defined in collaboration with EnglishConnect and other stakeholders; Digital Ops implements the technical integration and error handling.
Gathering selection
As part of the same flow, learners select a gathering (time and, where applicable, location or group). Digital Ops implements the logic and interfaces necessary to display available options, collect the learner’s choice, and pass that information correctly to the underlying systems.
Transition into standard Companion / BYU-Pathway flows
Once registration exists in Anthology, the learner re-enters the standard Companion experience for registered students. Digital Ops ensures that the EnglishConnect registration appears correctly wherever it needs to be surfaced in Companion and that the learner can move into any existing flows (such as payment capabilities) that apply to their situation.
Handoff to the EnglishConnect learning platform
The final step in the B2C workstream is to prepare the learner so that they can enter the EnglishConnect learning platform (where course content and activities live). Digital Ops does not own the learning platform itself, but is responsible for delivering the integrations and redirects that allow EnglishConnect to recognize the learner as registered and ready to participate.
In summary, on the B2C side, the role of Digital Ops is to design, build, and integrate the application and registration flow inside Companion for EC3 and higher levels, in alignment with the requirements defined by EnglishConnect.
B2B: Institution Portal (Digital Ops Work)
On the institution-facing side, Digital Ops is responsible for implementing a web-based portal where organizations can manage EnglishConnect participation at scale. The B2B experience is intended to support all EnglishConnect levels (currently EnglishConnect 1, 2, and 3, with future levels added as they become officially available).
From a Digital Ops perspective, the B2B portal will include:
Institution administrator access and sign-in
Digital Ops implements the authentication and access layer so that authorized administrators (for example, teachers, coordinators, or program directors) can sign in to the portal. The underlying identity model is aligned with Church Account and other existing systems; Digital Ops is responsible for wiring those systems into the portal in a secure and maintainable way.
Bulk learner identification
Inside the portal, administrators provide the identifiers of the learners they want to enroll (e.g., Church Account usernames, as defined in coordination with Church and EnglishConnect). Digital Ops implements the UI and backend logic to validate these identifiers and prepare them for registration.
Course and period selection across EnglishConnect levels
The portal allows administrators to select the EnglishConnect course and term for each group of learners. EnglishConnect defines which levels and time frames are available; Digital Ops builds the interfaces and data flows that make these selections operationally possible.
Group registration and payment flows
A key responsibility for Digital Ops is to implement the bulk registration and payment flows inside the portal. This includes:
Creating the appropriate registrations for all listed learners in the relevant systems (e.g., Anthology and related services), and
Enabling institutions to pay for their groups in a consolidated way.
Payment methods, pricing, and policies are governed by EnglishConnect and other decision-makers; Digital Ops implements the technical side of whatever model is approved.
Progress dashboard for institutions
The B2B portal also includes a dashboard component owned by Digital Ops from a technical standpoint. Based on the design agreed with EnglishConnect, the dashboard is expected to show high-level indicators such as:
Tasks or assignments submitted
Grades
Attendance or participation signals
Digital Ops is responsible for connecting to the EnglishConnect learning platform or related data sources, aggregating the necessary information, and presenting it in a usable and performant way for institutional administrators.
In summary, on the B2B side the role of Digital Ops is to design and implement the web portal that allows institutions to register groups at any EnglishConnect level, manage bulk payments, and view a basic progress dashboard, according to the functional and governance requirements defined by EnglishConnect.
B2B - Administration Portal Walkthrough
User Experience
Current EC3 Registration
Progress & Next Steps (Digital Ops Perspective)
Current Status – Digital Ops
Alignment with EnglishConnect
Digital Operations has conducted initial alignment sessions with EnglishConnect and the development team to clarify the overall concept of Application to Registration – EnglishConnect (EC App), the split between B2C (Companion) and B2B (portal), and which EnglishConnect levels are in scope for cada canal.
B2C – Companion Native (in progress)
From a Digital Ops standpoint, the student-facing flow inside Companion Native is already under active development. The team is working on the technical implementation that will allow eligible learners (EC3 and higher levels, as defined by EnglishConnect) to:
sign in with a Church Account,
apply for EnglishConnect,
select a gathering, and
have their registration created in Anthology before entering the standard Companion experience.
B2B – Institution Portal (concept defined)
The institution-facing portal (for schools, Church units, companies, etc.) has been defined conceptually together with EnglishConnect. The idea includes bulk registration, consolidated payments, and a progress dashboard (tasks, grades, attendance). Digital Ops is not yet building this portal; its implementation depends on governance and prioritization decisions at the EnglishConnect / PG level.
Dependencies and governance.
The broader EC App initiative remains subject to program-level approval and prioritization. Digital Ops is prepared to continue work on the B2C flow already in progress and to initiate B2B development once EnglishConnect and PG confirm scope, timing, and resourcing.
Next Steps – Digital Ops
From a Digital Ops perspective, the indicative next steps are:
Complete and refine the B2C flow in Companion
Continue iterating on the Companion feature for EC3+ learners, closing any gaps in the application, gathering selection, registration integration, and handoff to existing Companion / EnglishConnect flows.
Formalize technical design for the B2B portal
Prepare and validate a technical design for the institution portal (authentication, learner identifiers, course/term selection, bulk registration, payments, and dashboard data flows), so that development can start once approvals are in place.
Coordinate integrations and data contracts
Work with EnglishConnect, Anthology owners, and the EnglishConnect learning platform team to define data contracts, error handling, and update flows that EC App requires, both for B2C and B2B.
Plan pilots and internal validation
Support EnglishConnect in planning initial pilots, ensuring that the Digital Ops components (Companion feature and portal) are ready for internal testing and limited production use before wider rollout.
Digital Ops Scope & Boundaries within EC App
In Scope for Digital Ops
Within Application to Registration – EnglishConnect (EC App), Digital Operations is responsible for:
Companion (B2C) implementation
Designing and building the student-facing feature inside Companion Native that supports:
Church Account–based authentication for learners.
EnglishConnect application for eligible levels (starting with EC3 and higher).
Gathering selection within Companion.
Creation of course registrations in Anthology based on the approved rules.
Handoff from the EC App flow into existing Companion / BYU-Pathway experiences.
Institution portal (B2B) implementation
Designing and implementing the web portal used by institutions and organizations to:
Authenticate institution administrators.
Provide learner identifiers (e.g., Church Account usernames) for group enrollment.
Select EnglishConnect levels and periods for each cohort.
Register groups of learners in the relevant systems.
Support bulk or consolidated payments for groups, according to the payment model defined by EnglishConnect and other stakeholders.
Display a high-level progress dashboard that surfaces tasks submitted, grades, attendance, and similar indicators from the EnglishConnect learning platform.
Systems integration
Implementing and maintaining the technical integrations between:
Companion (B2C flow) and Anthology.
The B2B portal and Anthology.
EC App components and the EnglishConnect learning platform or related data sources for progress reporting.
Handling data mapping, technical error handling, and system-to-system communication, following the contracts agreed with EnglishConnect and related teams.
Ongoing support for these digital flows
Providing maintenance, incremental improvements, instrumentation, and monitoring for the Digital Ops components of EC App (Companion feature and portal), as prioritized by EnglishConnect and Digital Ops leadership.
Out of Scope for Digital Ops
The following areas are not owned by Digital Ops within this project, even though they interact with Digital Ops components:
EnglishConnect curriculum and pedagogy
Designing course content, activities, assessments, and pedagogical approaches.
Decisions about which learning outcomes, materials, and teaching methods are used at each level.
Program strategy and policy decisions
Determining which countries, institutions, or markets are eligible to use EC App.
Setting admissions policies, eligibility requirements, or participation rules for learners and institutions.
Defining pricing models, discounts, and payment policies for EnglishConnect.
Ownership of identity systems and Church Account
Creating, governing, and managing Church Accounts and user identity policies.
Digital Ops consumes and integrates with these identities; it does not own or define them.
EnglishConnect learning platform
The environment where learners actually take EnglishConnect classes (content, quizzes, assignments, etc.) is outside Digital Ops ownership.
Digital Ops integrates with it for registration confirmation and dashboard data, but does not control the platform itself.
Detailed analytics and research reporting
While Digital Ops will provide a practical, high-level dashboard for institutions (tasks, grades, attendance), more advanced analytics, research dashboards, or data science workstreams are not part of the initial Digital Ops scope for EC App unless explicitly prioritized later.
FAQ (Digital Ops Perspective)
1. What is “Application to Registration – EnglishConnect (EC App)” from a Digital Ops perspective?
From the Digital Ops side, EC App is a technical workstream that delivers two things:
A B2C feature inside Companion Native that supports EnglishConnect application and registration for eligible learners (EC3 and above).
A B2B web portal where institutions can manage EnglishConnect registrations, payments, and a basic progress dashboard.
2. What parts of EC App are Digital Ops actually building?
Digital Ops is responsible for the implementation of:
The Companion feature (UI, flows, and integrations) that takes learners from application and gathering selection to a created registration in Anthology.
The institution portal (UI, flows, integrations) that supports group registration, bulk payments, and a high-level progress dashboard.
The technical integrations between these products and systems such as Church Account, Anthology, and the EnglishConnect learning platform.
3. Which EnglishConnect levels are in scope for the Digital Ops work?
For the Companion feature (B2C), Digital Ops is implementing the flow starting from EnglishConnect 3 upward, as defined by EnglishConnect. This student-facing flow is not intended for EnglishConnect 1 or 2.
For the institution portal (B2B), the intent is to support all EnglishConnect levels (currently 1, 2, and 3, with future levels added when they are officially available), so that institutions can manage their full EnglishConnect offering in one place.
4. How does the Digital Ops work connect to Anthology and the EnglishConnect learning platform?
Digital Ops is responsible for the technical connections, including:
Creating and updating registrations in Anthology based on the information collected in Companion and the portal.
Providing the necessary data so that learners are recognized as registered when they reach the EnglishConnect learning platform.
Aggregating key progress signals (such as tasks submitted, grades, and attendance) from the learning platform or its data sources to feed the institutional dashboard.
Digital Ops does not define the business rules or curriculum, but ensures that the systems talk to each other correctly.
5. What is the current status of the Digital Ops work on EC App?
At this stage:
The Companion B2C feature for EC3+ is already under development by Digital Ops in coordination with EnglishConnect and the developers.
The B2B portal is in the conceptual and design phase and will move into active development once governance, approvals, and priorities are confirmed by EnglishConnect and PEG.
This page will be updated as Digital Ops completes major milestones or when scope changes are agreed with EnglishConnect.
6. Who decides which institutions or learners can use EC App, and how is that reflected here?
Decisions about where and with whom EC App is launched (countries, institutions, learner segments, pilots, etc.) belong to EnglishConnect and governing leadership, not to Digital Ops.
Digital Ops will implement the necessary technical capabilities (authentication, registration, payment, dashboard) and will configure or adapt them based on the rollout plans and policies provided by EnglishConnect.
7. Does Digital Ops own the EnglishConnect experience where learners do their coursework?
No. The learning experience (lessons, assignments, assessments) happens in the EnglishConnect learning platform, which is owned and managed outside Digital Ops. Digital Ops focuses on the journey up to “ready to study” (application, registration, payment, and system integrations) and on providing institutions with a concise operational view of learner progress.