Education and training: the record someone else will rely on

Current pressures

What providers describe as pressure in 2026; each is a failure mode, not an argument for new software.

The workflows a project touches

A first project cuts into this sequence. Decide which steps it owns before choosing software.

1. Enquiry and application. An interest becomes a named applicant, with eligibility, prior learning and funding route recorded once.
2. Enrolment and payment. Acceptance, contract, payment or funding claim, and one answer to whether the learner is enrolled.
3. Delivery. Scheduling, materials, attendance and participation, online or in person.
4. Assessment. Submission, marking, moderation, resubmission and appeal, with who decided what recorded.
5. Progression and completion. One rule for what counts as complete, applied the same way by every report.
6. Credential issue and verification. The record leaves the organisation, and a third party must be able to check it independently later.
7. Learner support. Questions, deadlines and technical problems, routed to whoever is entitled to answer.
8. Reporting. Funders, regulators, employers and quality review, produced from recorded events, not reassembled by hand.

Steps 1, 2 and 8 are the matching mechanics of ERP and back-office operations, with enrolments in the place of orders. Step 7 is customer support automation. Where courses are sold direct, checkout works as on retail, commerce and marketplaces.

Data sensitivity, and how it changes the design

This is where an education project differs from a commercial one: the data is sensitive, it frequently concerns minors, and that changes the architecture rather than the feature list.

• Lawful basis and consent are design inputs. Who may be contacted, for what, and who may consent on a learner's behalf are answered in writing first; guardian consent for minors changes the account model.
• Access is per role and per cohort. A tutor, an external assessor, an administrator and a funder each see a different slice, so role-based access control and multi-factor authentication on administrative screens are the baseline, not late hardening.
• Retention is long and uneven. Contact data, assessment evidence and the credential record have different clocks, and the credential outlives the rest, so deletion must be a specified feature.
• Safeguarding and accessibility notes need tighter handling than the rest of the record: who may read them, and what is logged when they do.

Netbase's published security practice is specific: secure code review and version control, role-based access control, multi-factor authentication on admin dashboards, contributors under non-disclosure agreement, and non-disclosure and data-processing agreements on request. OutsourcingVN holds no certification or accreditation of any kind, in education or elsewhere. Evidence of that practice in a project is on data security and compliance in outsourcing.

Where a first project starts

OutsourcingVN follows one delivery lifecycle: discovery and strategic alignment; team assembly and architecture planning; agile execution with outcome-based milestones; modular components; training and rollout; ongoing support.

1. Write down what completion means, as one rule every report will use, before anything is built.
2. Settle the data questions in writing: lawful basis, consent for minors, who sees what, and how long each part is kept.
3. Count the real volume. Enrolments per intake, assessments per cohort, support contacts per learner, and the peak week not the average.
4. Pick one programme or one cohort for a first milestone, with written acceptance criteria.
5. Prove verification early. A credential a third party cannot check independently is not finished, whatever the platform says.
6. Widen by programme, then by site, against the step-three baseline.

Most projects are agreed as fixed-scope contracts after discovery. Milestone acceptance is on the project delivery page, evidence labelling on the methodology page. The route for a system that does not exist yet is custom product engineering; where a student system has outgrown its shape it is legacy application modernization. Other shapes sit under services.

What delivery record exists, and what does not

OutsourcingVN publishes no delivered project for an education, training or workforce development organisation. No approved claim in the register describes a student information, learning, assessment or credential system. What can be stated is the surrounding record: Netbase has served more than 500 clients, in the United States, Europe and Asia-Pacific, with most projects coming from clients outside Vietnam. Those are service markets, not offices, and no project or country counter is published.

The relevant overlap is mechanical. Since 2020 Netbase has worked as offshore development and managing partner on a multi-tenant cloud ERP platform for a US client who is not named. Its first phase, from 2020 to 2023 and aimed at agency small and medium businesses, covers customer records, messaging, HR, a knowledge base, custom fields and workflows, and API integrations, on React and Next.js, Laravel and Strapi on AWS. A retail phase was planned work when that profile was written and is not presented as delivered. Per-tenant segregation, a record several roles write to, configurable workflows and an event history that must survive a dispute are the mechanics of cohorts, assessment decisions and a credential checked years later — a capability argument, not sector experience. That record and its limits are on the multi-tenant cloud ERP platform page; all published records sit under work.

So demand evidence rather than a sector client list: a first milestone narrow enough to reverse; a discovery output another supplier could reuse; a named delivery lead accountable for every change; and written answers on consent, access and retention before any design is approved.