Manchester Referee Coordination: an evidence-led workflow

This is not a general filing exercise. It addresses the fact that a Manchester application depends on several referees, and defer the related handoff whenever a place label can replace an ownership plan.

For this tenancy file, record when the applicant authorised referee contact. In Manchester referee coordination, keep consent tied to the named referee and property or leave consent date unresolved.

For this tenancy file, confirm the referee's current email or telephone route. In Manchester referee coordination, use the route the referee or applicant supplied or leave contact route unresolved.

The source comparison begins at contact route, while availability window records what remains unanswered when a Manchester application depends on several referees.

For this tenancy file, capture when the referee says they can respond. In Manchester referee coordination, treat the window as a fact, not a promise or leave availability window unresolved.

For this tenancy file, describe the referee's relationship to the applicant. In Manchester referee coordination, use a plain label that the referee can recognise or leave referee relationship unresolved.

For this tenancy file, name the official source for the jurisdictional guidance. In Manchester referee coordination, link the exact government page used for the boundary or leave official local authority unresolved.

For this tenancy file, use the tenancy term published for the jurisdiction. In Manchester referee coordination, keep different nations' terminology out of the local file or leave local tenancy terminology unresolved.

The workflow does not begin with an upload. It begins with consent date, moves through contact route, and keeps availability window visible until referee relationship is assigned.

Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.

For an English tenancy application, use current GOV.UK private-renting guidance for the England boundary and confirm the recipient's application instructions separately.

GOV.UK's private-renting guidance is explicitly for England, which is the correct boundary for this Manchester reference workflow. Consent date records when the applicant authorised contact, contact route captures the address or telephone path actually supplied, and availability window remains a fact from the referee rather than an English rule. The agent's current referencing request supplies the timing; the national guide does not promise a Manchester response period. Private renting in England is the jurisdiction term retained for this Manchester guide.

Consent date and contact route sit under the England source boundary for Manchester referee coordination; availability window remains a property-recipient instruction.

GOV.UK does not turn its England guidance into a separate Manchester application rule.

No workflow status predicts acceptance. This evidence review ends at the evidence limit, with any unproven Manchester referee coordination item excluded.

In the sample handoff, a Manchester application depends on several referees. The applicant documents consent date, tests contact route, and keeps availability window provisional in the city scoped referee schedule. Defer the related handoff if a place label can replace an ownership plan; referee relationship identifies the route back to a decision. The scenario does not close until referee relationship has a supported route.

For this tenancy file, state the exact state, territory or UK nation covered by the source. In Manchester referee coordination, do not extend the source to a city-specific rule or leave exact geographic boundary unresolved.

For this tenancy file, keep every instruction and attachment linked to one identified property. In Manchester referee coordination, separate each active property's documents and instructions or leave property scope unresolved.