Prompt for Clear Remote Work Policies for Distributed and Secure Teams

#ROLE
Act as a senior remote work transformation architect with deep expertise in operations, internal policy design, organizational communication, and distributed work systems. Combine strategic thinking with the ability to turn abstract principles into practical, implementable company policies.

#CONTEXT
Your task is to design a complete, realistic, and company-specific remote work policy. The goal is not to produce a generic template, but to build an operational framework that balances flexibility, accountability, security, accessibility, individual autonomy, and team cohesion.

The organization is moving toward a remote or hybrid model and may be facing common issues such as:
- resistance from managers used to in-person oversight,
- IT concerns around security and compliance,
- leadership anxiety about productivity and visibility,
- too much or too little communication,
- inefficient meetings,
- cultural friction or time-zone challenges,
- outdated policies that do not reflect how the team actually works.
You must create a useful, actionable policy aligned with the company’s operational reality, tools, culture, and constraints.

#STEPS

**Step 1: Behavior**
- Take a breath and follow the process without skipping steps.
- Think step by step before drafting.
- Prioritize clarity, usability, and adaptation to the real context.

**Step 2: Initial diagnosis**
Before drafting the policy:
- assess the company’s current infrastructure,
- detect cultural or operational barriers,
- identify security and coordination risks,
- evaluate how performance is currently measured,
- review whether existing tools, norms, or policies must be integrated or corrected.

**Step 3: Request missing information**
If the user has not provided enough context, ask for the missing details before finalizing the policy. At minimum, request whatever is missing from:
- company size and industry,
- current collaboration tools,
- company culture and values,
- security or compliance requirements,
- geographic distribution and time zones,
- team roles,
- desired model (fully remote, hybrid, flexible, etc.),
- main current remote-work problems.

**Step 4: Policy design**
Build the policy including at least:
1. executive summary,
2. clear expectations for availability, working hours, response times, and deliverables,
3. tools and work stack,
4. meeting norms,
5. security protocols,
6. internal communication practices,
7. translation of company culture into remote behaviors,
8. outcome-based performance standards,
9. troubleshooting guidance for common issues,
10. recommendations for review and continuous improvement.

**Step 5: Quality criteria**
Make sure the policy:
- is actionable, not aspirational,
- balances structure with flexibility,
- addresses both synchronous and asynchronous work,
- includes adaptations by role, team, or time zone when needed,
- does not promote invasive surveillance,
- reduces both isolation and meeting overload,
- turns company values into observable remote behaviors,
- avoids one-size-fits-all thinking.

**Step 6: Final drafting**
Write the final document in a professional, clear, and operational tone. It should read like an internal policy ready for review by leadership, HR, or operations.

**Step 7: Final verification**
Before delivering:
- confirm the document is specific rather than generic,
- verify every section has practical logic,
- make sure the rules are implementable,
- ensure all important assumptions are stated clearly.

#RESPONSE FORMAT
Deliver the response as an internal policy document with this exact structure:

1. **Executive summary**
- Explain why well-designed remote work is a strategic advantage rather than a compromise.

2. **Purpose and scope**
- Define who the policy applies to, what it is meant to solve, and in what context it operates.

3. **Remote work principles**
- List the core principles guiding the system (trust, clarity, results, security, autonomy, coordination, etc.).

4. **Operational expectations**
- Working hours or availability windows
- Expected response times
- Deliverable norms
- Communication channel usage
- Urgent issue handling

5. **Tools and work stack**
- Approved platforms
- Expected use of each tool
- Documentation and traceability best practices

6. **Meeting norms**
- When meetings should happen
- When they should be avoided
- Recommended duration
- Rules for teams across multiple time zones
- Use of asynchronous work as the default where appropriate

7. **Security and compliance**
- System access
- Data protection
- Device usage
- Password management
- Secure connections
- Special rules if compliance requirements exist

8. **Communication and culture**
- How to maintain cohesion without overload
- How work visibility should be handled
- How company culture translates into remote behaviors
- Suggested rituals if they add value

9. **Performance and evaluation**
- How results should be measured
- Which metrics to use
- Which practices to avoid
- How to distinguish real productivity from performative presence

10. **Common issue resolution**
- Isolation
- Meeting overload
- Lack of clarity in priorities
- Technical problems
- Misalignment between managers and team members
11. **Context-specific adaptations**
- Recommended adjustments by role type, team, seniority, or time zone

12. **Review plan**
- Policy review frequency
- Who should review it
- What signals indicate the policy needs updating

13. **Recommended appendices**
- Tool quick guide
- Remote onboarding checklist
- Security protocol
- Internal FAQ

#TASK CRITERIA
1. Do not produce an empty or generic policy.
2. Prioritize concrete, understandable, and enforceable rules.
3. Maintain balance between operational control and trust.
4. Design systems that reward outcomes, not surveillance.
5. Avoid copying office dynamics without adapting them to remote work.
6. If key data is missing, ask clarifying questions before finalizing.
7. When useful, include concrete examples of how a rule should be applied.
8. If the user’s information contains contradictions, flag them and propose a reasonable solution.

#REQUIRED INFORMATION
Complete or request these details before generating the final policy:
- Company size and sector: [INSERT]
- Current collaboration tools: [INSERT]
- Company culture and values: [INSERT]
- Security/compliance requirements: [INSERT]
- Geographic distribution and time zones: [INSERT]
- Team roles and functions: [INSERT]
- Desired remote/hybrid work model: [INSERT]
- Current problems or friction points: [INSERT]
- Existing policies that must be respected or corrected: [INSERT]

#OUTPUT FORMAT
Return the policy in English, clearly structured, with useful headings, practical bullet points, and professional language ready for internal review.