Current through Register Vol. 6, March 25, 2022
during the course of a school year, the district becomes obligated to provide
transportation for a student, the board of trustees immediately must:
(a) provide bus service for the eligible
(b) enter into a
contract with the parent, legal guardian or emancipated minor, and transmit a
copy of the contract to the county superintendent, who transmits one copy
immediately to the Superintendent of Public Instruction.
(2) The cost of such additional
transportation is met by the contingency item in the transportation budget or
nonoperating budget. Valid claims against the amount budgeted as contingency
are reimbursable by the state and county as on-schedule costs.
(3) If there is no contingency item (or the
appropriation therein is already obligated for other pupils in the district),
the district shall institute budget amendment proceedings to acquire the budget
authorization necessary to provide transportation for such students.
The on-schedule costs associated with the
contingency transportation, in excess of the contingency amount, are
reimbursable by the state and county only upon adoption of a budget amendment
increase as provided by
MCA, and, either county transportation committee approval of new or altered bus
routes or district approval of new individual transportation contracts, and
state approval of such transportation.
The state shall pay its share of these on-schedule costs as provided in
The county shall pay its
share of these on-schedule costs as provided in
(i) The county shall include in the levy
requirement for the ensuing year, any unpaid amount of the county's obligation
for contingency transportation.
The over-schedule costs of the
contingency transportation shall be paid by the district and funded by:
(a) the district's transportation
(b) budget transfers from
other line items in the transportation fund as provided in
MCA, if available; and
(c) any levy
assessed against the taxpayers of the district for purposes of funding the
Mont. Admin. R.
Eff. 8/6/75; ARM Pub.
11/26/77; AMD, 1992 MAR p. 203, Eff. 2/14/92; AMD, 1997 MAR p. 203, Eff.
1/28/97; AMD, 2000 MAR p. 632, Eff. 2/25/00.