Learning path · Level 5 · Tutorial 4

Triaging Email and Drafting Replies for Review

Create a manual email triage and drafting routine using selected, sanitized message excerpts. Categorize messages, draft context-aware replies, and keep sending under human control without connecting an assistant to a live mailbox.

  • Level: Intermediate
  • Duration: 16 min
  • 7 steps
Start tutorial Back to the path
Triaging Email and Drafting Replies for Review

What you will go through

  1. Classify the Response Needed Classify a selected email excerpt by the action needed next while keeping the assistant and manual sending under human control. 2 min
  2. Set Priority Separately Rank messages using deadlines and consequences without confusing priority with the response category. 2 min
  3. Establish the Current Thread State 2 min
  4. Build a Minimum Sufficient Excerpt Prepare a permitted, privacy-conscious excerpt that preserves the current request and relevant context without sharing an entire email thread. 2 min
  5. Specify the Reply Before Drafting Turn a sanitized thread state into a precise assistant request that supports a useful draft without inventing commitments. 2 min
  6. Review the Draft and Assign Its Status Review a proposed reply for recipient scope, supported commitments, internal information, and the correct draft-review status before manual sending. 3 min
  7. Apply the Complete Manual Routine Apply the complete manual email routine to a fresh fictional mini-inbox, correct an unsupported draft, and retain human control through manual sending. 4 min

What you will learn

  • Define clear triage categories and separate message priority from the type of response required.
  • Select a privacy-conscious excerpt that preserves the latest request and relevant prior commitments.
  • Request a reply with explicit tone constraints, approved facts, and unresolved details marked for confirmation.
  • Review the recipient, commitments, factual details, and sensitive information before approving a draft for manual sending.

Before you start

  • Building and Refining a Task Prompt
  • Writing and Summarizing Without Changing Meaning
  • Applying Basic AI Safety Checks

Step 1 of 7

Classify the Response Needed

Classify a selected email excerpt by the action needed next while keeping the assistant and manual sending under human control.

Use categories for the next action

Keep triage manual

Use an assistant only with a selected excerpt you are permitted to share. It can suggest a category, but it does not connect to a mailbox, move messages, or send anything.

You remain responsible for choosing one primary next action for each message. A category describes that action—not the sender’s seniority or how urgent the message may feel. Urgency is assessed separately later.

A human-controlled triage flow

A selected email excerpt goes to an assistant for a suggestion, then a person chooses an action while keeping sending under human control.

The assistant may suggest; a person selects the next action and keeps manual sending separate.

Tip

Decision rule

Choose the category that removes the current blocker. If a client asks for a decision that only an internal approver can authorize, route it for review first—even if you may later send a limited acknowledgement.

Identify the blocker before responding

Four categories

There are exactly four response categories. Use the evidence in the message and the information currently approved for communication.

Category guide

Choose the category that describes what must happen next.

Categories identify the primary next action, not priority.
CategoryUse it whenPrimary next action
ReplyApproved information supports an answer.Send a bounded response after human review.
ClarifyThe requester must provide a missing detail.Ask for the needed information.
Route for reviewAn internal decision, authorization, or specialist judgment is needed.Ask the appropriate internal person to decide.
No reply neededNo response is requested or necessary.Record or read the message; do not reply.

Example

Worked example

At 14 May 2026, 09:00 UTC, Alex at Harbor Works asks Maya for final files by 15 May 2026, 12:00 UTC and printing at no extra cost. Maya has committed only to sending a proof by 14 May 2026, 16:00 UTC.

The primary category is Route for review. Accelerated final delivery and free printing require Priya’s confirmation. The fact that Maya can acknowledge the request later does not turn the internal decision into an approved reply.

Apply the four categories

Practice: classify the action needed

Match each fictional message to its single primary response category.

Choose the primary next action

Match each message with the appropriate response category.

Tap an item and then its matching pair.

Step 2 of 7

Set Priority Separately

Rank messages using deadlines and consequences without confusing priority with the response category.

Priority answers a different question

Separate action from urgency

At the assessment time of 14 May 2026, 09:00 UTC, make two separate decisions for each message:

  • Category asks: “What is the next action?”
  • Priority asks: “How soon does attention matter, and what happens if it waits?”

A message can need a Reply without being High. Equally, a system notice can need No reply needed while still being High because work will be blocked. Do not let the sender, subject line, or category substitute for evidence about time and consequences.

Two decisions from one message

A message branches into an urgency path with time and consequence cues and a separate next-action path.

Use the time-and-consequence path to set priority; use the next-action path to select the response category.

Use a stated rubric and record the reason

Priority rubric

Apply the same rubric consistently. The evidence must be in the message: a deadline, an active blocker, or a stated consequence. Do not invent urgency from a vague request.

Priority is based on evidence at 14 May 2026, 09:00 UTC.
PriorityUse whenEvidence to record
HighAn imminent hard deadline or active work blocker has a stated consequenceTime and what will be blocked or lost
NormalAction is required, but the evidence does not show that urgencyRequested action and any known date
LowNo time-sensitive action or consequence is statedAbsence of requested action, timing, and consequence

Example

Evidence-based triage records

Record 1
Message: System notice — “At 14 May 2026, 10:30 UTC, the shared drive will become read-only; active uploads will stop.”
Category: No reply needed
Priority: High
Reason: An imminent stated interruption will block active work, even though nobody needs an email response.

Record 2
Message: Dana — “Please confirm attendance for the planning session.”
Category: Reply
Priority: Normal
Reason: A response is required, but no deadline or consequence is stated.

When timing or consequences are missing, say so in the Reason. Missing evidence is not proof that the message is Low.

Practice: rank the inbox

Rank by deadline and consequence

Put these messages in priority order, from highest to lowest, using the assessment time of 14 May 2026, 09:00 UTC.

  1. System notice: At 14 May 2026, 11:00 UTC, the proof server will pause unless the job queue is cleared. The Harbor launch proof will stop processing.
  2. Finance: Please provide a cost centre for May materials by 20 May 2026, 16:00 UTC.
  3. Community bulletin: The cafeteria menu was updated. No response or action is requested.

Keep category and priority separate

Classify the urgent notice

For the System notice in the previous screen, which Category–Priority pairing is justified?

Step 3 of 7

Establish the Current Thread State

Read a thread as a current state

Three parts of the current state

Before drafting anything, reduce a thread to its current state:

  • Latest request — what the sender is asking for now.
  • Existing commitments — promises that were actually made and still matter.
  • Unresolved questions — points that still need an answer, decision, or authorization.

Read the sender and sent date on each message. Quoted email blocks can make an older message look prominent, but the visible layout is not proof of sequence.

A newer request can replace or refine what someone wants. It does not automatically create a new commitment from the recipient.

From thread to current state

A dated stack of email cards being sorted into current request, existing promise, and unresolved question compartments.

Use the messages' senders and dates to sort evidence into the three parts of the current state.

Separate requests, commitments, and open decisions

Example

Worked thread: Harbor launch pack

At 14 May 2026, 09:00 UTC, Maya sees this Harbor launch pack thread. It is displayed newest first:

Alex — sent 14 May 2026, 08:45 UTC
“Please send the final files by 15 May 2026, 12:00 UTC. Can you include printing at no extra cost?”

Maya — sent 13 May 2026, 15:30 UTC
“I will send a proof by 14 May 2026, 16:00 UTC.”

Alex — sent 13 May 2026, 09:10 UTC
“Could the final files be ready this week?”

Project approval context: Priya is the internal approver for delivery and pricing. Neither accelerated final delivery nor free printing has been approved.

Build the record from evidence

Keep the newer, specific request. Retain Maya’s earlier proof commitment because it remains relevant. Do not convert Alex’s requested date or price into a promise.

Thread-state record

A compact record separates what Alex asks for from what Maya has committed to and what Priya must still confirm.

Current state of the Harbor launch pack thread
Thread-state headingRecordSupporting context
Latest requestFinal files by 15 May 2026, 12:00 UTC; printing at no extra costAlex — sent 14 May 2026, 08:45 UTC
Existing commitmentsSend a proof by 14 May 2026, 16:00 UTCMaya — sent 13 May 2026, 15:30 UTC
Unresolved questionsWhether final delivery can meet Alex’s requested time; whether printing can be freeAlex — sent 14 May 2026, 08:45 UTC; Priya confirmation is required

Apply the thread-state record

Practice: Complete the current state

Using the Harbor launch pack thread and approval context from the previous screen, write the compact thread-state record.

Use these headings exactly: Latest request, Existing commitments, and Unresolved questions. Do not turn Alex’s requested final-delivery date or free printing into an approved commitment.

Write at least 120 characters (0/120).

Step 4 of 7

Build a Minimum Sufficient Excerpt

Prepare a permitted, privacy-conscious excerpt that preserves the current request and relevant context without sharing an entire email thread.

Keep enough context

Keep the state, not the whole thread

A minimum sufficient excerpt is not simply the shortest possible text. It is the smallest permitted selection that still lets an assistant understand the current situation.

Keep the latest request, relevant existing commitments, timing, qualifications, and the roles needed to interpret an unresolved issue. Remove material that does not change the next response.

The assistant sees only the excerpt you deliberately provide. It does not need—and should not receive—a live mailbox or an entire thread.

How an excerpt preserves meaning

A diagram showing a long email thread filtered into a short excerpt that retains the request, timing, commitment, and approval context.

Filter for decision-relevant context, not for the fewest possible words.

Redact consistently and lawfully

Apply privacy before sharing

Permission comes before redaction. Check whether workplace policy permits this material to be processed by an assistant at all. Removing an address does not make prohibited content permitted.

When processing is allowed, remove unnecessary addresses, signatures, contact details, unrelated recipients, confidential side discussions, and repeated quoted history. Keep any mapping between real people and placeholders locally; do not include that mapping in the excerpt. If permission is unavailable, use the tutorial's fictional text instead of real email.

Warning

Permission is separate from redaction

Do not paste an original thread merely because it has been shortened. A permitted excerpt still needs a policy check, and it should contain no more personal or confidential information than the task requires.

Example

Example: preserve roles and open questions

A compact fictional excerpt can preserve the thread state without exposing unnecessary details:

Latest request
Alex, client at Harbor Works — sent 14 May 2026, 08:45 UTC: requests final files by 15 May 2026, 12:00 UTC and printing at no extra cost.

Existing commitments
Maya, coordinator at Northstar Studio — sent 13 May 2026, 15:30 UTC: committed to sending a proof by 14 May 2026, 16:00 UTC.

Unresolved questions
Priya is the internal approver for delivery and pricing. Confirmation is still required for accelerated final delivery and free printing.

This excerpt preserves roles, dates, the request, the commitment, and the approval state. It excludes signatures, phone numbers, unrelated recipients, and repeated quoted history. If an address is needed later in a reply package, represent the removed client address as [CLIENT EMAIL].

Verify the excerpt

Check for lost meaning

Before using a sanitized excerpt, what is the most useful final check?

Practice: choose what remains

Select and minimize a fictional excerpt

Assume this fictional source is permitted for assistant use. Choose the candidate that is both privacy-conscious and minimum sufficient. Then name one detail from the source that Candidate A appropriately leaves out.

Fictional source material
Alex, client at Harbor Works — sent 14 May 2026, 08:45 UTC. The sender field also contains [CLIENT EMAIL]. Alex requests final files by 15 May 2026, 12:00 UTC and printing at no extra cost. The signature includes a direct mobile number. An unrelated recipient is copied. A repeated older quotation discusses a color choice.

Maya, coordinator at Northstar Studio — sent 13 May 2026, 15:30 UTC: committed to sending a proof by 14 May 2026, 16:00 UTC.

Priya is the internal approver for delivery and pricing. Accelerated final delivery and free printing still require Priya's confirmation.

Candidate A: Alex's role and sent date; latest request; Maya's role, sent date, and proof commitment; Priya's approval context.

Candidate B: Alex's role and latest request; Maya's proof commitment.

Candidate C: Everything in Candidate A plus [CLIENT EMAIL], the direct mobile number, copied recipient, and repeated color-choice quotation.

Write at least 25 characters (0/25).

Step 5 of 7

Specify the Reply Before Drafting

Turn a sanitized thread state into a precise assistant request that supports a useful draft without inventing commitments.

Define the drafting boundary

From excerpt to a bounded draft

A reply specification is the instruction you give an assistant before it creates a draft. It defines the boundaries of the reply so the assistant can be useful without turning a client request into an unapproved promise.

Include: recipient role, purpose, questions to address, approved facts, tone, length, forbidden commitments, and the requested output format.

The assistant receives a selected excerpt and produces a proposal for review. It does not connect to a mailbox, send a message, or make a business decision.

A flow showing a sanitized excerpt becoming a bounded specification, then a draft for human review before manual sending.

The specification constrains the draft; human review and manual sending remain separate actions.

Separate requests from commitments

Map requests to what can be said

At 14 May 2026, 09:00 UTC, first separate what Alex wants from what Maya is authorized to state.

Latest request
Alex requests final files by 15 May 2026, 12:00 UTC and printing at no extra cost.

Existing commitments
Maya has committed to sending a proof by 14 May 2026, 16:00 UTC.

Unresolved questions
Can final delivery be accelerated? Can printing be provided at no extra cost? Priya must confirm both.

A client request belongs in the draft, but it does not become an approved fact merely because it appears in the excerpt.

Authorization map

Use this mapping when writing the specification.

Each requested answer needs an authorized handling path.
TopicWhat is knownInstruction for the assistant
ProofCommitted for 14 May 2026, 16:00 UTCState this as an approved fact.
Final filesRequested for 15 May 2026, 12:00 UTC; not approvedAcknowledge the request without accepting the date; flag it for confirmation.
PrintingRequested at no extra cost; not approvedAcknowledge the request without accepting the terms; flag them for confirmation.
PriyaInternal approver for delivery and pricingDo not claim Priya has approved anything.

Request a proposal, not an action

Give the assistant precise limits

Use observable constraints, not vague instructions such as “make it professional.” For this case, ask for a calm, courteous, concise body of no more than 120 words. Explicitly forbid unsupported certainty, acceptance of the requested deadline, and acceptance of free printing.

Ask for two outputs: a reply package and separate reviewer notes. Put unresolved details only in reviewer notes with square-bracket confirmation markers. The outgoing body must not present those details as settled.

Example

Example: a complete assistant request

Create a reply package for a client.

Recipient role: Alex, client at Harbor Works
Purpose: acknowledge the request and state the approved proof commitment.
Questions to address: final-file timing and printing at no extra cost.
Approved fact: Maya will send the Harbor launch pack proof by 14 May 2026, 16:00 UTC.
Unresolved: final delivery by 15 May 2026, 12:00 UTC and printing at no extra cost require Priya's confirmation.
Tone and length: calm, courteous, concise; body no more than 120 words.
Forbidden commitments: do not accept the final-delivery date, free printing, or imply Priya has approved either.
Output: To:, Cc:, Subject:, Body:, and separate Reviewer notes:. Use [CLIENT EMAIL] for the removed address. Put unresolved details in reviewer notes with confirmation markers. Create a draft for review only; do not send anything.

Example

Candidate draft produced from the specification

To: [CLIENT EMAIL]
Cc: None
Subject: Harbor launch pack next steps
Body:
Hello Alex,

Thank you for outlining the requested timing and printing option. We will send the Harbor launch pack proof by 14 May 2026, 16:00 UTC. We are checking the final-file timing and printing terms internally and will confirm them after review.

Best,
Maya
Reviewer notes:
[CONFIRM: final delivery date]
[CONFIRM: printing terms]

Write your own bounded specification

Practice: specify the reply

Using the established Harbor launch pack thread state, write a short assistant request for a reply package. Include the approved proof deadline, address both of Alex’s requests, set calm/courteous/concise tone and a 120-word body limit, and forbid acceptance of unapproved delivery or printing terms. Require separate reviewer notes with confirmation markers for the unresolved details. End by making clear that the output is a draft for review, not a sent message.

Write at least 250 characters (0/250).

Step 6 of 7

Review the Draft and Assign Its Status

Review a proposed reply for recipient scope, supported commitments, internal information, and the correct draft-review status before manual sending.

Use a deliberate review sequence

Review before assigning a status

A draft is a proposed outgoing message, not a completed action. Review it in three passes:

  1. Recipient and scope: Does the intended recipient need this reply? Does every copied recipient need the information?
  2. Factual support: Are dates, commitments, quantities, and answers supported by approved facts?
  3. Sendability: Is the tone suitable? Are internal details and confirmation markers outside the outgoing body?

Check actual addresses locally. A display name—and a sanitized placeholder such as [CLIENT EMAIL]—does not verify where the final message will go.

Three review passes

A visual flow showing recipient review, fact checking, and separation of internal notes from an outgoing email.

Review recipient scope, factual support, and sendability before assigning a draft-review status.

Tip

Local check

Use the assistant's draft as material to inspect, not as evidence. Verify recipient details and commitments against approved information and your local email system.

Choose Hold, Revise, or Approved

Status follows the intended scope

The right status depends on the intended reply scope. First ask what this particular reply is meant to accomplish.

  • Hold: an essential fact or authorization is missing for that intended reply.
  • Revise: the problem is understood and can be corrected with approved information; review the changed draft again.
  • Approved for manual sending: a human has reviewed the final intended reply. It has not been sent.

Missing authorization does not always require a Hold. If the intended scope is a bounded acknowledgement, the draft can acknowledge the request without accepting an unapproved date or price.

Contrasting status decisions

Choose the status from the purpose of the reply, not from the presence of an unresolved business question.

A missing authorization is essential only when the intended reply must communicate that decision.
Intended reply scopeReview findingStatusWhy
Confirm final-file timing and free printingPriya has not authorized either termHoldThe reply must state a decision that is not available.
Acknowledge Alex's request and state the proof commitmentThe draft promises unapproved delivery and printingReviseReplace the promises with a bounded acknowledgement using approved facts.
Send the checked bounded acknowledgementRecipient, facts, tone, and internal notes are all correctApproved for manual sendingHuman review is complete; sending remains a separate human action.

Warning

Copying is not approval

Do not label a draft Approved for manual sending merely because Priya is copied. A copied recipient does not grant authorization, and an unnecessary copied recipient may receive information outside the reply's scope.

Approve an acknowledgement without approving the request

A corrected bounded acknowledgement

For the Harbor launch pack, assume the intended scope is a bounded acknowledgement: recognize Alex's requests, state Maya's approved proof commitment, and avoid accepting unapproved delivery or printing terms. Priya's confirmation is not needed to send that limited acknowledgement.

The displayed package remains sanitized. Before assigning its status, Maya restored and checked the actual client address locally.

Example

Reviewed reply package

To: [CLIENT EMAIL]
Cc: None
Subject: Harbor launch pack next steps
Body:
Hello Alex,

Thank you for outlining the requested timing and printing option. We will send the Harbor launch pack proof by 14 May 2026, 16:00 UTC. We are reviewing the final-file timing and printing terms internally and will confirm them after review.

Best,
Maya

Reviewer notes:
[CONFIRM: final delivery date]
[CONFIRM: printing terms]

Review status: Approved for manual sending

Warning

Approval is not sending

Keep confirmation markers in reviewer notes, never in the outgoing body. Restore necessary recipient details locally, remove internal notes from the final outgoing version, and recheck it after any substantive change. Even an Approved for manual sending draft still requires a person to perform manual sending.

Practice: inspect and route the draft

Inspect the flawed draft

At 14 May 2026, 09:00 UTC, inspect this proposed Harbor launch pack reply. Its intended scope is only to acknowledge Alex's requests and state the approved proof commitment; it does not need to confirm final delivery or printing.

To: [CLIENT EMAIL]
Cc: Priya
Subject: Harbor launch pack final files
Body:
Hello Alex,
We will send the proof by 15 May 2026, 12:00 UTC. We will deliver the final files by then and include printing at no extra cost. Priya has not approved these terms yet.
Best,
Maya
Reviewer notes: None

Which review decision and next handling are correct?

Step 7 of 7

Apply the Complete Manual Routine

Apply the complete manual email routine to a fresh fictional mini-inbox, correct an unsupported draft, and retain human control through manual sending.

Reconnect the routine

One routine, separate decisions

This final practice joins the routine into one human-controlled sequence:

  1. Categorize the primary next action.
  2. Set priority from timing and consequences.
  3. Record the current thread state.
  4. Select a permitted, minimum sufficient excerpt.
  5. Specify the draft boundaries.
  6. Review the proposal and assign a status.
  7. Perform manual sending only after human approval.

An assistant can suggest a draft from selected text. It does not connect to a mailbox, choose recipients, authorize commitments, or send anything.

The manual workflow

A seven-stage flow from email triage through draft review to a separate human send action.

Keep each decision distinct: classification and priority come before drafting; review comes before manual sending.

Summary

Routine recap

  • Keep response category, priority, thread state, and review status as separate records.
  • Use only a permitted excerpt that preserves the request and context needed to avoid changing meaning.
  • A bounded acknowledgement can recognize an unapproved request without accepting it.
  • Approval for manual sending is not the sending action itself.

Read the fresh mini-inbox

Mini-inbox: source material

Assess this fictional mini-inbox at 14 May 2026, 09:00 UTC. It is permitted training text, not content from a live mailbox.

Message A is a short client thread. Message B is a separate competing notice. Read the sender and sent date for Message A before deciding what remains current. For a possible draft, retain only the source lines that preserve the request, prior commitment, and approval boundary.

Do not treat a client request as an approved commitment.

Messages to assess

The contact details and unrelated copied recipient in Message A are unnecessary for drafting. A sufficient sanitized excerpt would use a placeholder such as [CLIENT EMAIL] if an address field is needed later.

Message A contains a prior commitment, a later request, and an authorization boundary. Message B is a competing operational notice.
MessageSender and sent dateSource text
A — prior commitmentNadia, Brightline Design — 13 May 2026, 16:20 UTCI will send a display-layout proof by 14 May 2026, 15:30 UTC.
A — latest requestEvan, client at Summit Museum — 14 May 2026, 08:35 UTCCould you provide the final print-ready panels by 15 May 2026, 11:00 UTC and include onsite installation at no extra cost? We need confirmation before the venue reserves its loading window. Sender field includes [CLIENT EMAIL]; signature has a direct number; an unrelated recipient is copied.
A — approval contextLeah, internal approver for production timing and service pricing — 14 May 2026, 08:20 UTCExpedited final-panel delivery and no-cost onsite installation require my confirmation.
B — competing noticeFacilities system notice — 14 May 2026, 08:50 UTCAt 14 May 2026, 09:30 UTC, badge readers will be unavailable for maintenance. The delivery crew cannot enter the studio during the interruption. No reply is needed.

Inspect the proposed reply

Candidate draft to inspect

The following proposal was produced for Message A. It is not an outgoing email. Compare every claim with the source material and Leah's authorization boundary.

Example

Candidate reply package

To: [CLIENT EMAIL]
Cc: None
Subject: Summit Museum panel delivery
Body:
Hello Evan,

We will provide the final print-ready panels by 15 May 2026, 11:00 UTC and include onsite installation at no extra cost. We will also send the display-layout proof by 14 May 2026, 15:30 UTC.

Best,
Nadia

Reviewer notes:
None

Tip

Optional fictional-only trial

If you want an optional assistant trial after this tutorial, use only the fictional sanitized excerpt shown here and a permitted tool of your own. Request a proposal and separate reviewer notes, then perform the same human checks. Do not paste real mailbox content unless workplace policy permits it.

Warning

Do not promote requests into commitments

A requested date, service, or price is not evidence of authorization. Keep unresolved matters in reviewer notes until the appropriate internal approver confirms them.

Apply and close the loop

Final application: complete the manual routine

Create one concise review record using the mini-inbox and candidate draft from the previous screens.

Include all of the following:

  • Two triage records. For each, use exactly these headings: Message, Category, Priority, and Reason.
  • For Message A, a thread-state record with exactly: Latest request, Existing commitments, and Unresolved questions.
  • The sender and sent date of each Message A source line you would retain in a sufficient sanitized excerpt, plus the unnecessary details you would omit.
  • A brief assistant request specification for Message A: recipient role, purpose, approved fact, tone and 120-word body limit, forbidden commitments, and required reviewer notes.
  • A corrected reply package using To:, Cc:, Subject:, Body:, and Reviewer notes:. Use [CLIENT EMAIL].
  • One review status—Hold, Revise, or Approved for manual sending—and a source-based reason. For this decision, assume the corrected package is intended only as a bounded acknowledgement, the actual client address has been restored and checked locally, and no copied recipient is needed.
  • The remaining human action before the email can leave the mailbox.

Use short bullets where helpful. Do not add a commitment absent from the source material.

Write at least 500 characters (0/500).

Routine complete

Congratulations! You completed: Triaging Email and Drafting Replies for Review

You completed a full manual triage-and-drafting decision. Keep the final check human, and keep sending a separate manual action.

20 XP

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate