For district administrators and school offices
Parents submit once. Staff stop rekeying.
Enrollment packets, permission forms and policy libraries in one system, with a parent-facing side on the district website.

A year of intake in a few weeks
The work arrives all at once
Districts do most of a year's document intake between spring enrollment and the first week of term. That is the load the system has to absorb.
2 weeks
Carry most of the year
Enrollment opening and the first week back
Per school
Scoped by building
Each office works its own project
One form
Replaces the packet
Returned complete, indexed, in one piece
- Enrollment packets44%
- Permission and consent23%
- Policy and handbook access18%
- Vendor and contractor15%
The packet problem
You can see what is missing, per family
Not a pile of returned paper to sort. A form submission with fields, so completeness is a filter rather than a search.
- Registration formSubmitted
- Proof of residencyAttached
- Immunization recordAttached
- Emergency contactsSubmitted
- Media releaseAwaiting signature
- Transport requestNot required
One outstanding item, and it is a signature. Chase that, not the whole packet.

The year has a shape
The work is not evenly spread
Districts do most of a year's intake in a few weeks. The system has to absorb that, not buckle under it.
- 01
Spring
Enrollment opens, forms go live, packets start arriving
- 02
Summer
Chasing the stragglers, scoping records to next year
- 03
First week
Permission slips, emergency contacts, device agreements
- 04
All year
Policy library published once, answering itself
Sound familiar
Your week, roughly
- 01Enrollment packets returned half complete, in three different ways
- 02Chasing permission slips the week of the trip
- 03The same policy question from six different parents
- 04A cumulative file that has to be found before a transfer
- 05Board policy updates that nobody can confirm were published
And what it costs
What you are paying for now
A forms vendor
Separate from where the completed forms end up
A policy hosting service
Another subscription to publish documents you already hold
Office hours spent on retyping
Hand-keying what a parent already wrote on paper
Nucleus One absorbs all three.
Both sides of the line
One system for the office and the public
Staff work the whole thing. Everyone else sees exactly what you publish to them, and nothing else.
Inside: district and schools
- District administrationEvery school, record and process in one place
- School officesTheir own project, scoped to their building
- Special programmesSensitive records restricted to the staff who need them
What crosses
- A published policy libraryBoard policies and handbooks embedded in the district site
- Enrollment and permission formsSubmissions arrive indexed to the right school and student
- Agreements out for signatureSigned and filed without a separate e-signature account
Outside: families and vendors
- Parents and guardiansRead policies and handbooks without an account
- New familiesSubmit enrollment and supporting documents online
- Contractors and vendorsReturn signed agreements and clearances
How it works
What the office gets
- 01
One enrollment channel
A public form replaces the packet that comes back three different ways.
- 02
Scoped by building
Each school works its own project without seeing the others.
- 03
Policies published once
A themed folder on the district site answers the repeat question.
- 04
Records that survive a transfer
Indexed, searchable and permissioned, with history behind them.
FAQ
School district questions
Yes. Policy and handbook folders can be published publicly and embedded in the district website, so families read them without signing in.
Yes. A public form collects the information and attachments, and the submission arrives in the chosen project already indexed on the fields you defined.
Start with one form
Create a free account, publish an enrollment form, and watch a complete packet arrive indexed.
Prefer to talk? Call (863) 937-0272



