See what blog publishing changes at your institution
Before vs. after adding the blog to iVake
Where you are today
Holding you back
Faculty write everywhere but here
Research notes and commentary go to LinkedIn and personal pages, because posting on the institution’s site means emails, a login from IT and days of waiting.
Pain point
Every post goes through one desk
The communications team writes, formats, finds photos, chases the author’s bio and asks the web vendor to publish, one post at a time.
Pain point
One story, five versions
A topper’s story sits on the department page, the prospectus site, the alumni newsletter and social media, each copy edited separately.
Pain point
No link between posts and enquiries
Admissions can see page views, but not which posts the families who went on to enquire had actually read.
Pain point
- 3+Places the same story is kept
- DaysFrom finished draft to published post
- 2+Logins needed to publish one article
Your institution, transformed
Everything connected
Staff publish with their own login
Faculty and staff draft posts with the same sign-in they use for iVake, with no separate website account to request.
Solved
Author details filled in
Name, designation and department come from the staff record, so nobody chases a bio before a post can go live.
Solved
One post, shown wherever it belongs
A story is written once and listed in each section it belongs to, so every copy is the same copy.
Solved
Enquiries traced to the post
An enquiry form on a post carries its source into admissions, so the team sees which posts led families to enquire.
Solved
- 1Login for staff to write and submit
- 1Copy of each story
- 0Author bios typed in by hand
Ready to make the switch? See how it works for your institution.
Faculty and staff publish, editors approve
When getting one research summary online takes a week of emails, faculty stop trying. Here they write in iVake, and the post waits for the editor you name before anyone outside the institution sees it.
- Writing and submitting with the login staff already use, with no website training
- Name, designation, department and photo taken from the staff record
- Approval rules by author, department or category, with each step logged
Posts linked to the enquiries they bring in
More page views tell the admissions committee very little. Knowing which posts families read before they filled in an enquiry form tells it a great deal, and the enquiry lands on the same platform that holds the post.
- An enquiry form on a post passes the post to admissions as the source
- Enquiries counted by post, programme and city, not only page views
- Publishing scheduled around admission rounds, open days and scholarship deadlines
Alumni stories that keep graduates close
Graduate stories arrive by email and WhatsApp and are never published. An alumni section lets graduates send their own updates for the alumni office to review, and each story stays attached to the graduate’s profile.
- An alumni section with its own editors and approval steps
- Graduates submit career updates and stories for the office to review
- Each story linked to the graduate’s verified profile in the alumni directory
Blog publishing features
Everything you need to publish your institution’s own stories
Post editor
Text, images and attachments, with drafts saved as you write.
Author profiles
Designation, department and photo read from the staff record.
Approval workflow
Review steps by author, department or category before a post goes live.
Scheduled publishing
Set a date and time, then unpublish or archive when a post is out of date.
Sections & categories
Department, research, placement and alumni sections, each with its own editors.
Search settings
Page title, description, web address and share image for every post.
Enquiry tracking
Enquiry forms on a post send the post to admissions as the source.
Access & audit trail
Who can write, approve and publish is set by role, and every change is logged.
Frequently asked questions
Get answers to common questions about blog publishing
Do faculty need to keep a separate blog profile?
No. When someone is named as the author, their name, designation, department and photo are read from their staff record, and a later change there shows on their posts. Guest writers and alumni get a short contributor profile when they first submit.
Can some staff publish directly while others need approval?
Yes. Approval can be set by role, department, category or individual author. A head of department might publish to the department section straight away while anything aimed at applicants still goes to the communications office. Each review and approval is logged with the person and the time.
How do we see which posts lead to enquiries?
An enquiry form on a post, or a link from it to your admissions form, carries the post as the source. The enquiry arrives in admissions with that source attached, the same way a campaign’s does, so the team can count enquiries by post, programme and city.
What search settings does each post have?
Each post has its own page title, description, web address and share image for link previews, and images ask for alt text. Posts move through draft, in review, approved, scheduled, published and archived, and every change of state is logged.
How do alumni stories connect to the alumni office?
Posts in the alumni section are linked to the graduate’s profile in the alumni directory, where programme and batch come from the institution’s own record. The alumni office sees the story beside that graduate’s events, mentoring and giving.
Can departments and campuses run their own sections?
Yes. Each department, campus or office can have its own section, editors, categories and approval rules. The communications office sees every section’s queue and can move a department post onto the main blog when it deserves a wider audience.
Can we publish students’ names and photos?
Under the DPDP Act that needs a lawful basis, and for anyone under eighteen, a parent’s consent. Editors can check the consent held on the student record before approving a post. The decision, and compliance with the Act, remain your institution’s.
Cloud, hosted in your region
REST API & webhooks- SSO: Google, Microsoft & SAML
Encrypted, backed up daily
Built for the DPDP Act- Full security details
Built for your institution type
See how this feature works for your specific institution
CBSE, ICSE & state-board schoolsClass activities and results, approved before parents see them
UniversitiesA section per school and campus, one editorial view
Degree collegesFaculty research and placement stories, traced to enquiries
ITIs, polytechnics & skill centresBatch completion and placement stories for new enquiries
Playschools & pre-primaryShort updates for parents, checked before they go out- Coaching institutesPosts scheduled around admissions, with enquiries traced back
Integrations, comparisons & tools
Extend blog publishing with integrations, see how iVake compares, and run the numbers
Related features
News Portal
Campus news through one editorial queue, shown to each person by role and programme.
Community Forum
Searchable forums for programmes, clubs, hostels and alumni.
Notice Board
Notices and circulars to the classes, departments and parents they concern.
Admission Management
Enquiries from every source, your website included, on the record that becomes the student.
Alumni Management
A verified graduate directory with mentoring, events and giving.
Social Media Integration
Posts shared to your institution’s social channels from one place.
More in engagement & outreach
Explore other features in this category
Ready to publish your institution’s own stories?
See how iVake lets faculty, staff and alumni write for your website, with an editor’s approval and each enquiry traced back to the post.
Try it free for 30 days. No credit card required.