Get onboarded, meet your team, and start building
Starting a new mission? Your first week at work is critical to setting you up for success. You’ll sign contracts, set up payments, establish your points of contact, meet your new teammates, and create a solid foundation for your mission going forward.
Here’s your course of action for onboarding to a new mission:
Step 1: Sign the Mission Code of Conduct
After being selected for your first mission, your A.Team account will start to look a bit different. Next time you log in, you’ll be asked to agree to the Mission Code of Conduct. Take some time to read through it — it’s filled with important guidelines about what’s expected from you while working on a mission.
Step 2: Find your mission homepage
You’ll see a new button on your navigation menu (on the left side of your screen) — a colored circle with the first letter of your mission. This your mission homepage. Each mission you join has a homepage that contains the timesheet, documents, and other details relevant to that specific mission. It’s where you’ll log your hours, submit your Team Pulses, and your contracts.
Step 3: Sign your contract
Before you start any work, review and sign your contract. From the Mission homepage, go to the ‘My Documents’ tab. At the top, you’ll see ‘Agreements’.
Click ‘View’ on the pending agreement to see your contract.
Once you’ve read the agreement, check ‘Click to accept’ and then hit the ‘I Accept’ button to digitally sign. After that, the status of this agreement will change from ‘Pending’ to ‘Signed’ in the ‘Builder Status’ column.
When the company counter-signs the agreement, the ‘Client Status’ column status will also change from ‘Pending’ to ‘Signed’.
Clicking on ‘View’ will pull up the agreement — which includes the signed contract, your hourly rate, and the dates the agreement was signed by both you and the company.
Step 4: Set up your payment method
After you join a mission, you'll get a notification to set up your payment method. We advise you take care of this right away — you won’t be able to submit your timesheets or get paid until after you set up your payments.
Once you set up your payment method, our payment processor (Tipalti) will take a few days to review and approve your details. After that, you’ll be able to start submitting your timesheets and getting paid. (Learn more about setting up payment and submitting tax forms here.)
Step 5: Join your mission’s Slack channel
Now for the fun part — joining your missions’ private Slack channel.
Your private mission channel will include all the builders on the mission, and members from our Mission Success team who are here to support you. This channel is for intra-A.Team communication (i.e. check-ins about your mission, questions about payments/invoicing, etc.) and general team communication.
Step 6: Team and mission kickoff calls
After you’re all set up with contracts, payments, and Slack — keep an eye out for kickoff call invites.
If two or more builders are on your mission, our Mission Success team will schedule a team kickoff call. This is where you’ll meet your new teammates and Mission Success representative for the first time, and ask us anything about A.Team and your new mission. This call will prepare you to meet the company at the mission kickoff as a unified team.
After you’ve completed your team kickoff (or if you’re a solo builder on your mission) we’ll schedule a mission kickoff call with you, a member of our Mission Success team, and your point of contact at the company. The mission kickoff call is an opportunity to learn more about the mission, ask questions, and get the logistics. You’ll learn about exactly what you’ll be working on, key deliverables and dates, communication preferences, the tools you’ll be using, the work culture, any regular meetings, your expected availability, and so much more.
Step 7: Start building — and logging your hours
Once all of the above has been completed, you’re ready for takeoff. Just don’t forget to accurately log your hours in your timesheet every day — that’s how you’ll get paid. (More on that here.)