Custom fields help you track work according to your team’s needs. The name and value of any field is up to you and possibilities are almost endless. Here are a few examples that show various custom field types applied in different workflows:

Custom fields enable you to store all kinds of data in the task, so if you’re using Rindle to manage a client onboarding process, you can now store information about the account type, specific setup requirements, main account owner, dedicated project manager, email addresses, notes, so much more.

As tasks move through your workflow, you can also communicate if certain activities have been completed yet or information been provided through the use of the dropdown option. For example, let’s pretend that you need to communicate to your IT team to setup your new client’s account in your system. You can create a dropdown in the task that says “Has account been configured?” and then “Yes / No” for the options. 

As the task moves through the workflow, you can mark it complete after it’s confirmed that it’s completed, and anyone viewing the task afterwards will know that the crucial step has been completed.

You can also leverage custom fields if you’re using Rindle as a CRM. You can now store information about the company or person — like primary contact, budget, primary department, company size, company location, revenue, MRR, etc.

This is probably one of my favorite use cases — purely because I myself run a marketing team and always feel the need to communicate as much as possible to my freelancers and teammates. 

Custom fields enable you to provide context for your marketing activities to anyone viewing them! Store information like target persona, stage of the customer journey, goals, type of marketing activity (like product marketing, retention, outbound emails, etc.), OKRs, etc for the tasks in your marketing campaign and overall marketing function.

That way, when your boss or CEO wants to see what marketing is working on, not only will she be able to see the actual tasks, she’ll have a clearer view of who marketing is targeting, and what impact the tasks have on any specific strategic goals.

The possibilities are endless with custom fields for marketing campaigns, and can help provide an entire layer of context, communication, and efficiency to your workflow. 

Sometimes, our workflows have internal deadlines — meaning the things we need to make sure we’re executing on and preparing ahead of time. And there’s external deadlines — the looming deadlines we need to make sure everyone is aware of at all times.

A perfect example? The deadline for GDPR — the global data regulation for Europe that officially became enforceable on May 25th, 2018. 

Naturally, you wouldn’t want your team scrambling to get everything done on the date. You’d rather be early and prepared a month or two in advance to make sure all of your ducks were in a row, but it’s still important to communicate that extremely important external deadline. 

Otherwise you get the question “When are we supposed to be ready, again?” every day. 

A custom field for a date would be perfect in this scenario: it communicates the true deadline for the rest of the world, but you can still set your own due dates and start dates inside of Rindle for when your team will need to act on the tasks. 

This would also be excellent for virtually any kind of launch dates, event planning, or other deadlines that are crucial (or detrimental) to your success. 

If you’re managing a content marketing function in your business, whether internally or for clients, you’re going to love working with custom fields.

Custom fields are perfect for working efficiently with many writers, content mediums, official publish dates, and keeping track of if graphics are done, and more. 

Similar to the marketing campaigns, you’ll also be able to store important information like the target persona for the content piece, verify if the piece has been optimized for SEO, or the keyword you’re planning on targeting for the piece.

Content marketing has just gotten a lot easier — whether for your business or for your clients.

Another way to use custom fields is to track work requests and time costing. A design team might have a template task for others to make design requests. They could use a number custom field for the requester to input how much time they anticipate for the work. Then, designers can prioritize hours accordingly and know how much they’re working on before deciding to take on more work or not.

Every now and again we get the question, “Can we use Rindle for managing a product?” 

Yes — you definitely can, and even more so with custom fields. If you’re working with product in any kind of way, you can include information like release name, official release dates, technical requirements for your engineers, and even scrum points if you’re leveraging the scrum methodology.