Education providers · Universities · Public institutions

Education and software for public-sector clients.

Which assignment fits Extraara? What can you review today, and what do we clarify before commissioning? This overview brings together subject specialists, IT and procurement.

Three possible assignments. Clear outcomes.

Education & teaching

Teaching in programming, databases, software testing and networking fundamentals, with learning materials and workshops.

Agreed deliverables: An agreed teaching plan, sessions and materials. Learning objectives, prior knowledge, format and usage rights belong in the service specification.

Education with a learning example

Software development

Apps, web applications and interfaces for a specific workflow, including further development of existing software.

Agreed deliverables: A defined functional scope with test criteria, documentation and handover. Operation, maintenance and code rights are specified separately in the proposal.

Development with a product example

ExtraProof

Connect documented writing processes to a specific text version and verify Creation Records.

Use today: Verify is publicly available in the browser. Use of writing environments within an institution is agreed as a pilot; this is not blanket approval for routine operation.

ExtraProof for public institutions

ExtraProof

What you can check now.

A Creation Record documents observed events. It is not proof of the writer’s identity or the independent completion of an assessment. This distinction belongs in every deployment plan.

Try a sample record

Ready to use: Verify: check a record and its associated file locally in the browser, without an account or file upload.
Institutional use: A pilot by agreement. Availability and verification status differ between macOS, Windows, Word and Moodle. Current status by environment.

What is agreed before commissioning.

These points form the basis of the proposal and joint review. The evidence required depends on your procurement process and the agreed use.

Scope & acceptance: Desired outcome, deliverables, test procedures and acceptance criteria. Who on your side reviews the work and makes decisions.
Price & schedule: A proposal for the defined scope, milestones and payment terms. Ongoing costs for operation, maintenance or licences are listed separately.
Privacy & operation: Data types, responsibilities, storage locations, deletion and subcontractors for the specific solution. Where required, a data processing agreement before use.
Accessibility: Relevant interfaces and documents, applicable standards, and manual and automated checks. Known limitations belong in the assessment.
Handover & support: Documentation, access, usage rights, responsibilities and agreed response times. Development does not automatically include a support contract.
Procurement & invoicing: Tender documents, deadlines, qualification evidence and the required invoice format. We need these requirements when reviewing a proposal.

The next step

Send us your brief.

A short description is enough for an initial assessment. Include your institution, audience, desired outcome and timeframe. If tender documents, a budget or specific operational requirements already exist, we include them in the review.

Enquire about a project