chapter 16 · pdf filechapter 16 discipline ... 17-gangrel act 370 5b-kdnp stu 210 18-bus...

Revised September 8, 2011 16-1

CHAPTER 16

DISCIPLINE

Discipline in eSchoolPlus has been configured to meet the reporting requirements of both

the Fulton County School system and the State of Georgia. The code structure includes

local codes for “Incidents” which are correlated to state codes for reporting “incidents”; local

codes used for “Actions” are correlated to state codes for reporting “actions”.

Assistant Principals, responsible for discipline in each school, are expected to enter discipline

incidents and actions into the Discipline screens in eSchoolPlus for each student on a daily

basis. The Assistant Principal (AP) initiating the tribunal referral is also responsible for

entering the decision of the tribunal hearing into eSchoolPlus; likewise, the AP must enter

any tribunal decisions later modified or overturned by the Fulton County Board of

Education. Student discipline information should be monitored by each Principal for

accuracy and can be viewed by Area Superintendents at any time.

SECURITY LEVELS IN DISCIPLINE:

Security levels restrict the ability to view or assign information in the Discipline Center;

generally data clerks, assistant principals, administrative assistants (when assigned

discipline duties), and principals are allowed to view and add discipline data. Other core

team members given view only rights where applicable: resource officers, counselors,

discipline secretaries, counseling secretaries, and administrative assistants (when not

assigned discipline duties).

REQUIRED FIELDS:

The following fields are the minimum required for entering student discipline data into

eSchoolPlus:

On the INCIDENT DETAIL screen: Building, Incident, Incident Date,

Incident Time, Location, Reported By, Reported To, Description, and

Offender Name(s).

On the OFFENDER ACTION MAINTENANCE screen: Action Code,

Actual Duration, Scheduled Duration, Scheduled Start Date, Scheduled End

Date

If the action is removal from the classroom by a teacher, that teacher’s Staff

ID must be entered in the Reported By field.

In order for students coded as 620-Permanent Expulsion to be reported

correctly for end of year Student Record, the Scheduled End Date field must

be blank.


INCIDENT AND ACTION CODE STRUCTURE:

The local code structure is based on Fulton County Board of Education Policy and Procedure;

the code structure reflects the Board Approved Student Code of Conduct. The prefix in each

code description references the specific Board Procedure where a full description of the

incident can be found. Be advised that codes 800 and greater serve as indicators for rules

that have expired and are retained in eSchool for historical purposes only.

The State of Georgia requires specific types of incidents and actions to be reported annually.

All locally defined incident codes are not considered “reportable incidents” nor are all locally

defined action codes considered “reportable actions”; therefore, only those local codes deemed

reportable by the state are mapped to a state code for reporting purposes.

Of the following incidents and actions, any written in UPPERCASE are automatically

reported to the Georgia Department of Education each year. If any non-reportable (written in

mixed case) incident results in bus suspension, in-school suspension, out-of-school

suspension, expulsion, referral to court/juvenile system, teacher removal from class, or

assignment to an alternative school, that incident must also be reported to the state as state

code incident number 240, Other Serious Incident. Contact the Office of Student Discipline

with any questions about which code is appropriate for the incident or action.

DO NOT choose the Discipline Offense Code “000” for reporting “Continued Incident”. If

multiple offenses are entered correctly using the instructions defined in this chapter,

eSchool appropriately calculates the “000” during the state reporting Discipline Extract

process. The “000 – Not for Schools” in the Offense drop-down selection is there ONLY for

internal programming.


FULTON COUNTY DISCIPLINE INCIDENT/OFFENSE CODES

Description Code

Description Code

10-Disrgd rule 315

3-THEFT PRIV PR 125

10-MnrDisrptBeh 310

3-Theft prv mnr 145

10-TRSP PRV PRP 325

3-VEH THEFT PRV 130

10-TRSP SCH PRP 320

4a-BTRY EMPL 165

11a-Truancy 331

4a-HMCD EMPL 160

11b-Excessive Tardy 332

4b-Btry emp mn 180

11b-Unexcused Absence 333

4b-FIGHT EMPL 170

11c-Leaving Camp W/O Permission 334

4b-KDNP EMPL 175

12-Improp dress 335

4c-Aslt empl 185

13-TOBACCO PROD 340

4d-THREAT EMP 190

14-Gambling 345

4e-Bad lang/em 195

15a-SEXUAL MISCONDUCT 352

5a-BATTERY STU 205

15b-SEX BTRY EM 355

5a-HMCD STUDENT 200

15b-SEX BTRY ST 360

5b-Aslt studnt 220

15c-SEXUAL MOLESTATION 362

5b-Btry stu mn 225

16-CMPTR TRSPS 365

5b-FIGHT STU 215

17-GangRel Act 370

5b-KDNP STU 210

18-BUS INTERFER 375

5c-THREAT STU 230

19-OffCamMiscon 380

5d-Bad lang/st 235

1a-Use sch grnd 010

6a-Threats 240

1b-Bloc sch pro 015

6b-Harassment 245

1c-Prvt sch fnc 020

6c-BULLYING 250

1d-Prvt go clas 025

6d-Disrespect 255

1e-BlockTraffic 030

6e-Harmnt/Big 260

1f-Intrfr w/emp 035

7-SEX HARASSMT 265

1g-Pgr/cellphon 040

8-WEAPONS/FRARM 275

1h-Audio Vis Recording Device 046

8-WEAPONS/HNDGN 285

1i-SER DSRPT BE 047

8-WEAPONS/KNIFE 270

1j-Refused ID 051

8-WEAPONS/OTHER 280

1k-Bomb Threat 056

8-WEAPONS/RIFLE 290

1l-FseCall-911 061

9a-ALCOHOL 301

1m-Fse Fire Alarm 066

9a-DRUGS 300

1n-FseRptStaff 071

9b-Drug Paraphernalia 302

1o-Urge Violate 076

9c-False identification of drugs or alcohol 303

20-EncourMiscon 385

9d-Drug or alcohol distribution 304

2-Arsn sch nodm 105

9e-Influence of Inhalants 305

2-ARSN SCH PROP 100

9f-Over-counter medications 306

2-B&E SCH PROP 085

9g-Prescritpion drugs 307

2-DMG SCH PROP 080

Discipline Hrg 606

2-Theft sch mnr 110

Discipln Conf 604

2-THEFT SCH PRP 090

Not for Schools 000


2-VEH THEFT SCH 095

OTH SERIOUS INC 600

3-ARSN PRIV PRP 135

Other Firearms 028

3-Arsn prv nodm 140

SERIOUS BOD INJ 601

3-B&E priv prop 120

TADRA-NonCompl 602

3-DMG PRIV PROP 115

TADRA-ReInstate 603

3-ROB EMPL 150

3-ROB STUDENT 155


FULTON COUNTY DISCIPLINE ACTION CODES

Description Code

Description Code

Acad/atten beh contract 600

Parent conference/wrng 410

ADM LAW JUDGE REFERL 618

Parent notification 405

Administrative Detention 442

PERMANENT EXPULSION 620

Administrative Conference Held 522

Principal conference/wrng 415

Bus misconduct referral 450

Principal confrnc/tribunal 417

BUS SUSPENSION >10 456

Public detention 445

BUS SUSPENSION 1-10 455

Restitution 440

Comm ser hrs assgn 605

Retrn to comprehensive sch 645

COMMUNITY SCH REFERL 515

Rule withdrawn 630

Conference/other 420

Saturday opportunity sch 465

CONTINUED ACTION-PRIOR INCID 0

SAVTE program referral 525

Counselor referral 485

Special ed. Placement 650

COURT/JUVENILE REFERL 481

SST referral 475

Crossroads School Alternative Referral 511

SSW/VT referral 480

Disciplinary hearing referral 500

Student conference/wrng 400

EXPULSION 615

Student withdrawn 635

IN-SCHOOL SUSPENSION 460

TCHR RMV-ADM RETURN 472

Insight program referral 520

TCHR RMV-ADM SUPPORT 471

LONG-TERM SUSPENSION 610

TCHR RMV-PNL RETURN 474

Manifestation of Disablility 523

TCHR RMV-PNL SUPPORT 473

Not guilty 625

TimeOutOffic/OpprtntyRm 430

Not Manifestation of Disablility 524

Waived expulsion 660

OPEN CAMPUS REFERRAL 505

Waived long-term suspension 655

OSASP Referrell 521

Waived permanent expulsion 665

OTHER ALT SCH REFERL 516

Waiver of Disciplinary Hearing 667

OUTOFSCH SUSPENSION 470

WithdrawnfromFultonCnty 640


HOW TO ENTER DISCIPLINE INCIDENTS AND ACTIONS

Add Discipline Incident

Discipline Center>>Incident Detail

Note: If Incident List is not the first screen, click on Search

Click on New

The Incident Detail screen will open.

Enter information in:

o Building - Should default to current building; if not, key student’s

current building.

o Incident - select from the drop down table an incident code for the

disciplinary infraction.

o Incident Date (NOTE: The Incident date will default to the current

date; change as appropriate.)

o Incident Time - key the time the incident occurred

o Location – select from the drop down table the appropriate location

where the incident occurred

o Description Area - Type a Description of the incident

Skip (do not enter any data) in:

o Category Field

o Incident Timeframe


o Reported To

In the Reported By field choose from the drop down table either Staff,

Student or Other Non-Student

If Staff is chosen, on the next line, click on the drop down table and

choose the appropriate staff person

If Student is chosen, on the next line, click on the drop down table and

choose the appropriate student

If Other Non-Student is chosen, on the next line, click on the drop down

table

Click on Cancel

Key the First and last name

Click OK

Click on the Save button


Add Action “Taken By” To Incident

From the Incident Summary Screen, click on the incident number to go back to

the detail screen

Click on the District-Defined Tab

Click on Action Taken By

Click on the drop down and wait for the list

Choose the appropriate administrator

Add Offender To Discipline Incident

Click on the Offenders Tab

Key all or part of the last name in the Offender Name field; tab to the next field.


Highlight the correct student and click on OK. (Note: The Offender field is the

student’s ID and will self populate once the correct student has been chosen.)

The Category, Drug, and Weapon fields on the Offender line are not used.

Repeat to add a line for each offender involved in the incident.

Click on Save

Add Action to Student

From the Incident Summary Screen, Click on the student’s name

o General Tab

Click in the radio button to indicate guardian notification

Notify Date - will default to current date, adjust as needed

How Notified – Choose the appropriate response from the drop down table

Referred To – If applicable, choose Insight, SAVTE, or OSASP

Police Action – Choose Yes or No from the drop down table


o Actions Tab

Pay close attention to the “Action Duration Totals” as this is a running total

for OSS, ISS, Detention, and Saturday School assigned during the current

year. This is particularly helpful when the offender is a special ed student.

Click on New Action

Action Code – choose the appropriate action code from the drop down

table

Actual Duration - enter the actual number of school days the student

served (ISS or OSS).

Scheduled Duration – enter the number of school days the student is

scheduled to be suspended (ISS or OSS)

Scheduled Start Date – Key the date the suspension is to begin

Scheduled End Date – Key the date the suspension is to end (Required for

all types of suspensions and 615-EXPULSION; for one day of suspension,

the Scheduled Start Date and the Scheduled End Date will be the

same.) Be sure to use valid school days found in the ESCHOOL school

calendar.

Reason for Difference -- If there is a difference between Actual Duration

and Schedule Duration, choose Insight, SAVTE, or OSASP

For students coded 620-PERMANENT EXPULSION, leave the End

Date blank.

If the action is “removal from the classroom” by a teacher, that teacher’s

Staff ID must be entered in the Reported By field on the Discipline Incident

Detail Screen.


ADD AN ALERT ONCE THE TOTAL NUMBER OF DAYS FOR

ISS/OSS HAS REACHED THREE FOR ANY SPECIAL EDUCATION

STUDENT

Student Center >> Demographic >>Academic

Scroll to the bottom of the screen and click on the link for “Calculated Status”

Choose the Eligibility Tab

Eligibility Code: “Admin Conf required before any additional suspensions”

Effective Date: Date of Incident

ExpirationDate: Last Day of School

Building: Current Building

Reason: “Discipline – Special Ed Student”

Click Save

If a student has the Admin Conf required alert, the alert symbol A will be visible at

the top of the screen for the student. Click on the “A” symbol to reveal a dialog box with the

specifics.


INCIDENTS INVOLVING MULTIPLE STUDENTS

Per the DOE, all state reportable incidents involving two or more students must be

reported with a unique Incident ID Number. The State is asking that all schools now report

an “event identifier” that will enable the identification of multiple students that are tied to a

single incident. This requirement impacts incidents reported for all active and inactive

students in the 11/12 school year.

NOTE: The Incident ID will serve as the unique event identifier eliminating the

need for schools to maintain a block of event identification numbers previously

assigned to each school.

Incidents involving students from the same Fulton County School

Schools are to make certain to add all students involved as “offenders” to the same incident;

this will ensure that applicable multiple students will be reported with the proper unique

event identifier.

Incidents involving students from more than one Fulton County School

If an incident involves students from more than one building, the

administrators from each building must coordinate their efforts to enter the

discipline incident and actions properly. If the incident occurred on the

campus of one school, that school’s administrator will enter the incident in

eSchool; if the incident did not occur on either campus, the administrators

should decide which will begin the process in eSchool. For illustration

purposes, we’ll assume that the incident occurred during a football game at

Roswell High School and involved students from Roswell and Milton High

Schools. Roswell’s administrator will enter the incident in the same manner as

they would for any incidents involving only Roswell students. The only

“offender” added by the Roswell Administrator will be the Roswell student.

Once the incident has been added and the actions entered for the Roswell

student, Roswell will provide the Incident ID number to the Milton

Administrator.

At Milton:


Click on Search

Enter the Incident ID number provided by other school

Click on Search


Click on the Incident to open.

Note: If the Incident ID is not provided, search instead on the building number,

and then choose the incident from the list:

Using either method, open the incident.

Notice that the only offender listed is the student from Roswell.

Add the Milton student as an additional Offender

Click Save


Add the actions to the Milton student


INCIDENTS INVOLVING MORE THAN ONE OFFENSE

Multiple offenses occurring during the same incident are all added to the single incident. In

the event that the incident also involves multiple students each student could have different

additional offenses.


Choose the appropriate incident

Click on the Offender Name

Add additional offense(s) (choose the offense from the drop down table)


Delete Discipline Incident If necessary, an entire incident can be deleted. To do so, go to the Incident

Detail List

Discipline Center>>Incident Detail>>

Click in the radio button under the column heading, Delete

Click on the Delete Button

Confirm by clicking Yes

Delete Offender From Discipline Incident Individual students can be deleted from an incident without deleting the

incident itself.

Discipline Center>>Incident Detail>>Click on the Incident

On the same line as the student, click on the radio button under the column heading, Delete

Click on Save


COGNOS DISCIPLINE REPORT(S):

Note: Refer to the Cognos Companion Guide Chapter if any problems are encountered while

either accessing Cognos or printing any reports.

Student Discipline Verification

Student Information Coordinators should work with any other discipline administrators,

within the same school, throughout the school year to ensure discipline data is BOTH

accurate and complete at all times. Schools should run, (at a minimum) once a month, the

Cognos report titled: “Student Discipline Verification” in order to review and verify for

accuracy the Discipline data for the 2011/2012 school year.

Log onto Cognos Reporting

FCBOE Reports>>Discipline>>Student Discipline Verification

Choose Building

Select Start of date range

Select end of date range


For school wide verification purposes do not choose a grade level and do not choose any

particular students. Go to the bottom of the screen and click Finish

Watch for this prompt

Choose either Open or Save

Enter credentials

View, print, and/or save report


Other Cognos Reports Currently Available for School Use:

Log onto Cognos Reporting

FCBOE Reports>>Discipline>>

Historical Student Discipline Data

Incident Totals by Building~Date Range

Report View of Student Discipline Verification

Students With Discipline (Historical)

Students With Discipline at current school (Historical)

Students with NO Discipline

Totals by Discipline Action Type

Totals by Discipline Action Type by Grade

Totals by Discipline Action Type for Date Range

Totals by Discipline Incident SubCode

Totals by Discipline Incident Type

Totals by Discipline Incident Type by Grade


eSCHOOL DISCIPLINE REPORTS:

AVERAGE INCIDENT

Discipline Center>>Reports>>Average Incident

Select school, incident codes, start and end month

Click Run

Will progress from scheduled,

to current,

to completed; once the report is complete, click on the appropriate report name to view.



DAILY ACTION

Discipline Center>>Reports>>Daily Action

Enter school, start and end dates, include page break on date and print classification

Click Run

The report will progress from scheduled, to current, to complete; once the report is complete,

click on the appropriate report name to view.



INCIDENT

Discipline Center>>Reports>>Incident

Enter school, incident codes, start and end dates

Click Run





STUDENT DETAIL

Discipline Center>>Reports>>Student Detail

Enter school, choose how to list, start and end dates

Click Run

Note: If running for particular student, use this filter:





HOW TO ENTER DISCIPLINARY HEARING INFORMATION

It is extremely important that information entered in ESCHOOL is accurate and complete at

all times in order to ensure the integrity of the annual State Discipline Report and the

district information used to make decisions based on student discipline data.

When a school administrator sends a student to a Disciplinary Hearing, it is that

administrator's responsibility to ensure that the ESCHOOL data for this student is

completed, including the results of the Hearing immediately upon returning to school.

An additional action for any student referred to The Office of Student Discipline must be

included; codes "500-Disciplinary hearing referral" and/or “667-Waiver of Hearing” are to be

used. The discipline given to the student by the Hearing Officer or agreed to in the waiver is

to be added as another action on the same incident which brought him to the hearing in the

first place.

Immediately upon returning to school after any Disciplinary Hearing, enter the results of the

hearing in ESCHOOL. The actions entered from the hearing are according to the directions

received from the Office of Student Discipline; these should be given to you by the Director or

Coordinator of Student Discipline at the end of the hearing.

It is very important that hearing officer decisions are included in a student’s record as a

action under the added Disciplinary Hearing “incident code”. This is especially important

when a student receives discipline beyond the scope of the administrator’s authority; for

example, if a student is given more than a 10-day suspension, an expulsion, or either of these

along with a waiver for an alternative education placement.

Remember: ALL STATE REPORTED INCIDENT AND ACTION CODES MUST BE

INCLUDED IN ESCHOOL.

For discipline Waived Expulsions, if the student was assigned to an alternative school but

the program is full and placement will not start until the next school year, use the Leave

Code of “H”, do not use a drop-out code.

If a student is withdrawn from school but the discipline ordered resulted in a Waived

Expulsion, do not use the Leave Code “E”.

For questions regarding local discipline policies, procedures, and cycles, contact The Office of

Student Discipline, at the Jo Wells Center (404-763-5611).

chapter 16 · pdf filechapter 16 discipline ... 17-gangrel act 370 5b-kdnp stu 210 18-bus...

Documents