The Coders Guild

Process Map

The apprenticeship lifecycle in 12 stages. Click any stage to see the detail - substeps, decision points, who does what, and where things break down.

Apprenticeship Lifecycle
Lead Generation through to On-Programme Delivery
Stage 01
Lead Generation
10 channels feeding the pipeline. Prospect to lead definition. Mix of outbound, paid, events, PR, and referrals.
Monday.com Apollo Sales Navigator Google Ads LinkedIn Ads Eventbrite Calendly
Crispin, Francesca, Alex
1.1
Outbound email via affiliate networks through Monday.com. Crispin sends to known contacts and 10KSB network (50-100 at a time). Replies come back to Crispin, who BCCs the CRM and CCs Francesca/Alex to progress the lead.
Crispin Monday.com
1.2
CRM retargeting - Francesca or Alex email existing contacts (past learners, previous customers) via Monday.com sequences. Replies go to the CRM and the individual.
Francesca Alex Monday.com
1.3
Cold email outreach through Apollo to new prospects. Replies go to Apollo, not the CRM. If anything materialises, manual process to add to Monday.com. Currently being questioned for value.
Francesca Apollo
1.4
Google Ads - search placement and display (retargeting). Drive traffic to website. Prospect fills out web form, which generates an email and creates a lead in the CRM.
Google Ads Web form
1.5
LinkedIn Ads drive traffic to Eventbrite for monthly webinars. Attendee list downloaded manually, enriched via Apollo, followed up on Sales Navigator, then manually added to CRM leads board.
LinkedIn Ads Eventbrite Apollo Sales Navigator
1.6
LinkedIn organic outreach - roughly an hour a day engaging with ICPs. Commenting, interacting, training the algorithm to surface TCG content. Goal is inbound messages from prospects.
Francesca LinkedIn
1.7
Third-party cold calling - external company books meetings via Calendly or pushes prospects to Eventbrite. Not yet started at time of mapping.
External Calendly Eventbrite
1.8
PR managed by Brand Ambition. Focused on AI training for small businesses credibility. Feeds into SEO and large language model optimisation. Leads through web form.
Brand Ambition Web form
1.9
Events - webinars and in-person. Attendees processed via Eventbrite, enriched through Apollo and Sales Navigator, then into CRM.
Eventbrite Apollo Sales Navigator
1.10
Advocates and referrals - past learners, previous customers, and network contacts who refer opportunities. Come in as individual emails or messages.
Crispin Francesca
Pain points
Founder-led sales - Crispin's personal brand and credentials are the primary driver. Team wants to shift brand equity to the company.
Highly manual data movement. Contacts moved one-by-one between Eventbrite, Apollo, Sales Navigator, and CRM. CSV downloads, manual enrichment, manual CRM entry.
Apollo not providing expected value. Used mainly for enrichment now. Team questioning whether to replace with a Chrome extension (e.g. Kaspr) that enriches directly from Sales Navigator.
Too many disconnected tools. No single flow from lead source to CRM. Each channel has its own manual process.
Capacity - two and a half people doing sales with a lot of manual plate-spinning. The constraint is the manual nature of execution, not volume of activity.
Exhaustible outreach list. The 1,500-person affiliate outreach is a one-time opportunity with high open rates (60-70%). Once done, other channels need to be working.
Stage 02
Lead Processing and Qualification
Triage, qualify, and route. Company lead or individual learner? Genuine opportunity or noise?
Monday.com Sales Navigator
Francesca, Alex, Crispin
2.1
Lead arrives on Monday.com leads board from any channel.
Monday.com
2.2 - Decision
Quick triage: Is this a company looking to upskill employees, or an individual learner?
Company lead - progress to qualification
Individual learner - route to Felicity or generic careers advice. Not the sales team's concern.
2.3
Initial outreach - contact within 24 hours (target, not always hit).
Francesca Alex
2.4
Qualify: Is there genuine interest? Does the role suit an apprenticeship? Which standard?
Francesca Alex
2.5
If qualified, move to deal stage on the CRM.
Monday.com
Pain points
Learner noise. Individual learners fill out the company web form pretending to be employers (selecting "company looking to upskill my team" even when they're individuals). Often identifiable by Yahoo/Gmail addresses.
Domain language confusion. Prospect, lead, qualified lead, deal - definitions now clarified: Prospect = ICP fit, no engagement yet; Lead = has responded or declared interest.
Information from conversations not captured. Essential details from qualification calls not consistently entered into the CRM. Transcripts exist but aren't processed.
CRM struggles with complexity. Managing multiple apprenticeships for the same employer (different standards, different start dates, mix of existing staff and recruitment) is clunky in Monday.com.
Stage 03
Sales Conversion
Discovery calls, webinar follow-ups, consultative selling. Getting the employer to commit.
Calendly Monday.com Eventbrite
Francesca, Alex, Crispin
3.1
Discovery call booked via Calendly.
Francesca Calendly
3.2
Consultative discussion: understand employer's needs, which standard fits, number of apprentices, existing staff vs recruitment.
Francesca Alex Crispin
3.3
Webinar attendance and follow-up. Monthly webinars are a key conversion tool - some prospects convert in under 5 minutes post-webinar.
Eventbrite
3.4
Discussion of payment options: levy, invoice, levy transfer, 5% co-investment.
Francesca
3.5
Employer commits to proceed.
Employer
Pain points
Conversion process not fully mapped. The March 10 workshop acknowledged this was skimmed over. Exact steps between qualified lead and committed employer need more detail.
Payment type not identified early enough. Levy transfer is slow - requires applying to other companies, can take weeks, and if not in place before cohort start date the apprentice can't be enrolled.
No consistent data capture from sales conversations. Francesca knows details from calls that never make it into a system Shelley or Crispin can see.
Stage 04
Compliance Documentation
Post-conversion paperwork prep. Job scan, ELI, H&S documentation. Runs in parallel with DAS connection.
Email Google Drive Monday.com
Francesca, Shelley
4.1
Francesca sends standard information email containing: job scan form (Excel/Word), request for ELI certificate, request for H&S documentation, and DAS connection instructions with timestamped video links.
Francesca Email
4.2
Employer fills out job scan form - a table of questions confirming the apprentice's role provides exposure to required elements of the occupational brief.
Employer Job scan form
4.3
Francesca does an initial scan of the returned job scan. Shelley also reviews for compliance.
Francesca Shelley
4.4 - Decision
Does the role match the apprenticeship standard?
Role matches - continue to documentation collection
Issues identified - discussion with employer, potentially redirect to a different standard
4.5
Employer provides ELI certificate and H&S documentation. If employer has no H&S policy, TCG helps them create one (edge case but it happens).
Employer
4.6
All documents stored in Google Drive: structured by standard > employer > apprentice.
Google Drive
4.7
CRM stage updated to "enrolment onboarding" - but actual documents stay in Google Drive, not the CRM.
Monday.com
Pain points
Documents in two places. CRM holds organisation and stage details. Google Drive holds actual paperwork. No single view.
Manual document chasing. Follow-ups are manual emails.
Job scan is a standalone document. Currently Excel/Word - not integrated with any system. Could be a form that feeds data directly.
Stage 05
DAS Connection
Connecting the employer to TCG on the government's Apprenticeship Service. Controls all funding flows.
DAS Email
Francesca, Shelley
5.1 - Decision
Does the employer already have a DAS account?
Has account - send connection request and guide them through accepting it
No account - provide information and guidance on setting up (government videos with timestamps provided)
5.2
Send connection request or guide employer through account setup.
Francesca DAS
5.3
Confirm connection established. Funding pathway active.
Shelley
Pain points
Levy transfer is the bottleneck. If an employer needs a levy transfer, they must apply to other companies for funding. Can take weeks. If not in place before cohort start, the apprentice cannot be enrolled.
Payment type identified too late. The team only recently introduced a quick win to surface how the employer is paying earlier in the process.
Stage 06
Apprentice Onboarding (Initial Assessment)
Two paths: employer has an apprentice, or employer needs recruitment. Initial meeting, SGA, English/Maths testing, application processing.
PICS BKSB Google Forms Monday.com
Shelley, Crispin
Path A - Employer has an apprentice
6A.1
Collect apprentice details from employer (proforma).
Shelley Employer
6A.2
Shelley reaches out to employer and apprentice to introduce herself.
Shelley
6A.3
Initial meeting with apprentice (employer invited but optional) - discuss understanding, experience, career prospects, answer questions.
Shelley Apprentice
6A.4
Send apprentice an email containing: Skills Gap Analysis (SGA) Google Form, English/Maths assessment link (BKSB via PICS), application form (PICS), and next steps information.
Shelley Google Forms BKSB PICS
6A.5
Apprentice completes SGA, English/Maths assessment, and application form.
Apprentice
6A.6 - Decision
SGA reviewed - if all high scores, flagged for technical coach review. Auditors expect evidence that someone technical has challenged self-ratings.
Reasonable scores - proceed
All high scores - flag for technical coach review
6A.7 - Decision
English/Maths results checked. Need at least Level 1 for a Level 4 apprenticeship. Level 2 preferred.
Level 1+ achieved - proceed
Below Level 1 - heavy documentation required justifying why the person should proceed
6A.8
Application form verified on PICS - includes right to work evidence.
Shelley PICS
6A.9
If additional learning needs identified, Additional Learning Form completed.
Shelley
Path B - Employer needs recruitment
6B.1
Compliance documents (job scan, ELI, H&S) completed first to confirm role validity.
Shelley
6B.2
Vacancy posted on TCG website (Monday form) and government Find an Apprenticeship service (API integration being built by Steve).
Monday.com Find an Apprenticeship
6B.3
Applications come into Monday.com - anonymised.
Monday.com
6B.4
Eligibility filter: right to claim public funding, lived and worked in UK for 3+ years, right to work.
Shelley
6B.5
Quality filter: review answers to 3-4 open questions (what do you know, why do you want to do it, something you've taught yourself). Filter out non-starters, ChatGPT-generated answers, low effort.
Shelley
6B.6
SGA completed at this stage for recruitment candidates (earlier than Path A) to pre-qualify them.
Candidate Google Forms
6B.7
Technical filter if needed - if too many candidates pass, a technical reviewer further narrows the list.
Technical reviewer
6B.8
Shortlisted candidates sent to employer with CVs and details.
Shelley Employer
6B.9
Employer interviews and selects.
Employer
6B.10
Unsuccessful candidates go to a talent pool. Decision: don't actively manage the pool for now, but retain the data for future opportunities and cross-selling.
Monday.com
6B.11
Selected apprentice's details collected. Process continues as Path A from step 6A.2.
Shelley
Pain points
SGA is a standalone Google Form. Not integrated with PICS or any other system. Results must be manually reviewed and cross-referenced.
Self-assessment reliability. Apprentices frequently over-rate themselves. Requires manual review and sometimes a technical coach to challenge ratings. Auditors expect evidence of this challenge.
Sequential where it could be parallel. The initial meeting happens, then SGA and assessments are sent. If SGA was completed before the meeting, the discussion would be richer.
Scale concern. Reviewing 60 SGAs and application forms manually is significant work. The sending-out part is just emails with links, but review and verification is time-consuming.
Stage 07
Funding Calculation and Agreements
SGA results feed the funding calculator. Price, duration, and three-party agreements.
Spreadsheet DocuSign PICS
Shelley
7.1
Funding calculator (spreadsheet) populated with SGA results: which KSBs need training vs prior learning. Agreed duration discussed with apprentice (typically 12-18 months). Removes training hours for elements the apprentice doesn't need. Calculates total training hours, number of coaching sessions, and funding amount to request.
Shelley Spreadsheet
7.2
Contact employer with price and duration for approval.
Shelley Employer
7.3
Employer agrees.
Employer
7.4
Create and issue Apprenticeship Agreement - signed by three parties: provider, employer, and apprentice.
Shelley DocuSign
7.5
Create and issue employer contract - between employer and TCG only.
Shelley DocuSign
7.6
Documents signed. Enrolment processed through PICS.
PICS
Pain points
Funding calculator is a spreadsheet. Manual input, not connected to the SGA or PICS.
Multiple manual data transfers. SGA results (Google Form) manually entered into the funding calculator (spreadsheet), which then informs what goes into PICS for enrolment.
Speed and quality indicators needed. Speed = how quickly all documentation is completed. Quality = completeness (all fields filled out) and correctness (information is accurate and verified).
Stage 08
Handoff to Delivery
Transition from biz dev/onboarding to the delivery team. The critical seam in the process.
Monday.com Google Drive
Francesca, Shelley → Rob
8.1
CRM deal stage updated to reflect handoff.
Monday.com
8.2
All compliance documentation confirmed complete in Google Drive.
Shelley Google Drive
8.3
Delivery team (Rob, Shelley, Felicity) pick up from here.
Rob Shelley Felicity
Pain points
No formal handover trigger. Rob doesn't get a structured signal that a cohort is becoming viable. The start date arrives informally. Rob isn't included in the biz dev to Shelley handover call.
No pipeline visibility for delivery. Rob has no sight of the sales pipeline. He needs a minimum of six weeks lead time to book trainers. Historically, anticipated numbers and actual numbers have been different.
Information gaps in handoff. CRM automations don't always surface the right information. Details from sales conversations aren't consistently captured anywhere the delivery team can see.
Continuity break. Employer has to re-explain context already discussed with Francesca. No structured way to pass qualitative information from sales to delivery.
Stage 09
Cohort Scheduling and Trainer Booking
Draft delivery schedule, book trainers, handle content creation if needed. Runs in parallel with content work.
Monday.com Google Calendar Spreadsheets
Rob, Felicity, Shelley
9.1 - Decision
Does the content exist for this standard?
Content exists - continue to scheduling
No content - content creation sub-process kicks off in parallel (3-6 month lead time)
9.2
Training plan schedule created per cohort from a template (spreadsheet). Must exist before sign-ups because it's needed for the apprenticeship agreement.
Rob Spreadsheet
9.3
Training plan feeds into Monday.com for the cohort group with delivery dates.
Rob Monday.com
9.4
Draft delivery schedule. Confirm trainer availability. Share confirmed schedule with trainer via spreadsheet.
Rob
9.5
Feed schedule into Delivery Schedule Monday board. This becomes the single source of truth (trainer, session, materials, learners).
Rob Monday.com
9.6
Felicity and Shelley map one-to-ones, progress reviews, and pastoral reviews.
Felicity Shelley
9.7
Trainers booked and confirmed. Syncs to Google Calendar - learners and coaches invited.
Rob Google Calendar
Pain points
No pipeline visibility. Rob gets no signal when a cohort is becoming viable. Wants an earlier trigger to warm up trainers before formal confirmation.
Content creation has no home. The conditional branch ("does content exist?") isn't documented anywhere as a process. No clear ownership or workflow.
Six-week trainer lead time. Minimum required. Without pipeline visibility, this creates risk of either having trainers booked with no cohort or a cohort with no available trainer.
Cohort size drives profitability. 16 people is optimal. 12 is workable. Below that, unit economics suffer. But delivery effort is roughly the same regardless of cohort size.
Stage 10
Pre-Cohort Admin
Administrative setup immediately before a cohort starts. Slack, Drive, workbook, access grants.
Slack Google Drive
Rob
10.1
Create Slack channel for the cohort. Upload Learner Handbook and key documents.
Rob Slack
10.2
Create employer Google Drive folder containing: job scans (per-role, not per-individual), ELI certificate, H&S documentation, contracts. If same employer has multiple roles, subfolders per role.
Rob Google Drive
10.3
Create apprentice Google Drive folder (~8 subfolders): copies of reviews, progress reviews, portfolio templates, information, pastoral review documents, and others.
Rob Google Drive
10.4
Create the Google workbook ("the matrix") for each apprentice - their online learning platform containing: training plan, task details, feedback from coach, progress monitoring, portfolio progress. Central document that coaches, Shelley, apprentices, and employers all reference.
Rob Google Workbook
10.5
Set up Google Folders for cohort-level resources (recordings, slides).
Rob Google Drive
10.6
Grant learner access to relevant systems. Mostly manual - some automations exist but patchy.
Rob
Pain points
Largely manual. Automations exist but are inconsistent. Each new cohort requires the same setup steps done by hand.
No checklist or standard operating procedure documented. Rob is new to this role; Shelley and Felicity's input needed to fill blind spots.
Stage 11
On-Programme Management
Ongoing management during delivery. Coaching model, content management, quality assurance, employer engagement, and Shelley's operational rhythm.
Monday.com Google Workbook PICS Slack Laravel App
Rob, Shelley, Felicity, Trainers
11.1
One coach assigned per learner for continuity through the full duration of the programme. Different trainers may deliver group sessions based on availability and expertise.
Rob Coaches
11.2
Coach opens the Google workbook (matrix) during coaching meetings to check whether the learner is on track. The apprentice directs the coaching session; the coach guides.
Coaches Google Workbook
11.3
Coaches don't access Monday.com for learner data - they use the matrix only.
Google Workbook
11.4
Review course material ahead of each session. Keep subject matter current.
Trainers
11.5
Chase outstanding content (especially from external SMEs). Monitor SME hours if on retainer.
Rob
11.6
Pool of mostly contract trainers (only one full-time employed). Capacity currently managed through ad-hoc discussions - no stored data anywhere.
Rob
11.7
Full-time coach manages a maximum of 22 learners before burnout risk. Current capacity: can handle 60-80 apprentices before needing new hires. Plan to recruit a full-time trainer/coach when pipeline reaches 40-50.
Rob
11.8
Scheduling: sessions offered to preferred/available trainers, with specific trainers chosen for disciplines they're strong in.
Rob
11.9
Coaching and training meetings recorded, then dip tested.
Shelley
11.10
Feedback surveys for learners and trainers after sessions, submitted and monitored via Monday.com. Automations flag negative feedback for follow-up.
Monday.com
11.11
Monthly quality meeting with aggregated feedback roundup.
Shelley Rob
11.12
Content feedback loop: session delivered > trainer/learner feedback > session moved to "edits needed" on Monday > fix done internally or commissioned to SME > back to production for next delivery.
Monday.com SMEs
11.13
Employers attend progress reviews approximately every 8 weeks. They have access to the matrix but typically don't use it.
Employer Shelley
11.14
For larger employers with multiple apprentices, the economic buyer wants a simple overview (on track / not on track) rather than detailed narrative.
Employer
11.15
Shelley reaches out with information updates (awards, NMW changes) to stay connected. Balance of not bombarding employers but ensuring they feel supported.
Shelley
11.16
Monthly meetings with coaches to discuss all their learners. Quarterly standardisation meetings.
Shelley Coaches
11.17
Immediate issue/feedback escalation from coaches via email or Slack.
Coaches Slack
11.18
Shelley personally meets all apprentices approximately every 8 weeks as pastoral coach. Discusses apprenticeship support from both TCG and employer, addresses concerns.
Shelley Apprentice
11.19
Progress reviews are the primary employer feedback touchpoint.
Shelley Employer
11.20
Tracks KSB progress and off-the-job hours at apprentice level. Basic apprentice login exists (Shelley's login too, but basic).
Laravel App
11.21
Next development: employer login and admin login for multi-cohort/multi-employer views. Not yet commissioned. Planned to eventually replace the Google workbook matrix but development timeline unclear.
Laravel App
Pain points
Google workbook (matrix) is the critical manual tool. Contains attendance, tasks, feedback, monitoring for all stakeholders. Central to delivery but entirely manual, with no integration to any other system. THE low-hanging fruit for automation.
Biggest concern for scale. Managing 60 people on-programme is where quality could suffer. The administrative burden of reviewing paperwork and forms for a large cohort is the real bottleneck.
Coach capacity not stored anywhere. Managed through conversations. No data on who has capacity, who is approaching burnout risk, or how to optimise allocation.
No leading metrics for delivery quality or meeting execution. No way to see whether meetings are happening on time or information is being delivered correctly, other than Shelley personally monitoring.
Shelley monitors coaches and admins personally. Works at current scale but won't at 60+ apprentices. Single point of failure for quality oversight.
SME management undocumented. No formal process for managing external subject matter experts, their hours, or their content delivery.
Laravel app is very early stage. Planned to replace the matrix but employer and admin logins haven't been commissioned. Development timeline unclear.
Stage 12
Completion and Retention
End-point assessment, ongoing employer relationship, retention, and cross-selling. Not yet mapped.
TBC
TBC
This stage was not covered in any of the source sessions. It needs mapping in a future workshop.
Known gaps
Lifetime value not tracked. The team discussed learners progressing through short course to boot camp to apprenticeship to CPD, but there's no system tracking this journey.
Cultural change is part of the value but not part of the process. The apprenticeship is designed to drive organisational change, not just individual skill-building. Hackathons and workshops discussed as retention tools but aren't currently running.
Cross-selling and upselling not systematised. Repeat business is a key KPI but there's no structured process for it.
Working document

March 2026. Sources: Feb discovery, Mar 4 coordination, Mar 10 and Mar 17 process mapping workshops, Rob's ops notes, Shelley's Mar 18 PICS dashboard screenshots, and product strategy discovery questions.

Created by Specs for The Coders Guild