Standard Policies
Practical policies for project communication, approvals, change requests, temporary holds, resuming work, billing, and delivery expectations at mossmize.
These policies support transparent, consistent collaboration across Mossmize projects. They should be read together with the applicable proposal, statement of work, invoice, and terms of service.
Shared expectations
Clear responsibilities help both teams stay aligned before, during, and after delivery.
Change control
Scope changes are reviewed for impact before they affect cost, timeline, or delivery plans.
Hold and resume rules
Paused projects can restart smoothly once blockers, payments, and resource availability are confirmed.
The goal of these policies is simple: keep project work clear, documented, and fair for everyone involved. They help prevent uncertainty around pauses, changes, approvals, external dependencies, and delivery responsibilities.
1. Purpose and Scope
These Standard Policies explain the working practices mossmize follows for software development, consulting, product design, support, and related technology engagements.
They are designed to keep project responsibilities, communication, approvals, scope changes, holds, and handovers predictable. If a signed agreement or statement of work contains different terms, that written project document will control for that specific engagement.
2. Communication and Project Coordination
Each project should have a designated client owner who can provide decisions, feedback, approvals, access, and business context. mossmize may assign a project manager, technical lead, or account contact depending on the engagement model.
Project communication may take place through email, calls, project management tools, shared documents, messaging channels, or repositories. Decisions that affect scope, delivery, price, or acceptance should be confirmed in writing.
3. Client Inputs, Content, and Approvals
Clients are responsible for providing timely requirements, brand assets, content, credentials, third-party account access, test data, legal approvals, and any subject-matter guidance needed for the project.
When designs, milestones, documents, builds, or release candidates are submitted for review, clients should provide consolidated feedback within the agreed review window. Delayed or incomplete feedback may affect delivery plans and resource allocation.
4. Policy on Holding Projects
A project may be placed on hold when required information, feedback, access, approvals, payments, or decisions are not available for a reasonable period, or when the client asks to pause work.
During a hold, assigned resources may be released to other work, sprint schedules may be adjusted, and previously estimated dates may no longer apply. Any open invoices, committed costs, or completed milestones remain payable according to the applicable agreement.
5. Resuming Work After a Hold
To resume a paused project, mossmize may review current requirements, pending items, technical dependencies, third-party changes, resource availability, and any work needed to restart safely.
Resumption may require a revised timeline, updated estimate, refreshed discovery, environment review, dependency updates, or settlement of overdue amounts before active development continues.
6. Change Request Policy
A change request includes any new feature, altered workflow, revised design direction, integration change, architecture adjustment, content expansion, or requirement that was not part of the approved scope.
mossmize will assess change requests for feasibility, business impact, delivery impact, and cost. Work may begin after the client approves the revised estimate, timeline, or written change confirmation.
7. Minor Revisions and Rework
Reasonable minor refinements may be included when they are clearly within the approved scope and review window. Repeated revisions, new preferences after approval, dependency changes, or rework caused by incomplete requirements may be treated as additional work.
If rework is required because of a mossmize implementation issue within the agreed scope, mossmize will make reasonable corrections according to the project agreement or support terms.
8. Billing, Milestones, and External Costs
Invoices, retainers, milestone payments, hourly charges, or subscriptions are due according to the applicable proposal, statement of work, invoice, or agreement.
Third-party licenses, hosting, cloud usage, payment gateway fees, app store fees, domains, API charges, subscriptions, and other external expenses are generally the client's responsibility unless otherwise agreed in writing.
9. Delivery, Testing, and Acceptance
Deliverables may be shared through staging links, repositories, design tools, documents, packaged builds, deployment environments, or production releases. mossmize may use milestone reviews, sprint demos, QA cycles, and issue tracking to manage delivery quality.
A deliverable may be considered accepted when it substantially matches the agreed scope, is approved by the client, is used in production, or receives no material written objection within the agreed review period.
10. Third-Party Services and Dependencies
Projects often depend on third-party platforms, APIs, SDKs, hosting services, open-source packages, AI providers, payment processors, analytics tools, and app stores. Availability, pricing, policy changes, approval delays, and technical limits of third-party services are outside mossmize's control.
Clients should maintain ownership of business-critical third-party accounts and ensure that licenses, billing, permissions, and compliance obligations remain current.
11. Security, Access, and Credentials
Clients should share only the access required for the project and should use secure methods for credentials, production data, keys, certificates, and administrative accounts.
At project completion or termination, clients are responsible for reviewing access, rotating credentials where appropriate, and maintaining their production systems unless ongoing support has been agreed.
12. Policy Updates and Exceptions
mossmize may update these Standard Policies as services, tools, operating practices, and market conditions evolve. Updated policies apply when posted unless a signed agreement fixes different terms for an existing engagement.
Any exception to these policies should be documented in writing by authorized representatives of both parties.
13. Contact
For questions about these Standard Policies, please contact us at legal@mossmize.com.
Written scope
Confirm major decisions in writing before they affect the delivery plan.
Billing clarity
Milestones, retainers, and external costs follow the agreed commercial terms.
Approval records
Approvals and acceptance notes help avoid ambiguity during handover.