ProCraft — Case study 05India

AITMone record.

A VTU-affiliated engineering institute with departments, admissions, results and continuous news output — a large site with one source of truth.

Doc — WORK/05 · Rev AHigher educationWeb development, custom systems
Higher education · IndiaWeb development, custom systems
05

Anjuman Institute of Technology & Management (AITM)

02Project snapshot
Challenge

Five audiences, one institution

Objective

Everyone finds their task

Solution

Institutional site + separate results system

Outcome

Result pending — client-confirmed

Institute campus front, clean architectural line drawingPlate 03 — campus front
Fig. 01 — a VTU-affiliated engineering institute, one source of truth.Live at aitm.edu.in
04The challenge

Five audiences, one front door.

A VTU-affiliated engineering institute with departments, admissions, results and continuous news output.

Institutional sites serve several audiences at once — prospective students, current students, parents, faculty, regulators. Each wants something different and each will leave if they can’t find it. Traffic also spikes hard and unpredictably around results.

The friction

Five audiences, one navigation

Results-day spikes

Developer-dependent publishing

Before — results day
Results published
Traffic spike
Site strain
Manual updates
Frustration
05The transformation

Before

  • Org-chart structure
  • Results-day outages
  • Developer-dependent

After

  • Audience-task structure
  • Separate results system
  • Faculty publishing
06Project goals

What needed to change.

01

Serve five audiences at once without losing any of them.

02

Survive the results-day traffic spike.

03

Let faculty and administration publish without a developer.

04

Keep departments, admissions and news on one source of truth.

07Plan of work

Six stages, signed in order.

01Discover

We map the business, audience and where the current setup breaks.

02Strategize

What gets built, what stays manual, what it costs and how long.

03Design

Experience and interface agreed on paper before development.

04Build

Developed to the drawing with scalable, modern technology.

05Launch

Tested, deployed, the team trained — run in parallel until it holds.

06Grow

Improve, maintain and evolve. Support with a name and a number.

08Who it serves

One institute. Five audiences.

RoleProspective students

Courses, admissions, campus.

RoleCurrent students

Results, notices, timetables.

RoleParents

Fees, contacts, confidence.

RoleFaculty

Publishing without a developer.

RoleRegulators

Mandatory disclosures, findable.

Five audiences — one source of truth
09Information architecture

Structured by task, not org chart.

aitm.edu.in
Departments
  • Programmes
  • Faculty
Admissions
  • Apply
  • Eligibility
  • Fees
News
  • Notices
  • Events
Results
  • Separate system
  • Load-isolated
About
  • VTU affiliation
  • Campus
10System decision
Results day, survived

The spike that stopped mattering.

The results system is deliberately separate from the main site. On results day the load lands on its own system — students get their results, and the institute’s front door stays open.

Results published
Separate system takes the load
Main site untouched
Students get results
Campus, technical line drawingPlate 11 — the campus
11Deliverables

What we delivered.

01Institutional website

Departments, admissions and news in one place.

02Audience-task architecture

Each visitor finds their job, fast.

03Content system

Faculty and administration publish themselves.

04Separate results system

Results-day load, isolated by design.

12Technology

The build.

FrameworkDjango
ContentCustom CMS
ResultsSeparate system
HostingLoad-ready
13Result
Pending — client-confirmed metric

We publish results when the client confirms them — not before.

BeforeResults day as outage day
AfterResults day as a normal day

A business like this one?

Same starting condition, different sector — tell us where your current setup breaks and we’ll map it in one working session.