Document Workflow Platform for New Zealand Schools

PaperTiger is an educational document management platform built for schools in New Zealand that were drowning in paper-based administrative processes. School administrators, teachers, and department heads generate and process hundreds of documents every term - lesson plans, assessment records, compliance reports, policy documents, and parent communications. Most schools managed this through a combination of shared drives, email attachments, and physical filing cabinets - resulting in lost documents, version conflicts, and hours wasted searching for the right file. PaperTiger replaces this chaos with a structured digital workflow: document creation from templates, role-based approval chains, version tracking, and a searchable archive. The platform is designed specifically for how schools work - term-based cycles, departmental hierarchies, and compliance requirements that generic document tools ignore.

1. 01

   Schools relied on shared drives, email, and physical filing for document management. Administrative staff spent hours searching for documents, chasing approvals through email chains, and managing version conflicts. No existing SaaS product addressed the specific document workflows of the New Zealand education system.

2. 02

   Designing for users with widely varying technical proficiency - from tech-savvy younger teachers to administrative staff who had only used email and Word. The interface needed to feel simpler than a shared drive while supporting structured workflows like template-based creation, multi-step approvals, and compliance tracking.

3. 03

   Building a document management engine that handled template-based creation, collaborative editing, multi-step approval workflows, and full-text search across thousands of documents. The system needed to support school-specific hierarchies (departments, terms, academic years) while remaining fast and reliable on the internet connections typical of New Zealand schools.

• Admin dashboard with usage analytics

  School administrators see who is creating, approving, and accessing documents — surfacing bottlenecks and adoption patterns at a glance.

• Cloud-based document management web platform

  Browser-based platform reachable from any school computer, replacing the local-drive-and-email system that did not scale across staff.

• Email authentication and user management

  Email-based sign-in with admin-managed user provisioning so schools control exactly who can log in and what they can see.

• Multi-step approval workflow system

  Documents move through configurable approval chains with clear status, named approvers, and a full audit trail — no more chasing approvals by email.

• Role-based access for administrators, teachers, and department heads

  Each role sees only the documents and actions relevant to them, while department heads see everything inside their area.

• Searchable document archive with full-text search

  Full-text search across years of documents, returning hits in seconds where shared-drive searches used to take hours.

• Template-based document creation engine

  Schools start every document from an approved template — lesson plans, compliance reports, communications — keeping format consistent and reducing rework.

• 100%

  Digital approval workflows replacing email-based chains - with full audit trail and version history

• Zero

  Document version conflicts reported after migration from shared drives to the structured platform

• 5 months

  From discovery to production deployment, aligned with the school term calendar for smooth rollout

• 70%

  Reduction in time spent searching for and retrieving documents, based on user feedback after first term of usage

1. 1
   Step 1 / 4

   Visited the school to understand document workflows from creation through approval to archiving. Mapped the complete lifecycle of different document types - lesson plans, compliance reports, policy documents - and identified where paper-based processes created the most pain.

2. 2
   Step 2 / 4

   Designed interfaces for non-technical educators. Large clear actions, familiar patterns that mirror email and Word workflows, and visual approval status indicators that make it obvious where every document stands without training.

3. 3
   Step 3 / 4

   Built the document engine with template management, collaborative editing, approval workflows, and full-text search. Structured the data model around school hierarchies - terms, departments, document categories - so the system matched how schools naturally organize information.

4. 4
   Step 4 / 4

   Deployed during a term break to allow migration of existing documents. Conducted hands-on training sessions with administrative staff, teachers, and department heads. Monitored adoption during the first term and resolved usability issues in real time.