Practical resources for running a community service: CMS, apps, systems, policies and procedures, governance, auspicing, fundraising and social enterprise.
Bring your service information, programs and daily workflows together. Talk with GSL about content management, client and case-management needs, and the systems behind a small community service.
Map intake, referrals, appointments and follow-up before choosing software.
Define staff roles, access permissions and who maintains information.
Plan record ownership, exports, backups and support.
Explore our worker and client companion projects: clearer first steps, less repeated administration and more involvement in support planning. Public launch and wider pilots are being prepared.
ptSolace: worker-facing intake, notes and support planning.
ptSola: a planned client pathway to share information and stay connected.
AI suggestions remain subject to human review; early registration is launch interest.
Build practical systems that people can use confidently: secure records, sensible permissions, repeatable processes and a plan for keeping the service running.
Create an access register and a process for staff joining or leaving.
Record what information you collect, its purpose and retention arrangements.
Plan backups, recovery, incident response and staff training.
Make your policies usable in everyday work. Start with a register, identify an owner, agree how each procedure is followed and keep versions and review dates visible.
Consider safeguarding, privacy and consent, complaints, incidents and boundaries.
Include volunteering, supervision, finance and conflicts of interest.
Adapt templates to your service and arrange the appropriate approval and training.
Read the refreshed review of GSL’s earlier homelessness and housing proposals. It separates current law, regulator guidance, funding arrangements and recommendations for reform.
Compare the earlier local-government, SAAP and NDIS recommendations with current sources.
Review the requirements relevant to present services and future residential projects.
Use a practical action register to track evidence, responsibilities and next steps.
Understand whether an auspicing arrangement could fit a community project. Use a clear project brief and discuss responsibilities before entering an arrangement.
Clarify the project purpose, budget, delivery capacity and funding conditions.
Discuss money management, reporting, insurance, fees and decision-making.
Agree the arrangement in writing, including how changes and the end of the project are handled.
Make a clear case for community support: the need, the work, the budget and how you will report what was achieved. Match fundraising ideas to the organisation's capacity.
Prepare a project brief, a realistic budget and an evidence plan.
Identify donation, grant, workplace and local partnership opportunities.
Check current fundraising requirements before launching a campaign.
Explore how community retail, reuse, skills and enterprise can contribute to a service's sustainability. Haven Collective connects GSL's Op Shop with online retail opportunities.
Connect your enterprise idea with your charitable purpose and community benefit.
Plan stock, pricing, costs, volunteer roles and customer experience.
Build business, retail, AI and IT skills through suitable training and partnerships.
Original GSL planning worksheets to download and adapt. The registers are CSV files that open in Excel or another spreadsheet app; the project brief opens in a text editor.
Policy register
Track policy owners, approvals, versions and review dates.
These are planning starters, not adopted GSL policies or a complete compliance pack. Adapt them to your organisation and confirm approvals and requirements with the relevant authority or adviser. Linked guidance remains with its publisher.
Build the next step together
Bring us your service idea.
Talk with GSL about your organisation, the problem you are trying to solve and the tools or partnerships that could help. CMS support, training, systems work and any auspicing arrangement depend on project fit, capacity and an agreed scope. This page does not create an agreement or grant access to staff systems.
For an initial enquiry, share your organisation and project overview. Keep identifiable client information out of the enquiry.