Home / Registry / Record
Publishing rights & compliance · Illustrative record

Reading Lolita in Tehran

Middle East & Global Security · Publication and program dossier

By Azar Nafisi

Master file reference · illustrativeGPRCC-ILL-2003-AN-438162
Cover of Reading Lolita in Tehran by Azar Nafisi
Representative publication · edition may varyFind this edition ↗ (opens in a new tab)
Illustrative case statusApprovedScenario review date · 8 February 2003 – 7 February 2004 (release day unverified)
09Program records
36Review controls
0Open items

Master case overview

Master file reference
GPRCC-ILL-2003-AN-438162
Illustrative status
Approved
Author / reference identity
Azar Nafisi
Subject area
Middle East & Global Security
Work
Reading Lolita in Tehran
Review focus
Conflict terminology, historical attribution and regional context. Program questions are selected for this subject area; no passage-level findings are asserted.
Proposed formats · scenario
Print, ebook and audiobook
Proposed market scope · scenario
Domestic release with a proposed translation-rights package
Book release date
2003
Publication history ↗
Registration date · illustrative
8 January 2003 – 7 January 2004 (release day unverified)
Publication and registration basis
Reading Lolita in Tehran: Title and author matched publication-history record. Original-language/edition differences are retained where specified. The modeled registration is seven days after release. Where a source gives only a month or year, dates are shown as a range rather than inventing a day.
Modeled review date
8 February 2003 – 7 February 2004 (release day unverified)
Source basis
Library title, author, subject mapping and catalog program definitions; no manuscript examined.

Programs & status

This illustrative file covers 9 program records, 36 review controls and 0 open items. Select a program for its review details, document checklist and next action.

All requirements completed

All submitted documents are accepted in this scenario. No outstanding requirements remain.

36 / 36 completed
NDISApproved

News, Documentary & Investigative Source Integrity

GPRCC-ILL-2003-AN-438162-NDIS

Review scope: source provenance, confidentiality handling, redaction control.

3 review controls0 open items

Illustrative fee · USD$3,400

View review details ↓
IMRCApproved

International Media & Reputation Clearance File

GPRCC-ILL-2003-AN-438162-IMRC

Review scope: non-affiliation wording, edition-specific publicity, escalation protocol.

3 review controls0 open items

Illustrative fee · USD$3,950

View review details ↓
CBCSApproved

Cross-Border Contract & Restricted-Territory Screening

GPRCC-ILL-2003-AN-438162-CBCS

Review scope: market scope, local referral, edition variations.

5 review controls0 open items

Illustrative fee · USD$2,250

View review details ↓
RCCRApproved

Religious & Cultural Content Review

GPRCC-ILL-2003-AN-438162-RCCR

Review scope: cultural context, belief and attribution, translation sensitivity.

5 review controls0 open items

Illustrative fee · USD$2,850

View review details ↓
TFRRApproved

Translation & Foreign Rights Record

GPRCC-ILL-2003-AN-438162-TFRR

Review scope: translation grant, translator rights, terminology control.

3 review controls0 open items

Illustrative fee · USD$3,400

View review details ↓
IDLCApproved

International Distribution & Licensing Compliance File

GPRCC-ILL-2003-AN-438162-IDLC

Review scope: agreement inventory, license boundaries, retail metadata.

5 review controls0 open items

Illustrative fee · USD$3,950

View review details ↓
IRTCApproved

International Rights & Territory Control File

GPRCC-ILL-2003-AN-438162-IRTC

Review scope: chain of title, territory and format scope, edition history.

4 review controls0 open items

Illustrative fee · USD$2,250

View review details ↓
CAVRApproved

Cover, Artwork & Visual Asset Rights Record

GPRCC-ILL-2003-AN-438162-CAVR

Review scope: designer permissions, credit requirements, edition approval.

3 review controls0 open items

Illustrative fee · USD$2,850

View review details ↓
IBEMApproved

International Brand Enforcement & Monitoring File

GPRCC-ILL-2003-AN-438162-IBEM

Review scope: protected assets, authorized channels, monitoring exclusions.

5 review controls0 open items

Illustrative fee · USD$3,600

View review details ↓
NDIS · Illustrative program record

News, Documentary & Investigative Source Integrity

Approved
Program reference
GPRCC-ILL-2003-AN-438162-NDIS
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
3 of 3 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 3

  1. NDIS-101

    Source provenance

    For the proposed scope of Reading Lolita in Tehran, trace research inputs to their origin and document verification limits. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. NDIS-102

    Confidentiality handling

    For the proposed scope of Reading Lolita in Tehran, separate public references from material requiring restricted access. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. NDIS-105

    Redaction control

    For the proposed scope of Reading Lolita in Tehran, define version controls for any required redactions. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

  • Source provenance registerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: NDIS-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Source handling matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: NDIS-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Redaction and access logCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: NDIS-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

IMRC · Illustrative program record

International Media & Reputation Clearance File

Approved
Program reference
GPRCC-ILL-2003-AN-438162-IMRC
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
3 of 3 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 3

  1. IMRC-102

    Non-affiliation wording

    For the proposed scope of Reading Lolita in Tehran, review references to people and institutions for unintended endorsement implications. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. IMRC-104

    Edition-specific publicity

    For the proposed scope of Reading Lolita in Tehran, align retailer summaries and campaign copy with the edition proposed for release. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. IMRC-105

    Escalation protocol

    For the proposed scope of Reading Lolita in Tehran, define which disputed statements would require specialist review before reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

  • Non-affiliation wording sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IMRC-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Campaign and jacket-copy comparisonCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IMRC-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Media review escalation planCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IMRC-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

CBCS · Illustrative program record

Cross-Border Contract & Restricted-Territory Screening

Approved
Program reference
GPRCC-ILL-2003-AN-438162-CBCS
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
5 of 5 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 5

  1. CBCS-101

    Market scope

    For the proposed scope of Reading Lolita in Tehran, identify the proposed distribution markets before country-specific review. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. CBCS-102

    Local referral

    For the proposed scope of Reading Lolita in Tehran, define questions for qualified local review without inventing restrictions. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. CBCS-103

    Edition variations

    For the proposed scope of Reading Lolita in Tehran, track any proposed market-specific changes separately from the source edition. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  4. CBCS-104

    Partner checks

    For the proposed scope of Reading Lolita in Tehran, document proposed distribution partner responsibilities. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  5. CBCS-105

    Release gates

    For the proposed scope of Reading Lolita in Tehran, record market-specific prerequisites before release authorization. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

  • Target-market scheduleCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CBCS-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Country-review referral briefCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CBCS-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Market edition comparisonCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CBCS-103.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Partner responsibility matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CBCS-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Market release checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CBCS-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

RCCR · Illustrative program record

Religious & Cultural Content Review

Approved
Program reference
GPRCC-ILL-2003-AN-438162-RCCR
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
5 of 5 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 5

  1. RCCR-101

    Cultural context

    For the proposed scope of Reading Lolita in Tehran, identify contextual notes needed for cross-cultural presentation. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. RCCR-102

    Belief and attribution

    For the proposed scope of Reading Lolita in Tehran, distinguish an author’s interpretation from an attributed community position. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. RCCR-103

    Translation sensitivity

    For the proposed scope of Reading Lolita in Tehran, flag terms that could change meaning across languages. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  4. RCCR-104

    Consultation scope

    For the proposed scope of Reading Lolita in Tehran, define any proposed specialist consultation without implying community endorsement. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  5. RCCR-105

    Promotional framing

    For the proposed scope of Reading Lolita in Tehran, preserve distinctions between discussion, criticism and affiliation. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

  • Cultural context review briefCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: RCCR-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Belief and attribution mapCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: RCCR-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Cultural terminology sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: RCCR-103.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Consultation scope planCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: RCCR-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Cross-cultural publicity reviewCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: RCCR-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

TFRR · Illustrative program record

Translation & Foreign Rights Record

Approved
Program reference
GPRCC-ILL-2003-AN-438162-TFRR
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
3 of 3 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 3

  1. TFRR-101

    Translation grant

    For the proposed scope of Reading Lolita in Tehran, identify language, territory and format boundaries for a proposed translation. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. TFRR-102

    Translator rights

    For the proposed scope of Reading Lolita in Tehran, document translator credit, assignment and permitted reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. TFRR-103

    Terminology control

    For the proposed scope of Reading Lolita in Tehran, prepare a terminology guide appropriate to the work’s subject area. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

  • Foreign-rights grant matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: TFRR-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Translator agreement checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: TFRR-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Translation terminology briefCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: TFRR-103.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

IDLC · Illustrative program record

International Distribution & Licensing Compliance File

Approved
Program reference
GPRCC-ILL-2003-AN-438162-IDLC
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
5 of 5 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 5

  1. IDLC-101

    Agreement inventory

    For the proposed scope of Reading Lolita in Tehran, identify proposed publisher, distributor and retail permissions for the named work. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. IDLC-102

    License boundaries

    For the proposed scope of Reading Lolita in Tehran, map term, format, territory, language and sublicensing limits. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. IDLC-103

    Retail metadata

    For the proposed scope of Reading Lolita in Tehran, reconcile title, author credit, edition description and rights-holder attribution. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  4. IDLC-104

    Accounting and reporting

    For the proposed scope of Reading Lolita in Tehran, document royalty reporting intervals, deductions and audit provisions. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  5. IDLC-105

    Termination controls

    For the proposed scope of Reading Lolita in Tehran, define takedown, stock sell-off and rights reversion responsibilities. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

  • Distribution agreement inventoryCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Distribution license matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Retail metadata approval sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-103.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Royalty and reporting scheduleCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Termination and reversion checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

IRTC · Illustrative program record

International Rights & Territory Control File

Approved
Program reference
GPRCC-ILL-2003-AN-438162-IRTC
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
4 of 4 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 4

  1. IRTC-101

    Chain of title

    For the proposed scope of Reading Lolita in Tehran, identify the party authorized to grant rights and reconcile contributor assignments. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. IRTC-102

    Territory and format scope

    For the proposed scope of Reading Lolita in Tehran, map languages, formats, exclusivity and reserved territories without assuming worldwide rights. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. IRTC-103

    Edition history

    For the proposed scope of Reading Lolita in Tehran, separate original publication rights from revised-edition and supplementary-material rights. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  4. IRTC-104

    Quotation permissions

    For the proposed scope of Reading Lolita in Tehran, record the basis for reuse of any third-party extracts in the proposed edition. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 4

  • Ownership and contributor assignment scheduleCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Territory, language and format matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Edition and rights chronologyCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-103.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Third-party permissions registerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

CAVR · Illustrative program record

Cover, Artwork & Visual Asset Rights Record

Approved
Program reference
GPRCC-ILL-2003-AN-438162-CAVR
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
3 of 3 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 3

  1. CAVR-102

    Designer permissions

    For the proposed scope of Reading Lolita in Tehran, separate designer deliverables from third-party stock and font licenses. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. CAVR-104

    Credit requirements

    For the proposed scope of Reading Lolita in Tehran, record mandatory image credits and license conditions. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. CAVR-105

    Edition approval

    For the proposed scope of Reading Lolita in Tehran, track the approved cover version for each proposed edition. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

  • Designer and supplier rights checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Visual credit-line sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Cover version approval logCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

IBEM · Illustrative program record

International Brand Enforcement & Monitoring File

Approved
Program reference
GPRCC-ILL-2003-AN-438162-IBEM
Master file
GPRCC-ILL-2003-AN-438162
Review scope
Print, ebook and audiobook
Evidence position
5 of 5 controls complete in scenario
Publication context
Reading Lolita in Tehran by Azar Nafisi · Conflict terminology, historical attribution and regional context

Review controls and scoped outcome 5

  1. IBEM-101

    Protected assets

    For the proposed scope of Reading Lolita in Tehran, separate protectable text and artwork from third-party names and lawful references. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  2. IBEM-102

    Authorized channels

    For the proposed scope of Reading Lolita in Tehran, distinguish approved editions and sellers from items that need verification. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  3. IBEM-103

    Monitoring exclusions

    For the proposed scope of Reading Lolita in Tehran, exclude commentary, criticism and other lawful references from proposed monitoring. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  4. IBEM-104

    Control verification

    For the proposed scope of Reading Lolita in Tehran, identify who may authorize use of the proposed author and publication branding. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

  5. IBEM-105

    Notice readiness

    For the proposed scope of Reading Lolita in Tehran, specify evidence capture and rights-holder approval before any proposed notice. Apply this check in the context of conflict terminology, historical attribution and regional context.

    Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

  • Protected asset inventoryCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IBEM-101.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Authorized edition and channel registerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IBEM-102.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Monitoring keyword and exclusion planCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IBEM-103.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Brand and account control checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IBEM-104.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
  • Evidence capture and escalation protocolCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IBEM-105.Submission attempt 1 · 13 January 2003 – 12 January 2004 (release day unverified) · reviewed 8 February 2003 – 7 February 2004 (release day unverified) · illustrative
Maintenance standard. Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. This is a modeled workflow, not a notice issued to the author.

↑ Back to programs

Evidence and document index

A modeled evidence schedule for Reading Lolita in Tehran. These are document requirements and scenario states, not uploaded attachments or manuscript citations.

Control referenceDocument requirementScenario state
NDIS-101Source provenance registerCompleted · submitted and reviewed
NDIS-102Source handling matrixCompleted · submitted and reviewed
NDIS-105Redaction and access logCompleted · submitted and reviewed
IMRC-102Non-affiliation wording sheetCompleted · submitted and reviewed
IMRC-104Campaign and jacket-copy comparisonCompleted · submitted and reviewed
IMRC-105Media review escalation planCompleted · submitted and reviewed
CBCS-101Target-market scheduleCompleted · submitted and reviewed
CBCS-102Country-review referral briefCompleted · submitted and reviewed
CBCS-103Market edition comparisonCompleted · submitted and reviewed
CBCS-104Partner responsibility matrixCompleted · submitted and reviewed
CBCS-105Market release checklistCompleted · submitted and reviewed
RCCR-101Cultural context review briefCompleted · submitted and reviewed
RCCR-102Belief and attribution mapCompleted · submitted and reviewed
RCCR-103Cultural terminology sheetCompleted · submitted and reviewed
RCCR-104Consultation scope planCompleted · submitted and reviewed
RCCR-105Cross-cultural publicity reviewCompleted · submitted and reviewed
TFRR-101Foreign-rights grant matrixCompleted · submitted and reviewed
TFRR-102Translator agreement checklistCompleted · submitted and reviewed
TFRR-103Translation terminology briefCompleted · submitted and reviewed
IDLC-101Distribution agreement inventoryCompleted · submitted and reviewed
IDLC-102Distribution license matrixCompleted · submitted and reviewed
IDLC-103Retail metadata approval sheetCompleted · submitted and reviewed
IDLC-104Royalty and reporting scheduleCompleted · submitted and reviewed
IDLC-105Termination and reversion checklistCompleted · submitted and reviewed
IRTC-101Ownership and contributor assignment scheduleCompleted · submitted and reviewed
IRTC-102Territory, language and format matrixCompleted · submitted and reviewed
IRTC-103Edition and rights chronologyCompleted · submitted and reviewed
IRTC-104Third-party permissions registerCompleted · submitted and reviewed
CAVR-102Designer and supplier rights checklistCompleted · submitted and reviewed
CAVR-104Visual credit-line sheetCompleted · submitted and reviewed
CAVR-105Cover version approval logCompleted · submitted and reviewed
IBEM-101Protected asset inventoryCompleted · submitted and reviewed
IBEM-102Authorized edition and channel registerCompleted · submitted and reviewed
IBEM-103Monitoring keyword and exclusion planCompleted · submitted and reviewed
IBEM-104Brand and account control checklistCompleted · submitted and reviewed
IBEM-105Evidence capture and escalation protocolCompleted · submitted and reviewed

Consolidated program status

ProgramIllustrative statusOpen itemsNext action
NDISApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
IMRCApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
CBCSApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
RCCRApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
TFRRApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
IDLCApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
IRTCApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
CAVRApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.
IBEMApproved0Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment.

Illustrative review history

Generated milestones showing how this workflow could progress; these events did not occur for the named author.

Scenario dateModeled milestone
8 January 2003 – 7 January 2004 (release day unverified)Registration modeled
13 January 2003 – 12 January 2004 (release day unverified)Evidence package submitted · scenario
25 January 2003 – 24 January 2004 (release day unverified)Submitted evidence reviewed · scenario
8 February 2003 – 7 February 2004 (release day unverified)Scoped approval modeled

Program fee breakdown

The original illustrative case total is allocated across the 9 programs below. These example amounts are not payment receipts or quotations.

ProgramProgram nameAllocated fee (USD)
NDISNews, Documentary & Investigative Source Integrity$3,400
IMRCInternational Media & Reputation Clearance File$3,950
CBCSCross-Border Contract & Restricted-Territory Screening$2,250
RCCRReligious & Cultural Content Review$2,850
TFRRTranslation & Foreign Rights Record$3,400
IDLCInternational Distribution & Licensing Compliance File$3,950
IRTCInternational Rights & Territory Control File$2,250
CAVRCover, Artwork & Visual Asset Rights Record$2,850
IBEMInternational Brand Enforcement & Monitoring File$3,600

Total illustrative fees · USD$28,500

These restored case allocations are separate from the planning bands for new quotes. A written scope and quote determine the charge for an actual matter.

Next steps

  1. Retain the edition, format and rights schedules modeled in this record.
  2. Check proposed changes against each program’s maintenance standard.
  3. Reassess new translations, licenses or substantial promotional changes before extending scope.

This sequence describes the modeled approved workflow only.

Record statements

Illustrative scope. The author and publication identify a library entry. Review details and registration milestones are synthetic; book publication dates are sourced; the page makes no claim that the author applied, supplied evidence, paid fees or received a determination.

Program references. GPRCC-ILL identifiers label scenarios, not statutory registrations. Document states and allocated fees are not proof of review or payment.

Publication context. The modeled status makes no finding about the publication’s legality, accuracy, ownership or suitability. Real determinations require a submitted record and an authorized review.

Author Case Library