Schedule output and sharing
Review the final schedule by camp
Switch the final SummerCan result into a camp-grouped view for provider-by-provider follow-through.
The problem
a child-by-child schedule is readable, but registration often happens by camp provider. For parents who want to handle registration or confirmation provider by provider, that means the hard part is not just finding camps; it is preserving the decisions that make the final family schedule trustworthy.
How SummerCan helps
SummerCan keeps a by-child view and a by-camp view for the same final result. SummerCan is a planning tool: it helps organize discovery, comparison, review, and schedule output while leaving final provider confirmation with the family.
How it works
- Start with setup: children, date window, location/source choices, and unavailable blocks.
- Use discovery to open a chooser-ready set of camp groups and dated sessions.
- Choose and review camp interests before the schedule builder runs.
- Use the final schedule, share link, provider links, and calendar output as the handoff for real-world follow-through.
Feature-to-benefit table
| Feature | Why it matters here | Example |
|---|---|---|
| By child toggle | Keeps the page focused on camp schedule by camp instead of generic camp browsing. | Cluster repeated camp titles together. |
| By camp toggle | Connects the family constraint to an observable planner surface. | Open provider links while working camp by camp. |
| provider grouped result cards | Turns reviewed decisions into a practical output families can inspect. | Keep the chronological timeline available beside the grouped summary. |
Use-case examples
Initial setup
Cluster repeated camp titles together.
Decision review
Open provider links while working camp by camp.
Schedule handoff
Keep the chronological timeline available beside the grouped summary.
Objections and limitations
Is this a replacement for provider registration?
No. SummerCan helps with planning and schedule organization. The actual provider remains the source for enrollment, availability, pricing, and policy confirmation.
What about stale demo data?
The public app displays a frozen Summer 2026 catalog notice. Treat demo data as planning context and verify details before relying on them.
How private is a shared schedule?
Shared schedule links are bearer links. Send them only to people who should see the read-only schedule.
FAQ
How does SummerCan help with camp schedule by camp?
SummerCan keeps a by-child view and a by-camp view for the same final result. The relevant product fit is By child toggle, By camp toggle, provider grouped result cards.
Does SummerCan book camps or guarantee availability?
No. SummerCan helps families organize discovery, comparison, preferences, and schedule output. Families should verify availability, pricing, policies, and enrollment directly with each provider.
What should a family prepare before using this workflow?
Have the children, ages, date window, unavailable blocks, and the schedule output and sharing decision context ready before moving into camp choice and review.
Can the finished plan be shared?
Yes, finished schedules can be shared through a read-only schedule link, and calendar output is available from the result page when the plan is ready.
What makes this schedule output and sharing page specific?
It focuses on a child-by-child schedule is readable, but registration often happens by camp provider, using By child toggle and By camp toggle rather than repeating a generic camp-planning checklist.
Plan with the family constraints in view
Switch the final SummerCan result into a camp-grouped view for provider-by-provider follow-through.
Open SummerCan