These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Question Paper Generator
- Features
- Question bank lines
Question bank lines
Capture the detail attached to each enrollment.
OverviewPending question bank lines×
Question Paper Generator · Question bank lines
New
Pending question bank lines
Approval conditions
| Sequence | Question text | Operational record | Source record id | Status | |
|---|---|---|---|---|---|
| 20 | QT-965 | ENR-63879 | SRI-312 | Pending | |
| 20 | QT-453 | ENR-29103 | SRI-429 | Pending | |
| 60 | QT-871 | ENR-68096 | SRI-640 | Pending | |
| 50 | QT-151 | ENR-25822 | SRI-989 | Pending | |
| 10 | QT-731 | ENR-69873 | SRI-484 | Pending |
6 of 6 records
QT-965Question bank · QB-72651
PendingSequence20
Operational recordENR-63879
Source record idSRI-312
What you can do
Keep line detail attached to its case
Question bank holds ordered lines connected to an enrollment. Each line can retain its question text, quantity, unit, observed date, source reference and review status. The child strip on the Enrollments screen keeps this detail beside the selected case, so an Instructor can compare a line with the enrollment it supports.
How the work is organized
- Identify each source line. The Instructor records a source record ID and sequence with the line attached to the enrollment.
- Review its status. Pending, accepted and rejected values show which details still need attention.
- Explain corrections. A changed source reference or rejected line needs a decision reason that the reviewer can inspect.
What to agree during setup
Agree which source record ID is used for each line and how the team recognizes a repeated source line. Decide what Pending, Accepted and Rejected mean in your operating procedure. Keep the decision reason with any rejected line that needs explanation.
Check the handoff on an actual case
An Instructor enters lines for an enrollment and later receives a corrected source document. The old and corrected details should be compared by their source references before another line is accepted. An Academic Reviewer sees which lines remain pending. The team records the reason for a rejected line and assigns any needed correction to the right person.
In the rehearsal, ask the Instructor to identify the source record and explain the change. Ask the Academic Reviewer to find the supporting evidence and decision for the same revision. The Read Only Analyst should be able to inspect the recorded outcome without editing it.
At the handoff, compare the latest status with the source reference and recorded reason. Identify who made the last decision before acting on a corrected case.
What your team sees
- Pending question bank lines — Lines awaiting review show their source IDs and related enrollments.
- Question bank decisions — Accepted and rejected lines show the decision reason beside the case.
Follow the work through
Use the source and revision when passing a case to the next person. If an action remains open or an operation has an uncertain result, inspect its related records before recording the outcome.
- Submission and review: Prepare the case and route it for an independent decision.
- Decision and delivery: Trace the approved case through the recorded outcome.
Review the implementation plan and the data model before preparing your first import.
What it keeps track of
Data model- Question bank
- Observation-level requirement, document and line detail captured against a service application.
- Enrollments
- Requests, applications and cases submitted for a public service.
- Follow up actions
- Assigned outstanding actions, corrections and outstanding requests for a case.
Who uses it
Permissions- Instructor
- , Academic Reviewer.
- The Instructor prepares the case and supporting records.
- The Academic Reviewer checks the decision against the case revision.
Set up Question Paper Generator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.