Skip to content

Cancellation Process - Functional Breakdown

NOTE Review along with full FRS

1. Overview

Cancellation refers to the process of nullifying an existing property record or transaction due to legal, administrative, or operational reasons. This process ensures that the property status is updated and all related endorsements are removed from the system.


2. Actors Involved

  • Maintenance Manager: Reviews and assigns tasks.
  • Officer: Captures cancellation request and validates documents.
  • Scrutinizer: Performs quality assurance and final checks.
  • System: Handles workflow routing, notifications, and updates to property records.

3. Inputs

  • Cancellation request letter.
  • Proof of authority (e.g., court order, official directive).
  • Supporting documents (e.g., title deed, previous transaction details).

4. Preconditions

  • Property record exists in the system.
  • All required documents are submitted.
  • Payment verification completed (if applicable).

5. Process Flow

  1. Capture Request
  2. Officer selects "Cancellation" process type.
  3. Uploads required documents.
  4. Completes mandatory fields (e.g., property ID, reason for cancellation).

  5. Validation

  6. System checks:

    • Mandatory fields completed.
    • Document formats correct.
    • Authority verification (court order or directive).
  7. Workflow Routing

  8. Task moves to Maintenance Manager for review.
  9. Manager assigns to Officer for processing.
  10. Officer completes data entry and submits for QA.
  11. Scrutinizer reviews and approves/rejects.

  12. System Actions

  13. Update property status to "Cancelled".
  14. Remove endorsements from diagrams and general plans.
  15. Trigger GIS update to reflect cancellation.
  16. Generate notification letters.

  17. Outputs

  18. Updated property record marked as cancelled.
  19. Notification letters sent to applicant and stakeholders.
  20. Audit trail updated.

6. Business Rules

  • Cancellation must be supported by legal authority.
  • All related endorsements must be removed before final approval.
  • Audit trail must capture every status change and user action.

7. Integration Points

  • Deeds Office API: For verification of title deed status.
  • GIS Service: For spatial data updates after cancellation.

8. Exceptions

  • Missing documents → Request returned to applicant.
  • Invalid authority → Process halted until resolved.
  • GIS update failure → Escalate to technical support.

9. Estimated Effort for Implementation

Component Effort Points (EP)
UI Form + Validation 6 EP
Workflow Routing 4 EP
Backend Logic 8 EP
Integration (Deeds/GIS) 6 EP
Document Upload & Output 4 EP
Testing (Unit + UAT) 6 EP
Total 34 EP

10. Key Screens

  • Capture Request Screen: Dynamic fields for Cancellation.
  • Maintenance Tab: Displays process status and linked documents.
  • QA Checklist Screen: For Scrutinizer validation.

11. Notifications

  • Email and system inbox alerts for:
  • Task assignment.
  • Approval/rejection.
  • Completion of process.

12. Audit Trail

  • Log every action:
  • User ID.
  • Timestamp.
  • Status change.
  • Comments.