co-teachers and co-authoring in pear assessment

Co-Teachers, Sharing & Co-Authoring in Pear Assessment

Modern school teaching is a team sport played, too often, on solo software accounts. Co-teachers and co-authoring in Pear Assessment close that gap: co-teachers share a class — its roster, assignments, and results — while co-authoring lets colleagues build the same assessment draft together instead of emailing versions back and forth. Both sit in the platform’s premium collaboration family, and both repay a little setup thought, because sharing done carelessly creates the exact confusion it was meant to end.

This guide covers adding a co-teacher, sharing a draft for joint editing, the real difference between sharing and co-authoring, and the troubleshooting for the classic complaint every team eventually hits: “I shared it, but my colleague can’t find it.”

how do i add a co teacher to my pear assessment class

Adding a co-teacher happens at the class level: open the class, find its teacher/members management, and invite the colleague by their school account email; once they accept, the class — and the assignments and results attached to it — appears in their account too, with the co-teacher able to work with the class’s assessments and students according to the role’s permissions.

Do the human setup before the digital one. Agree on who owns what: who assigns, who grades constructed responses, who communicates results to families. Co-teaching on a shared class goes wrong socially before it goes wrong technically — two teachers releasing scores on different schedules, or both assuming the other graded the essays.

A two-sentence norms note in a shared doc (“Maria assigns and releases; James grades writing; both can redirect attempts”) prevents a semester of small frictions. Revisit it at the term’s first co-planning session, because roles drift as units change hands, and the note should describe the team you are now, not the one you were in September. Co-teacher access is also how interventionists and special education colleagues get legitimate, auditable windows into the classes they support — vastly preferable to the shared-password habits it replaces. Teachers new to the platform’s class structures will find the vendor’s getting started guide a useful orientation to how classes and groups are organized.

Two co-teachers in Pear Assessment editing the same assessment draft side by side on laptops

how can i share an assessment draft with another teacher for joint editing

Sharing an assessment for joint editing means handing a colleague access to the draft itself — the living document — rather than a copy. In Pear Assessment’s sharing model, you share the assessment with specific colleagues (or place it in a shared school/district library), and collaborators with editing access open the same draft, add and revise items, and see each other’s work in one canonical version.

Working norms make co-authoring productive instead of chaotic. Divide by strength, not by halves: one teacher drafts items, a second vets them against the standards, a third reviews for bias, clarity, and reading load. Comment or initial your significant edits in the item notes where your workflow allows, so decisions stay auditable (“changed distractor B after PLC review”). And set a freeze moment: joint editing ends at an agreed time, after which one named owner makes final calls — assessments that are edited until the bell are assessments nobody fully vetted.

For department common assessments, co-authoring is the feature that changes the politics as much as the logistics: when everyone literally built the test, nobody’s class was ambushed by it, and the post-test analysis meeting starts from shared ownership instead of quiet blame. It belongs to the premium collaboration family mapped in our premium features guide.

what is the difference between sharing an assessment and co authoring in pear assessment

The distinction is ownership of the object. Sharing gives a colleague access to use an assessment — to view it, assign it to their own classes, and often to copy it into their library and adapt their copy. The original remains yours; their teaching runs on their instance; changes they make do not flow back into yours. Sharing answers “can you use my test?”

Co-authoring makes the draft jointly owned: multiple teachers edit the same assessment, and every edit is an edit to the one shared object that all of you will assign from. Co-authoring answers “shall we build this test together?” Choose sharing when a finished product should travel (a strong unit test offered to the department); choose co-authoring when the product does not exist yet and its quality depends on several minds. Confusing the two causes the classic mishaps: expecting a shared copy’s fixes to appear in the original (they will not), or co-authoring a test that three teachers then assign at three different stages of unfinished. Name the mode when you send the invite: “I’m sharing this for your classes” or “I’m adding you as co-author — edits are live for everyone.”

Teacher sharing an assessment draft with a colleague for joint editing with co-teachers in Pear Assessment

i shared an assessment but my colleague can’t find it in pear assessment

Work the usual suspects in order; one of them is almost always guilty.

Wrong library view. Shared items live in shared/school library areas and “shared with me” style views, not in the colleague’s personal library list. Have them check the library filters and the school/district collections before concluding anything is missing.

Wrong account. The share went to their school email while they are signed in with a personal account (or vice versa) — the single most common cause, and the reason to always share to the exact address the colleague uses for the platform.

Scope mismatch. An item shared at school level is invisible to a colleague at another school in the district, and district-level placement works the other way; confirm which collection received it.

Draft state and permissions. A view-only share cannot be edited, and a draft shared before it was saved or published to the shared space may simply not be where you think it is; re-open your copy, confirm its location and sharing settings, and re-share deliberately.

Class versus item. Finally, confirm you shared what you meant to: sharing a class (co-teacher) and sharing an assessment are different doors, and colleagues regularly wait at the wrong one.

If none of these resolves it, your school’s platform admin can see sharing at the organizational level — bring them the assessment name, the address you shared to, and the date; that trio makes the support conversation short.

Sharing culture: the etiquette that scales

Teams that share well adopt three habits. Name things for strangers: “Grade 7 — Unit 3 Fractions Final (2026, PLC-approved)” finds itself; “test copy final FINAL” does not. Curate the shared library seasonally: one short meeting a term to archive the stale and promote the proven keeps the school collection a resource rather than a junk drawer. Credit authors in the title or notes: shared libraries run on generosity, and generosity runs on being seen. And when your sharing involves the class structures themselves — groups spanning rosters and teachers — our guide to custom groups in Pear Assessment picks up where this one leaves off. Teachers syncing classes externally may also want our walkthrough of Pear Assessment for Google Classroom.

Teacher team planning together in a PLC built around co-authoring in Pear Assessment

A PLC workflow built on co-authoring

Here is what mature use looks like across one unit. Week zero: the PLC’s co-authored draft opens with last year’s test as the skeleton; each member claims the standards they taught deepest and drafts those items. Week one: a vetting rotation — every item is solved and challenged by someone who did not write it, in the shared draft, with fixes made live. Test week: all sections assign the same canonical assessment; co-teachers watch their shared boards. Grading week: constructed responses are divided by question across the whole team (calibration is automatic when three teachers score the same prompt against one rubric). Analysis meeting: the team reads one shared question analysis, names the reteach, and — the step everyone skips — edits the canonical draft with the fixes while the evidence is fresh, so next year’s test is born improved.

Notice what never happens in that workflow: no attachments, no “final_v3” files, no teacher discovering mid-test that their copy differs. The shared draft is the process.

Permissions and student data: the serious paragraph

Sharing widens access, and access to student data carries obligations. Add co-teachers who genuinely serve the class — co-instructors, interventionists, case managers — and remove access when roles change, at term boundaries at the latest. Share assessments generously (items are not sensitive), and share results narrowly (they are). Never export or screenshot shared-class data into personal accounts or drives to “work on it at home”; the shared platform is the auditable home the data is entitled to. These are not platform rules so much as professional ones, but collaboration tools test them precisely because they make sharing effortless. Effortless is good; thoughtless is not. A department that pairs its co-authoring norms with a one-line data norm — “student data stays in the platform, access follows the roster” — gets the benefits of both.

Two teachers reviewing one quiz question together while co-authoring in Pear Assessment

FAQ

Can a co-teacher see grades and reports for the class?
Yes — that visibility is the point of the role: co-teachers work with the shared class’s assignments and results so every adult serving those students reads the same evidence at the same time, in meetings and in the moment alike.

Does co-authoring require a premium plan?
The collaboration family — co-teachers and draft co-authoring — sits in premium packaging. Basic sharing options vary by plan and school setup; check your institution’s plan for exactly which doors are open.

We keep stepping on each other’s edits in a shared draft. Any fix?
Process, not technology: claim sections visibly (a quick message — “I’m in items 1–10 until 3 p.m.”), avoid simultaneous editing of the same item, and let the freeze-and-owner rule end every cycle. Teams also benefit from a standing rule that the person who teaches a standard last has final say on its items; most co-authoring collisions are really undecided authority wearing a technical disguise.

Can I unshare or remove a co-teacher later?
Yes. Sharing and co-teacher access are revocable from the same management screens where they were granted — sensible when staffing changes each term. Build a start-of-term access review into your routine so yesterday’s rosters do not linger into next year.

Conclusion

Co-teachers and co-authoring in Pear Assessment turn assessment from a solo craft into the team practice it should be: shared classes with clear norms, jointly built drafts with one canonical version, and sharing used deliberately — for travel or for construction, named as such. Master the two modes and the find-it troubleshooting, and your department’s collective library becomes what shared drives always promised and never delivered: one place, current versions, everyone’s best work. Start small — one co-taught class, one co-authored unit test — and let a single clean collaboration convert the skeptics that no feature list ever could.

Leave a Comment

Your email address will not be published. Required fields are marked *


Math Captcha
3 × 1 =


Scroll to Top