How it works

Six stages from source titles to an approved release

CoPressAI follows the way publishing teams already work. People with the right role approve each stage, and the AI only ever drafts and suggests.

  1. Knowledge curator

    Upload your sources

    Add authorised titles. CoPressAI extracts explanations, worked examples and questions, and maps them to the curriculum with their permissions attached.

    • Uploads are extracted into complete teaching units with a link to the source page.
    • Each unit is mapped to curriculum objectives with a confidence level.
    • A curator approves the material, and source permissions control what it may be used for.
    Learn more →
  2. Editor

    Approve the book plan

    Review chapters, objectives, question counts and page estimates. Missing or duplicated coverage is flagged before anything is drafted.

    • The plan lists chapters, subchapters, outcomes, question counts and page estimates.
    • Coverage gaps, duplication and unsupported claims are shown before approval.
    • The approved plan is versioned and records who approved it and when.
    Learn more →
  3. Editor

    Authorise and generate

    See how many credits a job needs, set a limit and generate chapter by chapter, with honest progress for each stage.

    • Choose chapters and see how many credits the job needs.
    • Set one "authorise up to" credit limit; jobs pause rather than go over it.
    • Progress shows the real stage: retrieving, drafting, checking, waiting for review.
    Learn more →
  4. CoPressAI

    Compute and check

    Answers are verified against a structured specification. The draft is checked for errors, coverage gaps and content in the wrong edition.

    • Answers are verified against a structured specification and approved sources.
    • An independent review checks that each question leads to its expected answer.
    • Checks flag coverage gaps, house-style issues and teacher content in a pupil edition.
    Learn more →
  5. Editor and reviewer

    Edit and resolve

    Accept or reject suggested changes, resolve issues in review rounds and see your pages laid out as you go.

    • AI changes arrive as suggestions with sources and affected items.
    • Reviewers comment in rounds; editors resolve issues against exact blocks.
    • Every save is a revision; restoring a version never loses later work.
    Learn more →
  6. Chief editor and designer

    Proof and release

    Export IDML to InDesign for the final proof, then approve and lock a versioned release.

    • Page previews show fit estimates and raise overflow early.
    • IDML exports to your InDesign templates for the designer’s final proof.
    • The chief editor approves and locks a release with a manifest of every revision.
    Learn more →
Roles

Who does what

Permissions follow the people already in your editorial process.

RoleResponsibilities
Tenant adminInvites users, assigns roles and manages credits.
Knowledge curatorUploads sources, reviews extraction and approves material for use.
EditorCreates books, approves plans, authorises generation and edits manuscripts.
ReviewerComments on chapters and checks subject accuracy in review rounds.
Chief editorReviews the whole publication set and approves the final release.
DesignerOpens the IDML export in InDesign and returns the final proof.

CoPressAI is in its pilot phase with selected publishers. Features are released to pilot workspaces in stages; your demo shows exactly what is available today.

Start your pilot with 20 000 free credits

Each verified publisher gets 20 000 platform credits to plan a book and generate a sample lesson in a private workspace.

  • See the credits each AI job needs and set your own limit
  • Editing by hand never uses credits
  • Your work is kept when credits run out