Control may transfer.
The obligation may not.
Put the head lease, assignment and sublease economics, candidate package, landlord consent, release language and closing evidence into one controlled Canadian transfer file.

Control the consent path before control of the premises changes.
This control file saves only on this device.
Identify the file, lease and intended transfer path.
A transfer label does not answer what rights exist, what premises move, who remains liable or what the landlord must receive.
Compare the entered cash paths without manufacturing market evidence.
These are deterministic user-entered scenarios. A lower present value does not establish feasibility, consent, candidate credit or a legal release.
Keep every remaining payment visible.
Enter the first increase, repeat interval, lease-year table or exact lease-month schedule. The transfer case does not erase the head lease. Read the plain-language timing guide →
Add cash items the standard fields leave out.
Each item is treated as cash in this schedule. Enter its basis, start and end month, and growth interval; keep allowances and concessions in their dedicated fields.
Model what is collected—and when.
The recovery can use its own percentage, fixed-dollar, lease-year or exact month schedule. Place deferred free rent and recovery growth separately. Read the plain-language timing guide →
Add cash items the standard fields leave out.
Each item is treated as cash in this schedule. Enter its basis, start and end month, and growth interval; keep allowances and concessions in their dedicated fields.
assignment is lowest on the current entries.
Scenario result only · not a recommendation or feasibility conclusion
Build the counterparty package before calling anyone selected.
Readiness measures only the nine entered workflow controls. It is not a credit decision, approval, registry verification or representation of suitability.
Missing controls: Legal name · Intended use · Proposed occupancy date · Source reference · Financial information · Business history · Signing authority · Insurance · Use review
Close the transfer file from source documents—not confidence.
A satisfied row means only that the user marked the workflow control satisfied. The Due Diligence handoff deliberately keeps verification unverified.
Resolve what can still break the transfer.
Issues are generated from explicit gaps and inconsistent states. They are not legal findings.
Record the executed document set and exact transfer-clause reference before relying on a transfer path.
Reconcile the transferred premises, area and any retained space to the operative lease and plans.
This workspace never infers consent, a reasonableness standard, waiver, approval or satisfaction of consent conditions.
Assume continuing tenant and guarantor exposure until qualified counsel confirms the executed release and surviving obligations.
Review transfer, replacement, replenishment, survival and release terms in every separate security instrument.
Model the exit. Then control the transfer.
Use the Exit Strategy engine for the complete remaining-liability comparison, then carry the candidate, consent, security, release and closing evidence through this workspace.