Tools for a clearer
team review.
Work through these prompts together. For every unchecked item, agree an owner, an action and a review date.
No sign-up required. Checkboxes are temporary and are not saved or submitted.
Three practical worksheets. Start with the problem.
Open a worksheet to read its instructions and completed example. Fill the blank fields and print or save as PDF. Download HTML for an offline copy. Your entries are temporary and are not submitted or saved automatically.
Collection-to-receipt reconciliation worksheet
Compare bag identifiers at collection and receipt, then assign and close each difference.
How to use it and what the example demonstrates
- Choose the same route, date window and reporting cut-off for both extracts. Record the source references; totals from different scopes cannot be compared reliably.
- Count distinct bag identifiers and compare the actual sets. Record duplicates, missing receipts and unexpected receipts separately.
- Investigate each difference against field and plant evidence. A missing digital receipt is not proof that a physical bag is missing.
- After an authorized correction or recovered upload, rerun the comparison and record the evidence supporting closure. Keep the original record history.
Fictional example: Bag identifiers · 100 unique IDs: DEMO-001 to DEMO-100 · 98 unique IDs: DEMO-001 to DEMO-098 · DEMO-099 and DEMO-100 have no matched receipt. Investigate; do not assume physical loss. · Receiving supervisor; remains open
Read the supporting guide ↗ · Version 1.0 · 14 September 2026
Barcode exception and correction register
Record duplicate scans, unreadable labels and uncertain uploads without losing the original event history.
How to use it and what the example demonstrates
- Assign a case reference and record what was observed, when it occurred and who captured it. Keep the event reference separate from the bag identifier.
- Classify the issue before correcting it: a retry, a second physical event and an unreadable label need different investigations.
- Assign an owner and next review date. Preserve the original value and any approved correction with a reason.
- Close only when supporting evidence is attached or referenced and an authorized reviewer accepts the outcome.
Fictional example: DEMO-EX-01 / DEMO-BAG-01 · Same local event sent twice after reconnection · Compare local event IDs, payload references and acknowledgements. · Integration owner: confirm retry handling and one accepted event. · Open until receiver outcome verified
Read the supporting guide ↗ · Version 1.0 · 14 September 2026
CBWTF software pilot acceptance scorecard
Use the same scenarios and evidence criteria to evaluate each supplier. Record outcomes, blockers and retests.
How to use it and what the example demonstrates
- Agree the scenarios, expected evidence and must-pass conditions before the demonstration. Use fictitious HCF and collection data.
- Give each supplier the same test pack, including interruption and correction cases. Record the tested version and environment.
- Use Pass only when the expected evidence is observed. Fail means a demonstrated mismatch; Blocked means a dependency prevents a decision; Not tested means no test was performed.
- Keep must-pass failures and unknowns visible. Agree remediation and retests before signing acceptance; do not let a numerical average hide a critical blocker.
Fictional example: Offline capture and reconnect · Five sample events remain visible offline and synchronize once each. · Five captured; five distinct server events; no pending items. · Pass (fictional example) · Pilot lead: retain event export
Read the supporting guide ↗ · Version 1.0 · 14 September 2026
These templates support operational review. They do not replace official forms or your facility’s approved procedures. Examples and outcome labels are editorial illustrations, not CPCB API fields or status codes.
For the wider daily review process, read CBWTF SmartCare’s daily operations guide. Both websites are maintained by e-Planet.
Quick team checklists
Use the short prompts below for a discussion, or open a worksheet above to capture evidence and follow-up actions.
SmartCBWTF.in • Team: __________________ Date: __________________
HCF onboarding: a record that field teams can trust
Read the supporting guide ↗Owner: __________________ Next action: __________________
Biomedical waste barcodes: design the exception workflow
Read the supporting guide ↗Owner: __________________ Next action: __________________
12 data checks before a CPCB API submission
Read the supporting guide ↗Owner: __________________ Next action: __________________
How to evaluate CBWTF software with real scenarios
Read the supporting guide ↗Owner: __________________ Next action: __________________
These are operational discussion aids, not statutory forms or a complete compliance audit. Use the official reference sources and your facility’s approved procedures to establish applicable requirements.