Custodia Registry · D01

Borrower digitization

35 minutes. · 10 slides

Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.

Open video on YouTube ↗

Download slide guide (PDF)10 pages · 3.5 MB

Work through the lesson

Use these explanations alongside the slide guide. Expand any section to read its full explanation.

Your task and authority

  • Confirm your assigned duties
  • Use the fictional training case
  • Verify the result and its history

Learning outcome
Scans are attached to the correct record and borrower authority remains limited to that loan.

Read the full explanation

Our audience is digitization_intern; digitization supervisor coaching. Before the demonstration, confirm these prerequisites: C01–C04; fictional active loan and sample PDF. The action-level access conditions are: record_checked_out_file_manage or valid record/loan-specific approval; active borrower and clearance. Check the actual account and record state. The goal is not simply to find a button: Scans are attached to the correct record and borrower authority remains limited to that loan.

Confirm your loan

  • Confirm that the actual file is checked out to your account.

What to check
Check that this record is currently checked out to your own account. Being a digitization intern does not provide general Registry editing authority. Your file operations depend on the actual loan and applicable clearance.

Read the full explanation

Confirm that the actual file is checked out to your account. Check that this record is currently checked out to your own account. Being a digitization intern does not provide general Registry editing authority. Your file operations depend on the actual loan and applicable clearance. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.

Temporary file authority

  • Open its matching record; request temporary file permission only if required.

What to check
Open the matching record and inspect the available file controls. Request loan-specific approval only when needed. The approver’s current authority and the loan state remain relevant after approval.

Read the full explanation

Open its matching record; request temporary file permission only if required. Open the matching record and inspect the available file controls. Request loan-specific approval only when needed. The approver’s current authority and the loan state remain relevant after approval. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.

Upload and inspect

  • Upload the fictional scan with correct metadata and inspect its preview.

What to check
Use the supplied fictional scan and enter the appropriate metadata. Inspect the preview for the correct record, orientation and complete pages. A successful upload does not establish that the scan is readable or correctly attached.

Read the full explanation

Upload the fictional scan with correct metadata and inspect its preview. Use the supplied fictional scan and enter the appropriate metadata. Inspect the preview for the correct record, orientation and complete pages. A successful upload does not establish that the scan is readable or correctly attached. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.

Versioned replacement

  • Replace a deliberately incorrect scan using the versioned workflow and verify history.

What to check
Replace the deliberately incorrect practice scan using the supported version workflow, then inspect history. Protected retention evidence has additional restrictions; add a separate file when replacement is prohibited.

Read the full explanation

Replace a deliberately incorrect scan using the versioned workflow and verify history. Replace the deliberately incorrect practice scan using the supported version workflow, then inspect history. Protected retention evidence has additional restrictions; add a separate file when replacement is prohibited. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.

End of borrower authority

  • Return the physical file and verify that temporary authority no longer implies general Registry access.

What to check
Return the physical file through the custody workflow. Temporary borrower authority does not become permanent Registry access. An ended loan or revoked approval can prevent further file operations.

Read the full explanation

Return the physical file and verify that temporary authority no longer implies general Registry access. Return the physical file through the custody workflow. Temporary borrower authority does not become permanent Registry access. An ended loan or revoked approval can prevent further file operations. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.

Exceptions and recovery

  • Identify the blocked condition
  • Preserve the relevant evidence
  • Use the authorized next step

Important boundary
Borrower permission is not Registry authority. Wrong borrower, ended loan or revoked approver authority can block uploads. Preserve captured retention evidence; add a separate file instead of replacing protected evidence.

Read the full explanation

Consider the exception before deciding to retry. Borrower permission is not Registry authority. Wrong borrower, ended loan or revoked approver authority can block uploads. Preserve captured retention evidence; add a separate file instead of replacing protected evidence. Explain what you expected and what was actually shown. Keep the record identifier and sanitized error context, then refer the issue to the person responsible for that decision. A missing or blocked control is not a reason to borrow a more powerful account.

Guided practice

  • Work within the assigned role
  • Show the resulting state
  • Explain one exception

Your exercise
Under the assigned borrower account, inspect an active loan, upload the sample scan and explain what happens to that authority after return.

Read the full explanation

Now use the approved fictional example. Under the assigned borrower account, inspect an active loan, upload the sample scan and explain what happens to that authority after return. Explain the identity, current state and intended action before acting. At the end, show the evidence of the result and name the next responsible person if the workflow cannot proceed. Destructive actions and live external sends are discussed using prepared examples.

Practice debrief

  • Correct identity and authority
  • Traceable result and history
  • A justified next step

Expected answer
The correct borrower, active loan and record are identified; scan quality and version history are checked; the learner does not claim continuing general file-management rights.

Read the full explanation

The answer should establish the following: The correct borrower, active loan and record are identified; scan quality and version history are checked; the learner does not claim continuing general file-management rights. Walk through the evidence in the same order as the workflow. Explain the specific boundary discussed in this lesson. If a result could not be established, report it as unverified and identify what would be needed to complete the task.