---
title: Development Review Policy
---

**POLICY GOVERNING REQUESTS FOR CODE REVIEWS, PROJECT PLANNING CONSULTATIONS, AND TECHNICAL WRITING REVIEWS**

## 1. INTRODUCTION AND SCOPE

### 1.1. Policy Overview

This Development Review Policy ("Policy") establishes the terms, conditions, and procedures governing requests for code reviews, project planning consultations, and technical writing reviews from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.

### 1.2. Service Availability and Eligibility

**IMPORTANT: Development reviews are provided as a FREE service EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement. We reserve the right to verify community membership and activity before accepting any development review request.**

### 1.3. Legal Framework Integration

**IMPORTANT: This Policy does not create any binding obligations to provide development reviews or feedback. All development review requests are subject to our sole discretion and assessment of our relationship with the requester. Comprehensive disclaimers, warranty limitations, and liability protections are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**

### 1.4. Scope of Application

This Policy applies to:
**(a)** All requests for code reviews and feedback;
**(b)** All requests for project planning consultations;
**(c)** All requests for technical writing reviews;
**(d)** All development review-related communications and interactions.

## 2. TYPES OF DEVELOPMENT REVIEWS AVAILABLE

### 2.1. Code Reviews

**Code Review Services:**
**(a)** Review of specific code submissions, pull requests, or codebase sections;
**(b)** Feedback on code quality, best practices, and potential improvements;
**(c)** Suggestions for code organisation, structure, and maintainability;
**(d)** Recommendations for performance optimisation, security considerations, and testing;
**(e)** Code reviews are provided based on industry best practices and professional standards;
**(f)** We reserve the right to decline code reviews if code is incomplete, inaccessible, or exceeds reasonable scope;
**(g)** Code reviews focus on specific, bounded submissions rather than entire codebases.

### 2.2. Project Planning Consultations

**Project Planning Consultation Services:**
**(a)** Written consultation responses to plan new projects or side projects;
**(b)** Guidance on project architecture, technology stack selection, and technical decisions;
**(c)** Assistance with project scope definition, milestone planning, and timeline estimation;
**(d)** Recommendations for project structure, development workflows, and best practices;
**(e)** Project planning consultations are provided in WRITTEN FORMAT ONLY; we do NOT schedule calls or video meetings for consultations;
**(f)** Project planning consultations are provided based on industry best practices and professional experience;
**(g)** We reserve the right to decline project planning consultations if projects exceed our expertise or if we cannot provide meaningful guidance;
**(h)** Consultations are one-time written responses focused on planning rather than ongoing project management.

### 2.3. Technical Writing Reviews

**Technical Writing Review Services:**
**(a)** Review of technical blog posts, articles, documentation, README files, or other technical writing;
**(b)** Feedback on clarity, structure, technical accuracy, and audience appropriateness;
**(c)** Suggestions for improving readability, organisation, and presentation of technical content;
**(d)** Recommendations for formatting, code examples, and visual aids;
**(e)** Technical writing reviews are provided based on technical communication best practices and professional standards;
**(f)** We reserve the right to decline technical writing reviews if content is incomplete, inaccessible, or exceeds reasonable scope;
**(g)** Reviews focus on specific pieces of writing rather than ongoing content creation.

### 2.4. Development Review Limitations

**IMPORTANT DISCLAIMERS:**
**(a)** Development reviews are provided for educational and improvement purposes only;
**(b)** We provide constructive feedback based on industry best practices and professional standards;
**(c)** We reserve the right to decline any development review request at our sole discretion;
**(d)** We are not obligated to provide reasons for declining development review requests;
**(e)** Development reviews do not guarantee improved outcomes, project success, or publication acceptance;
**(f)** Reviews are provided as one-off services and do not include ongoing support or follow-up consultations.

## 3. REQUEST ELIGIBILITY AND REQUIREMENTS

### 3.1. Relationship Requirements

**ELIGIBILITY REQUIREMENT - ACTIVE COMMUNITY MEMBERSHIP:**

**IMPORTANT: Development reviews are FREE services provided EXCLUSIVELY to active members of our community. These services are NOT available to the general public or individuals who are not actively engaged in our community.**

For comprehensive eligibility requirements, eligibility criteria, and information about becoming an active community member, please refer to our [Community Membership Eligibility Policy](/about/community-membership-eligibility).

### 3.2. Request Information Requirements

**Required Information:**
**(a)** **Review Type**: Specify which type of development review is requested (code review, project planning consultation, or technical writing review);
**(b)** **Materials Access**: Provide access links, attachments, or materials to be reviewed;
**(c)** **Review Purpose**: Clear explanation of why the review is needed and what you hope to achieve;
**(d)** **Specific Focus Areas**: Any particular areas, concerns, or questions you'd like addressed;
**(e)** **Deadline Information**: Specific deadline for when feedback is needed, if applicable;
**(f)** **Relationship Context**: Brief summary of connection to our community or organisation.

### 3.3. Material Submission Requirements

**Submission Standards:**
**(a)** **Code Reviews**: Code must be accessible via GitHub, GitLab, or similar platform, or provided as files; code should be substantially complete and ready for review;
**(b)** **Project Planning**: Project ideas or proposals should be clearly described; existing project materials may be provided for context;
**(c)** **Technical Writing**: Writing must be substantially complete and accessible; documents should be provided via web URL;
**(d)** Materials must be substantially complete and ready for review;
**(e)** Incomplete or inaccessible materials may result in request decline or delay;
**(f)** We reserve the right to request additional information or clarification before accepting a development review request.

### 3.4. Request Submission Process

**Submission Requirements:**
**(a)** All development review requests must be submitted through our official development review request form;
**(b)** Requests submitted through other channels may not be processed or may experience delays;
**(c)** Incomplete requests may be returned for additional information before processing;
**(d)** We reserve the right to request additional information or clarification before accepting a development review request.

## 4. DEVELOPMENT REVIEW PROCESS AND TIMELINES

### 4.1. Request Review and Acceptance

**Review Process:**
**(a)** We review all development review requests to assess eligibility, material completeness, and our ability to provide meaningful feedback;
**(b)** Request review typically occurs within five (5) business days of submission;
**(c)** We will notify requesters of acceptance or decline within five (5) business days;
**(d)** Request acceptance does not guarantee review completion if materials are later determined to be incomplete or inaccessible.

### 4.2. Review Preparation Timeline

**Timeline Expectations:**
**(a)** Accepted code reviews and technical writing reviews are typically completed within seven (7) to ten (10) business days of acceptance;
**(b)** Project planning consultations are typically completed within seven (7) to fourteen (14) business days of acceptance;
**(c)** Rush requests may be accommodated at our sole discretion but are not guaranteed;
**(d)** Requesters should provide a minimum of two (2) weeks advance notice for development review requests;
**(e)** Requests with less than two (2) weeks notice may be declined or may not be completed by the requested deadline;
**(f)** We are not liable for missed deadlines if insufficient notice is provided or if requesters fail to provide required materials in a timely manner.

### 4.3. Review Delivery

**Delivery Methods:**
**(a)** All development reviews are provided in WRITTEN FORMAT ONLY and are delivered via email to the requester;
**(b)** We do NOT schedule calls or video meetings to conduct development reviews; all feedback is provided in written format;
**(c)** Review content includes written comments, suggestions, and recommendations;
**(d)** Requesters are responsible for providing accurate contact information;
**(e)** We are not responsible for delivery failures caused by incorrect contact information or email system failures;
**(f)** Requesters will be notified when reviews have been completed and delivered.

## 5. REVIEW CONTENT AND STANDARDS

### 5.1. Review Accuracy and Honesty

**Content Standards:**
**(a)** All development reviews are provided honestly and constructively based on industry best practices and professional standards;
**(b)** We will provide actionable feedback and specific recommendations for improvement;
**(c)** Reviews reflect our genuine assessment of materials based on professional standards and best practices;
**(d)** We reserve the right to decline requests if we cannot provide constructive feedback in good faith.

### 5.2. Review Scope

**Content Limitations:**
**(a)** Reviews address materials submitted and focus on professional best practices and improvement opportunities;
**(b)** We will not verify all factual claims or test all code functionality in detail;
**(c)** Reviews focus on quality, best practices, structure, and professional presentation;
**(d)** We are not obligated to address every aspect requested if it falls outside our expertise or review scope;
**(e)** Reviews do not include rewriting code, creating content, or implementing changes; feedback is provided for requester implementation.

### 5.3. Confidentiality and Privacy

**Privacy Protections:**
**(a)** Review content and submitted materials are confidential and shared only with designated reviewers;
**(b)** Review content and materials are subject to our Privacy Policy and data protection practices;
**(c)** We maintain confidentiality of development review requests and materials except as necessary for review provision or as required by law.

## 6. LIMITATIONS AND RESTRICTIONS

### 6.1. Development Review Limitations

**Service Limitations:**
**(a)** We reserve the right to decline any development review request at our sole discretion;
**(b)** We will not provide reviews if we cannot do so constructively and helpfully;
**(c)** We are not obligated to provide reasons for declining development review requests;
**(d)** Development review provision does not guarantee any specific outcome or result for the requester;
**(e)** Development reviews are provided for educational purposes and do not guarantee project success, code acceptance, or publication.

### 6.2. Frequency Limitations

**Request Frequency:**
**(a)** We may limit the number of development reviews provided to the same requester within a specified time period;
**(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritised at our discretion;
**(c)** We reserve the right to decline requests if we determine development review provision would be excessive or burdensome;
**(d)** Requesters should coordinate multiple review needs to minimise burden and ensure timely completion;
**(e)** Updated materials may be submitted for re-review after implementing previous feedback.

### 6.3. Scope Limitations

**Review Scope Restrictions:**
**(a)** **Code Reviews**: Limited to specific, bounded code submissions (e.g., single pull requests, specific features, or codebase sections); entire codebase reviews are a separate paid service;
**(b)** **Project Planning Consultations**: Limited to planning sessions; ongoing project management or implementation support is a separate paid service;
**(c)** **Technical Writing Reviews**: Limited to specific pieces of writing; ongoing content creation or editing services are a separate paid service;
**(d)** Development reviews are one-off services and do not include ongoing support, follow-up consultations, or iterative review cycles.

If you require long-term review, consider [hiring us as a consultant](/about/hire).

### 6.4. Prohibited Uses

**Restrictions:**
**(a)** Development reviews may not be used for purposes other than professional development and improvement;
**(b)** Requesters may not misrepresent review feedback or claim endorsements that were not provided;
**(c)** Development reviews may not be used to support fraudulent, illegal, or unethical activities;
**(d)** Violation of these restrictions may result in refusal of future requests.

## 7. LIMITATION OF LIABILITY AND DISCLAIMERS

### 7.1. Reference to Comprehensive Liability Framework

**IMPORTANT: Comprehensive liability limitations, damage exclusions, maximum liability caps, and all related legal protections are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference and governs all matters related to development review requests and provision.**

### 7.2. Development Review-Specific Disclaimers

**Additional Limitations:**
**(a)** Development reviews are provided as FREE services offered in good faith, to the best of our ability and knowledge;
**(b)** We are NOT liable for ANY outcomes, decisions, or results that arise from development reviews we provide, including but not limited to project success, code acceptance, publication, professional opportunities, or any consequences of implementing our feedback;
**(c)** What you do with the information, feedback, and recommendations provided in development reviews is YOUR OWN RESPONSIBILITY;
**(d)** We do not guarantee project success, code acceptance, publication, or professional opportunities based on our reviews;
**(e)** We are not responsible for third-party decisions, evaluation criteria, or acceptance processes;
**(f)** Our liability is limited to the maximum extent permitted by applicable law;
**(g)** Development reviews are provided "as is" without warranties of any kind;
**(h)** We are not responsible for requester implementation of feedback or changes made to materials based on our reviews.

## 8. REQUEST FORM AND SUBMISSION

### 8.1. Official Request Form

**Submission Channel:**
**(a)** All development review requests must be submitted through our official development review request form;
**(b)** The development review request form is available at: [Development Review Request Form](https://forms.nhcarrigan.com/o/docs/forms/3s8FCSwo4YtpMoptRmWxgU/4);
**(c)** Requests submitted through other channels may not be processed or may experience significant delays;
**(d)** The form collects all required information for development review request processing and preparation.

### 8.2. Form Completion Requirements

**Form Requirements:**
**(a)** Requesters must complete all required fields in the development review request form;
**(b)** Incomplete forms may be returned for additional information before processing;
**(c)** Requesters should provide accurate, complete information to ensure timely and accurate development review preparation;
**(d)** False or misleading information in request forms may result in request denial or review refusal.

## 9. CONTACT INFORMATION AND INQUIRIES

### 9.1. Development Review Inquiries

For questions about this Policy or development review requests:

**Email:** contact@nhcarrigan.com

**Subject Line:** Development Review Policy Inquiry - [Brief Description]

**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.

### 9.2. Request Status Inquiries

For questions about the status of submitted development review requests:

**Email:** contact@nhcarrigan.com

**Subject Line:** Development Review Request Status - [Your Name]

**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.

### 9.3. General Contact

For general inquiries about our organisation or services:

**Email:** contact@nhcarrigan.com

**Discord Community:** https://chat.nhcarrigan.com

## 10. ACKNOWLEDGEMENT AND AGREEMENT

### 10.1. Policy Acceptance

By submitting a development review request, you acknowledge that you have:
**(a)** Read, understood, and agree to comply with this Policy;
**(b)** Understood that development review provision is at our sole discretion;
**(c)** Provided accurate and complete information in your request;
**(d)** Acknowledged all disclaimers, limitations, and legal protections incorporated by reference.

### 10.2. Request Accuracy

**IMPORTANT: By submitting a development review request, you represent and warrant that all information provided is accurate, complete, and truthful. False or misleading information may result in request denial or refusal of future requests.**


---

*This Development Review Policy establishes the terms and procedures governing development review requests. This Policy does not create binding obligations to provide development reviews. All development review requests are subject to our sole discretion and assessment of our relationship with requesters. For questions about this Policy or to submit a development review request, please use the official development review request form or contact us at contact@nhcarrigan.com.*

