How Red6 Digital Learning works

Clear from the start. Useful at every stage.

Accountable delivery

You know who is responsible.

Red6 Digital Learning owns the agreed scope of each engagement. Marc Denman is your accountable lead for scoping, technical decisions and delivery oversight.

Before work starts, we agree the deliverables, responsibilities and who will carry out the work. Marc reviews delivery against those requirements and discusses any proposed changes with you.

Working alongside your delivery team

Agree the working relationship before the work starts.

For a partner engagement, the scope records what Red6 Digital Learning will deliver, how it will be reviewed and accepted, and which decisions or dependencies sit with your team or the end client. Marc leads technical decisions and delivery oversight for Red6 Digital Learning’s agreed work.

Before starting, agree:

Deliverables, milestones, acceptance criteria and the people authorised to approve changes.
Client contact, branding and confidentiality requirements.
Access permissions, test environments and dependencies on other suppliers.
Progress reporting, escalation and handover documentation.

Delivery dates and arrangements are confirmed for the specific scope. A request for support is the start of a scoping conversation.

Discuss a work package

Independent advice and paid delivery

Clear about the scope and the relationship.

Advice and delivery have different scopes. In an advisory engagement, recommendations are assessed against the client’s requirements. In a subcontracted engagement, Red6 Digital Learning delivers the work agreed with the commissioning organisation.

A paid delivery engagement does not by itself mean platform resale, referral commission or exclusive vendor allegiance. Where a delivery relationship is relevant to a selection recommendation, we explain it before giving that advice.

From evidence to delivery

The route changes with the condition of the estate.

Each stage has an output and a decision. Material recovery work is separated from routine service.

Stage 01
Access and evidence
Meet the people who rely on the platform, inspect how it is configured and map demand, dependencies and the work that cannot wait.
Stage 02
Stabilise where needed
Agree a separate scope for material faults, backlog or missing controls. If the estate is ready, move directly into transition.
Stage 03
Operate or deliver the project
For managed services, confirm the operating calendar, capacity, request routes and responsibilities. For projects, work to defined outputs and acceptance criteria.

Terms in advance

You should not need a proposal to discover the ground rules.

Managed-service incidents are acknowledged and triaged by impact during the agreed UK business-hours window. The service schedule confirms exact targets, update rhythm and escalation contacts.

UK business hoursInitial managed-service coverage

Impact-basedAcknowledgement and triage

3 monthsInitial managed-service term

30 daysNotice after the initial term

Good boundaries make good work

What Red6 Digital Learning will—and will not—do.

You can expect

Plain-English findings and decisions
Documentation you can keep and use
A direct answer when your current system is good enough
Early warning before scope or capacity changes
Written approval before additional work starts
A usable handover at the end of the engagement

You will not get

Software chosen to satisfy a reseller agreement
Changes to agreed delivery responsibilities without discussion
Unapproved work appearing on an invoice
Guaranteed resolution of third-party faults
Artificial dependency on undocumented knowledge
A replacement project when a repair is enough

Start with evidence

An independent LMS review helps you choose the right first move.

Explore review options