TurtleDock
Index

Notes on running an institution

The TurtleDock blog is written by the implementations desk rather than by marketing: operational pieces on fee cycles, admission seasons, examination cycles and the portals Indian institutions file into. Figures are labelled and corrections are made in the page, dated.

These are notes from doing the work, not research. Where a piece describes a regulation or a portal, verify against the primary source before acting on it.

Most software company blogs exist to rank for their own product name. This one is closer to a record of what implementations desks keep having to explain — which is a narrower and more useful thing.

If a piece is about a filing or a regulation it names its source and the date it was checked. If it contains a number, the number says where it came from.

Written by
Implementations, not marketing
Covers
Fees, admissions, examinations, compliance
Sources
Named and dated on anything factual
Corrections
In the page, dated, not silently
01

What gets written about

  • The fee cycle. Reminders, instalments, concessions and the reconciliation that follows a term.
  • Admission season. What to configure before it opens, and what breaks when you do not.
  • Examinations. Identity, evaluation, moderation and the audit trail that makes a result defensible.
  • Compliance. UDISE+, APAAR, board portals, the DPDP Act and what each actually requires.
  • AI in education. What it does, what it should not be allowed to decide, and how to tell the difference.
02

Where the writing comes from

Every piece is written by the desk that does the work it describes and reviewed by that desk before publication. That is the reason the tone is operational rather than aspirational — the people writing have had the argument being described, usually more than once.

It also means the pieces are opinionated about what does not work, which is unusual for a vendor blog and is most of what makes them worth reading.

FAQ

Questions people ask

Phrased the way they arrive, answered so each one stands on its own.

How often do you publish?

When there is something worth writing rather than on a schedule. In practice that has meant two or three pieces a month, weighted toward the seasons when institutions are under the most pressure.

Who writes these?

The implementations desk, and for product pieces the product desk. Each page names the desk that reviewed it and the date it was checked.

Can we reprint a piece for our staff?

Yes, for internal training, with attribution and without alteration. Ask before republishing one publicly.

Related

Read next

Provenance

Who checked this, and against what

Accountability

Checked by the Implementations desk on 2 September 2026. Corrections go in the page, dated, rather than quietly.

No call required

Tell us your enrolment, we will tell you the number.

Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.

See pricing

Bring your own structure. We configure it live on the call.

Forty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.