Designed for: Web agencies and development studios handling recurring website edits, fixes and improvements.
The situation
A client has several small improvements in flight and asks for a status summary before each weekly meeting. Your team already records the work in Linear but manually assembles a client-facing update.
A concrete example
A maintenance client wants to update opening hours, add a contact form and fix a broken booking link. Track each as its own request so the client can see what is complete and what still needs attention.
Illustrative workflow, not a customer case study.
How the workflow fits together
- Associate the client’s work with their Linear Customer and review the portal’s visibility filters.
- Ask the client to submit each new piece of work as a separate portal request.
- Prioritize and update the underlying issues in Linear as your team works.
- Use the portal’s request statuses as a starting point for your next client review.
What to prepare
Agree which work belongs in the portal and how your team communicates status. Check that any visibility filter still includes completed requests you want the client to reference.
What to agree with the client
Request status does not establish retainer usage, budget remaining or contractual approval. Keep those commitments in your existing commercial process.
What to check in a pilot
- The client can find both current and relevant completed work.
- Your team keeps the underlying statuses up to date.
- The client understands how new requests are reviewed and prioritized.
Use the first-portal checklist to test the complete flow, or review the Linear connection and permissions.
Related workflow: Organize agency client requests.