Skip to main content
GullySystem

Notices, Circulars and Student Requests

This module publishes notices to selected groups and moves common student requests through submission, review and approval. Each notice and request keeps a record of who acted and when.

Notices and requests in one place

Colleges send notices through a notice board, class groups, email and messages from individual staff, while students ask for certificates and corrections through paper forms and counter queues. This module puts both on one system, so a notice reaches the right group and a request has a visible status.

How notices work

Selected groups

A notice goes to the groups that need it, such as a programme, a semester, a section, a department or the faculty, and students in other groups do not see it at all.

Published by role

Offices and departments publish within the access their role allows. The examination section posts exam notices, and the placement cell posts placement notices.

Where it reaches people

Notices appear in each user’s own view, and where the college connects them, the same notice can also go out by SMS, email or the WhatsApp Business API.

A record of what was sent

The system keeps each notice with its date, its audience and the person who published it. A later question about what students were told has a direct answer.

How student requests work

Submitted by the student

A student raises a request from the student view, with the details the college asks for. The request does not depend on a visit to the office.

Reviewed by the right office

Each request type goes to the office or person who handles it, so a faculty advisor, a department or the administrative office can each be the first reviewer.

Approval steps

Where a request needs more than one approval, the steps run in the order the college sets. The request moves on only when the current step is cleared.

Status the student can see

The student sees whether a request is submitted, under review, approved or returned. A student does not need to ask at the counter.

Request types set by the college

The college decides which requests the system carries. The list is agreed during implementation and can be extended later.

Who uses it

  • Students see notices for their group and track their own requests
  • Faculty and advisors review requests from the students they support
  • Departments and offices publish notices and process requests in their area
  • College leadership sees what has been published and how requests are moving

What it does not do

Notices and requests follow the college’s own rules and approvals, and the software does not decide them. Which requests exist, who approves each one and what a student may ask for are set by the college. Sending notices over SMS, through email or on WhatsApp needs the matching accounts and approvals, which are set up with the college.

FAQ

Frequently asked questions

Can a notice go to one section only?

Yes. A notice can be limited to a programme, semester, section or department, so students outside that group do not see it.

Can notices go out on WhatsApp?

Where the college connects the WhatsApp Business API, yes. The account, the message templates and the consent rules are set up during implementation.

Which student requests can the system handle?

Common requests that move through submission, review and approval. The college chooses the list, and request types can be added after launch.

Does a request need an approval chain?

Only where the college wants one. Some requests need a single reviewer, and others pass through several offices in order.

Is there a record of who approved a request?

Yes. Each step records the person and the time, so the history of a request can be read later.

Talk to us

Tell us what you need.

Send a short brief and one of our engineers will come back to you within one business day.

  • No obligation
  • A reply within one business day
  • Your details stay private

All fields are required. A short description is enough.

Your details stay private. Privacy policyProtected by reCAPTCHA.