ASSAMঅসম চৰকাৰGovernment of AssamLand Record
Time MachineOfficer sign-in

How it works

Who uses it, and how

From a scanned register page to a checked answer on any past date. Links to signed-in screens open the sign-in page first.

The record’s journey

  1. Scans uploadedAn administrator creates a volume (village, Jamabandi or Chitha, year) and uploads its scanned pages.
  2. Two operators type itTwo operators enter each row separately against the scan, without seeing each other’s work.
  3. Verifier checksRows where both agree are confirmed in one click; where they differ, the verifier decides from the scan.
  4. History builtEach verified register edition becomes a dated entry: grade B where the operators agreed, C where the verifier decided.
  5. Replay on any dateThe engine applies the changes in order and grades every value.
  6. Answer and reportOfficers read it directly; others request it. Each report is numbered and fingerprinted.
  7. Anyone checks itA report number shows whether the report is genuine and unaltered.

Pattadar, legal heir, advocate, court, bank or registration office

No sign-in

  1. Fill in the requestStart from “Request a past record” on the home page. Give your name, who you are, contact, village, dag, the past date, and the purpose. Advocates and courts add a case number. Tick the declaration of lawful interest.
  2. Keep two codesYou get a request number and an access code. The access code is shown only once.
  3. Circle Officer decidesThe officer checks who you are and why you need it, then approves, or rejects with a reason.
  4. Check status and collectEnter both codes. Once approved, the record is shown with grades for each value, and you can download it as a PDF.
  5. Anyone checks the reportA bank or court enters the report number to confirm it was issued and has not been altered.

Safeguards: At most 5 requests per connection an hour · nothing is shown before approval · a wrong code looks the same as an unknown number · every step is in the audit log

Circle Officer

Sign in: password, then one-time code · Demo account: co.dimoria, password password

  1. Start at HomeRecent parcels and the reports you have issued.
  2. Find a dag or villageSearch by village and dag, old dag number before the 1998 resurvey, or patta.
  3. Pick a date and a readingSee pattadars, shares, area, land class and map boundary on that date. "As the register stood" shows what the register said then; "As now known" includes corrections and decrees recorded later.
  4. Open the source pageEach value links to the scanned register page it came from.
  5. Flag an errorIf a value looks wrong, flag it from the parcel page with a note. The flag is saved and logged for the verifier to check against the source.
  6. Compare two datesSee what changed between them and which event changed it.
  7. Trace lineageFrom a parcel, open Lineage: a graph from the old dag through the 1998 resurvey and later partitions to today’s dags. Point at a dag to light up its line.
  8. See the whole villageEvery dag on a date on one map, and a check of the replay against today’s record.
  9. Search by personNeeds a reason, such as a case number. The reason is logged.
  10. Export a reportFrom a parcel, give a case number; the server rebuilds the record, numbers it and stores its fingerprint.
  11. Decide public requestsApprove to issue a report, or reject with a reason. Each request can be decided only once.
  12. See digitised registersDags built from verified rows, on any date, with each value linked to the scanned page and row it came from.
  13. Review the audit logEvery view, search, export and digitisation step, with a check that no entry has been altered.

Safeguards: Pages and APIs need a session · person search needs a reason · reports carry “Reconstructed view, not a certified copy”

Data-entry operator

Sign in · Demo accounts: operator.dimoria and operator.two, password password

  1. Pick a pageEvery uploaded page is listed with its status: not started, needs a second entry, ready to verify, verified or flagged.
  2. Type each row beside the scanRow number, dag, patta, pattadar, father’s name, share, area in bigha, katha and lessa, and land class. Edit or delete your own rows until they are verified.
  3. Blind double entryA second operator types the same page. Neither sees the other’s rows, so mistakes do not get copied. Sign in as both demo operators to try it.
  4. Flag what can’t be readMark a page blank, damaged or needing a rescan instead of guessing.

Safeguards: Operators see only their own rows · verified rows are locked · operators cannot see ownership history, the audit log, reports or admin pages

Verifier

Sign in · Demo account: verifier.dimoria, password password

  1. Verify typed pagesFor each row, both operators’ entries are shown side by side with differences highlighted. Pick the right value from the scan or type it, then confirm. Rows where both agree can be verified in one click.
  2. See digitised historyVerified rows become dated register editions, replayed on any date with grade B where operators agreed and C where you decided.
  3. Clear page flagsOnce a blank, damaged or rescanned page is dealt with, clear its flag so typing can go on.
  4. Error flags from officers (sample screen)Flags raised by officers on parcel values land here for checking against the source.
  5. Confirm events (sample screen)Link sales, inheritances, partitions and decrees to their order or deed with an effective date. Nothing overwrites an earlier record.

Safeguards: A row needs two operators before it can be verified · verified rows are locked for operators · each value keeps its source page and a grade of how sure it is

District administrator

Sign in · Demo account: admin.kamrup, password password

  1. Watch the pilotOverview of villages, pages published and open alerts.
  2. Upload register scansCreate a volume (village, Jamabandi or Chitha, year) and upload its pages as JPEG, PNG, WebP or PDF. Files are checked, stored outside the public site and shown only to signed-in staff.
  3. Track digitisationEvery page’s status, how many operators have typed it, and rows waiting for the verifier.
  4. Set up villages (sample screen)The villages in the pilot circle and their record coverage.
  5. Import and map today’s records (sample screen)Bring in present-day records for the reconciliation check.

Safeguards: Admin pages are closed to every other role except the state super admin · admins cannot create accounts or change roles

State super admin

Sign in · Demo account: super.assam, password password

  1. Manage every accountCreate accounts for any role, including administrators and other super admins, and see how many people hold each role.
  2. Change roles and reset passwordsA role change or password reset signs that person out at once, so the new access applies on their next sign-in.
  3. Remove accessRemoving an account ends its sessions immediately.
  4. Open any consoleAdmin, officer, verifier and digitisation pages and the audit log are all open to the super admin.
  5. Check what changedEvery account created, changed, reset or removed is in the audit log with who did it.

Safeguards: Only a super admin can open the accounts page · nobody can change their own role or remove their own account, so the last super admin always stays