Here’s the homepage draft. Let’s keep feedback in this thread before Friday’s review.
Homepage draft.pdf240 KBCoplace for public-sector teams
Keep work moving across departments.
Discuss work in department channels, keep decisions in shared notes, and see who owns each task. Review access, data location, and deployment requirements with your institution’s technical team.
launchOctober launch
Playing one sample message and reply.
Enter to send · Shift + Enter for a new line
Start with your institution’s requirements.
Daily use and technical evaluation are parts of the same plan. Identify a decision owner and a scope to review for each topic.
Departments and members
Define workspaces, team channels, and who will join. Plan administrator roles separately from everyday member access.
Data and network
Share data-location, file, calling, and network-access requirements with your technical team. Define the scope for cloud or deployment on your own servers together.
Evaluation and operations
Document a pilot team, use cases, acceptance criteria, and support responsibilities. Review institution-specific regulatory and procurement requirements separately.
Day-to-day work
Give departments a shared, current plan.
Add meeting decisions to a shared note. See the owner and status of follow-up work in the same workspace. Keep that context for the next conversation.
- A place for the conversation
- Start a discussion in a department or project channel. Keep replies about the same topic together.
- A record of the decision
- Keep meeting notes and the shared plan in Canvas. Add links to the relevant tasks.
- Work to follow up
- Give each task an owner, status, and date. Evaluate this flow with a real project during the pilot.
welcome
Open an example
The first-week plan
Our plan for welcoming new teammates.
Decision
We’ll start the first day with introductions and a short workspace tour.
Try editing the decision in this sample note.
Let’s keep the first-week guide in this channel’s Canvas tab.
What comes next
| Task | Owner | Status |
|---|---|---|
| First-week guide | Maya | In progress |
| Channel descriptions | Alex | In progress |
| First-day schedule | Jamie | To do |
Welcome tasksRelated link
Welcome planning notes
Monday · People and culture team
Agenda
- First-week guide
- Team channels and the people who can help
- The first-day schedule
Decision
We’ll add the team channels and people who can help to the guide. New teammates will tour the workspace together on their first day.
Try editing the decision in this sample note.
Guide: Maya. Channel descriptions: Alex. Schedule: Jamie.
Project planRelated link
Take a closer look at related topics.
Questions about your evaluation
How do we assess the fit for our institution?
Define use cases, the access model, data requirements, and technical acceptance criteria. Institution-specific legal and procurement conditions need a separate review within that evaluation.
Can we use our own infrastructure?
You can discuss Coplace deployment on your own servers with our team. Service scope, network access, and operating responsibilities are defined together during technical discovery.
Evaluate Coplace with your own work.
Share your use case, technical requirements, and open questions. We’ll define the pilot scope and acceptance criteria together.