Tuition centres running several tutors. WAJD creates the account and sends the first administrator their invitation; after that the centre invites its own tutors. A centre can hold no pupil data until its data processing agreement is recorded.
Families who asked for a tutor on the public form. Approved tutors whose subjects and levels match are emailed, and the first to claim gets the contact details. A claim with no outcome after 7 days returns to the pool automatically. Watch the waiting figure: an enquiry nobody claims is a family we let down and a gap in tutor coverage.
Schools that asked for a demo, a pilot, prices or the papers on /for-schools. Nothing here happens by itself: a person replies to every one, and the school was told to expect that within two working days. A request still waiting after that is counted as overdue, so keep that figure at zero. Move each request along as it goes, so the counts stay true.
Self-registered tutors apply through a structured form (subjects, levels, experience, DBS position) and cannot add or manage any students until you approve them. Approve only after identity verification, an interview and a recorded Enhanced DBS check. Approving or rejecting emails the applicant automatically. Retention: a rejected application keeps a minimal who/when/outcome marker, and its free text detail is deleted automatically after 6 months (ICO recruitment guidance). Use Delete on obvious junk.
Every child account and whether timestamped parental consent is on record. Children enrolled by a tutor must not be left without consent. Recording consent here stamps the date and your name to the audit log.
Approved tutors and the state of their DBS check. Lapsed or soon-to-expire checks (within 60 days) are surfaced first. When a certificate arrives, use File DBS or Update on the tutor's row to record the checking body, certificate number, date checked and renewal date, and to attach a scan of it. Reminder emails go out automatically each day; tutors with a lapsed or soon-due check are nudged (at most once a fortnight) and the admin team gets a daily digest.
Attaching a scan is optional. The DBS code of practice says a copy of a certificate must not be kept longer than six months, so any scan you upload is deleted automatically on the date shown in its row. The recorded details stay on file as the safeguarding record.
Applications come from the public Sponsor page. Approve a sponsor to show them on the wall; "Feature" sets the headline sponsor used on the monthly draw.
On-platform donations and sponsor pledges, for reconciling against Stripe. Stripe is your book of record for card payments (it handles VAT, refunds and payouts and has its own accounting export); these CSVs add the who/why/which-campaign detail to match against the Stripe payout.
Codes parents enter on the Pro page or the tutor form. Switch one on, set its dates and limits, and the Pro page, the checkout and the written terms follow by themselves. Money off is set up in Stripe for you the first time a code is used.
Create staff directly (these tutors are pre-approved). Self-registered tutors appear above for approval. Learners sign up themselves.
Branded leaflets with a QR code to the site. Print, save as PDF, or screenshot for social. The school pack is for heads of year, PTAs, libraries and community groups. The tutor poster is the one to put in front of private tutors: staff rooms, tuition centres and tutor groups.
The parent launch campaign, end to end. Each category below is one job: when it starts, where it shows, the creative, and the live results from every channel.
| Day | Channel | Status | Likes | Comments | Shares | Posted | Link |
|---|
No posts published yet. Connect a channel (Facebook or LinkedIn tokens) and run the auto-poster, or publish from the kit CSV. Posting and metrics appear here automatically.
One place to connect every channel. Profile links and handles show in the site footer and feed the campaign. A green badge means the auto-poster can publish there tonight. Secrets are stored on the server and never shown here: paste, save, and they stay saved.
Instagram has no button of its own. Connect Facebook and, if an Instagram Business account is linked to the Page, it is picked up in the same step.
Upload a real recorded clip (a friendly adult or a child) for each WAJDcrew character, greeting in their own language. It plays when a visitor opens that character on the challenge page. No robotic voices and no paid API: clips are stored and served for free. Keep them under 6 MB (mp3, m4a, ogg, webm or wav).
Run the sponsor-funded monthly prize draw, curate reviews, and publish announcements site-wide.
Open growth studio →Growth, money (MRR, conversion), engagement, content and tutor performance, with 30-day trends.
Open analytics →Live posture of wajd.co.uk and every subdomain: transport security, browser protection headers, certificate health, and the domain records that stop someone sending email in our name.
Open security review →Every class a teacher has created, with its code and how many students joined (school-wide view).
Loading…
Questions parents send privately; you publish the answers as editorial pages at /qa. New questions wait here until answered or archived.
Open Q&A studio →See what is built across the core GCSE and 11 Plus map, where the gaps are, and fill question banks for missing topics.
Open coverage map → Content studio (generate & review) → Read the written lessons →Fills the past-paper directory with links to the official board sites. Runs yearly from cron, or trigger it now. It only collects links, never files, and respects each site's robots.txt.
The latest UK exam-board specifications, found automatically and categorised by board, subject and qualification. Links only to the official source: specifications are the exam boards' copyright, so WAJD never copies or hosts them, and WAJD is not affiliated with or endorsed by the boards. robots.txt respected. Internal tool (not public). Runs monthly, or refresh now.
An append-only record of consequential admin actions. Kept for accountability under the Children's Code; it cannot be edited or deleted in the app. Only alerts (failures, rejections and deletions) are surfaced; routine actions are aggregated below. The CSV export always contains every row.
