Practice guide
How microschools document learning progress for project-based work so parents can see it
Parents at a project-based school are not really asking what their child made. They are asking whether their child is learning, and how you know. Here is a way to answer that every week without documentation becoming a second job.
Written by the Pearspark team · pricing verified August 2026 · updated · about 10 minutes
In short
Keep three separate records rather than one pile of finished work: what the child can now do, written as a skill and rated from the most recent evidence; how they worked, marked on its own scale so effort never hides achievement; and dated evidence — a photo, a two-line observation, a rubric with a sentence per criterion. Parents can read that. A folder of photographs, however good the projects were, leaves them guessing.
The question the documentation has to answer
A photograph of a finished tiny house tells a parent what their child did. It does not tell them what their child learned, and that is the thing they are quietly worried about. The question underneath most parent questions at a project-based school is: would my child be behind if we went back to a normal school? Documentation that never answers it leaves the parent to guess — and a guessing parent eventually asks for letter grades, which is usually the wrong fix for a real problem.
So write the claim, not only the evidence. "Applied area and scale to a floor plan, and measured to the nearest quarter inch without help" is a claim about a child. The photograph is what makes it believable. Most schools that feel behind on documentation have plenty of evidence and no claims: hundreds of pictures, no sentence anybody could put on a report card.
The other half is keeping the parts of a project apart. A project contains achievement, effort and improvement at once, which makes a single project grade the least interpretable mark a school can give. Thomas Guskey calls the result a hodgepodge grade — as confounded as one "physical condition" score combining height, weight, diet and exercise — and the standard fix is to report product, process and progress separately rather than to average them into a number nobody can decode.
Eight practices that keep it honest without a second job
Roughly in the order they happen. Where Pearspark does the thing we say so, and where it does not we say that too.
- Name the learning before the project starts. Gold Standard PBL asks for learning goals that pair standards-based content with success skills — critical thinking, collaboration, self-management — and the naming is what makes documentation possible later. In Pearspark the school writes its own list: a standards catalog built by hand or imported from CSV, in whatever shape you use (state, classical, Montessori, homegrown). There is deliberately no built-in standards database, so nothing arrives pre-filled. A lesson is tagged with what it teaches, an assignment with what it assesses, and the coverage report then shows each skill as taught, assessed and mastered — with the untouched ones highlighted, which is the report you actually want in March.
- Rate the skill, not the project. A project is an occasion for evidence; the record should be per skill, so that a child who struggled in October and did it unaided in March reads as having learned it. Pearspark derives current mastery from the rating history — latest evidence wins by default, best-ever if a class prefers it, never an average — and the family sees the same map in the portal, labelled "Most recent level — newer work replaces older ratings" so nobody mistakes it for a running score.
- Score with a rubric, and write one sentence per row. The rubric is the honest version of "this is worth more than that": criteria are the rows, performance levels the shared columns, a row that counts double carries a weight. Families see the breakdown on the assignment — the level picked for each criterion, the descriptor, and the teacher's comment for that row — with unmarked rows shown as unmarked rather than hidden. Two things to know: rubrics ship off and are switched on in Settings, and outside a rubric there is nowhere to write a comment on one piece of work. A plain score has no comment field anywhere in the product.
- Keep a running observation log, one line at a time. This is the Reggio-descended practice Project Zero calls making learning visible, and it is the only documentation habit that survives a busy term, because each entry costs about twenty seconds. In Pearspark an observation is a child, what you saw, an optional curriculum area and an optional photo, filed at the time it happened; on a phone it is two taps from the classroom floor. The list of children nobody has observed in five days is on the same screen, which is the part that keeps coverage even. Limits worth knowing: one photo per note, tagged by curriculum area rather than by standard, and sharing with the family is a per-note choice that starts off.
- Document the revision, not only the product. Critique and revision is one of the seven essential design elements, and it is where the learning is most visible and least photographed. Note the first attempt when it happens: Pearspark keeps no history of an earlier rating or score, so a re-rating replaces the old one silently. If the growth is the story you want to tell in May, it has to have been written down in October — an observation is the place for it.
- Mark habits separately, on the school's own scale. Diligence, listening, finishing what you start: named by the school, marked per grading period, printed in their own section of the report card under whatever heading and scale the school uses. Keeping them off the achievement mark is what lets a teacher say a child worked hard and has not got it yet — the sentence a project-based school most needs to be able to say.
- Close each period with a paragraph about the child. Not per class — per child. Pearspark keeps one narrative per student per grading period, written on the report card screen while you are reading the card, alongside a shorter per-class remark. Standards can print as a checklist matrix instead of letters, so a school with no letter grades still produces a document that reads as a report card. The honest gap: there is no separate mid-term progress report. The grading period is the unit, so a school that wants monthly news either sets shorter periods or leans on shared observations between cards.
- Put the work itself where families can see it, and be clear that a school system is not that place. Pearspark shows classroom photo moments on a lesson, which families read in their week — caption and image only, never tagged to a student — and a school running the Community feed can post the public product to it, with a warning before a photo reaches a space containing a child whose media release is off. What it does not have is a portfolio: no per-student document store, no student uploads, nowhere for a scanned draft to live. Most schools keep that in Google Drive or Google Classroom, and that is a reasonable answer.
What a parent wants to know, and where the answer lives
The middle column is what any school ought to be able to produce. The right-hand column is Pearspark today, including six things it does not do.
| What the parent is asking | Where the answer should live | In Pearspark today |
|---|---|---|
| Is my child learning what they should? | A named skill list with a level per skill | Yes; your own standards catalog, mastery per skill, visible per class in the portal |
| How do you know? | The assessed piece of work and the criteria behind the judgement | Yes; a rubric breakdown per criterion with the teacher's sentence on each row (module ships off) |
| What did they actually make? | The artifact itself, kept somewhere durable | No; no per-student document store and no student uploads — the work lives in a drive |
| Can I see the work in progress? | Photos of the room and the process | Partly; photo moments on a lesson (never student-tagged) and one photo per observation, shared per note |
| Was there feedback on this piece? | A written comment attached to the work | Only through a rubric criterion; a plain score carries no comment field |
| Did they improve? | The earlier attempt beside the later one | No history is kept; a re-rating replaces the old one, so write the first attempt down as an observation |
| How did they work, not just how did they do? | Effort and habits reported apart from achievement | Yes; work habits on the school's own scale, posted per period, their own section on the card |
| What does my child say about it? | A student reflection in their own words | No; students can tick off tasks and flag a struggle, and that is all — no reflection field, no uploads |
| What does the teacher think, in writing? | A narrative each grading period | Yes; one narrative per student per period, plus a per-class remark |
| What about between report cards? | A shorter, lighter cadence | No mid-term progress report; shared observations are the between-cards channel |
| Would my child be behind if we left? | A transcript and a records packet | Yes; posted grades print as a conventional transcript and a records packet |
Three records, not one
The practical shape of all this is three records kept side by side, each answering a different question, each on its own scale.
The claim: what the child can now do, written as a skill and rated from the most recent evidence. The habits: how they worked, marked separately so that effort never quietly inflates achievement and a hard-working child who has not got it yet is described accurately. The evidence: dated notes, photos and rubric rows that make the first two believable and that let anybody — a new teacher, a skeptical grandparent, a receiving registrar — see how the judgement was reached.
Guskey and Bailey's product, process and progress criteria are the same three seen from the grading side, and the reason to keep them apart is not tidiness. It is that a parent can act on them separately. "She has the fractions and she is not finishing" leads to one conversation at home; "B minus" leads to none.
A rhythm that survives October
What this costs, honestly, at a school of thirty or forty children.
- During the work session: three or four observations, twenty seconds each, on the children you actually watched today. Not the whole roster — the whole roster over two weeks.
- End of the week: check who has not been observed in five days and start there on Monday. Publish the week to families, and post any photo moments with it.
- End of a project: rate the skills it evidenced, score the rubric with a sentence on each row, and note one thing the child revised. Ten minutes a child, once, rather than a running commentary.
- End of the grading period: post mastery, post habits, write the paragraph, print the card. About half an hour a child, and most of it is reading what you already wrote.
Who each system is actually for
Read from our comparison pages, so a correction there corrects this. Two are worth naming here: Transparent Classroom does Montessori lesson tracking and a parent window better than we do and costs less, and Google Classroom holds the work itself, which we do not hold at all. A project-based school running Classroom for artifacts and a school system for the record is a normal, sensible arrangement.
- NavEd
- Microschools, co-ops and hybrid programs that want a gradebook, attendance, transcripts and a parent portal at the lowest published price, and don't need a lending library, equipment booking, volunteer check-in or records escrow.
- SchoolCues
- Small schools whose hardest job is reaching families — newsletters, yearbooks, alumni, conference scheduling, and texting they never have to count — and who don't mind asking for a quote rather than reading a rate off a page.
- QuickSchools
- Schools of 40 students and up that want a conventional SIS at the lowest published per-student rate and don't mind that report cards and the parent portal sit one tier up.
- Skooly
- Enrichment, tutoring and activity-based programs whose job is scheduling, bookings, attendance and billing rather than a permanent academic record — no report cards, no transcripts.
- Gradelink
- Private schools of 75–400 students that want a mature, widely used SIS.
- FACTS SIS (formerly RenWeb)
- Established private schools of 200+ students with dedicated admin staff, need-assessed financial aid, and enterprise tuition finance.
- Blackbaud K-12 Solutions
- Established independent schools with a development office, an audited general ledger and enough staff to run an implementation — the size of school Blackbaud has served for forty years.
- Sycamore School
- Independent schools of 100–400 students that want per-student pricing and integrated payments.
- TeacherEase
- Schools focused on standards-based grading with a handful of teachers, especially where per-teacher pricing beats per-student.
- Alma SIS
- Independent and charter schools of 150+ students that want a modern SIS and don't mind quote-based buying.
- Google Classroom
- Distributing and collecting classwork, especially if your school already lives in Google Workspace.
- ThinkWave
- Schools on the tightest budgets that mainly need academics: gradebook, report cards, transcripts.
- Jupiter Ed
- Schools that want a powerful teacher gradebook with LMS features and don't need operations modules.
- Transparent Classroom
- Montessori programs whose core need is tracking lessons presented and mastered, Montessori-style.
- Procare Solutions
- Child care centers, preschools and Head Start programs staying early-childhood — ratios, subsidies, meals and daily reports, with no graded class on the way.
- CohortLedger
- An ESA-funded microschool or learning pod in one of its nine states whose back-office pain is the quarterly disbursement cycle, and whose academic records live somewhere else.
- Spreadsheets & the DIY stack
- A new school's first semester with fewer than about ten students, before records, billing and parent access all need the same source of truth.
The parts of Pearspark involved
Each page says what the feature does today and what it does not.
Watch the loop
Logging an observation, sharing it, rating skills on a piece of work, posting mastery and habits at term end, and what the parent sees. A minute each.
Common questions
What are effective ways for microschools to document learning progress for project-based work so it is clear to parents?
Keep three records rather than one. First, the claim: what the child can now do, written as a named skill and rated from the most recent evidence, so growth reads as growth. Second, the habits: effort, collaboration and self-management marked on their own scale, never blended into the achievement mark. Third, the evidence: dated observations, photos and a rubric with a sentence per criterion, gathered a few minutes at a time rather than in a documentation week nobody has. Then close each grading period with a paragraph about the child.
How do you grade a project without a test?
With a rubric, and by rating skills rather than the project. The rubric names what is being judged (the rows), the levels of quality (the columns), and what counts double; the teacher picks a level per row and writes a sentence saying why. The skills the project evidenced get rated separately, so the record survives the project: next term's evidence updates the same skill instead of adding another orphaned grade.
What should a project portfolio contain?
The starting point, two or three pieces of process evidence, the feedback the child received and what they changed, the finished product, and a short reflection. The revision is the part most often missing and the part that shows most learning. Keep it somewhere durable and school-owned — a shared drive or Google Classroom — rather than on the teacher's phone, and remember that a portfolio explains a record; it does not replace one.
How often should a project-based school report to parents?
Little and often for evidence, formally each grading period for judgements. A shared observation once a week or so per child keeps a parent oriented at almost no cost, and the report card carries the claims: skill levels, habit marks and a narrative. Schools that report only twice a year are the ones whose parents ask for letter grades, because twice a year is not enough to build trust in an unfamiliar system.
Does Pearspark store a portfolio of student work?
No. There is no per-student document store and no student uploads, so the artifacts themselves have nowhere to live in Pearspark. Files can attach to an application, a health record or a service plan, and that is all. Photos exist in two narrower forms: photo moments on a lesson, which are never tagged to a student, and one optional photo on an observation, which only that child's family can see. If keeping the work matters more to you than keeping the record, buy something else for that half — most schools use Google Classroom or a shared drive.
Can students document their own learning in Pearspark?
Barely, and it is worth knowing before you plan around it. A student with a login can see their week, tick off the tasks on it and flag one they got stuck on with a note — which does reach the teacher. There is no reflection field, no journal and no way for a student to upload anything. Student-written reflection, which is one of the strongest documentation practices there is, has to live in whatever tool holds the work.
How do you show a parent that their child has improved?
By rating the same named skills repeatedly and letting the latest evidence replace the earlier rating, which is what standards-based mastery is for: a child who could not do it in October and can in March reads as having learned it, instead of averaging out to a middling grade. The catch in Pearspark is that the earlier rating is not kept — the new one replaces it — so if the before-and-after is the story, write the before down as an observation at the time.
Do project-based schools still need report cards and transcripts?
Yes, and the flexible teaching is exactly why. A family that transfers out, a scholarship or ESA program, and any receiving registrar all read conventional documents; a portfolio does not tell them which grade the child goes into. Keep the projects and keep a standard record of them — skills, marks, credits at high-school age, attendance — so that leaving is a printing job rather than a reconstruction.
Sources
Vendor pricing is read from each vendor's own published pages and re-verified quarterly; last checked August 2026. Where a vendor doesn't publish a price, this guide says so rather than estimating one.
- PBLWorks (Buck Institute for Education): Gold Standard PBL, the seven essential project design elements
- PBLWorks: Gold Standard project based teaching practices, including assessing student learning
- Thomas R. Guskey, "Five Obstacles to Grading Reform" (ASCD) — on hodgepodge grades and reporting product, process and progress separately
- Harvard Project Zero: Making Learning Visible — documentation as a tool for assessing individual and group learning
The full comparison behind each row
Each one is sourced feature by feature, last reviewed August 2026, and says plainly where the other system is the better choice.
See it before you decide
Every task is on video — one minute each — and your first 30 days are free. No sales call.