Content review process
This page answers one question without hedging: which content on this site has a person read before it was published, and which has not. The table below covers every type of content we publish.
Next review due .
The short answer
Examination pages, pricing, policy and these trust pages are written and read line by line by the editorial team.
Skill guides, subject guides, blog articles, practice questions and their explanations are AI-drafted from the platform’s own database and have not been signed off by a named subject specialist. Specialist review is scheduled. Until it has happened and been recorded, we will not describe that material as reviewed.
The three labels we use
Every page on the site carries one of these three labels, in a strip directly under its heading. There is no fourth, vaguer option.
A person on the DigiTransact Mastermind editorial team wrote this page and read it line by line before it was published.
Human review: Yes — read line by line before publication.
This text was drafted with AI assistance from the questions and topics already stored on the platform. A subject-specialist review is scheduled but has not yet been recorded, so we do not claim it here.
Human review: Not yet. Subject-specialist review is scheduled; this page will say so once it has happened.
These figures and labels are read directly from the platform database or from a fixed mapping in the code. No model wrote them and no wording was invented.
Human review: The mapping and the code that produces it are maintained by the editorial team; the individual values are not hand-written.
Every content type on the site
| Content type | How it is produced | Human review | Date shown |
|---|---|---|---|
| Practice questions and their explanationsPractice sessions, sample questions on subject and skill pages | Generated into the platform database with AI assistance, then served exactly as stored. Learner-reported problems are the main way errors surface today. | Not yet reviewedNot yet. Subject-specialist review is scheduled; this page will say so once it has happened. | None |
| Skill study guidesSkill pages | Drafted with AI assistance from the skill’s own questions, topics and levels. The model used is recorded against each guide in the database. | Not yet reviewedNot yet. Subject-specialist review is scheduled; this page will say so once it has happened. | Last updated only |
| Subject overview guidesSubject pages | Drafted with AI assistance from the subject’s categories, skills and levels. The model used is recorded against each guide in the database. | Not yet reviewedNot yet. Subject-specialist review is scheduled; this page will say so once it has happened. | Last updated only |
| Examination pagesBECE, WASSCE, GES curriculum and the other exam pages | Hand-written by the editorial team and stored in the code, not generated. Each page carries its own review date and next review date. | Reviewed by the teamYes — read line by line before publication. | Last reviewed + next review due |
| Blog articlesBlog | Drafted with AI assistance against a planned editorial calendar, then published. Figures quoted about the platform are read from the database rather than written by the model. | Not yet reviewedNot yet. Subject-specialist review is scheduled; this page will say so once it has happened. | Last updated only |
| Curriculum and examination notesSubject, skill and exam pages | Produced by a fixed mapping from the education levels a page actually covers. No model writes these labels and they never assert approval by an examining body. | Data, not proseThe mapping and the code that produces it are maintained by the editorial team; the individual values are not hand-written. | None |
| Catalogue counts and statisticsHome page, hub pages, blog articles | Read live from the platform database at request time. They are never rounded up and never estimated. | Data, not proseThe mapping and the code that produces it are maintained by the editorial team; the individual values are not hand-written. | None |
| Free course listingsFree courses | Catalogue metadata for courses published by third parties. We link to them and describe them; we do not write, own, review or accredit the course content itself. | Data, not proseThe mapping and the code that produces it are maintained by the editorial team; the individual values are not hand-written. | None |
| AI tutor replies and writing feedbackTutor and writing tools | Generated live by a language model in response to what the learner types. Nobody reads these before the learner does, and they are not stored as published content. | Not yet reviewedNot yet. Subject-specialist review is scheduled; this page will say so once it has happened. | None |
| Policy, pricing and trust pagesThis page, the editorial policy, pricing, privacy and terms | Written and checked by the editorial team. These pages carry a review date and a next review date. | Reviewed by the teamYes — read line by line before publication. | Last reviewed + next review due |
The steps a page goes through
- Scope. We decide which subject, skill or examination the page covers, and which education levels it applies to. This comes from the platform database, not from a keyword list.
- Draft. Hand-written for examination, policy and trust pages. AI-drafted from the platform’s own questions and topics for study guides and blog articles. The model used is recorded.
- Automated checks. Every page is checked in the build for missing headings, broken internal links, orphaned pages, duplicate titles, over-length titles and descriptions, and structured data that does not match what is on the page. These are machine checks. We do not call them review.
- Editorial read. Applies to examination, policy, pricing and trust pages. A person reads the page against its source and the claim rules in the editorial policy, then sets the review date.
- Publication and labelling. The page is published with the label that matches what actually happened to it — never a more flattering one.
- Corrections and re-review. Reader reports come back through the corrections process. Trust and policy pages are re-read on a six-month cycle; examination pages carry their own next review date.
What has to change before we claim specialist review
Specialist review will be claimed on a page only when all four of these are true: a named reviewer exists and their background has been verified; that reviewer has read the specific page; the review is recorded against the page with a date; and the reviewer is listed on authors and reviewers. The reviewer slots currently open are shown on that page as labelled placeholders.
Questions people ask about this
Which content on DigiTransact Mastermind is reviewed by a human?
The examination pages, the pricing and policy pages and the trust and transparency pages are written and read line by line by the editorial team before publication. Skill guides, subject guides, blog articles and practice-question explanations are drafted with AI assistance and have not yet been signed off by a named subject specialist; those pages say so on their face.
Does a subject specialist check the practice questions?
Not at present. A subject-specialist review is scheduled but no sign-off has been recorded, so we do not claim one. Errors are currently surfaced through the corrections process, which anyone can use.
What does the “last updated” date mean?
Last updated records when the text of an AI-drafted page last changed. It is not a review date. Only pages a person has actually read carry a “last reviewed” date, and those are always paired with a next review date.