ESA attends ceremonies, paired code reviews, workshops (Next.js, Directus, TypeScript, Docker, CI/CD).
Status & Progress
Rocket Lab is responding to two RFQs from Education Services Australia (ESA) — edu.au (website rebuild) and myfuture (platform rebuild). Both are separate submissions to the same contact, same deadline. Last updated: 23 Mar 2026.
Questions Deadline
19 Mar
Closed
Target Submit
25 Mar
2 days away
Hard Deadline
2 Apr
5 PM AEST Thursday
Overall progress
~65%
13
Sections Done
All scored criteria + security, contract, COI, declaration, Indigenous, ESG, PDF output
3
Partially Done
Respondent details, insurances, declaration (need values)
4
Blocked — Needs Input
Personnel, experience (4 projects), pricing, referees
📄 Generated PDFs
Submission Roadmap
19 Mar
Questions deadline (4 PM AEST)
closed
20–22 Mar
Proposal site built, content drafted, structure finalised, repo organised
done
23 Mar
Today — security compliance, insurances, contract review, conflict of interest, declaration, Indigenous participation, ESG drafted. Remaining: personnel, past projects, referees, pricing
in progress
24 Mar
Pricing: calculate phase totals, portfolio discount. Fill personnel bios, past projects, referees, insurance policy details
to do
25 Mar
Target submit — final review, format into Schedule 4 PDF, email both proposals
target
26–1 Apr
Buffer week — handle any ESA clarification requests or late changes
buffer
2 Apr
RFQ closing (5 PM AEST, Thursday) — hard deadline
deadline
Deliverables Checklist
Everything the RFQ requires in the submission, per Schedule 4 (RFQ Response Form). Each item must be in both the edu.au and myfuture submissions.
Scored Criteria (80% of evaluation)
-
✓Understanding of ESA (10%) — demonstrated understanding of ESA's position done
-
✓Technical capability (30%) — stack, architecture, security, scalability done
-
✓Proposed methodology (10%) — phases, timeline, risk management done
-
✓Co-development approach (10%) — progression model, governance, handover done
- Experience (10%) — 4 past projects: client, name, year, outcomes needs input
- Key personnel (10%) — per person: name, role, quals, skills, days, % EFT needs input
- Pricing (20%) — total (excl/incl GST), phase breakdown, assumptions, milestone-linked needs input
Schedule 4 Required Parts
-
~Part 2: Respondent details — legal name, ABN, ACN, address, business type, directors drafted — needs ABN/ACN/directors
- Part 3: Contact for liaison — name, title, postal address, phone, email needs input
-
✓Part 4: Statement against evaluation criteria — each criterion on separate page drafted
- Part 5: Previous experience — 4 projects (client, name/year, description/outcomes) needs input
-
✓Part 6: Solution overview — technology stack and architecture done
-
✓Part 7: Project plan — phases, timeline, delivery approach done
- Part 8: Personnel — role, name, title, quals, skills, contribution, days, % EFT per person needs input
- Part 9: Referees — 2 referees: company, contact, phone, email, project, nature of work needs input
- Part 10: Subcontractors — name, ACN/ABN, address, expected work (or "none") drafted — confirm none or add details
-
✓Part 11: Risk management plan — risk, likelihood, impact, mitigation done
- Part 12: Pricing — total price table, phase breakdown, all assumptions needs input
-
✓Part 13: Compliance with draft contract — review Annexure A, flag non-compliance drafted — no exceptions noted
-
✓Part 14: Security & privacy compliance — ISM/IRAP, ISO27001, SOC2, privacy, data storage drafted
-
~Part 15: Insurances — PL, PI, ML, WorkCover (Certificates of Currency) drafted — needs policy details & CoCs
-
✓Part 16: Conflict of interest — disclose any potential or actual conflicts drafted — no conflicts
-
~Part 17: Respondent declaration — signed declaration drafted — needs signatory name & signature
Optional (Recommended)
-
✓AI tools disclosure — tools, usage, ESA recommendations, security risks done
-
✓Cross-portfolio efficiency — address efficiency across ESA's Digital Services rebuilds done
-
✓Indigenous Participation Plan — Indigenous procurement policies or activities drafted
-
✓Sustainability / ESG — proposed strategy for ESG outcomes drafted
Blockers & Decisions
These need human input — they can't be generated. Grouped by urgency.
Critical Path (blocks submission)
- Day rates and team size — what rates are we quoting? How many people on each project? Business
- Personnel assignments — who is named? Need names, qualifications, bios, availability (days, % EFT) Business
- Pricing strategy — fixed price per phase? T&M with cap? Margin? Portfolio discount? Business
- Past projects — which 4 projects to reference? Need client permission to name them Business
Required (blocks completeness)
- Referees — who are the 2 referees? Need their permission and current contact details Business
-
~Respondent details — Rocket Lab legal name, ABN, ACN, address, directors (structure drafted, values needed) Admin
- Insurance certificates — current Certificates of Currency for PL, PI, ML, WorkCover (insurer/policy/sum/expiry) Admin
-
✓Security compliance answers — ISM/IRAP (Partially), ISO27001 (Partially), SOC2 (N/A), privacy (all Yes) — drafted Business
-
✓Draft contract review — reviewed, no exceptions noted; IP assignment and data sovereignty explicitly accepted Legal
-
~Subcontractors — using any? Drafted as TBC — confirm "none" or add details Business
-
✓Conflict of interest — drafted: no conflicts declared Business
Nice to Have
-
✓Indigenous Participation Plan — drafted: IPP commitment, Supply Nation offer, myfuture Indigenous community angle Business
-
✓Sustainability / ESG — drafted: remote-first, open-source, GovZone, platform longevity Business
- Ongoing maintenance pricing — optional monthly/quarterly retainer (structure drafted, amounts needed) Business
Open Questions
Things we need to decide or clarify before finalising the proposals.
Strategy Questions
- Are we bidding for both or just one? — the proposals reference each other (cross-portfolio efficiency). If we only bid for one, that section needs rewriting
- Do we position as a portfolio partner or per-project vendor? — current approach is portfolio. Should we offer a portfolio discount?
- How aggressive on pricing? — value for money is 20% of evaluation. Do we compete on price or differentiate on quality?
- Do we need to register interest first? — RFQ says "all potential respondents register their interest via email to Schedule 1 email". Have we done this?
Technical Questions
- GovZone experience — do we have direct GovZone deployment experience? If not, how do we frame this?
- Directus at scale — can we point to a production Directus deployment as evidence?
- ISM compliance — what's our actual ISM/IRAP posture? This is required (Part 14)
- myfuture VWX — build vs buy decision. RFQ says "if off-the-shelf, must integrate seamlessly". Do we have a recommendation?
Logistics Questions
- Who signs the declaration? — Part 17 needs an authorised signatory
- PDF format requirements? — RFQ says email to corinna.maloney@esa.edu.au. Any file size limits? Do we send one PDF or multiple?
- Do both proposals need identical shared sections? — or can we cross-reference between the two submissions?
- Annexure A (draft contract) — do we have access to it? Need to review for compliance response
📄 Submission Documents
Both proposals are rendered as print-ready documents. Open, review, fill in the highlighted placeholders, then print to PDF from your browser (Cmd/Ctrl + P → Save as PDF).
edu.au — Website Build
4-month project, Apr–Aug 2026. All Schedule 4 parts included.
- Parts 2–4: Respondent details + all 7 evaluation criteria
- Parts 5–12: Experience, personnel, plan, pricing scaffolds
- Parts 13–17: Contract, security, insurance, COI, declaration
myfuture — Platform Rebuild
14-month project, Apr 2026–Jun 2027. All Schedule 4 parts included.
- Parts 2–4: Respondent details + all 7 evaluation criteria
- Parts 5–12: Experience, personnel, plan, build streams, pricing
- Parts 13–17: Contract, security, insurance, COI, declaration
How to Finalise → PDF
- Open each proposal link above
- Fill in all amber/yellow highlighted placeholders — these are the fields requiring human input
- Attach Certificates of Currency (Part 15) as separate files
- Click "Save as PDF" button at top, or use browser print (Cmd/Ctrl + P → Save as PDF)
- Email both PDFs separately to
corinna.maloney@esa.edu.au
How to Submit
From the RFQ documents (Section 8.2 — Lodging method):
Submission Method
- Email only to
corinna.maloney@esa.edu.au - Hand delivery, courier, post, and fax are explicitly rejected
- You will receive a receipt of lodgement email confirming time and date
- Two separate submissions — one per RFQ (edu.au and myfuture)
Download Draft Submissions
Generated from proposal markdown via Schedule 4 format. Review, fill placeholders, then email to ESA.
📄
edu.au — Schedule 4 PDF
Download draft submission
📄
myfuture — Schedule 4 PDF
Download draft submission
To regenerate: python3 scripts/generate-pdfs.py
Response Format — Schedule 4
Each submission must follow the RFQ Response Form (Schedule 4) structure. Each evaluation criterion response starts on a separate page using the criterion as the header. No word limit but "respondents are encouraged to keep their answers succinct".
- Part 2 — Respondent details (legal name, ABN, ACN, address, directors)
- Part 3 — Contact for liaison and notices
- Part 4 — Statement against each evaluation criterion (separate pages)
- Part 5 — Previous experience (4 projects)
- Part 6 — Solution overview (stack + architecture)
- Part 7 — Project plan
- Part 8 — Personnel (per person detail)
- Part 9 — Referees (2)
- Part 10 — Subcontractors
- Part 11 — Risk management plan
- Part 12 — Pricing information
- Part 13 — Compliance with draft contract
- Part 14 — Security & privacy compliance table
- Part 15 — Insurances (Certificates of Currency)
- Part 16 — Conflict of interest
- Part 17 — Respondent declaration (signed)
Important Notes
- Prices must be inclusive of GST and all costs/expenses/duties/taxes
- Payment linked to milestone/task performance
- Must review Annexure A (draft contract) and indicate compliance
- Any subcontractors must agree to public disclosure of their details
- Offer period is 28 days after RFQ closing
About ESA
Education Services Australia is a not-for-profit owned by all Australian Ministers of Education, serving as the bridge between national education policy and practical digital delivery. Unlike typical government agencies or commercial entities, ESA must balance ministerial accountability, cross-jurisdictional coordination, and direct service delivery.
ESA's internal teams need to own and evolve these platforms long after the initial build. This is not a project where a vendor builds something clever and walks away — it requires genuine partnership, knowledge transfer, and technology choices that ESA's team can confidently maintain.
What ESA Explicitly Wants
- Collaborative partner who recommends best practice and challenges the status quo
- Sustainable solution with consistency/efficiency across ESA products
- Co-development — vendor does bulk of build, ESA team contributes to learn
- Low-maintenance platform easily managed by product team, straightforward for Technology team
- Cross-portfolio thinking — efficiency across all Digital Services rebuilds
Contact: corinna.maloney@esa.edu.au
The Two RFQs
edu.au — Website Build
Rebuild of the edu.au domain registrar information website. The sole registrar for Australia's closed edu.au second-level domain (operating within auDA licensing rules).
- Type: Public informational website — no user accounts
- Timeline: Apr–Aug 2026 (4 months)
- Complexity: Low
- Key challenge: Brand refresh, SEO, clean information architecture
myfuture — Platform Rebuild
Australia's national career education platform for students, educators, parents and carers. Multi-user platform with personalised journeys.
- Type: Multi-user platform — 5+ user types with dashboards
- Timeline: Apr 2026–Jun 2027 (14 months)
- Complexity: High
- Key challenge: Multi-tenancy, career tools, personalisation, integrations
| edu.au | myfuture | |
|---|---|---|
| User accounts | No | Yes — students, educators, parents, jurisdiction admins, staff |
| Hosting | GovZone | GovZone |
| Compliance | ISM OS, WCAG 2.1, OWASP, APPs | ISM OS, WCAG 2.1, OWASP, APPs |
| Co-development | Required | Required (more intensive) |
| Content migration | Existing website content | Content + users |
Evaluation Criteria
Identical for both RFQs:
| # | Criteria | Weight | Our Status |
|---|---|---|---|
| 1 | Understanding of ESA | 10% | done |
| 2 | Technical capability | 30% | done |
| 3 | Proposed methodology | 10% | done |
| 4 | Co-development approach | 10% | done |
| 5 | Experience in relevant services | 10% | needs input |
| 6 | Key personnel | 10% | needs input |
| 7 | Value for money | 20% | needs input |
60% of the evaluation is content we've already drafted. The remaining 40% (experience, personnel, pricing) needs human input.
Unweighted (Still Assessed)
| Criteria | Our Status |
|---|---|
| Compliance with RFQ and draft contract | not started |
| Indigenous Procurement (optional) | optional |
| Sustainability / ESG (optional) | optional |
| Security and Privacy (required) | partial |
Source Documents
All source material is in the Git repo at Rocket-Lab-Skunkworks/esa-rfq-prep.
| File | Description |
|---|---|
sources/rfq-pdfs/ | Original RFQ PDF documents from ESA |
sources/rfq-text/ | Text extracts from PDFs + full markdown extracts |
analysis/edu-au/ | edu.au requirements, evaluation criteria, deliverables checklist |
analysis/myfuture/ | myfuture requirements, evaluation criteria, deliverables checklist |
proposals/ | Draft proposal content (markdown) per RFQ |
docs/ | This site (GitHub Pages) |
CLAUDE.md | Project context for AI chat sessions |
Open the repo in Claude Code or GitHub Copilot to chat against the full knowledge base. The CLAUDE.md file gives any new session immediate context.
Technology Stack
Shared core stack across both platforms. Purpose-built for ESA: low maintenance, open source, straightforward for the Technology team.
Front-end: Next.js (React)
- SSR and SSG for performance + SEO
- Decoupled from backend
- Huge ecosystem reduces hiring risk
- Built-in image optimisation, code splitting
CMS: Directus
- Open-source, self-hosted headless CMS
- REST + GraphQL APIs natively
- Intuitive admin for non-technical authors
- Self-hosted in GovZone
Database: PostgreSQL
- Row-level security for multi-tenancy
- Full-text search
- Automated backups, point-in-time recovery
Infrastructure
- Docker containers for GovZone SIT/UAT/PROD
- GitLab CI/CD pipelines
- IaC (Terraform/Pulumi)
- CDN, secrets management
Platform-Specific Additions
| Component | edu.au | myfuture |
|---|---|---|
| Search | Meilisearch (site search) | Meilisearch (full-text, faceted) |
| Auth | N/A (public site) | NextAuth.js + SSO + MFA |
| Caching | CDN + SSG | Redis (sessions, data) |
| Newsletter integration | Notifications + newsletters | |
| External APIs | — | Labour market, courses, SSO |
Architecture Principles
┌─────────────────────────────────────────────────┐ │ CDN / Edge │ ├─────────────────────────────────────────────────┤ │ Next.js Front-end (SSR/SSG) │ ├─────────────────────────────────────────────────┤ │ API Layer (REST + GraphQL) │ ├──────────────┬──────────────┬───────────────────┤ │ Directus │ Search │ Integrations │ │ (CMS) │ (Meili) │ (Email/APIs) │ ├──────────────┴──────────────┴───────────────────┤ │ PostgreSQL Database │ ├─────────────────────────────────────────────────┤ │ GovZone Infrastructure (Docker) │ └─────────────────────────────────────────────────┘
Same structural pattern for both. edu.au is CMS-driven; myfuture adds auth, career tools, multi-tenant data. One deployment playbook, one learning curve, one security posture.
Security & Compliance
ISM Classification 'OS'
- All data in GovZone
- AES-256 at rest, TLS 1.3 in transit
- RBAC, SSP Annexes maintained throughout
- Vulnerability scanning via CI/CD
OWASP Top 10 & ASVS L1
- Automated SAST/DAST scanning
- Input validation, CSRF, CSP headers
- GitLab dependency scanning
- Rate limiting on auth endpoints
WCAG 2.1 AA
- Accessibility in design system from day one
- axe-core in CI/CD
- Screen reader + keyboard testing
- Audit before each launch
Privacy
- Australian Privacy Principles (APPs)
- Privacy-by-design
- No data leaves Australia
- Cookie consent, secure deletion
Compliance Table (needs completion)
| Requirement | Status |
|---|---|
| Information Security Manual (ISM) / IRAP assessment | [NEEDS ANSWER] |
| ISO27001 / certification | [NEEDS ANSWER] |
| System and Organisation Controls (SOC2) | [NEEDS ANSWER] |
| Approved Privacy Policy satisfying APPs | [NEEDS ANSWER] |
| Collect/use/disclose Personal Information per Privacy Act 1988 | [NEEDS ANSWER] |
| Data stored on servers outside Australia | No |
Co-Development Approach
Core project requirement, consistent across both platforms.
1
Observe & Learn
2
Contribute
ESA assigned to features, pair programming, submits MRs reviewed by Rocket Lab.
3
Co-Lead
ESA leads features with Rocket Lab support. ESA manages deployment pipeline.
4
Own
Handover sprints: ESA leads all development. Rocket Lab advisory only.
Governance
- Steering committee: Rocket Lab + ESA PM + Technology Dev Team + Business team
- Tooling: GitLab (code), Jira/Azure DevOps (tracking), Confluence/SharePoint (knowledge base)
- Cadence: Sprint demos (fortnightly), steering (monthly), retros (fortnightly)
- Accountability: Rocket Lab responsible and accountable for all deliverables
AI Tools Disclosure
Tools: Claude Code, GitHub Copilot
AI-assisted code generation, review, testing. All output reviewed by humans. Same MR review process. No ESA data shared with AI services.
Recommendation for ESA
AI assistants reduce maintenance effort. Recommend ESA adopt with clear guidelines. Useful for content management, accessibility checking, test writing.
edu.au — Overview
Rebuild of the edu.au domain registrar information website. Brand refresh, content migration, CMS for non-technical editors.
Key Objectives
- User-centric website conveying edu.au's role and authority
- Increase direct traffic, enhance analytics
- Reduce maintenance effort and cost
- Scalable architecture for future product lines
edu.au establishes the shared foundation — design system, infrastructure patterns, co-development practices — that accelerates myfuture.
edu.au — Requirements
Functional
- Dynamic homepage with news and events
- Content page templates for easy editing
- Site search, news section (categories, dates, archives)
- Contact form, newsletter subscriber capture
Non-Functional
- Decoupled front/back end, API-driven (REST + GraphQL), open source
- ISM OS, OWASP Top 10, ASVS L1, WCAG 2.1
- GovZone hosting, GitLab source code, ESA owns post-implementation
edu.au — Architecture
┌─────────────────────────────────────────────────┐ │ CDN / Edge │ ├─────────────────────────────────────────────────┤ │ Next.js Front-end (SSR/SSG) │ ├─────────────────────────────────────────────────┤ │ API Layer (REST + GraphQL) │ ├──────────────┬──────────────┬───────────────────┤ │ Directus │ Meilisearch │ Email Service │ │ (CMS) │ (Search) │ Integration │ ├──────────────┴──────────────┴───────────────────┤ │ PostgreSQL Database │ ├─────────────────────────────────────────────────┤ │ GovZone Infrastructure (Docker) │ └─────────────────────────────────────────────────┘
SSG for public pages (near-zero server load), ISR for news/events, componentised email integration, Directus extensibility for product team.
edu.au — Methodology & Timeline
Phase 1: Discovery & Requirements (2 weeks)
Workshops, content audit, IA review, requirements sign-off.
April 2026Phase 2: Design (3 weeks)
Wireframes, brand refresh, design system, accessibility review.
May 2026Phase 3: Build (6–8 weeks)
2-week sprints, ESA embedded, progressive SIT deployment, content migration.
May–June 2026Phase 4: Testing & Training (2–3 weeks)
UAT, CMS training, accessibility audit, security testing.
June 2026Phase 5: Launch (1 week)
Staged PROD deployment, DNS cutover.
June–July 2026Phase 6: Hypercare & Handover (4 weeks)
Post-launch support, training, knowledge base, handover sign-off.
August 2026edu.au — Risks
| Risk | L | I | Mitigation |
|---|---|---|---|
| GovZone deployment complexity | M | H | Early environment setup; containerised approach |
| Content migration gaps | M | M | Content audit in discovery; migration scripts tested in SIT |
| Scope creep during discovery | M | M | Requirements sign-off gate; change request process |
| ESA team availability | M | M | Agreed schedule at kick-off; async code review fallback |
| Brand refresh delays | L | H | Design can proceed with existing brand; refresh as overlay |
myfuture — Overview
Australia's national career education platform. Trusted, non-commercial, evidence-based. Serves students, educators, parents, jurisdiction administrators.
Key Objectives
- Platform meeting all audience groups with personalised experiences
- Live data integrations (labour market, courses)
- Multi-tenancy (jurisdiction > sector > school > class > student)
- Scalable architecture with international market potential
myfuture — Requirements
Dashboards
Educator
Manage classes, assign activities, monitor engagement.
Student
Personalised recommendations, progress tracking, career suggestions.
Jurisdiction
Real-time insights into engagement, professional learning, school-wide usage.
Parent
Student reports, recommended resources, communication tools.
Non-Functional
| Category | Requirement |
|---|---|
| Architecture | API-first; open standards; microservices-ready |
| Security | ISM OS (MFA, RBAC); OWASP Top 10; end-to-end encryption |
| Multi-Tenancy | Secure data separation; configurable per stakeholder |
| Accessibility | Full WCAG 2.1 AA |
myfuture — Architecture
┌──────────────────────────────────────────────────────────┐ │ CDN / Edge Cache │ ├──────────────────────────────────────────────────────────┤ │ Next.js Application (SSR/SSG) │ │ ┌──────────┬──────────┬───────────┬──────────────┐ │ │ │ Public │ Student │ Educator │ Admin │ │ │ │ Pages │ Dashboard│ Dashboard │ Dashboard │ │ │ └──────────┴──────────┴───────────┴──────────────┘ │ ├──────────────────────────────────────────────────────────┤ │ API Layer (REST + GraphQL) │ │ ┌──────────┬──────────┬───────────┬──────────────┐ │ │ │ Auth │ Career │ Content │ Analytics │ │ │ │ (SSO/MFA)│ Tools │ (Directus)│ Service │ │ │ └──────────┴──────────┴───────────┴──────────────┘ │ ├──────────┬───────────┬───────────┬───────────────────────┤ │PostgreSQL│ Redis │ Meili- │ External APIs │ │(Multi- │ (Cache/ │ search │ (Labour market, │ │ tenant) │ Session) │ │ courses, SSO) │ ├──────────┴───────────┴───────────┴───────────────────────┤ │ GovZone Infrastructure (Docker/K8s) │ └──────────────────────────────────────────────────────────┘
Multi-tenancy: PostgreSQL row-level security. Jurisdiction-specific settings. Bulk user management at school/jurisdiction level.
Auth: NextAuth.js + SSO (SAML/OIDC) + MFA. RBAC across 5+ user types. Invitation-based registration.
myfuture — Career Tools
My Career Profile
Interests/strengths/values → personalised career suggestions. Server-side matching. Progressive profiling.
Career Bullseyes
Interactive subject-career linking. Data via Directus. Deep links to exploration tools.
Virtual Work Exploration
Modular — build or integrate. Form builder, assessment engine, points/progress.
Worksheets
Pre-built (Explore) + builder (Build). Drag-and-drop. PDF export. Curriculum-aligned.
myfuture — Methodology & Timeline
Phase 1: Discovery (6 weeks)
Stakeholder workshops, platform review, architecture, personas, GovZone setup.
Apr–May 2026Phase 2: Design (8 weeks)
Wireframes, brand toolkit, design system, user testing nationally.
May–Jul 2026Phase 3: Build (8 months)
| Stream | Scope | Sprints |
|---|---|---|
| Core Platform | Auth, RBAC, multi-tenancy, CMS | 1–6 |
| Public Website | Homepage, content, news, SEO | 3–8 |
| Student | Dashboard, Career Profile, Bullseyes | 5–12 |
| Educator | Dashboard, classes, worksheets | 7–14 |
| Parent/Jurisdiction | Dashboards, reporting | 9–14 |
| VWX | Virtual Work Exploration | 8–14 |
| Admin | Admin tools, ads, newsletters | 10–16 |
| Integrations | External APIs, email, SSO | 6–14 |
| Migration | Content + users | 12–16 |
Phase 4–5: Testing & Launch
UAT, user testing (school terms), accessibility audit, staged rollout.
Timing: school calendarPhase 6–7: Hypercare & Handover
8 weeks support, handover sprints, ESA leads development.
Apr–Jun 2027myfuture — Risks
| Risk | L | I | Mitigation |
|---|---|---|---|
| VWX scope complexity | H | H | Early spike; modular; consider buy vs build |
| School timing for testing | H | M | Identify windows early; remote testing; backup dates |
| External API reliability | M | H | Abstraction layer; caching; data quality monitoring |
| Multi-tenancy isolation | M | H | Row-level security from sprint 1; pen testing |
| Migration complexity | M | M | Scripts in SIT from Phase 3; parallel run |
| 14-month scope growth | M | H | Sprint scope sign-off; change request process |
Cross-Portfolio Efficiency
Shared Design System
Component library + accessibility patterns. Built on edu.au, extended for myfuture.
Shared Infrastructure
Terraform/Pulumi modules, CI/CD templates, GovZone playbooks. Created once, used twice.
Shared CMS Patterns
Directus config, extensions, content workflows transferable between projects.
Consolidated Co-Dev
ESA skills from edu.au accelerate myfuture. One learning curve, two applications.
Sequencing advantage: edu.au finishes first → GovZone patterns proven, design system battle-tested, ESA team already contributing code, governance established.
Key Personnel needs input
| Role | Name | Key Skills | Contribution |
|---|---|---|---|
| Head of Engineering | Sergey Ivochkin | Engineering leadership, software architecture, CI/CD, DevOps, government delivery, cloud platforms, AI integration and responsible AI practices, co-development, engineering governance | Technical workstream leadership, architecture oversight, CI/CD design, engineering governance, AI oversight and responsible AI integration, co-development facilitation, ESA team capability post-handover |
| Tech Lead / Architect | [NAME] | Next.js, React, TypeScript, Directus, PostgreSQL, Docker, GovZone, ISM | Architecture, leadership, code reviews, ESA mentoring |
| Senior Full-Stack Dev | [NAME] | Next.js, React, TypeScript, Node.js, PostgreSQL, API design, CI/CD | Core platform, API layer, career tools, co-dev |
| UX/UI Designer | [NAME] | User research, IA, wireframing, design systems, accessibility | Research, wireframes, design system, brand, user testing |
| Project Manager | [NAME] | Agile, gov project delivery, stakeholder management | Planning, sprints, stakeholder comms, steering committee |
| Front-end Dev | [NAME] | React, Next.js, TypeScript, Tailwind, accessibility | Dashboard UIs, career tools front-end, component library |
Need: Names, qualifications, number of days, % EFT for each person.
Experience needs input
Project 1
[Government/education CMS build, similar stack, content migration, accessibility]
Project 2
[Co-development, knowledge transfer, working with internal teams]
Project 3
[Multi-user platform, role-based dashboards, API integrations]
Project 4
[GovZone or secured government hosting experience]
Need: Client name, project name/year, description/outcomes for each. Need client permission to name them.
Pricing needs input
edu.au
| Phase | Price (excl. GST) |
|---|---|
| Discovery & Requirements | $[AMOUNT] |
| Design | $[AMOUNT] |
| Build | $[AMOUNT] |
| Testing & Training | $[AMOUNT] |
| Launch | $[AMOUNT] |
| Hypercare & Handover | $[AMOUNT] |
| Total | $[AMOUNT] |
myfuture
| Phase | Price (excl. GST) |
|---|---|
| Discovery & Requirements | $[AMOUNT] |
| Design & Wireframes | $[AMOUNT] |
| Build — Core Platform | $[AMOUNT] |
| Build — Student & Educator | $[AMOUNT] |
| Build — Parent, Jurisdiction & Admin | $[AMOUNT] |
| Build — VWX | $[AMOUNT] |
| Build — Integrations & Migration | $[AMOUNT] |
| Testing & Training | $[AMOUNT] |
| Launch | $[AMOUNT] |
| Hypercare & Handover | $[AMOUNT] |
| Co-development overhead | $[AMOUNT] |
| Total | $[AMOUNT] |
Need: Day rates, team size, pricing strategy (fixed/T&M), margin, portfolio discount amount. Prices must include GST and be milestone-linked.
Referees needs input
Referee 1
Company: [COMPANY]
Contact: [NAME, POSITION]
Phone: [PHONE]
Email: [EMAIL]
Project: [NAME AND DATE]
Nature of work: [DESCRIPTION]
Referee 2
Company: [COMPANY]
Contact: [NAME, POSITION]
Phone: [PHONE]
Email: [EMAIL]
Project: [NAME AND DATE]
Nature of work: [DESCRIPTION]
Need: 2 referees who ESA can contact. Need their permission and current details.