How do you translate Google Classroom assignment instructions through the Classroom API without changing the work students receive, the date it is due or the records their teachers rely on? A CourseWork JSON object contains readable fields such as a title and description alongside IDs, states, timestamps, grades, linked materials and assignment settings. Translating every string indiscriminately is not a safe strategy. The right approach is to understand what is learner-facing prose and what is a live education-system record.
This detailed Google Classroom CourseWork localization guide explains the distinction between CourseWork and CourseWorkMaterial, assignment titles and descriptions, linked Drive resources, work types, topics, due dates, scheduled publication, individual-student targeting, grading and response states. It is written for education developers, schools, university teams, professional training providers, localization specialists and teachers delivering lessons internationally. The examples use fictional course records rather than private learner data.
Google’s Classroom API reference documents CourseWork properties including title, description, materials, state, dueDate, dueTime, scheduledTime, workType, maxPoints, assigneeMode and topicId. Some fields identify records and others control distribution or grading; some are read-only or restricted by the API. Successful localization therefore means approved changes to visible language, not a translation of JSON keys, course IDs or stored evidence. Every example in this article starts from that basic separation.
How this guide is organized
Start with the distinction between instructional language and Classroom data, then use the thirty-seven cases to examine common production and teaching decisions. The worked end-to-end example, four-week plan and FAQ help you check whether a localized assignment is readable, properly targeted, accessible and still governed by the intended rules.
Google Classroom CourseWork architecture and translation boundaries
CourseWork is an assignment object
CourseWork describes work created for learners, not a complete course export. It has an ID, course association, content fields and delivery or assessment rules. You may translate its title and description under the right authority; you must not assume that changing the text permits moving the work to another course, changing its identity or reassigning students.
CourseWorkMaterial is a different resource
CourseWorkMaterial describes teacher-provided resource posts. It can have title, description, materials, state and other properties, but it is not the same thing as an assignment requiring student submissions. Decide which resource is being handled before developing extraction, translation or patch logic. An incorrect resource type creates operational errors even when all sentences are correct.
Keys and values have different jobs
JSON property names are API contracts. Values can be learner text, fixed enums, identifiers, timestamps, links or numbers. Translate only the intended human-readable portions of values; never localize the API field names, enum spellings or opaque IDs. A field-level content inventory is more reliable than a blanket find-and-replace.
State and publication are consequential
Draft and published coursework have different visibility, and scheduled publication creates another dimension. Do not turn an internal teacher draft into a live assignment during localization. Agree on a release owner and check the final state under student permissions before describing an item as available.
Dates require explicit clocks
The API represents dueDate and dueTime on a UTC basis. A natural target-language deadline can be confusing if readers interpret it as their local timezone. Keep the stored time meaning intact and provide approved, explicit explanations for international learners. Check the actual learner view where possible.
Materials are linked and permissioned
An attachment may reference a Google Drive file, a YouTube resource or an external link with its own permissions and rights. Translating the assignment’s title does not translate or re-share the attached asset. Treat every material as a separate dependency, including file access, alternative language editions and accessibility.
Grading and targeting are not editorial fields
maxPoints, workType, assigneeMode, individualStudentsOptions and grade-category behavior serve academic or distribution functions. They are not synonyms to rewrite for a target language. Distinguish technical changes that require teacher or administrator approval from legitimate language adaptation.
Use permitted API workflows
Classroom API methods have permission requirements and constraints, and some properties cannot be changed after creation. Build localization around supported read and update operations, record the intended fields and handle errors explicitly. Test on authorized sandbox coursework rather than experimenting with live student assignments.
Thirty-six CourseWork localization and API decisions
1. Course ID
An instructor’s class has a courseId that appears beside assignments in API responses. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Replacing the identifier with a translated school name would detach the item from its actual class. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Treat courseId as a stable platform reference and translate only an approved display label. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Read back the assignment and verify its parent course association. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
2. Assignment ID
Two assignments have similar titles but different assigned identifiers. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Matching by a translated title may update the wrong assessment. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Use the returned id as the primary record reference in synchronization. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Fetch the intended object by ID before and after localization. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
3. Title field
A teacher names an assignment with a short phrase describing a laboratory report. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
The title can be localized, but an over-shortened version may hide the required task. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Review the title alongside the detailed description and approved lesson objective. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check the title in the student’s classwork list. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
4. Description field
The description contains an ordered set of tasks and required output files. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Translation may change sequence, negation or an important submission condition. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Treat the description as instructional content requiring subject review. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Have a teacher compare the resulting student action in each language. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
5. CourseWorkMaterial
A lesson reading is posted as material instead of an assignment. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Confusing a material post with gradable CourseWork can create false submission expectations. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Identify the resource type before selecting the proper API collection and wording. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Verify the student sees a reading, not an invented graded task. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
6. Materials array
A teacher attaches several Drive documents and one external website link. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
The description can be correct while a linked attachment stays in the source language. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Inventory every material and decide whether it needs an authorized translated equivalent. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Open the links as a student with no privileged Drive access. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
7. Attachment limit
A developer attempts to add too many separate material objects during localization. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Exceeding supported API limits can make the request fail before publication. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Check limits and consolidate instructional assets only when it preserves clarity. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Validate API errors and count the actual material entries in the saved object. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
8. Drive sharing
A translated worksheet is copied into a new Drive file with different permissions. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Students may see a permission error instead of the localized worksheet. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Coordinate sharing and ownership under school policy, not by changing the text field. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Open the target Drive file with a test student account. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
9. External URL
An assignment points to a research article through a stable DOI link. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Replacing a permanent identifier with a translated title can change the referenced work. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Keep the stable resource identity and translate the surrounding explanation. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Open the destination and verify that it is the intended edition. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
10. YouTube resource
A teacher attaches a demonstration video to a Classroom material post. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
The linked video may lack captions or may be restricted to a region. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Review access, licensed language variants and timed captions separately. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Play the video from the learner’s permission context. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
11. Work type
The API identifies an assignment or a multiple-choice question through workType. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Changing that enum to a translated phrase corrupts the API contract and activity meaning. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Preserve the supported machine value and translate only its visible explanation. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Confirm the object retains the expected workType after readback. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
12. Immutable type
A team decides to turn a published question into an assignment solely through localization. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
The resource type is not an ordinary editable title field and may be immutable. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Plan a separately authorized new item if the academic task actually changes. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check the API’s allowed update fields and test a legitimate workflow. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
13. Draft state
A teacher stores an unreviewed translation as draft coursework. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Setting the state to published during a language edit could reveal unfinished instructions. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Keep editorial review and teacher publication as separate decisions. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check visibility with a teacher and a student before release. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
14. Scheduled publication
An educator schedules a task to appear next week in another country. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A localized sentence that says ‘available now’ can contradict scheduledTime. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Translate announcement text against the actual publishing schedule. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check the scheduled timestamp and student visibility at the intended time. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
15. Due date
An international class has dueDate and dueTime expressed on a UTC basis. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A target-language date without timezone context may shift by a calendar day locally. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Preserve stored values and give an explicit timezone when it matters. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Compare the API fields with the learner’s displayed deadline. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
16. Time omission
A teacher chooses a date without a separate local-time explanation. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Adding a guessed hour to the translation invents a policy not stated by the source. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Use only verified deadline values and explain ambiguity rather than silently resolving it. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Ask the owner to approve any additional timing guidance. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
17. Maximum points
A task is ungraded or has a defined maxPoints value. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A translated prompt that calls it a ten-point assignment may misrepresent grading. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Leave the numeric value unchanged unless formally approved by the teacher. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Compare the student-facing instruction with maxPoints and grade records. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
18. Grade category
An assignment belongs to a grading category visible elsewhere in the course. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Translating the description does not authorize changing gradebook classification. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Review category context and follow the API’s read-only or controlled-field rules. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check the gradebook view in the intended Classroom environment. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
19. Assignee mode
A lesson is assigned only to a selected set of students. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A translation saying ‘everyone must submit’ can expose a misleading obligation. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Make the prose match ALL_STUDENTS or INDIVIDUAL_STUDENTS as configured. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Use test accounts to verify who actually sees the task. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
20. Individual options
A small intervention group has its own coursework assignment. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Replacing student IDs with localized names could redirect the task or breach privacy. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Keep identifiers private and use only permitted assignment distribution APIs. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check authorized recipients without exporting unnecessary personal records. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
21. Topic reference
A teacher organizes assignments under a Classroom topic with topicId. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Changing the ID to a translated category label may break the reference. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Keep the stable topic link while translating human-facing topic explanations. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Confirm the assignment appears in the intended topic. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
22. Question choices
A multiple-choice CourseWork question contains alternatives in its details. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A paraphrase may turn distinct choices into overlapping statements. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Translate choice text with the stem and teacher’s intended learning objective. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Answer the question as a student and assess clarity of each option. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
23. No automatic key
A teacher assumes every multiple-choice question object stores a reusable correct-answer key. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Inventing an answer-key field in localized JSON is not legitimate translation. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Consult the actual Classroom resource schema and preserve supported data only. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Read back the saved question and inspect documented fields. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
24. Assignment instructions
A practical task says upload a PDF showing one sample and one explanation. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A negative phrase lost in translation may reverse what must be included. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Use explicit, learner-tested wording without changing submission requirements. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Ask a student reviewer to summarize what they will submit. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
25. Submission state
A student has turned in work and the teacher considers revising the assignment text. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
The translated wording must not be presented as proof that an old submission changed. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Separate CourseWork editing from StudentSubmission record handling. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Verify the original submission state remains what the system recorded. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
26. Submission modification
An activity has rules about whether learners can edit after turning in. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A translated message promising unlimited edits can contradict the configured mode. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Match instructional wording to the actual submissionModificationMode. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Test allowed and prohibited edits in a safe class. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
27. Visibility
A course item is accessible to teachers but not visible to enrolled students. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A localization reviewer signed in as a teacher may mistakenly say it is ready. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Test draft, published and targeted visibility from the correct role. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Capture the student-view evidence before release. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
28. Creation timestamp
An API response includes creationTime and updateTime values. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
These are chronology records, not prose dates that may be freely altered. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Render dates for readers when necessary but preserve the underlying timestamps. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Compare readback records with the original before making audit claims. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
29. Updated content
The source instructor changes an instruction after the translation was approved. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A stale translation can disagree with current academic expectations. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Track revisions at the field level and request renewed approval for substantive changes. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Compare updated source and localized description before publishing. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
30. UTF-8 text
A course uses a target language with accented characters and non-Latin script. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Bad encoding or text normalization can turn readable instructions into replacement glyphs. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Preserve Unicode and test the actual API payload through readback and student display. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Inspect punctuation, symbols and proper names in the destination. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
31. Right-to-left text
An Arabic assignment includes programming commands and numerical expressions. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Bidirectional layout may reorder Latin code or misplace punctuation. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Keep literal tokens protected and apply directionality to visible prose appropriately. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Review mixed-script instructions on mobile and desktop. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
32. Accessible attachments
A PDF activity guide contains labelled diagrams and a table needed for the task. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Translating its filename alone leaves a student with inaccessible source-language content. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Produce a genuinely accessible translated asset with usable headings and text alternatives. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Open the attached file with relevant accessibility tools. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
33. Permissions
An integration service attempts to patch coursework without teacher authorization. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
A translation workflow does not confer access to classes or student records. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Use documented OAuth scopes and administrative approval for intended actions. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Confirm successful API calls use only the permissions actually needed. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
34. Failed request
A patch request returns an error after some related asset work has completed. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Treating partial progress as publication can leave mismatched texts and links. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Log field-level failures, maintain rollback information and avoid ambiguous completion claims. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Read back every affected resource before reporting success. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
35. Duplicate work
Two translated assignments are created for the same unit with different IDs. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
Students may submit to the wrong copy and teachers receive split work streams. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Use a source-to-target registry and agreed edition ownership. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Check for duplicate titles, targets and identifiers in the classwork list. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
36. Privacy review
A translator asks for students’ names and submissions to understand the assignment. Before translating anything, ask whether the field is authored for learners or whether it is a reference, status or operational condition. A human-facing phrase needs accurate meaning in context. An identifier or enum needs stability, even if its spelling looks unfamiliar to an editor.
That personal data is unnecessary for most instructional localization. This problem matters because teachers and students rely on more than the title they see. Classroom can apply targeting, visibility, assessment and linked-resource rules independently of prose. The review should therefore include the learning purpose and the actual delivery behavior.
Use fabricated examples and tightly scoped sample records under authorized policy. Record the original field, approved target expression, affected resource and permission owner. If the change would alter who receives work, how it is graded or when it appears, stop treating it as translation and seek explicit academic and administrative approval. Keep source and target evidence distinguishable.
Confirm no student-identifiable records appear in translation deliverables. A successful request or convincing teacher preview is not the same as a correct student experience. Verify the saved object through the supported API and, where possible, inspect what a properly authorized student sees. Preserve enough detail for a second reviewer to reproduce that result.
A full worked example: multilingual geography coursework
An international school uses Google Classroom to run a geography class with weekly reading materials, two data interpretation assignments and a final presentation. The teacher wants a new language edition for a separate cohort. The school first records the original course IDs, tasks, title and description fields, linked resources, deadlines and target groups. It confirms which records belong to a different class and which original identifiers must not be repurposed.
The translator prepares approved titles and instructions while a subject teacher checks that map directions, data terminology and assessment criteria retain their meaning. A paragraph that says ‘compare two methods’ remains an evaluation task, not a request to describe either method alone. The linked Drive worksheet receives a genuinely translated copy under authorized sharing permissions; the original scientific source references remain stable.
A test developer workflow uses the appropriate API resources and known fields. It distinguishes CourseWork from CourseWorkMaterial, preserves enum values, keeps due-time semantics and verifies whether the intended posts are drafts or published. Targeted assignments are tested with appropriate authorized recipients. A teacher confirms that an assignment intended for one support group is not described as compulsory for the entire class.
The school reads back each saved item and checks the live student view. One translated resource link initially leads to a permission prompt, so the owner corrects the file sharing instead of pretending the localization is complete. A further review catches a deadline that would cross into the next calendar day for the target cohort; an explicit local-time explanation is approved without silently modifying the stored due date.
Only after content, targeting, grading, privacy and resource access are verified does the teacher publish the new edition. A source-to-target record is retained for future corrections. The original assignments and past submissions are not rewritten to produce the new learning experience.
A four-week practical learning and release plan
Week 1 — Inventory objects and intent
Identify CourseWork, CourseWorkMaterial, related topics, linked resources and permissions. Capture the source titles, descriptions, dates, work types, grades and visibility states. Record what will be translated and what must remain an intact data reference.
Week 2 — Translate and obtain teaching approval
Translate learner-visible text and authorized resources. Review diagrams, multiple-choice options, accessibility, filenames and institutional terminology with a subject specialist. Preserve identifiers, API schema, enums and timestamps unless a separately approved functional change is required.
Week 3 — Test through the API and student view
Use safe test classes and permitted API operations. Read back saved records and review drafts, published items, assignment targeting, deadlines, links and allowed submission modes. Have the teacher check that the real student action matches the translated instructions.
Week 4 — Release with controlled maintenance
Publish only with the teacher’s approval and appropriate permissions. Keep revision mappings, acceptance records and recovery steps. Establish a process for source changes so translations remain aligned without rewriting historical submissions or unrelated classes.
Frequently asked questions
What is CourseWork in the Google Classroom API?
It is a resource for class work with properties including identifiers, title, description, materials, work type, state, dates and assessment information.
Is CourseWorkMaterial the same as CourseWork?
No. Material posts and coursework are distinct resource collections with different teaching purposes. Check the object type before editing.
Should JSON field names be translated?
No. Property names are API contracts. Translate only the intended learner-facing values, leaving identifiers, enums and machine fields intact.
Does a translated description change an assignment’s due date?
No. DueDate and dueTime are separate fields. Make the localized words match the real date and specified timezone.
Can an assignment’s workType be translated?
The enum must retain its supported machine value. Its natural-language explanation may be localized separately.
Can all learners see every translated assignment?
Not necessarily. Publication state and assignee targeting affect visibility. Verify with authorized test student accounts.
Do attached Drive files become translated automatically?
No. The files and their permissions must be assessed separately.
Is maxPoints an editorial choice?
No. It is an assessment property. A teacher should authorize changes to grading expectations.
How should privacy be handled?
Use minimal authorized data and fictional instructional samples. Do not export student submissions merely for linguistic work.
How do I confirm a successful localization?
Read back resource fields, inspect student visibility and test permissions, materials, deadlines, directions and grading implications.
Official API references and related guides
Read the Google Classroom CourseWork REST resource, CourseWorkMaterial resource and Manage CourseWork guide. API details, permissions and preview-only fields can evolve; consult the current documentation for the exact operation.
Related eduKateSG resources: OneRoster 1.2 school records, QTI 3 assessment packaging, Canvas course exports and the Translate Like a Pro index. This guide concerns Google Classroom API resource localization, not general gradebook or assessment interchange.