Chelmsford College website demonstration
A working ASP.NET demonstration of the design, core journeys and staff publishing. This foundation can support earlier delivery, with live integrations and launch preparation still to complete.
Delivery foundation
The shared design and core journeys are in place. Delivery can focus on college integrations, content migration and launch preparation.
Shared layouts provide consistent navigation, course presentation and editing as content is added.
Dedicated C# services separate the public pages from course data, admissions and payments, allowing live connections to be developed around the demonstrated journeys.
Content preparation can run alongside integration work, with regular college reviews to resolve decisions and limit rework.
Proposed delivery programme. We aim to complete the build well before the end of the advertised February–August 2027 contract window. An accelerated programme would be agreed around system access, payment-provider readiness and content approvals.
The proposed review points below would be scheduled with the college at project start.
Approve the content map, SQL mappings, admissions routes and payment approach.
College review: scope & accessDevelop live integrations while migrating the full catalogue and page content.
College review: connected journeysResolve review findings, complete accessibility work and train your staff.
College review: launch readinessAgree release approval, switch over, check live services and begin launch support.
College review: handover acceptedThroughout the build: a weekly written progress update, a fortnightly working demonstration and a shared list of decisions, dependencies and next steps.
Student experience
A student-focused design for course discovery, comparison and applications.
College photography, course search, subject features, student work, news and support share one homepage.
Explore the homepageEngineering’s design process and Creative Industries’ fashion photography introduce each subject alongside relevant courses.
Explore Engineering Explore Creative IndustriesVisual guides explain levels, entry requirements and funding across all 45 records, alongside learning activities, assessment and progression.
Explore a courseVisitors can review campus programmes, save presentations to My visit list and print a plan, with campus and travel guidance linked.
Plan an open evening Presentation choices are a personal shortlist; arrival booking remains a separate step.Printable guidance covers study routes, funding, an instalment example and campus travel.
Explore the enrolment guideStaff can choose homepage features, edit stories, select photography and preview drafts before publishing.
Explore staff editing Staff sign-in protects drafts. Published changes retain a history, while imported course facts stay separate from editorial content.Responsive college photography. Images are sized for mobile, tablet and desktop, with smaller files and reserved layout space. Supplied originals are preserved.
Full website scope
Reusable layouts support courses, news, events and student support across the full website.
Proposed improvements
The examples below show the proposed changes. Live system connections remain to be developed.
College, adult and apprenticeship courses appear in separate lists on the same subject page.
Switch learning route while keeping the subject and compatible filters. Save choices to compare.
The full-time instructions require completion in one sitting and recommend preparing longer answers separately.
Keep course context, move back without losing answers, resume a draft in the same session and review before submitting.
Carpentry’s title says Level 2, while its level field says Level 1. The college needs to confirm the correct level.
Show the level in context and flag conflicting information for staff, with the original course source available.
Students and staff use college portals, external enrolment forms, video and careers tools alongside the website.
Keep approved portal links, make embedded tools accessible and connect college data through interfaces agreed with your IT team.
Technical approach
The demo uses ASP.NET as requested. Separate course, application and payment services provide defined points for college integrations.
Public pages and existing college services
Course catalogue, content pages and application entry points.
Courses, job adverts and newsletters use college-owned data.
Separate routes for full-time, adult and apprenticeship applicants; selected courses use external forms.
The tender requests a new payment facility. Existing finance interfaces need confirmation.
Public .asp addresses are visible on the current site. Your IT team would confirm the underlying software, database versions and planned changes.
The working foundation for the new website
Accessible HTML structure, consistent page styling and JavaScript for search, filters and in-page updates.
Course discovery, editorial content, applications, bookings and payments.
45 course records, editable content and fictional applications, bookings and payments.
An ASP.NET application with stored content, server-managed sessions and staff sign-in.
These layouts and services can be extended to meet the full production requirements.
Connect the college and prepare for launch
Migrate the full site and agree who can edit, approve and publish content.
Connect course records and updates to college SQL data through secure server-side access.
Agree admissions delivery, notifications and staff sign-in through approved college services.
Connect the selected provider, verify payment confirmations and match receipts to learner references and finance records.
IT and finance teams would agree the integrations and operating arrangements before launch approval.
The next stage connects the working ASP.NET demo to approved course, admissions and finance systems.
Content governance
Separate college-owned course information from the campaigns, stories and homepage features managed by communications staff.
Open the staff demonstrationThe demo uses supplied and public course records. A live connection to your SQL data is planned for production.
The staff demo supports drafts, previews and publishing. Production permissions and approvals would be agreed with your team.
Training and aftercare
Proposed training, documentation and support for day-to-day publishing and technical operations.
Sawaiz Mirza will lead ten hours of remote training using college content, guided exercises and questions. Training is included in the proposed build fee, separate from monthly support hours. Initial sessions precede launch, followed by clinics after staff have used the system.
Create pages, select homepage features, add accessible images and links, preview changes and publish.
Practice: take a college story from draft to publication.Manage the agreed access roles, review content history, identify course-source issues and follow publishing responsibilities.
Practice: investigate a content issue and follow the administration guide.Work through configuration, deployment, SQL and payment interfaces, logging, backup, restoration and escalation routes.
Practice: follow the operating runbook and recovery checklist.Address staff questions and practise tasks, including payment records and reconciliation where relevant.
Practice: resolve questions using the guides and agreed workflows.Proposed support package
Sawaiz Mirza will manage support, with Eliyas Brown covering his absence. Named college contacts would use an agreed reporting channel, with priority, investigation and progress updates confirmed.
Included defect fixes: for the first three calendar months from accepted production launch, we will fix defects against the agreed acceptance criteria within the build fee. These fixes remain included whether or not the college purchases general assistance.
Optional general assistance: £600 per month excluding VAT for the first three calendar months after accepted launch, providing 16 hours per month at £37.50 per hour. Defect fixes and the included training package do not consume these hours. Unused hours do not roll over, additional work needs prior agreement, and there is no automatic renewal. Support after month three is agreed separately.
Proposed coverage: Monday–Friday, 09:00–17:00 UK time, excluding public holidays.
These are initial response targets during support hours, not guaranteed restoration times or 24/7 coverage. The final contract would record the support periods, responsibilities and escalation arrangements; fixes involving college infrastructure or providers would be coordinated with their teams.
Optional support for three years or more can cover maintenance, security updates, accessibility reviews, refresher training and new features. The college retains day-to-day control; ongoing scope and cost would be agreed separately.
Demonstrated workflows
Use the provided fictional details to complete an application, visit booking or test payment.
College, adult/HE and apprenticeship routes
Campus schedules and arrival slots
Student or parent/carer payment
Accessibility approach
The demo includes responsive layouts, keyboard navigation, visible focus and clear form errors. The production website is to meet WCAG 2.2 Level AA before acceptance.
Film and PDF accessibility remain unfinished. Final accessibility assessment, assistive-technology and manual checks are still required before sign-off.
View the accessibility statusSources include the tender specification, supplied course and event material, and college pages available on 2 November 2026.
IT and service teams would confirm private workflows, software versions and integration requirements during planning.
Course pages distinguish confirmed campus details, department-based estimates and unconfirmed information. Payment amounts and event availability are illustrative.
