What's new in v1.3

Since v1.2 the platform gained its productisation layer — subscriptions/billing, a property-agent referral program, account blocking and a public brand refresh — and the tenancy authority model was tightened. Additions since v1.2:

Tenancy authority is landlord-only. The PMCA is now read-only on tenancies — no invite / create / edit, and no amend or terminate. Those belong to the landlord. (This supersedes the v1.2 "PMCA acts with landlord-side standing" note below.)
Subscriptions & billing. PMCAs submit a bKash/bank payment proof (monthly/annual); the super admin approves or rejects; expiry triggers a read-only lock; renewals stack; the super admin can extend / grant grace.
Property Agent program. A new agent role: self sign-up + KYC + super-admin approval, a referral code, referral capture at PMCA sign-up (link or manual code) and adoption by existing PMCAs, commission on approved payments, a sales pipeline, an opportunity pool with claims, and payouts. See Tester 4.
Block & account. PMCA→landlord, landlord→tenant and super-admin→PMCA block / unblock, with role-appropriate login-denial messages.
Comms & invite actions. A public Contact-Us (Turnstile) feeding a super-admin Messages inbox; Resend / Change-address / Revoke on PMCA-admin and tenant invites.
Public brand refresh. New logo across the site, a Bengali wordmark and a new hero on the landing page.

Heads-up on the tenancy steps below. Where older guidance says a PMCA can invite a tenant or amend / end a tenancy, that no longer applies — the PMCA tenancy pages are view-only. The landlord drives those flows.

Note on production Production (ghorduar.com) has gone live with a clean slate — only the super-admin account exists, and real onboarding begins with the super admin inviting the first PMCA. You are still testing on staging.ghorduar.com, which keeps its full test dataset.

Earlier — v1.2 (note: the PMCA tenancy standing below has since been removed)

Tenancy lockdown. Once a tenancy leaves Draft, its terms can't be edited directly; the edit page is read-only and points to the Amend or End-tenancy workflow.
Amend a tenancy. A change (rent, deposit, service charge, end date) is proposed with an effective date; the tenant must agree before it applies; it auto-applies on the effective date.
End a tenancy (mutual termination). One side requests; the other agrees on an effective date; the unit returns to Vacant when it applies.
Signed addendum. When a tenant agrees to an amendment, GMS generates a formal Addendum to Rental Deed with both electronic signatures.
Dashboard auto-apply. Due amendments/terminations apply on any tenancies-dashboard load.

Earlier — what was new in v1.1

In-browser camera capture for KYC photos (NID front, NID back, selfie) with automatic resize.
Auto-populated "From your registration" panel on the tenant police-report form.
Tenant Submit & sign — electronic signature with timestamp + IP; form locks after signing.
Landlord Return to tenant — sends the report back with a required note; tenant revises and re-signs.
PMCA Police Reports view-only compliance overview; Landlord Police Reports list.
Police-report form prints on a single A4 page in DMP format.

Welcome — read this section first

Thank you for testing the Ghorduar Management Systems (GMS) staging build. This manual is for the role-specialised testing model: three testers, each playing one role, exercising the system as a real-world relay.

You only need to read your own role's guide after this section, but skimming the others gives useful context for the handoffs.

The big picture

GMS is a property & tenancy management system for Bangladesh. It serves four kinds of users:

Role	What they do
Super Admin	System-level oversight; sees all PMCAs, creates them.
PMCA Admin	Manages a Property Management & Caretaker Association (a housing society or cooperative). Invites landlords, reviews their KYC, oversees compliance.
Landlord	Owns or manages one or more units in a PMCA-registered property. Invites tenants, signs agreements, files police reports.
Tenant	Rents a unit. Signs the Rental Deed electronically, fills the police-report form, signs and submits to the landlord.

How this round of testing works

Three testers, three roles. You hand work off to the next tester via the system's own invitation flows — real emails get sent, real links get clicked, real handoffs happen. That makes the test much closer to production usage than if one person played all roles.

Tester	Role	Primary workflow
Tester 1	PMCA Admin (+ super admin set-up)	Creates the org, invites the landlord (Tester 2), reviews KYC, monitors compliance, records observations in the QA Test Tracker.
Tester 2	Landlord	Accepts invite, completes KYC via camera, invites the tenant (Tester 3), countersigns agreements, manages police reports.
Tester 3	Tenant	Accepts invite, completes KYC via camera, signs the Rental Deed, fills + electronically signs the police-report form.

Where you're testing You're testing on staging.ghorduar.com. Anything you create here is throwaway test data. The yellow banner at the top of every page reminds you that you're on staging, not production.

Before you begin

1. Browser setup

Use Chrome, Edge, or Safari on a recent version. Each tester works in their own browser session — if you must share a computer, use separate browser profiles (Chrome → profile picker → Add) or open one window in Incognito and one normal. Do not log in as multiple roles in the same browser session at the same time.

2. Email addresses for invitations

During testing you'll need separate email addresses for each handoff. Real Gmail addresses with the plus-address trick let you have many functional inboxes from one Gmail account: yourname+landlord@gmail.com, yourname+tenant1@gmail.com, etc. All of those deliver to yourname@gmail.com, but the system treats each as a different user.

Tip Decide your plus-addresses in advance and write them down. Example: jane+gmsland@gmail.com for the landlord account, jane+gmstn1@gmail.com for the first tenant.

3. Login for Tester 1

Your initial super-admin credentials are sent to you separately by the reviewer. Once logged in, you'll create a PMCA organisation and become the PMCA admin via invitation.

4. Coordination channel

Set up a shared chat (WhatsApp / Slack / Telegram — whatever you already use together). All three testers should be in it during the test session. The handoff points are listed in the next section.

5. Camera permission

The KYC step uses your browser's camera to capture NID front, NID back, and a selfie. The browser will ask permission once at the start of the KYC form. Click Allow. Audio is not requested.

Coordination playbook

Thirteen handoff points between testers. Whoever finishes the task on the left messages the next tester to start theirs.

#	Tester 1 (PMCA)	Tester 2 (Landlord)	Tester 3 (Tenant)
1	Creates PMCA org & invites Tester 2 →
2		← Accepts invite, completes KYC & waits
3	Reviews + approves Tester 2 KYC →
4		Adds property + units, invites Tester 3 →
5			← Accepts invite, completes KYC
6		Approves tenant KYC →
7			Signs Rental Deed →
8		Countersigns the Rental Deed →
9			Fills + Submit&sign police report →
10		Returns once (deliberate test) →
11			← Edits + re-signs
12		Records submission to thana →
13	PMCA monitors via Police Reports page

Optional rotation round After step 13 the linear pass is complete. If time and energy allow, do a rotation: Tester 1 becomes Tenant, Tester 2 becomes PMCA, Tester 3 becomes Landlord, using new plus-addressed emails. Fresh eyes on each role catch UX issues that the specialist gets used to.

Tester 1 — PMCA Admin your role

You set up the world and oversee compliance. You also own the QA Test Tracker and record observations from all three testers.

Your steps in order

Log in as super admin with the credentials you received separately. URL: https://staging.ghorduar.com/login.php. You land on the super-admin dashboard.
Create a PMCA organisation. Super Admin → PMCAs → Add new. Fill in name (English + Bangla if applicable), short name, type (cooperative), office address, email, phone. Save.
Invite yourself as the PMCA admin. On the PMCA detail page, click Invite PMCA admin. Use a plus-addressed Gmail like you+pmca1@gmail.com. The invitation email arrives in your real Gmail inbox.
Accept the invitation. Click the link, complete registration (name, mobile, password). You're now a PMCA admin. The left sidebar should read "PMCA: [your org name]".
Invite Tester 2 as a landlord. PMCA Admin → Landlords → Invite landlord. Use Tester 2's plus-addressed email (they'll tell you). Send invitation. → Message Tester 2: invite sent, check inbox.
Wait for Tester 2's KYC. They'll message you when ready. PMCA Admin → KYC Review → open their submission → check NID photos + selfie for clarity → click Approve KYC. → Tell Tester 2: KYC approved.
Wait while Tester 2 adds property + units and invites Tester 3. No action from you during this stretch.
Approve Tester 3's KYC when it appears in KYC Review. Same flow as step 6. → Tell Tester 3: KYC approved.
Watch the workflow play out. Testers 2 and 3 sign the Rental Deed; Tester 3 fills the police report and signs it; Tester 2 returns it once, Tester 3 re-signs; Tester 2 marks it submitted to thana.
Open PMCA Admin → Police Reports. This view-only page should show every police report across your PMCA. Verify the status column updates correctly as Testers 2 and 3 progress.
Throughout the session, log observations in the QA Test Tracker (see the section further down). You're the scribe — the others tell you what they saw and you log it.

Specific things to verify (the polish from v1.1)

Tester 2's KYC photos look reasonable in size and clarity (camera capture working).
PMCA → Police Reports page loads and shows rows for your org only.
The page is view-only — no submit, return, or edit buttons.
Status colours update through the lifecycle: Awaiting tenant → Tenant filled (not signed) → Signed — awaiting landlord → Returned to tenant → Signed — awaiting landlord (after re-sign) → Submitted to police.
Overdue rows highlight red when due_date is past.

Tester 2 — Landlord your role

You receive your invitation from Tester 1, complete KYC via your browser camera, then orchestrate the tenancy with Tester 3.

Your steps in order

Wait for Tester 1's message that an invitation has been sent. Check your Gmail inbox using the plus-address you gave them.
Click the invitation link in the email. The browser opens a registration page pre-filled with your invited email.
Complete registration — create a password, enter your full name and mobile number.
Complete KYC. The KYC page opens automatically (mandatory before anything else). Fill personal details (name as on NID, NID number, DOB, gender, profession, current and permanent addresses). In section 4 "Documents":
- Click Take photo next to NID — front. Allow camera permission. The modal opens with the rear camera. Hold up your NID, tap Capture, review, tap Use this photo. A thumbnail appears next to the file input.
- Repeat for NID — back.
- For the selfie: same flow but the modal uses the front camera. Hold your NID next to your face, capture.
Submit KYC. → Message Tester 1: KYC submitted, please review.
Wait for the KYC-approved message. Once approved, your landlord dashboard becomes fully functional.
Add a property and at least one unit. Landlord → My Units. If no property yet, you'll be prompted to add one first (name, address, division, thana, police force). Then add a unit (unit number, floor, type).
Invite Tester 3 as a tenant. On the unit row, click Invite tenant. Use Tester 3's plus-addressed email. Set monthly rent, start date, optional end date. Send. → Tell Tester 3: invite sent.
Approve Tester 3's KYC when prompted in Landlord → Approvals. (Tester 1 / PMCA may also need to approve depending on the configured flow.)
Wait for Tester 3 to sign the Rental Deed. When done, the Rental Deed appears under Landlord → Rental Deeds with status "Awaiting your countersignature".
Countersign the Rental Deed. Open it, scroll to the bottom, click I countersign. The tenancy becomes Active and the police-report row is auto-created.
Wait for Tester 3 to fill + Submit & sign the police report. When done, open Landlord → Police Reports. The report shows status "Awaiting your submission to police".
Practice the Return-to-tenant flow. Open the report. Scroll to "Need the tenant to fix something?". Type a specific note like "Please add your daughter's name to the family members list." Click Return to tenant. → Tell Tester 3: returned with a note, please re-sign.
Wait for Tester 3 to re-sign. Once they do, the report comes back with a fresh signature.
Print the police-report form. Click Print form. Confirm it prints on a single A4 page with only the tenant signature line (no landlord line) and no chrome.
Record submission. Set today's date, optionally upload a fake receipt image, click Mark as submitted. Status changes to "Submitted to police".

Specific things to verify (the polish from v1.1)

Camera capture works for all three photos; thumbnails preview correctly.
If you deny camera permission, Choose file fallback still works.
Sidebar shows the new Police Reports nav item between Rental Deeds and Approvals.
List view shows all reports with correct status colours and overdue highlighting.
After Tester 3 signs, the landlord page shows "Signed by the tenant on [date], (IP X.X.X.X)" banner.
Return-to-tenant requires a note — empty note is rejected.
You cannot mark the report submitted until the tenant has signed.
Print preview: single A4 page, no blank page 2, no staging banner, only one tenant signature box on the left half.

Tester 3 — Tenant your role

You're the resident of a unit. You receive an invitation from Tester 2, complete KYC, sign the Rental Deed, and fill the police report. You exercise the trickiest piece: the "return & re-sign" edit cycle.

Your steps in order

Wait for Tester 2's message that an invitation has been sent.
Click the invitation link in the email. The browser opens a registration page pre-filled with your invited email.
Complete registration — password, full name, mobile.
Complete KYC. Same camera-capture flow as Tester 2 (NID front + NID back + selfie via browser camera). Submit. → Tell Tester 2: KYC submitted.
Wait for KYC approvals from Tester 1 (PMCA) and Tester 2 (Landlord). Once approved, you'll get an email saying the tenancy is ready.
Sign the Rental Deed. Tenant → Rental Deed. Read carefully (prepared by the landlord from the clause library, with the rent and dates filled in). Tick "I have read and agree", click I agree. Status becomes "Awaiting landlord countersignature". → Tell Tester 2: signed.
Wait for Tester 2 to countersign. Once they do, your tenancy becomes Active and a yellow banner appears on your dashboard (Pending police report).
Open the police-report form. Tenant → Police Report. At the top you'll see a read-only From your registration panel with your name, NID, DOB, gender, mobile, email, permanent address, property/unit, move-in date. Verify these are correct — they'll appear on the final form.
Fill in the manual fields: father's name, marital status, religion, occupation, workplace, education, emergency contact, family members (if any), helpers (if any), previous tenancy (if any).
Click Save draft first. Reload the page; verify your values are preserved and the form is still editable.
Click Submit & sign. A confirmation dialog appears. Click OK. The page refreshes — form is now locked, shows a green "Signed on [date+time]" banner, and the rendered document below shows your electronic-signature line. → Tell Tester 2: signed, please review.
Tester 2 will deliberately return the report. When they do, you'll see a yellow banner at the top: "Returned by your landlord on [date] with the note: [their note]". The form becomes editable again.
Edit per the note. For example, if they asked you to add a family member, fill in that row.
Click Submit & sign again. Same confirmation flow. The report is now signed with a fresh timestamp + IP. → Tell Tester 2: re-signed.
Optional: print preview. Click Print / save copy. Verify the form is a single A4 page with only your signature line at the bottom-left.

Specific things to verify (the polish from v1.1)

The From your registration panel shows the right data and is read-only.
Save draft preserves edits without locking the form.
Submit & sign requires confirmation and locks the form afterwards.
After signing, you see the e-signature provenance line ("Electronically signed by [name] on [date], IP X.X.X.X") on the rendered form.
Camera capture during KYC produces small files (no "file too large" errors).
After being returned, the yellow banner clearly shows the landlord's note and the form unlocks.
Tenant dashboard nav says My Unit (not "My Home").
Sidebar header shows "Ghorduar Management Systems" on top and "Tenant: [PMCA name]" below.
Print preview: single A4 page, no blank page 2, no staging banner, only your wet-signature line on the left half.

Tenancy changes — amend, end, addendum

These flows are new in v1.2 and touch all three roles. Run them after the main relay (once a tenancy is Active). They share one golden rule: an active tenancy's terms are never edited directly — every change is a proposal the other side reviews.

Amend a tenancy (change rent, deposit, service charge, or end date)

Propose — as Landlord (/landlord/amend.php) or PMCA admin (Tenancy view → Propose amendment). Change one or more values, set an effective date a few days out, give a reason, submit.
Tenant reviews — Tenant sees a banner and a "current → proposed" table at /tenant/amend.php; clicks I agree (or declines with a note).
Applies — on the effective date the new terms take effect automatically; the badge clears.

Verify: while pending, nobody (not even the proposer) can edit the amendment; the proposer can withdraw it.
Verify: a too-soon effective date and a "no fields changed" amendment are both rejected.
Verify (PMCA standing): a PMCA-proposed amendment shows on the landlord's page as "PMCA admin requested this on your behalf".

End a tenancy (mutual termination)

Request — any of Tenant (/tenant/terminate.php), Landlord (/landlord/terminate.php), or PMCA (/pmca/terminate.php): pick an effective date + reason.
Other side responds — the counterparty agrees or declines. The requester (or their side) can withdraw while pending.
Applies — on the effective date the tenancy ends and the unit returns to Vacant; it can be re-rented.

Verify: the requester can't agree to their own request; only the other side can respond.
Verify (PMCA): a PMCA request emails the tenant (not the landlord); the tenant's dashboard banner names the actual requester.
Verify (PMCA): the PMCA can respond to a tenant-initiated request on the landlord's behalf.

Signed addendum

When the tenant agrees to an amendment, GMS produces a formal Addendum to Rental Deed (references the original agreement, lists old→new terms, shows both electronic signatures).

As Tenant: after agreeing, a View signed addendum button appears on the amend page and the dashboard banner.
As Landlord / PMCA: open the tenancy view → View signed addendum (agreed card, or the Doc column in amendment history).
Verify (access control): a user from a different PMCA who opens the same addendum link gets "Not found".

Dashboard auto-apply

To check that due changes apply on their own: get an amendment to agreed, ask Tester 1 to set its effective date to today in phpMyAdmin, then simply load the tenancies list for any role — the badge should clear and the new terms appear, without opening the amend page.

Tester 4 — Property Agent optional role

Property agents refer PMCAs to Ghorduar and earn commission when a referred PMCA subscribes. Run this as a 4th person, or as Tester 1 in a second browser profile.

Your steps in order

Sign up as an agent. Open the public Property Agent sign-up page and register with a +addressed email. You land in a pending approval state — the dashboard isn't available yet.
Submit KYC. Complete the agent KYC. → Tell the super admin: agent KYC submitted.
Wait for approval. The super admin approves you and sets your commission % and area (police force → thana). You now have a referral code and can log in to the agent dashboard.
Share your referral. Copy your referral link (request-access.php?ref=YOURCODE) or the code. Have a brand-new PMCA sign up through it — or have an existing, unattributed PMCA adopt your code (via the link after signing in, or the Referral code field on their Subscription page).
Watch the pipeline. Open Sales Pipeline — your referred PMCA appears with a derived status (Demo / Payment pending / Active-paid / Lapsed / Suspended).
Earn a commission. When that PMCA submits a payment and the super admin approves it, a commission accrues (rate × amount) under Commissions. Nothing accrues before approval.
Opportunities & claims. Open Opportunities — unattributed self-signed PMCAs in your thana are claimable. Claim one (only one agent can hold an active claim); unconverted claims auto-release after 30 days.
Get paid. When the super admin records a payout to you (optionally with a proof slip), confirm receipt from your side; an unconfirmed payout auto-confirms after 7 days.

Specific things to verify

A PMCA never sees your name — only the referral code.
A code, once adopted by a PMCA, can't be switched to a different agent (first valid adoption wins).
Commission is created only at payment approval and never double-credits on re-approval.

Super-admin checks Tester 1 also

Beyond setting up the world, the super admin owns several productisation flows. Verify each on staging:

Subscriptions. Review the payment queue; approve (PMCA activates, tier + period set) or reject with a reason (PMCA can resubmit). Check the expiry read-only lock, renewal stacking, and calendar Extend / Grant grace.
Agent approvals. Approve a pending agent, set commission % + area; confirm the referral code is generated.
Commissions & payouts. See accrued commissions per agent; record a payout (declare → record → confirm) with an optional proof slip.
Messages. Open the Messages inbox; move a Contact-Us submission new → read → closed; watch the unread badge.
Blocks. Block / unblock a PMCA admin and confirm the blocked-login message.
Attribution override. On a PMCA, re-assign or clear the referral agent — the only place a locked code can be changed.

QA Test Tracker

All three testers feed observations into one shared place: the QA Test Tracker on staging. Tester 1 typically owns the tracker (they finish their direct setup work fastest), but the other testers can also add rows.

How to access

The yellow banner at the top of every staging page has an Open QA Test Tracker → link. Click it. You'll see all defined test cases grouped by section.

How to record an observation

For each test case you encounter:

Run the test (it's described in the case).
If it works as expected, set the dropdown to Pass.
If it doesn't, set to Fail and write what went wrong in the notes box. Be specific: which page, what you clicked, what you saw vs. expected.
If you can't run it (other tester not ready, not applicable to your role), leave as Not run.
Click Save.

Tip — good bug report URL + numbered steps + what you expected + what actually happened + screenshot if visual. Clear, specific, factual. Don't worry about being polite or hedging.

Glossary

PMCA	Property Management & Caretaker Association — a housing society, cooperative, or similar entity managing one or more properties.
KYC	Know Your Customer — identity verification by NID + selfie + address. Done once per user; gates access to all features.
Tenancy	A specific period during which a tenant rents a specific unit. Has start date, optional end date, monthly rent.
Rental Deed	Auto-generated rental contract. Signed electronically by tenant, countersigned by landlord.
Police Report / TIF	Tenant Information Form — landlords are required to file this with the local thana when registering a new tenant. GMS generates it and tracks submission.
Thana	Local police station. Each property is mapped to one.
DMP	Dhaka Metropolitan Police — metropolitan force covering Dhaka.
NID	National Identity Card — Bangladesh government-issued photo ID. Number can be 10, 13, or 17 digits.
Plus-addressing	Gmail feature: `name+anything@gmail.com` delivers to `name@gmail.com` but the system treats each as a unique address.
Reviewer	The person coordinating the test (Mahmud) — reads tracker entries and follows up on bugs.

Thanks for taking the time to do this carefully. Specific, factual observations are what make the difference between a smooth launch and a rough one.

— Muhammad Mahmud Hussain, Reviewer
Ghorduar Management Systems