CivicActions Employees Handbook

Home
LICENSE
- 00 contributing
- README
- Docs governance
- File structure
- Git workflow
- How to get involved
- Markdown
- Read the docs
- Travis ci
- Writing style guide
- 01 welcome to civicactions
- Civicactions bio instructions
- Skillset survey
- Team resume instructions
- Welcome
- 02 about us
- Background and history
- Elevator pitch
- General contacts and listservs
- Mission values operating principles
- Org chart
- 03 policies
- Annual review process
- Benefits
- Code of conduct
- Compensation
- Employment
- Health safety security
- Leaving civicactions
- Prodev community participation
- Required stuff
- Security
- Travel 101
- Workplace guidelines
- 04 how we work
- Agileoverview
- Balance scores
- Bookmarks
- Common vocab
- Equipment
- Gold star program
- Training resources
- Virtual workplace basics
- 05 engineering
- Accessibility
- Back end development
- Dev environments
- Drupal site building
- Engineer role in client relationships
- Engineering roles
- Git gitlab github bitbucket
- Internalmeetings
- Qa
- Security compliance
- Systems sandboxes
- 06 project management
- Contract expiration tracking
- Contractual requirements
- Invoicing
- Listserv setup
- Offboarding contractor from project
- Onboarding new project team member
- Planning onsite meetings
- Pm role
- Pm training
- Pto request approval process
- Starting new project
- Templates
- 07 sales and marketing
- Civicactions website
- Sales guild
- Sales proposal process
- Social media
- 08 hr admin
- Offboarding process
- 09 security
- Awareness
- Drupal rmf support
- Encryption
- Incidents

CivicActions Employees Handbook

Docs »
07 sales and marketing »
California agile »
1 proposal response process
Edit on GitHub

California Agile Proposal Response Process

Proposal Response

Next Previous

Built with MkDocs using a theme provided by Read the Docs.

Read the Docs