Distinguish referrals from a joint service at Singapore partnership events

The problem

A Singapore nonprofit operator meets a potential partner and calls the idea a joint programme, but the two organisations have only agreed to introduce people to one another.

Start with the action both organisations actually mean

Write a verb before using a partnership label: share a public resource, introduce an appropriate contact, direct an enquiry to another service, coordinate an agreed handoff or jointly deliver specified work. Ask each side what its action would be and what remains proposed. NCSS describes a collaboration spectrum from competition to integration. It provides context for distinguishing levels, without prescribing a particular arrangement or validating your two organisations. NCSS’s collective-impact description concerns a structured partnership around a common agenda for a specific social problem; a shared event or friendly introduction does not establish that structure. Choose the level that answers the actual need rather than announcing the most ambitious description available. Find an appropriate contributor for the bounded programme task and confirm the actual contribution they can make.

• NCSS Collaboration ↗ · Source checked 20 October 2026

Name the receiving step as well as the contribution

A resource helps only at the scope it supplies. Identify who receives it, what they can do with it and which further question is still unanswered. A public contact address may supply a route for an enquiry without confirming that the receiving organisation accepts a case or provides the desired service. A suggestion to meet a team remains an introduction until the actual interaction occurs. Record the stated audience and scope of a supplied resource instead of applying it to a different programme. Avoid writing a beneficiary’s details into a public working example. This guide helps you inspect the proposed route; the organisations’ actual service, eligibility and information processes determine what may happen in a real handoff.

Make a contribution map with an explicit open condition

Use five columns: contribution agreed; party making it; recipient; next action expected from that recipient; and condition still needing confirmation. Add the record or response that establishes each agreed entry. Put proposed work in a separate row so it cannot be mistaken for an accepted responsibility. For a referral enquiry, the sender’s introduction and the receiving team’s acceptance answer different questions. For shared work, ask who owns the specific delivery step and how the other party learns its state. A map is a preparation aid rather than an agreement or authority to exchange records. One person may perform several actions, but do not collapse sending, receiving and deciding into a single completed label merely because the people already know one another.

Compare three invented ways to help the same team

In this wholly fictional case, Team R needs to identify where to ask about a learning resource for its own staff. Organisation S offers A: the link to a public resource directory; B: an agreed introduction to a relevant contact, with that contact’s response pending; or C: a proposed jointly hosted staff-learning session, with scope and organisers unconfirmed. A can resolve where R begins its search if the resource fits. B can establish an enquiry route while leaving the answer open. C adds delivery work and does not become ready because it sounds more collaborative. These are not NCSS offers, actual service referrals or present programmes. R can use a smaller contribution for its immediate information question without claiming acceptance into a service or shared delivery. If the directory does not answer the need, record that exact gap instead of calling A a failure for lacking a partnership label.

Follow one fictional handoff to the unanswered action

Extend offer B only as an invented process. S has agreed to make the introduction through an accepted contact route. R prepares its bounded resource question; the receiving contact has not yet answered. The map can record introduction sent only when it was actually sent, and response received only when it arrives. It cannot record a scheduled learning session from that sequence. Ask who should receive the answer, what it would establish and which enquiry remains if the contact cannot help. In a real service handoff, keep the actual permission, receiving conditions and organisational approvals separate from this paper exercise. A networking conversation authorises no transfer of personal case information. The example follows an organisational information question so it does not require beneficiary records or fabricate a service-acceptance rule.

Choose the smallest useful contribution without hiding its limit

Ask what decision the present contribution lets you make. A relevant public resource might help you formulate the next enquiry; an agreed introduction might identify the right receiving person. Neither must become a co-delivered programme to be useful. Keep the evidence of help at its actual scope: resource obtained, question clarified, contact response received or proposed work awaiting approval. Contact count and an enthusiastic conversation do not establish programme outcomes. Do not add ongoing advice to a one-time resource offer or repeatedly enlarge a request because the other party was generous. If another contribution would help, describe it as a new optional request through the agreed route. The contribution map should make a remaining gap visible rather than making the smaller offer appear to solve more than it does.

Specify the extra work before moving toward joint delivery

When shared delivery is actually needed, identify the activity each party would perform, the receiving role, preparation and availability, decision route and question raised when a handoff cannot proceed. Ask which responsibilities have been approved and which need another conversation. Keep a task-and-capacity note with the actual contribution and available time; a common mission does not supply staffing. Keep a training contribution separate from implementing the capability through the existing learning-versus-deployment companion. Use the shared-indicator companion before combining activity counts. Those are distinct investigations that a partnership label cannot settle. No standard allocation of costs, legal responsibility, data access or escalation is prescribed here. Establish actual terms through the responsible organisational process before representing proposed work as ready.

Describe the resulting arrangement accurately after follow-up

Retain the contribution map and the latest actual response. Summarise what is agreed, what happened, who owns the next action and what remains unanswered. Ask the responsible parties to resolve unclear descriptions before announcing a joint programme. A successful introduction can remain an introduction; confirmed shared work should be described only at its approved scope. If the next proposal changes the activity, do not silently extend the earlier resource or referral answer. Use Boardzip’s free partnership-event search when another organisational discussion would address the remaining question, then verify the programme’s participant roles and working format. Search access is free, while event entry and any later arrangement have their own conditions. An accurate smaller result is a usable record even when no current verified event or approved shared service resolves the larger need.